If I’m understanding you correctly, your install of the plugin is missing a required table: _object_sync_sf_object_map (starting with whatever your prefix is). The plugin is unable to connect records to each other without this table.
Usually, this table gets added when the plugin is installed, but there are some hosts that seem to have trouble with it. It’s unclear why, and I’ve never been able to reproduce it myself.
But to fix it, if you have access to your database, you can create the table with the following SQL. You’ll want to replace wp_ in the table name with whatever your install prefix is, if it’s not wp_:
CREATE TABLE wp_object_sync_sf_object_map (
id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
wordpress_id varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL,
salesforce_id varbinary(32) NOT NULL DEFAULT '',
wordpress_object varchar(128) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
created datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
object_updated datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
last_sync datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
last_sync_action varchar(128) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
last_sync_status tinyint(1) NOT NULL DEFAULT '0',
last_sync_message varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
PRIMARY KEY (id),
UNIQUE KEY salesforce (salesforce_id),
UNIQUE KEY salesforce_wordpress (wordpress_object,wordpress_id),
KEY wordpress_object (wordpress_object,wordpress_id),
KEY salesforce_object (salesforce_id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
I’m assuming your install process was able to create the field map table, but in case it was not, this is the SQL for that table:
CREATE TABLE wp_object_sync_sf_field_map (
id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
label varchar(64) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
name varchar(64) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
wordpress_object varchar(128) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
salesforce_object varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
salesforce_record_types_allowed longblob,
salesforce_record_type_default varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
fields longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
pull_trigger_field varchar(128) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'LastModifiedDate',
sync_triggers text COLLATE utf8mb4_unicode_520_ci NOT NULL,
push_async tinyint(1) NOT NULL DEFAULT '0',
push_drafts tinyint(1) NOT NULL DEFAULT '0',
weight tinyint(1) NOT NULL DEFAULT '0',
version varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
pull_to_drafts tinyint(1) NOT NULL DEFAULT '0',
PRIMARY KEY (id),
UNIQUE KEY name (name),
KEY name_sf_type_wordpress_type (wordpress_object,salesforce_object(191))
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
You’ll probably want to deactivate and reactivate the plugin, since there are some things it is supposed to do after it creates the tables.
Finally, if you want the post to be published instead of a draft when it arrives from Salesforce, you can do this in two ways:
- Create a field in Salesforce that has a value of ‘publish’ and map it to the post_status field in WordPress
- Use a developer hook to set the value of the post_status field. It would be something like this:
add_filter( 'object_sync_for_salesforce_pull_params_modify', 'change_pull_params', 10, 6 );
function change_pull_params( $params, $mapping, $object, $sf_sync_trigger, $use_soap, $is_new ) {
$params['post_status'] = 'publish';
return $params;
}
