Import Settings Not Working - take II

[MatthewMarichiba 0]

I see another forum post with the same title and same (sort of) issue. I am transferring from localhost to a live server, but PlatformPro isn't accepting the settings file, so the results (obviously) doesn't look like what I designed. FYI, here's the process I followed: * copy all wordpress files directly from localhost to the live server. * export the mysql database to a file. * export the PlatformPro settings to a .dat file. * do search-and-replaces on both files to account for the URL changes. * set up a new mysql database, and import the database file. * update wp-config.php to point to the new database & account for the URL changes. * browse to the site (it is active and live. content is correct, but the rendering is broken) * open wp-admin, go to Pagelines > Settings, scroll to the bottom of the page, specify my .dat settings file. * click "Upload New Settings" button. After a second, it returns a message: "Congratulations! New settings have been successfully imported." * ...but it lies. Unfortunately, none of my PlatformPro settings have actually changed. For example, the banner URL is unchanged, and the Custom Code page is devoid of all my custom CSS. Please help! Thanks! Matthew

[Simon 248]

No settings at all?

[MatthewMarichiba 0]

No settings that I see. Some of the first settings in the .dat file set the favicon and the .dat file, but not even those get updated. FYI, the previous post I saw with a similar issue is http://www.pagelines.com/forum/topic/10486 take care, Matthew

[Simon 248]

See I think this is server specific. Some hosts are very restrictive with certain php functions it could even be suhosin. Can you provide any more information?

[MatthewMarichiba 0]

In case it might be an issue with the formatting of the output file, I've mounted it here: www.marichiba.com/files/PageLines-PlatformPro-Settings-20110629-updated.dat

[MatthewMarichiba 0]

Simon, I appreciate your help. You said: "it could even be suhosin" -- I didn't quite catch that. What do you mean? Update: I just uploaded the default settings files provided with PlatformPro, and it imports just fine. Random tweaks and CSS entries all show up. Thus, I don't think this is a server-side issue. Thanks again!

[Simon 248]

It says updated, is this the original file?

[MatthewMarichiba 0]

You're onto something! And you're right. The "-updated" one is the one I did the text search-n-replace on to fix URLs. When I import the untouched .dat file, it does import. Yay! I went through my custom CSS & and Global Settings pages and did all the updates manually, and things appear to be fine. Any idea why a touched-up file wouldn't import? Any invisible characters in there my text editor might be squishing? I'd still like to be able to search-n-replace, so I don't have to manually do this every time. Thanks again!

[catrina 103]

Maybe the touched-up file wouldn't import because of the server. I'm not sure. Some servers aren't as friendly as others...

[Simon 248]

matthew the reason is simple, the file is a php serialised array of all the settings they are set out like this.. setting name, setting value length, setting value you changed some of those values, but NOT the length value.

[MatthewMarichiba 0]

Thank you, Simon. I get it now. I wish it wasn't so, but I get it. How are other people managing this? I can't be the only person in the world going from localhost development to a live server with totally different URLs, wanting a way to automate the transition... I *could* update the string length in my modified .dat file, but that'd be more cumbersome than updating the settings manually.

[makeylon 0]

I just did the same thing, and didn't know how to fix it, so all I did was copy and paste all the info from my dev to my host. Annoying, but figured it was faster.

[kennwebguy 0]

I think this might solve my other issue I posted, here: http://www.pagelines.com/forum/topic/11437 Future suggestion. Make the importing and exporting of settings not length dependent. Instead make it identify beginning and ending characters so the length can vary and people can change url lengths. (most common with relocating the install) ... sigh ...