Change Sub-Domain / Domainname breakes Customizr Settings

I use free Customizr-Theme in some projects and am very satisfied with it.

There’s only one thing I’m not sure if it’s a Customizr problem, or if I’m making a mistake:

My normal procedure is this:
I create a dev version of the project under a sub-domain or on another server with a different domain name.

When I then create the project Live, I make a copy of the database and search and replace old domain names with new domain names.

As long as they have the same number of letters, there is no problem.
e. g.
tmp. mydomain. com
is replaced by
https://www.mydomain.com
doesn’t cause any problems.

But I’m replacing
test. mydomain. com
through
https://www.mydomain.com
or
tmp. mydomain. com
through
https://www.myotherdomain.com

then the customizr settings are partially destroyed and I have to rebuild them manually.

I can prevent this by entering the right number for serializing in the database, for example.
s: 38:”https://tmp.myotherdomain.com/feed/rss/”
to the length of the following string.

That’s very tedious, of course.

Is this a Problem of Customizr-Theme?
I haven’t had the problem with any other theme yet.
How can I avoid this without having to make so many changes in the database?

• This topic was modified 7 years, 2 months ago by montviso.