How to downgrade from 5.6.3.4 to 5.6.3.3?
Permalink
Is there a way to get concrete5 to downgrade?
I think the 5.6.3.4 upgrade was a /concrete directory replace - is there a way to get the c5 upgrade script to recognise a lower version?
The answers I've found don't work sorry - any help would be much appreciated.
Cheers
Ben
I think the 5.6.3.4 upgrade was a /concrete directory replace - is there a way to get the c5 upgrade script to recognise a lower version?
The answers I've found don't work sorry - any help would be much appreciated.
Cheers
Ben
Thanks for that, if it's not there (because it was upgraded by replacing the concrete directory) do I just add it to site.php, then add the directoryfiles into /upgrades ?
So tried:
- Copying a fresh download of 5.6.3.3 into /updates/concrete5.6.3.3
- Adding a line to site.php: define('DIRNAME_APP_UPDATED', 'concrete5.6.3.3');
- Going > Dashboard > System & Settings > Update concrete5
But the Dashboard won't recognise the older update.
Does anyone know if there's a way to force c5 to downgrade? We have an issue with Advanced Forms and the developer doesn't seem to respond (there's another person with the same issue and got no response - downgrading was the only way they got it working).
Any help would be much appreciated as none of the forms (8x) work on this site currently.
Cheers
Ben
- Copying a fresh download of 5.6.3.3 into /updates/concrete5.6.3.3
- Adding a line to site.php: define('DIRNAME_APP_UPDATED', 'concrete5.6.3.3');
- Going > Dashboard > System & Settings > Update concrete5
But the Dashboard won't recognise the older update.
Does anyone know if there's a way to force c5 to downgrade? We have an issue with Advanced Forms and the developer doesn't seem to respond (there's another person with the same issue and got no response - downgrading was the only way they got it working).
Any help would be much appreciated as none of the forms (8x) work on this site currently.
Cheers
Ben
Restore from a full files and data backup is the only way to be 100% confident in a downgrade.
Having said that, I am not aware there were any changes to database schema, so simply downgrading the core files as you have done may work. It all depends on what data and other files have been traumatised since you upgraded.
Having said that, I am not aware there were any changes to database schema, so simply downgrading the core files as you have done may work. It all depends on what data and other files have been traumatised since you upgraded.
Awesome mate, we also changed Config –> SITE_APP_VERSION in the database back to 5.6.3.3.
So in future, we shouldn't upgrade by replacing the /concrete directory?
Or is the only way to downgrade, is to replace everything from a backup?
Cheers, and thanks heaps for your help.
So in future, we shouldn't upgrade by replacing the /concrete directory?
Or is the only way to downgrade, is to replace everything from a backup?
Cheers, and thanks heaps for your help.
When I upgrade, for major upgrades I clone and swap once proven. For minor upgrades I use the /upgrades directory, either automatic or manual. Once I am 100% sure, if I want to tidy up and never revert, I may then (and only then) move the upgrade over to the /concrete directory and hack site.php to remove the upgrades pointer.
Thanks mate, good to know.
Our issue is that the person doing the upgrade didn't properly test ALL the forms - so there were too many content updates since Nov!
Thanks heaps for your help!
Our issue is that the person doing the upgrade didn't properly test ALL the forms - so there were too many content updates since Nov!
Thanks heaps for your help!
define('DIRNAME_APP_UPDATED', 'concrete5.6.3.4');