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.