Evo 1.0.4 MODX_BASE_PATH installation problem

Hello,

never before experienced so much frustration when installing MODx in the last five years than today...

I was copying one installation to an other server. I imported the database and changed config.inc.php as well as .htaccess files in root and manager (the original installation was set to use friendly urls). Everything was green when doing advanced upgrade in install process with changing database details. (One thing: in the list of which chunks and snippets will be updated some lines only read "Install/Update - " - not naming what chunk/snippet ...)

What I’m gettig all the day after calling /manager/ is


I’m using the lateste Evo 1.0.4. and tried on PHP 5.3.1. with MySql 5.1.3.9 (and on an other server with slightly older versions)

It seems to me that MODX_BASE_PATH and $database_type (which is mysql and should fill into the two dots in dbapi..class) are not created or are stored in the wrong place.

I also tried to set in the .htaccess files

(with server path) as proposed here http://rtfm.modx.com//display/MODx096/Friendly+URL+Solutions but I got a 500 Internal server error, and no Internal server error but also no change on the MODX_BASE_PATH error when commenting out the second line.

I overwrote the old assets/cache/siteCache.idx.php with a fresh one, but this did not change the error, too.

I also tried a fresh install, and tried on two different servers with new table prefixes/new tables. No change!? Can’t believe something is wrong with the MODx 1.0.4. package ...

So at the moment I am stuck. I’m sure I’m overseeing a simple thing. File permissions were set correctly. I made sure to upload everything and did it three times ...

So thanks if anyone has an idea for me.

It seems to have to do with the siteCache.idx.php file and/or changing manager settings. When I upload a fresh siteCache.idx.php or a saved from the old installation the manager login works and looks fine.

After saving a configuration change or after saving a module change I get a lot of marks and error messages like:



assets/cache has permissions 777, and siteCache.idx.php too.

Hm ... any ideas? Thanks again!!

open the manager/includes/config.inc.php, delete ?> closing tag

Hi, thanks for your reply. I had tried that, also in the siteCache.idx.php, and ensured that there are no empty signs before and after php tags ... also ensured that the files are saved as utf-8 without BOM ...

I today found out when investigating the siteChache.idx.php that there were strange codes, and found in the database in the htmlsnippets, snippets, plugins, modules and templates tables new entries without title and description but with code like


This code is not present in the original database that I had copied from. So in the process of copying the database and installing the MODx upgrade (all done on Mac OS X 10.5.8. with Firefox 3.6.13 - and installed into two different server environments PHP5, MySql 5, overwriting manager files several times from PC also) somehow the new code was generated and written into these tables.

Removing the code from siteCache.idx.php didn’t help, but deleting the entries with that code in the database tables finally solved the problem.

Now what could have caused this phenomenon? Virus? When uploading to the new destination I had deleted some of the ._ files (Mac "dot-underbar" files, former ResourceFork). Maybe this was the cause? "com.apple.quarantine" seems to be a flag that normally files downloadeed from the internet are getting when Max OS X thinks they could be harmful.

Any more insights would be helpful, but maybe I don’t switch FTPying between platforms any more (I did becaus Filezilla is very slow in transferring data on my Mac). Thanks again.

It looks like a character set issue. Maybe the data in some of the tables or fields is not in the same character set as the new DB or doesn’t match the MODx Manager charset.

The other possibility is that one or more files were corrupted at some point in the process -- it happens. It can happen when you download the package, or when you FTP the files between servers.

It’s annoying, I get exactly the same problem again with a totally fresh 1.0.5 installation on a completely different server. Is there a problem with Mac / Filezilla/ ...?

I’ll try it on Windows, grhhh

Update: Downloading modx-105.zip to Windows, uploading from Windows via Filezilla: works! Everything fine!

Can anybody confirm Mac 10.5.8/Filezilla 3.3.5 issues?

Thanks!