This will happen only when the previous version of shortcoder is v5.0.x otherwise it should not happen.
Unless you were playing with DB or made manual change to shortcoder_data value by copying from some other place/replaced with older one and then upgraded to 5.2.
There was a bug during 5.0 time for which automatic fix was made by copying the data from shortcoder_data. Once this is done a flag will be set saying the fix is made. Only when this flag is missing, the data from shortcoder_data will be taken.
I tried this in my local setup and it works as expected.
Anyways, if it had happend for some reason, the only way is to perform the changes manually again.
Thanks,
Aakash
I had the same problem. I had version 5.2 installed, I have updated to the new version 5.2.1, and I have lost all the changes of the shortocodes and now they are in a much earlier version.
It is not a minor change. It should have been notified before updating 🙁
There is no intentional change.
As per my testing, there is no issue like this.
If possible and if you have access to the wordpress database, could you please share the value of shortcoder_data field from wp_options table ?
That should help me give some idea to debug this issue.
If not you could also send me a temporary administrator username and password to my contact form. http://www.aakashweb.com/contact I’ll login and check the issue.
Thanks,
Aakash
We have deleted all instances of shortcoder_data across all our websites to ensure the problem does not reoccur and are currently in the process of copying all entries of the wp_posts table that have post_type=shortcoder from a back-up to our live websites. After that it should be as if the old version never existed.
I had to prioritize restoring our websites over analyzing the bug in this case, so I’m afraid I can’t provide a lot of insight.
Though I guess 3dmakernow’s suggestion of adding a prompt before importing from the shortcoder_data field would make it a little bit more foolproof, and perhaps a button somewhere in the settings to redo this import should it be missed when first upgrading to v5+
