Blocks stop being displayed when the site is moved and are displayed.
Page Builder data is stored in serialized form in the `wp_postmeta` table, where the `meta_key` field is equal to ‘panels_data’
Here’s an example, part of that data (domain=home.pl):
a:3:{i:0;a:8:{s:5:”title”;s:4:”Home”;s:4:”link”;s:20:”https://home.pl/add/”;s:7:”picture”…
By changing the site address (domain), you also change the links to your files on the hosting in the database, for example to this (domain=example.com):
a:3:{i:0;a:8:{s:5:”title”;s:4:”Home”;s:4:”link”;s:20:”https://example.com/add/”;s:7:”picture”…
And as a result, the page https://example.com/add does not display the blocks.
The reason for this is that:
1. Page Builder data stores the number of letters in a block element (for example,s:20)
2. The number of letters in the link changes.
Therefore, in order for everything to work, you need to change the old number of letters in the link to a new one, as here:
a:3:{i:0;a:8:{s:5:”title”;s:4:”Home”;s:4:”link”;s:24:”https://example.com/add/”;s:7:”picture”…
And unfortunately, this needs to be fixed for every block on pages that have YYYY blocks…
The developers are requested to propose a simple solution to this problem, or fix it in the next updates of Page Builder.
Hi
Thanks for posting your question.
We recommend using a search and replace plugin that supports serialized data such as https://wordpress.org/plugins/better-search-replace/.
Thank you.
Does this plugin (better-search-replace) perform the above substitutions in the meta_value field in the wp_postmeta table?
Hi, thanks for the update.
Better Search and Replace or any “find and replace” method that supports serialized data is required.
Serialized data should ideally not be edited manually.
Unfortunately, if a find and replace operation is made in way that doesn’t support serialized data and for some reason, the migration can’t be repeated, this becomes more of a custom development type situation.
We’re available here on our free support forum for any basic usage queries; I’ll ask Alex here to take a look at the potential manual fixes you might be able to do but ideally the database import should be repeated.
I solved this problem in a different way) by writing a PHP script that goes through this data and changes the hyperlink length in the appropriate places.
That’ll do the trick. Glad to hear you’ve made progress.
All the best.
Andrew