OK, here's what I gather from the docs; just making sure I have it right.
1) Download 1.12
2) Backup everything.
3) Wipe all the directories, keep database intact.
4) Run upgrade10xto11x.php (I assume from the directory in which Zikula will reside).
5) Reinstall any modules that got erased.
6) Make sure everything works.
7) Download 1.2
8) Follow the instructions in docs/upgrade.html, pretending that it's a 1.1.11 installation.
I'm hoping this is correct.
--
Bart Lidofsky
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
- rgasch created topic »Using PageUtil::addVar() to load script code« 11:48 AM
- michiel responded to »password problem« 10:01 AM
- mazdev responded to »Hide "Register new account" and change template to 3 col« 07:50 AM
- mesteele101 created topic »Zikula 1.3.3 - Site Search 1.5.2 - Unable to turn off plug-ins« 07:48 AM
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
Upgrading from 1.0x to 1.2
-
- Rank: Freshman
- Registered: Aug 06, 2006
- Last visit: Dec 06, 2009
- Posts: 53
-
- Rank: Team Member
- Registered: Sep 06, 2006
- Last visit: May 09, 2010
- Posts: 2446
May need a some middle points:
3.5) Restore the custom modules / theme / stuff not included in the 1.1.2 package
5) May not be needed if perform 3.5
To have the modules and themes in use in the site can avoid some issues.. is better to have them there when the upgrade script regenerates the list
just my 0.01
--
- Mateo T. -
Mis principios... son mis fines -
- Rank: Developer
- Registered: Jun 16, 2003
- Last visit: May 29, 2010
- Posts: 1966
3.1) unpackage 1.1.2 in your directory
3.2) copy old config.php into new config/ -
- Rank: Freshman
- Registered: Aug 06, 2006
- Last visit: Dec 06, 2009
- Posts: 53
OK, I'm regenerating (with any luck, this will end up in the docs as a summary). At this point, I'm using an outliner to keep this straight. I'd like to point out that Craig's 3.1 isn't in the documentation, 3.2 is not clear in the documentation, nor is Mateo's 3.5
Upgrading Zikula from 1.0x
1. Download 1.1.2
2. Backup everything.
3. Wipe all the directories, keep database intact.
4. Unpackage 1.1.2 in your base directory.
5. Copy the old config.php into the new config/ directory.
6. Restore the custom modules, themes, images, etc. not included in the 1.1.2 package
7. Run upgrade10xto11x.php in your base directory.
8. Make sure everything works (notably reinstall anything missed in step 6).
9. Download 1.2
10. Follow the instructions in docs/upgrade.html, pretending that it's a 1.1.11 installation.
Any other additions/corrections?
--
Bart Lidofsky -
- Rank: Developer
- Registered: Jun 16, 2003
- Last visit: May 29, 2010
- Posts: 1966
-
**unknown user**
- Rank: Expert
- Registered: Mar 16, 2002
- Last visit: Apr 02, 2010
- Posts: 1208
In regards to #4:Quote
Upload all files from the package you downloaded.
In regards to #5:Quote
... make sure you have a backup of the files, especially the config/ directory.
Quote
... replace the config-directory from the new package with the config directory of your previous installation.
In regards to #6:Quote
... then copy restore the files (such as third party modules, themes and downloads, images, and so on) ...
2.5) Login as administrator, disable and remove Members_List module (also in the docs)
7.5) Read item 4.4 in the docs. -
- Rank: Helper
- Registered: Sep 19, 2003
- Last visit: May 25, 2010
- Posts: 612
This is great info guys. I used the upgrade option on my 1.1.2 site (moved a copy of live to development). This seems to be a cleaner way to do it. What would help us all would be for a final list of things to do using this process.
Thank you all... -
- Rank: Freshman
- Registered: Aug 06, 2006
- Last visit: Dec 06, 2009
- Posts: 53
Sorry it took me so long to get back. Wendell, Item 4.4 in WHICH docs? In any case, except for Wendell's last item, here it is, with a couple of my own additions:
Upgrading Zikula from 1.0x
1. Download 1.1.2
2. Backup everything. Make a second backup of the config/ directory, just in case of a problem with step 8.
3. Log in as administrator, preferable on two computers.
4. Disable and remove Members_List module.
5. Wipe all the directories, keep database intact.
6. Unpackage 1.1.2 in your base directory.
7. Upload all the files from the package
8. Copy (don't move) the contents of the old config/ directory into the new config/ directory.
9. Restore the custom modules, themes, images, etc. not included in the 1.1.2 package
10. Run upgrade10xto11x.php in your base directory.
11. Make sure everything works (notably reinstall anything missed in step 9).
12. Download 1.2
13. Follow the instructions in docs/upgrade.html, pretending that it's a 1.1.11 installation.
--
Bart Lidofsky -
- Rank: Developer
- Registered: Aug 05, 2003
- Last visit: May 06, 2010
- Posts: 187
-
- Rank: Team Member
- Registered: Sep 06, 2006
- Last visit: May 09, 2010
- Posts: 2446
BTW, is really needed to convert all the PHP and htm templates Sven?
works for me only converting the language files
--
- Mateo T. -
Mis principios... son mis fines -
- Rank: Helper
- Registered: Sep 19, 2003
- Last visit: May 25, 2010
- Posts: 612
Is it necessary or prudent to replace all instances of iso-8859-* in my Zikula install with UTF-8? -
- Rank: Softmore
- Registered: May 30, 2005
- Last visit: May 31, 2010
- Posts: 340
I am leery of doing this on my production server. Can you get an upgrade process like this to work on a local machine and then copy it back up? -
- Rank: Team Member
- Registered: Feb 27, 2005
- Last visit: Apr 12, 2010
- Posts: 665
Theoretically yes, if your local machine is a clone of your production server.
However, if your production environment allows you to have multiple databases, you could at least make a snapshot of your current production DB (mysqldump) and import it in a separate newly created DB. Then, make a subdirectory or subdomain where you have all the original files installed, and point them to the copy of the database. You could even use the same user/pw credentials, just a different DB. Then you would have created a clone of your website.
Just make sure that there are no absolute (physical) paths anywhere in your database (for example the location of pnTemp or something, since you don't want to share directories between the sites), and if so, change them.
If the clone works correctly and as expected, you could 'safely' play around first, and start the upgrade process. If everything is upgraded and works as expected, then you would just have to 'swap' the two physical paths of the files (original production site, and temporary subdomain or subdirectory), and your production site is good to go.
All depending on your server / hosting environment, and skills on working directly on the server.
--
-- Teb
-- Dutch Zikula Community
Support questions in a Personal Message will be ignored. Use the forums at all times! -
- Rank: Softmore
- Registered: May 30, 2005
- Last visit: May 31, 2010
- Posts: 340
Teb,
Thanks a bunch that is the best path to take and I think I have the skills to pull this off on the server. I can basically do the upgrade on the copy.
- Moderated by:
- Support
