Upgrading Concrete on QA server
Permalink
I've upgraded Concrete successfully on my dev box from 5.4.1.1 to 5.4.2.2. However, once I commit the new code (new concrete folder update) to our QA server, and re-run:
/index.php/tools/required/upgrade
The page says "Your site is already up to date! The current version of Concrete5 is 5.4.1.1.".
This is against our QA database (which hasn't been upgraded). So, with the new codebase, should the upgrade script be prompting for the 5.4.2.2 upgrade on QA?
Thanks,
Blake
/index.php/tools/required/upgrade
The page says "Your site is already up to date! The current version of Concrete5 is 5.4.1.1.".
This is against our QA database (which hasn't been upgraded). So, with the new codebase, should the upgrade script be prompting for the 5.4.2.2 upgrade on QA?
Thanks,
Blake
How did you update the site? overwrite the concrete directory?
I did a full replacement of the directory. (Removed the old directory, and added the new Concrete folder).
can you open /concrete/config/version.php
The version on QA doesn't match my version on dev (argh).
So, the problem was, my deployment script wasn't pulling from the right repository. The code on QA *wasn't* the upgraded source.
Thanks man, you've helped a ton!
So, the problem was, my deployment script wasn't pulling from the right repository. The code on QA *wasn't* the upgraded source.
Thanks man, you've helped a ton!
