Zapier
Tweaks
- Resolved a fatal error caused by mismatched parameters in the generate_key method
Fixes
- Issues with Stripe gateway not triggering new donations since updating to GiveWP 2.20.0 have been resolved
Features
- Updated the logging to use the fancy new logging system in GiveWP 2.10.0
Fixes
- Improved logging for failed zaps
Fixes
- Resolved an issue where real data and test donations sent through Zapier would have the incorrect donation status of "publish" or "give_subscription" rather than "Complete".
Features
- Added a setting and support for logging Zapier events and errors. This is not turned on by default, so if you would like to use it please enable it within the add-on's settings. Note: Zapier also logs so if you're troubleshooting you can use both logs to help troubleshoot any issues.
Features
- Updated how Zaps are processed so that they are more reliable on websites processing many donations. We moved away from using WP Cron to using a background processing utility that is more reliable.
Fixes
- There was an issue with connecting to Zapier if you did not have the Recurring Donations add-on activated. This is because Zapier was expecting a response from the newly created "Subscription Completed" trigger added in the previous version. This fix now allows all users with or without Recurring Donations active to connect to Zapier.
Features
- Added a trigger for "Subscription Completed".
Fixes
- Resolved issue with the "Pending Donation" trigger not firing properly.
- Resolved an issue with Zapier pulling in sample data correctly. Note: you must update to the latest version of Give Core 2.4.5+ for this to work.