-
Posts
-
We’re using a child theme based on Enfold. Our footer widgets are getting stored as serialized data, and our host is WPEngine. WPEngine’s copy methods (sandbox to production for example) have issues with serialized data. I’ve confirmed this with them, the know it’s an issue, but resolution date is unknown.
Meanwhile I’d like to recode our footer to not use serialized data. Do you have a recommendation for the best way to accomplish this?Hey darh,
I apologize, but I am not sure about your question. May you explain it with other words and some screenshots?
Best regards,
John TorvikThe footer is set up as 5 columns of text widgets that contain HTML (under Appearance ->Widgets). This data is stored as serialized data in the database under wp_options, widget_text, in the format “a:6:{i:3;a:7:{s:5:”title”;s:0:””;s:4:”text”;s:807:…”
WPengine has a problem copying that serialzed data from one install to another. I need a work-around so the footer HTML doesn’t get lost (and replaced by the default footer) every time I copy the install.
I could hack footer.php to display what we want, but then the footer text will be hardcoded, which has it’s own issues. My question is if there is a better way to accomplish this, without using serialized data in the database.Hi darh,
You could write your own migration script and run it on deploy. Did you investigate what kind of problem is it with WPengine?
Best regards,
VictoriaThe issue is with serialized data. I don’t want to write my own migration script. I want to store the footer in such a way that it’s not stored as serialzed data.
Hi darh,
It is core WordPress functionality, I guess, you could as the same question at a WordPress forum. Here is some reading on the topic:
http://www.vsellis.com/how-one-wordpress-migration-plugin-has-saved-us-thousands-of-dollars/
https://wordpress.stackexchange.com/questions/203410/where-are-widget-configurations-storedIf you need further assistance please let us know.
Best regards,
Victoria
- You must be logged in to reply to this topic.