Version 1.3.1

• Bug fix: this release fixes 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 user @rtd2 for reporting this.
• Bug fix: this release makes the data import preserve the field structure.

Version 1.3.0

• New: this release adds an interface for importing and exporting plugin data. It includes fieldmaps (which map object types to each other), object maps (individual objects mapped to each other) and plugin settings. Data is exported to a single JSON file that can be imported.
• Bug fix: this release supports a datetime change in MySQL versions newer than 5.7.4 in which default values can no longer be 0000-00-00. See this StackOverflow page for details.
• Bug fix: this release fixes an issue where admin notices for this plugin would sometimes be empty.
• Also fixed a ton of code formatting stuff, including translation spots.
• This release also fixes the previously broken Travis CI build's issues with older PHP versions.

Version 1.2.8

• New: this release adds a new developer hook, object_sync_for_salesforce_push_update_params_modify, which allows the data being pushed to Salesforce to be modified in the event that an existing Salesforce object is being updated.
• Bug fix: the install script adds --prefer-dist to the composer install to hopefully prevent issues on Pantheon. Thanks to WordPress user @joepahl for reporting this.
• This releasse also makes a number of corrections and clarifications to the plugin documentation.

Version 1.2.7

• Bug fix: in some cases, a fieldmap with the Salesforce update trigger checked, but not the Salesforce create trigger, it would still create data in WordPress. This data should, rather, be skipped.
• New: there are also a number of small tweaks to in-page help, documentation and code comments.

Version 1.2.6

• Bug fix: in some cases, date fields coming from Salesforce were not correctly formatted for use in WordPress. This release causes any core date fields to be formatted as WordPress expects them. Thanks to GitHub user @prowp for the report on this.
• Note: to apply this fix, you need to clear the plugin cache, and then re-save any the fieldmap(s) that need it.
• This release also includes a small documentation update about restricted picklist fields.

Version 1.2.5

(forgot to release this on GitHub when the plugin version was released)

• Bug fix: trying to save a high number of fields in a single fieldmap was failing. Thanks to GitHub user @prowp for the report.
• New: some in-page help to users who may be missing meta fields when trying to add them to a fieldmap. This happens if these meta fields are new fields without data, and thus cannot be found in the database by the plugin.
• New: we now store the plugin version in the database when saving a fieldmap. This allows us to check fieldmaps to make sure they use the most up to date schema.

Version 1.2.4

• This release fixes a rare bug in which Salesforce changes that occur between a query and the completion of the pull operation would not sync to WordPress. Thanks to GitHub user @charmoney for the report and the fix.
• This release also removes the "weight" field from the screen that adds and edits fieldmaps. This field should have been removed in the past, as it doesn't currently do anything, although in the future we'd like to investigate the ability to map multiple WordPress objects to the same Salesforce object and sync them using the weight field.

Version 1.2.3

• This release fixes a bug in which deleting field pairs from an existing fieldmap, saving, and then adding more field pairs could result in data not being saved. Thanks to WordPress user @pavelwld for reporting this.
• This release also adds a Settings tab field to choose whether or not the plugin should delete its data when it is deactivated.

Version 1.2.2

• This release fixes a bug in which an object map could not be created if the Salesforce ID was the same, with case insensitivity, as another Salesforce ID. Salesforce, however, is case sensitive with these IDs and can occasionally create IDs like this. Thanks to WordPress user @pavelwld for reporting this.

Version 1.2.1

• This release fixes a bug caused in 1.2.0. Users were unable to sync data without re-saving fieldmaps. This does a version checker and uses previous data structures until users re-save.
• Make sure you update your plugin fieldmaps.