Answered Failed upgrade of Modx Evo 1.015 to 1.2

I tried to upgrade Modx from 1.015 to the new 1.2 but failed miserably to get beyond the start pages.

The "Upgrade Existing Install" button wouldn't work and the problem
seems to be the password is wrong.

So on the custom page it says:

Enter the database host (server name or IP address), the username and password before testing the connection.
Database host: localhost:3306
Database login name: MyCMSAdminName
Database password: Tried every password

I suppose the Database host is right. I'm on Bluehost.

I couldn't get the test database server connection to work at all.

The Username used by the upgrade program by default is the one I use in the manager
(I changed this from admin because someone was trying to hack in every day and disabled
it). The Database password I obviously don't know which one it was trying by default.

But I tried every combination of TWIC CMS password and MySQL username and
password I could think of an it wouldn't recognise any of them.

So I guess I have to ask which username and which password is Modx looking for?

MySQL database username and password? or CMS username and password?

Not that any of these seem to work.

Any ideas how to procede? I'm at the end of my ideas.

Mark Crowther

It sound like your config file might be missing: /manager/includes/config.inc.php

Make sure your original config.inc.php file is there, and that it is 'writable' (644). Ensure that permissions are set back to 400 or 404 after the upgrade.

Quote from: andytough at Dec 09, 2016, 10:41 AM

It sound like your config file might be missing: /manager/includes/config.inc.php

Make sure your original config.inc.php file is there, and that it is 'writable' (644). Ensure that permissions are set back to 400 or 404 after the upgrade.

The file is there and I also tried using the details in it on the next page.

I made the file very writable to anyone. You just reminded me to undo that for the moment.

I did wonder if my .htaccess file might have something to do with it. I now make sure every address on my website goes from
http://www.websitename.com to http://websitename.com. When I have a second go I may stop this for a while.

But the fact I manually tried to put the info in the config inc file into the upgrade page and it didn't work suggests it
might not be that.

Mark

You could try removing the port number :3306 as this Bluehost documentation does not make mention of it being necessary. https://my.bluehost.com/cgi/help/2222. But if it worked before with a port number specified in version 1.1 I would have thought it would work OK with the upgrade.

I have just noticed this in the Bluehost doc.

Database name = (cpanelUsername_databaseName)
Database username = (cpanelUsername_databaseUsername)

This suggests that you should be using a combination of your cpanel name and database name or database user name with an underscore between them. But again, if the config file was working OK before I can't see why you would need to change it now.

Quote from: andytough at Dec 09, 2016, 11:20 AM

You could try removing the port number :3306 as this Bluehost documentation does not make mention of it being necessary. https://my.bluehost.com/cgi/help/2222. But if it worked before with a port number specified in version 1.1 I would have thought it would work OK with the upgrade.

I didn't go with version 1.1.1 (I was intending to upgrade to that and then noticed the new version) and maybe that's an issue.

Perhaps try going through that upgrade first?

On the second page I tried to login using the port number and then removing it. I really think I tried every combination.

Fortunately I've managed to revert for the minute although I'm getting blank pages every now and again (refreshing them a few times does bring the pages up). It's all gone very bad for no apparent reason.

Modx nearly sent me insane setting things up years ago. I try and make as few changes as possible but the upgrade and fixing
these issues is now a huge priority.

Quote from: andytough at Dec 09, 2016, 11:23 AM

I have just noticed this in the Bluehost doc.

Database name = (cpanelUsername_databaseName)
Database username = (cpanelUsername_databaseUsername)

This suggests that you should be using a combination of your cpanel name and database name or database user name with an underscore between them. But again, if the config file was working OK before I can't see why you would need to change it now.

I tried some variants. I have a code which accesses the database fine with a username and password with this extension. But as you say it worked fine before on my last upgrade and something clearly has changed.

What version of MODX Evo are you running?

It may be that an interim version upgrade is required if it is an older version.

If you are being prompted to enter user names and passwords it sounds to me as if the config file is not being read by the installer, or the version you are running is not upgradable.

If the "Upgrade Existing Install" button does not work then I think the only other option is to do a complete/new install? You should not attempt to do this as, if successful, it would overwrite the existing website.

Quote from: andytough at Dec 09, 2016, 11:40 AM

What version of MODX Evo are you running?

It may be that an interim version upgrade is required if it is an older version.

If you are being prompted to enter user names and passwords it sounds to me as if the config file is not being read by the installer, or the version you are running is not upgradable.

If the "Upgrade Existing Install" button does not work then I think the only other option is to do a complete/new install? You should not attempt to do this as, if successful, it would overwrite the existing website.

I put the version in the header. Failed upgrade of Modx Evo 1.015 to 1.2.

OK I downloaded the older version. I will give that a go on Sunday when I have time to fix things if it doesn't work.

The last upgrade to 0.015 worked out of the box, hopefully that will work.

Anyone else had a problem with this upgrade missing out the last version?

Mark

Just a guess, but to run 1.2 your server must have PHP5.5 and above installed, better is PHP 7

I updated a very old client site last week and couldn't figure out why it wouldn't install / update properly.

Then I looked at the server and found that the PHP version in use was below that required for 1.2