Version 1.8.3

• Bug fix: In what seemed to be rare cases, manual push or pull requests from the WordPress admin were failing to actually save any data.

Version 1.8.2

• Bug fix: 1.8.0 accidentally disabled a developer filter. This re-enables it.

Version 1.8.1

• Bug fix: 1.8.0 introduced a possible issue with checking for updated records.

Version 1.8.0

• New: we can now map multiple WordPress objects to the same Salesforce object. Each WordPress record will update the Salesforce record, and the Salesforce record can update each WordPress record, all according to the fieldmap. Thanks to WordPress forum user @joecanas1 for the initial report some time ago.
• New: if Soap is enabled in the plugin settings, it is capable of responding to merge events. For example, if two Contacts are merged in Salesforce and a user is mapped to the old one, it will become mapped to the new one.
• New: WordPress 5.1 changed its new user notification parameters. Thanks to GitHub user @synthetiv for the fix.
• New: we've added a few additional debug log entries.
• New: there is better error checking on saving metadata for users, posts, and comments.
• Bug fix: 1.7.0 introduced an activation issue that this release fixes. There is also improved database versioning that occurs upon activation.
• Bug fix: a bug existed in fieldmaps that had a Salesforce field like a record ID, which cannot be pushed to Salesforce but can be pulled from Salesforce, but the sync was failing. Thanks to WordPress forum user @walexparadis for the report on this.
• Developers: we've updated our included version of ActionScheduler to 2.2.1.
• Developers: the load_by_wordpress and load_by_salesforce methods on the salesforce_mapping class have been deprecated in favor of load_all_by_wordpress and load_all_by_salesforce, though the deprecated methods have not been removed.

Version 1.7.0

• New: improve handling of custom meta fields that are required by Salesforce. This plugin would fail to create objects if required fields were missing when a record was created. It should handle these situations much better.
• New: update to version 2.2.0 of the ActionScheduler library.

Version 1.6.0

• New: we have added some basic REST API endpoints to the plugin. They can be used to check for updated/deleted records in Salesforce, pull a specific record from Salesforce by ID, or push a specific record from WordPress by Id and type.
• Bug fix: pull queries were sometimes skipping records that should have been processed, especially when some records in the group were not allowed by the fieldmap.
• Bug fix: as of 1.5.0, Salesforce records were not being deleted when a corresponding WordPress record was deleted. This release restorese that functionality.
• Developers: the object_sync_for_salesforce_pull_object_allowed and object_sync_for_salesforce_push_object_allowed hooks now require that a value be returned, regardless of whether it is true or false. This was always the better way of handling these hook, but it was possible to use them without, and the documentation was incorrectly written.

Version 1.5.2

• Bug fix: as of 1.5.0, when a Salesforce record is deleted, the corresponding WordPress record is not deleted. This release restores this functionality. Thanks to WordPress user @bswift for the report.
• Developers: this release allows API calls that return data from Salesforce to return either json, the full PHP array (the default) or both, if the $options array is populated. Thanks to WordPress user @yanlep for the request.

Version 1.5.1

• New: update to version 2.1.1 of the ActionScheduler library.
• Bug fix: when processing more than 2000 records, the offset and limit combination fails due to Salesforce API restrictions. In this release, the plugin changes the date parameter on the API query to the value for the last processed record.

Version 1.5.0

• New: the Mapping Errors tab supports deleting multiple error rows via checkboxes.

• New: when caching API responses, the plugin caches the full array rather than the full array and the JSON data. This reduces the memory usage for object caches a little.
• New: this plugin should be usable on WordPress VIP environments; it now checks for user_attributes instead of user_meta in those cases.
• Bug fix: this plugin can now be properly deployed on hosts like Pantheon. Thanks to WordPress user @joepahl and GitHub user @BrianBenninger for reporting this.
• Bug fix: when using meta fields for prematch, the plugin previously could fail to find a match even if the value existed. It now uses different matching for meta fields. This requires that users resave their fieldmaps, and also that we end support for WordPress 4.5.. Thanks to WordPress user @nodakjones for the bug report and testing assistance.
• Bug fix: when using the ActionScheduler library, the plugin fails to process multiple rounds of pull requests. Now it uses the limit setting to page through all possible updated records. Thanks to WordPress user @jonsayer for the report and WordPress user @harmoney for help testing.
• Developers: this release adds a new developer hook, object_sync_for_salesforce_pull_query_modify, which can modify the Salesforce API SOQL query before it pulls data from Salesforce. Thanks to WordPress user @yanlep for the suggestion.

Version 1.4.2

• Bug fix: ensure the queue functionality is present when activating the plugin.