Hello
We have a agama pro and child on a test server.
We are preparing the migration of the server in production
When we move the wordpress site and the database, we lose the agama configuration
Is it blocked? Is the configuration linked to the name of the server (domain name)?
Thank you in advance
William
I thank you for this information
Actually it’s the “replace all” that breaks the customization
Our database administrator looks for which field is blocking
We find the error!
It’s when we do replace in “theme_mods_agama-pro-child” into wp_options beta.domain.fr to http://www.domain.fr
When reloading page, this field becomes 'a:2:{s:19:"agama_slider_height";s:2:"40";s:18:"custom_css_post_id";i:10993;}' instead of all the customization