Version 1.4.1

• Bug fix: in some plugin update scenarios, the database version number checker was not running. It runs all the time, now.

Version 1.4.0

• New: this plugin now uses the Action Scheduler library for scheduling tasks and queueing data in a more performant and scalable way. This removes the need for some of the administrative settings, but as long as you resave from the plugin's Schedule tab, it should not break any existing functionality.
• Bug fix: this release also stores composer library files in its Git repository. This should fix a deployment bug with some web hosts, such as Pantheon.
• This release also brings plugin JavaScript in line with WordPress code formatting guidelines.
• Thanks to GitHub user @charmoney for help reviewing this release.

Version 1.3.9

Bug fix: when Salesforce Key was selected on a fieldmap's field, it was incorrectly being ignored when saving a record's data in WordPress after a Salesforce pull. Thanks to WordPress user @ken-nguyen for reporting this.

Version 1.3.8

• New: basic support for the Ultimate Member plugin. Users created by its registration form can be pushed to Salesforce. Thanks to @atomicjack for the report and assistance testing.

Version 1.3.7

• New: modifications to dropdown fields when creating or editing fieldmaps allow users to pick whether to use the API name from Salesforce, and also allow for searching in a dropdown's contents. A developer hook allows some modification of the search/dropdown combo.
• Bug fix: non-required date fields in Salesforce, if blank, would set the corresponding WordPress field to today's date. Thanks to GitHub user @synthetiv for the report and the fix.
• Update some documentation and documentation formatting, including new documentation for importing and exporting.

Version 1.3.6

Bug fix: this release fixes an issue where the plugin can fail to save setting values in older WordPress versions, which keeps it from ever being activated. Thanks to WordPress user @amstertam for bringing this to our attention.

Version 1.3.5

• Bug fix: this release fixes an issue where the plugin can fail to map certain fields in certain cases when the Salesforce value it is attempting to save in WordPress is empty.

Version 1.3.4

Bug fix: this release refixes an issue in which a custom post object with custom fields was not sending its custom fields on the first save, causing it to fail if the fields were required in Salesforce. Thanks to WordPress users @rtd2 and @bill5roses for reporting that the previous fix was not sufficient.

Version 1.3.3

• Bug fix: a modified Salesforce Contact, which is not mapped to a user in WordPress but when the fieldmap does exist, would try to create a new user in WordPress but fail to add the email address to the email field. Thanks to GitHub user @mcculloughcm for the report.
• Bug fix: the key and prematch fields were ignored if their Salesforce status was not updateable, so this broke prematch checking in those cases. Thanks to GitHub user @johnpbloch for the report.
• New: small tweaks to plugin readme, inline form text.

Version 1.3.2

• Bug fix: this plugin would sometimes conflict with jQuery from other plugins, especially older ones. This puts the object into an enclosure instead.
• Bug fix: allow mapped date fields to be empty without causing a push error.
• Bug fix: make sure plugin notices only appear on pages related to this plugin.
• Bug fix: doing an import with only one object map would fail.