wp1222

Hi Daniel,
thanks for your support! I will let you know if freemius has solved the issue.
Best regards

I just installed the plugin in a fresh wordpress installation without any backend adjustments and without any further plugins to check if the issue is also there. Unfortunately yes, the database entry also includes the string “…s:22:”?FS_Entity?_is_updated”;b:0;…”

Hi Daniel,

thanks for your fast reply! I would like to comment your answers:

…without properly understanding the format. You added characters but didn’t change the string length (s:22).

Well I know that the value “s:22″ refers to the following string length and that it always has to match. That’s the reason why the plugin fails with the original database entry. Also https://www.unserialize.me fails to unserialize the original data. The original string lenght is not 22 characters long as the following example shows. You can test with https://www.unserialize.me:

Original string:
a:1:{s:22:”?FS_Entity?_is_updated”;b:0;}
Result: fails

Test #1:
a:1:{s:26:”?FS_Entity?_is_updated”;b:0;}
Result: OK

Test #2 (as mentioned in my 1st post):
a:1:{s:22:”XFS_EntityX_is_updated”;b:0;}
Result: OK

Try a S&R plugin that was built to handle serialized data.

The plugin I used is especially designed for this purpose: https://interconnectit.com/products/search-and-replace-for-wordpress-databases/.

Changing them is not a good idea as the names your changing reference PHP classes.

I adjusted the serialized data only for test purposes to debug the issue.

Do you have a suggestion how to solve this issue?

Best regards

Additional info:
When I monitor the sql queries thats what the plugin writes into the table ws_options:
…s:22:\”\0FS_Entity\0_is_updated\”…