wont work, upgrade is always a upgrade procedure..
what kind of problems are you experiencing?
Is rollback from 1.0beta6 to 0.13 possible?
-
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: Is rollback from 1.0beta6 to 0.13 possible?
One should always seriously evaluate every new version before rushing it into production, especially if you don't have the capabilities to fix any issues yourself. Each new version should be thoroughly evaluated to ensure that there are no difficulties before moving that new version onto a production site. This should be common procedure to everybody. As it eliminates those "emergency problems" where you realize something is totally fubarred when you have already gone live.
With these "emergency problems" people usually post emergency questions in the forum or on irc, and panic even more when they don't receive an immediate answer, or a satisfactory hand holding. Then, due to somebody elses lack of preparation and thorough testing, they start to form a negative image about the support they received for the product.
I'm reminded of an axiom: "A lack of foresight on your part does not constitute an emergency on my part". I don't know who originally said that, but these situations have come up quite a bit of late. and not just with the 1.0 betas either.
That aside:
If you have already moved a 1.0beta install into production, and now you wish to roll back, you should be prepared for serious difficulty. The package is designed to allow older installations to upgrade, but not to allow downgrade.
For the core itself (not counting any modules you're using) you'll have to compare the schemas of each database table, to see what has changed, and what as not, and then prepare the appropriate sql scripts to export and re-import the data into the new format. I hope you know SQL fairly well.
Then you'll have to be very careful as to the steps you do things in. I.e: you'll have to backup the data, prepare your import script, test it, then downgrade CMS (by deleting the 1.0-bx installation, and re-installing 0.13, and then backing up this database (completely), then run your import script.
And then there's the modules, a similar process will have to be examined for each of these, I hope you don't have too many to worry about.
It may be easier (depending on the amount of content) to export the site as static, and then re-import everything manually. and hope that you aren't relying on any functionality that was added in the 1.0 series and not available in 0.13.
The manual process can be aided by saving all of the stylesheets to text files, and the same with all of the templates, and each pages content area(s) could go in a separate file too.
Hope this helps.
With these "emergency problems" people usually post emergency questions in the forum or on irc, and panic even more when they don't receive an immediate answer, or a satisfactory hand holding. Then, due to somebody elses lack of preparation and thorough testing, they start to form a negative image about the support they received for the product.
I'm reminded of an axiom: "A lack of foresight on your part does not constitute an emergency on my part". I don't know who originally said that, but these situations have come up quite a bit of late. and not just with the 1.0 betas either.
That aside:
If you have already moved a 1.0beta install into production, and now you wish to roll back, you should be prepared for serious difficulty. The package is designed to allow older installations to upgrade, but not to allow downgrade.
For the core itself (not counting any modules you're using) you'll have to compare the schemas of each database table, to see what has changed, and what as not, and then prepare the appropriate sql scripts to export and re-import the data into the new format. I hope you know SQL fairly well.
Then you'll have to be very careful as to the steps you do things in. I.e: you'll have to backup the data, prepare your import script, test it, then downgrade CMS (by deleting the 1.0-bx installation, and re-installing 0.13, and then backing up this database (completely), then run your import script.
And then there's the modules, a similar process will have to be examined for each of these, I hope you don't have too many to worry about.
It may be easier (depending on the amount of content) to export the site as static, and then re-import everything manually. and hope that you aren't relying on any functionality that was added in the 1.0 series and not available in 0.13.
The manual process can be aided by saving all of the stylesheets to text files, and the same with all of the templates, and each pages content area(s) could go in a separate file too.
Hope this helps.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Re: Is rollback from 1.0beta6 to 0.13 possible?
I have experienced the same thing.
I went from 0.13 to 1beta6.
Not realising that modules need to be ready also for this beta.
I am now back on 0.13
But it was a pain.
What I did:
I cut and paste all template text (at least the templates that I had changed for my site) to a txt document on my pc.
This was possible because the admin part worked ok in 1beta6
Also I copied the source of the content pages to a text file.
Save this all local on my pc.
Backed up the site images via ftp
Then reinstalled 0.13 and deleted the sql database.
And started all over.
It took me some time to cut and paste things back but better than changing everything by hand and regerating the site from scratch.
regards,
corvus
I went from 0.13 to 1beta6.
Not realising that modules need to be ready also for this beta.
I am now back on 0.13
But it was a pain.
What I did:
I cut and paste all template text (at least the templates that I had changed for my site) to a txt document on my pc.
This was possible because the admin part worked ok in 1beta6
Also I copied the source of the content pages to a text file.
Save this all local on my pc.
Backed up the site images via ftp
Then reinstalled 0.13 and deleted the sql database.
And started all over.
It took me some time to cut and paste things back but better than changing everything by hand and regerating the site from scratch.
regards,
corvus