Support | Kriesi.at - Premium WordPress Themes » Topic: Move site to new server, lost all theme optionhttp://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/feed/
Wed, 01 Apr 2015 00:07:14 +0000http://bbpress.org/?v=2.5.4-5380en-UShttp://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/#post-19788http://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/#post-19788
Mon, 28 Jan 2013 07:52:17 +0000sbxstrategies
Hello, I recently moved my site built with Flagship to a new server and have a new URL (it was built on a dev URL and then moved to the clients hosting). Upon moving the site and updating the URL references in the database from the old one to the new one the site completely loses its Flagship options and setting. Any ideas why this would occur or how I would stop it from happening?

The only reason I can think of would be if you changed the theme name. Since wordpress saves the options for each based on its name, changing a theme name in the main style.css of the theme would cause it to use a new set of entries in the wp_options table.

Regards,

Devin

]]>
http://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/#post-105034http://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/#post-105034
Thu, 31 Jan 2013 17:33:47 +0000chembro303
I also had the same experience, but using Velvet 1.3 – developed site on test server, saved a backup of files and database, updated url references, and loaded onto live server. Upon first viewing the site on the live server, all the customized theme options (dynamic templates, etc) were not there and I had to re-do each option manually on the live site, looking at the settings pages on the temp site for reference. It was a pain, but it worked.

I can confirm that the same thing happens when you change the theme name in style.css since I stupidly did that too, a few days after that. But the problem definitely occurred just in moving the site to a new database and server, with no other changes made to the name or site files. The only change was updating the URLs in the database.

]]>
http://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/#post-105035http://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/#post-105035
Fri, 01 Feb 2013 16:20:30 +0000Devin
It definitely shouldn’t. All the theme settings are saved in the wp_options and are attached to the theme name.

I’ll tag the topic for Kriesi to see if he has any other suggestions.

Regards,

Devin

]]>
http://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/#post-105036http://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/#post-105036
Mon, 04 Feb 2013 18:42:16 +0000Kriesi
Hey Guys! I cant reproduce these issues but I have been told that it happens from time to time, probably due to different server settings.

Could any of you do the following:

Do a database export from your local installation, import it to your live server and then send me access details to your ftp server and myphp-admin? I can than fix the issue once and for all :)

Just make sure that after importing the database to the live server you press the save settings button in your admin panel so i can do some trial and error testing…

So in the meantime I copied the database again but did not do a find/replace on the instances of the dev URL but went into phpmyadmin and updated the server manually for the wordpress location. The site works but I know there are thousands of references to the dev location and if I kill the dev location my site will go with it.

Kresi, I am willing to install a copy of the site in another URL I am not using. I will do the find/replace on the database and get the site up and running to reproduce the issue on a location I don;t care about. I can let you in there to do whatever you need to so that way if something blows up there is no loss. If you are okay with that I will send the details.

With your detailed description you might have given me the final clue to the solution. I think the search/replace of the URL also iterates over the database entry that holds all the framework information.

The problem here: this information is stored as a serialized array, which means any direct changes to the database (like a URL replacement) might mess the serialization up.

Serialized entries always have a number before each entry. for example {20:http://www.kriesi.at} the number describes the character count of the string that follows. If the number doesnt match, the serialization is broken and fetching the entry will return an empty value. So if you run a search/replace on the domain name and the new domain has a different character count than your test server, which is very likely, then the array gets messed up.

Why does it happen for only a few people: because there are few framework options that actually store a URL. From the top of my head the only ones that I can think of are custom logos and favicons.

If you want to test this theory before setting up a new installation for me: reset the custom logo and the custom favicon, then create a new database dump and import it to the live server. If everything works then, you dont need to setup a new installation for me ;)

In the meantime I will test it myself as well and try to find a solution if its the cause of the problem.

]]>
http://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/#post-105039http://www.kriesi.at/support/topic/move-site-to-new-server-lost-all-theme-option/#post-105039
Thu, 14 Feb 2013 06:58:01 +0000lostyetidesign
New to this forum. Just did the same exact deployment that others have outlined above. Same issue for me, all of my theme settings I’ve set in my dev environment disappeared.

Just install WP MIGRATE DB plugin on your local dev installation. Follow directions and it will output a properly formed .SQL replacing all the serialized strings as it should. Just did it and voila, perfect migration. Good times.