New version install - Config Parse Error on 2.2.7 - Issue does not happen on new 2.2.6 install?

Hello all,

This is my 1st post as I've not had any issues until today, I've tried to install a fresh copy of Revo 2.2.7 onto my server, everything is fine until I get to the Next button where it usually brings up the login screen, not this time, there is a parse error in the core/config/config.ini.php on line 13. Looking at the config file it appears that there are no adjustments to the config.ini.php file at all, i.e. no sql details etc have been updated.

After trying every usual suggestion for this issue which has occured to others previously. I decided to do a new install using 2.2.6 onto the same server, not doing anything differently to my 2.2.7 failed install, except this time no errors? I could login as usual, where 2.2.7 fails, only guess is there is a possible issue with 2.2.7, or there is some other new procedure for set-up??

MySql 5.1.68-cll
PHP 5.3.20

I've ran 5 installs on 2.2.7 and haven't run into that issue personally yet. No insult, but it said it could write to the config file in the summary page would be the first thing to jump to mind.

Can you also tell what OS and Web Server your running.

Cheers

It wouldn't be unusual for the config.inc.php file not to change between versions. Did you upload the files individually with FTP? That often results in corrupted or missing files.

Quote from: charless at Apr 10, 2013, 04:23 PM

Can you also tell what OS and Web Server your running.

Hello the OS is Linux and I'm using a shared webserver if that is any help?

Quote from: BobRay at Apr 10, 2013, 09:28 PM

It wouldn't be unusual for the config.inc.php file not to change between versions. Did you upload the files individually with FTP? That often results in corrupted or missing files.

BobRay,

I unzipped the traditional Modx files directly onto the webserver via file manager, then moved all of the files from the unziped file direct to the root using Move in the control panel which is best practice as I understand it?

My main point is; what I found odd was that when I gave up with 2.2.7 and decided to upload the previous build 2.2.6 instead it worked exactly as I would expect it to and as it has done on many times before for a fresh install. I did nothing different to my install process with 2.2.7 as I did with 2.2.6? The MySql DB I set up was new for each attempt with 2.2.7 as it was with the install of 2.2.6, so no possible corruption there, the user name and password the same as normal for the DB. All the usual files were checked as writable on the server.

I can only guess that there is something in 2.2.7 which denied the config.ini.php from updating the MySql details during install, although I tried to place a blank version of core/config/config.ini.php for one of my failed attempts as it was suggested in troubleshooting before and that did not work either (it was writable as well).

Maybe I'm misunderstanding you, but you don't want a new DB for an upgrade install. When MODX sees the config.inc.php file, it assumes that you want to upgrade an existing install (and its existing DB).

Quote from: BobRay at Apr 11, 2013, 02:54 PM

Maybe I'm misunderstanding you, but you don't want a new DB for an upgrade install. When MODX sees the config.inc.php file, it assumes that you want to upgrade an existing install (and its existing DB).

Hey BobRay, No this is not an upgrade this was a new fresh install onto a fresh SQL DB. When I have a bit more time myself I will try another run at this, trying a fresh install of Modx 2.2.7 on the shared server I use and see what is preventing a correct install. If no one else is having this issue with new fresh installs of 2.2.7 then it is most likely a disagreement somewhere between the shared server I use and Modx 2.2.7..

Thank you for looking at this anyway. I will keep checking back here to see if anyone else has come accross this error as well..

Cheers

Matt