Forum Replies Created
-
-
Hi,
I understand that serialising data make it better and there is no reason to stop that. The current version of the theme is just not migration-friendly. This can be fix by handling data differently. Instead of storing the full url, just store the path from root then get the root url from the main WordPress settings. That’s just an example of course. That might not fit everyone’s needs but there is tons of workarounds out there to fix that.
Regards,
I found the issue. Because you store everything as a JSON formatted string, when you try to migrate the website JSON breaks.
Your theme would greatly benefit from a fix there as more and more website switch to a multiple stage deployment process. Especially that when you export/import this is from different installation so we’ll need to change urls at some point.
If some of you are stuck with this, the workaround here is to don’t forget to update the property length when you edit something.
for example :
[…]s:4:”logo”;s:50:”http://oldurl.ltd/content/uploads/2014/08/logo.png“[…]
will become
[…]s:4:”logo”;s:55:”http://www.new-url.ltd/content/uploads/2014/08/logo.png“[…]
