Fork me on GitHub

Upgrading from 1.0x to 1.2  Bottom

  • 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
  • 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 icon_wink just my 0.01

    --
    - Mateo T. -
    Mis principios... son mis fines
  • 3.1) unpackage 1.1.2 in your directory
    3.2) copy old config.php into new config/
  • 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
  • 0. Backup everything.
  • 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.
  • 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...
  • 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
  • I miss the UTF-8 conversion to UTF-8 of modules not supporting gettext!

    Code

    find . -name "*.php" -exec iconv -f ISO-8859-15 -t UTF-8 {} -o {} \;
    find . -name "*.htm" -exec iconv -f ISO-8859-15 -t UTF-8 {} -o {} \;


    --
    | scribite! | TNGz | piwik | zweet |
  • BTW, is really needed to convert all the PHP and htm templates Sven?
    works for me only converting the language files icon_confused

    --
    - Mateo T. -
    Mis principios... son mis fines
  • No, but it's easier to handle on the complete site instead of moving around in folders.

    The script is from slam and does what we need ;)

    --
    | scribite! | TNGz | piwik | zweet |
  • Is it necessary or prudent to replace all instances of iso-8859-* in my Zikula install with UTF-8?
  • 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?
  • 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!
  • 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.

This list is based on users active over the last 60 minutes.