moving modx Evo 1.0.2 to another server [SOLVED]

SOLVED. Host is running php 5.1.6 while I was developing on 5.2.9. Twitter template contained a PHx call to a bit of code in DateTime() that was implemented in a version later than 5.1.6. Was causing a fatal error.

2 days down the drain! Glad I have it sorted now though.


ORIGINAL POST


I have a 1.0.2 Evo site ( I’ll upgrade to Evo 1.0.5 when it’s transfered ) and I’m attempting to move it from an:

Apache Tomcat
PHP Version 5.2.9
MySQL 5.1.30

to:

shared hosting Linux server
PHP Version 5.1.6
MySQL 5.0.77

I have followed the steps in http://wiki.modxcms.com/index.php/Moving_Site_To_Another_Location except the Furls, which I have switched off in the manager after the xfer and renamed the .htaccess to htaccess.local .

I can get into the manager, and it’s all ok functionality wise but it does display some weid characters when I go to Tools>configuration. See attached. This is the only page it appears.

When I try to visit the site I get a blank white page. Does anyone have any clues where I have gone wrong? Could it be directory permissions? Everything is set to 755 except for the folders and contents mentioned in the above link which are set to 777.

Anyone? Was hoping to get this site up today.... Thanks

not sure, but you could check if you’re using the same database character set for both installations

Thanks Sharkbait. They’re the same character set.

I’m going to attempt a clean install of 1.0.2, make sure it works. Then upload the assets folder and import my DB and see what happens.

Clean install worked, uploaded templates and assets and all was ok. As soon as I messed with FURLs the homepage went blank and what’s even weirder I couldn’t reverse it. Will attempt again....

Who is the new hosting company? Transfering the files and running the upgrade should work fine.

Files should be chmod 644 and folder 755 on most servers (well if using phpsuexec).

Unbelievably, I’ve tracked this down to the FeedX snippet.

This was my call that breaks the site


And to fix:


No idea why. If i use the flickr preset it’s ok. I’m about to delve into the twitter preset and see what in the world could be causing it.