Scott Offord

Thanks!

I can’t believe there hasn’t been a reply about this massive bug yet from the support team.

I had the same problem with Username Changer Version 3.1.3

I found a way to get the plugin to ignore the false positive:

https://scott.offord.me/g2GI <~~ screenshot

Ah ha!

I just updated to PHP Version 5.3.24 and I’m able to activate the Plugin now.

Sorry for the hassle, but hopefully this support thread will help others if they find it.

Scott O.

PHP Version 5.2.17

Interestingly enough, I did have this plugin enabled in the past. Here are the DB table items:

https://scott.offord.me/fXiH

I deleted all the plugin files as well as deleted those entries from my DB and the error still occurs when I try to activate the plugin.

yes. it is use CloudFlare\IpRewrite;

https://scott.offord.me/fXDY (screenshot)

and this is what is contained in that file: https://scott.offord.me/fXF4 (txt)

Version 1.3.23.

However, I just updated to Version 1.3.24 and it still gives me the parse error.

I have no other plugins activated. I am using default installation of the Twenty Sixteen theme.

Thanks for the followup.

Absolutely. I’d love to be able to send the display_name by default (and not as a custom field). Since the First/Last or Full Name is a built-in feature of CM, it would seem easy enough to send that info along with the email address without having to create custom fields for their name.

I think this feature would make your plugin even more valuable to your users.

bump.

I would be willing to donate some $ to the cause if this feature could be implemented sooner (this week) than later.

I figured out what is causing the plugin to want to log me out when clicking “save and sync”.

I have a custom field in Campaign Monitor that is already set up using the name ‘status’, however, it is a dropdown choice, not a plain text field.

It seems that your plugin doesn’t like when a custom field already exists and is not a plain text field.

So, when I click ‘save and sync’, for some reason, it brings me to the login page of my WP site.

I figured out what is causing the :

Campaign Monitor synchronization error.
Field Key Already Exists

I have a custom field in Campaign Monitor that is already set up using the name ‘status’, however, it is a dropdown choice, not a plain text field.

It seems that your plugin doesn’t like when a custom field already exists and is not a plain text field.

Yes, a checkbox for that option would be great! Thank you. I think others would also enjoy a checkbox for:

RestartSubscriptionBasedAutoResponders

and for:

Resubscribe