Elena Mukhina

Hello!
Unfortunately I can’t reproduce this bug. Can I get access to a website with this error? Or how else can I help you?

In fact, I don’t know what to do with it. I can’t create a new field, and I can’t store data using the field name with letters in different case.
Any ideas?

It seems there is another reason. Our plugin uses a case-sensitive comparison of field names. Probably you have ‘status’ field in WP and ‘Status’ field in CM.

QueueSubscriptionBasedAutoResponders is not set to true.
Adding the checkbox doesn’t seem difficult. But I have to discuss it with Carlo first.

Hi!
I don’t think this is related to the upgrade. Probably some field names can cause the error. My email is pilotessa at gmail dot com. Send me a screen dump with the checkboxes and tell what plugins you use. I will try to help you.

We use Batch Import API Method to perform ‘save and sync’. And we add people individually when a new wordpress user is created.

Hi!
Unfortunately I can’t reproduce this feature.
Try to update the plugin.
Probably it happens because of user metafields used in other plugins. Try to sync native user data only, e.g. first name and last name.

Hi Lee,

Our plugin performs this check too. The issue is slightly different. We use the latest Createsend API version, and everything works properly. But our plugin generates the following error

Campaign Monitor synchronization error. Must supply a valid HTTP Basic Authorization header

when your plugin is installed and the old API files are used. When I replace API files in your plugin folder everything works perfectly again.
You can read in more details here https://www.ads-software.com/support/topic/sync-error?replies=11.