Fork me on GitHub

Upgrading from 1.0.2 (!)  Bottom

Go to page 1 - 2 [+1]:

  • OK, I've been putting off the inevitable for a year, but now I have sufficient reason to want to upgrade. I won't be able to go to 1.3 for several months (until my server upgrades PHP). I have pretty decent instructions to upgrade to 1.1.2 (I hope they're still good). What I want to know is what is the upgrade path from there; can I go straight to 1.2.7, or do I take a few steps along the way?

    Here's what I have (to upgrade to 1.2):
    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 recently did this and the above is basically what I did. Note that in the docs it says to get the Profile, Legal and maybe other modules in the right location. It also seems to be, at the time, that there were some missing instructions on upgrading your config.php file in one of the upgrades. It was obvious, the instructions referenced some changes in the docs that weren't there. If you don't see that problem the docs have been fixed.
  • In the details, it looked like my basic question was lost: When I migrate from 1.1.2, can I go directly to 1.2.7, or are there intermediate steps?

    --
    Bart Lidofsky
  • I think I did it with 1.2.6, and I doubt that's changed for 1.2.7.
  • OK, I'm slow. But I found a "better" way of upgrading. Given a site at xxxx.com, create a subdomain called "mirror.xxxx.com", copy the installation to that directory, upgrade THERE, and then copy it over to the main directory. So, I started that. One LITTLE problem.

    I can't find 1.1.2 anywhere.

    Can anybody tell me where it's hidden?

    Thanks.

    --
    Bart Lidofsky
  • http://code.zikula.o…-dutch/downloads/90

    When you upgrade from a simple copy of your main site it will use the original database. Just to be on the safe site, i'd do the upgrade from a copy of your database. The way you'll describe it you won't lose your original files if anything goes wrong but your site will still be useless as your database has changed.
  • Here:- http://go.zikula.org/downloadmigrate

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak
  • Thanks, Drak! I got it. I don't have time to do the upgrade until Sunday afternoon, but I'll put in a report of how it went (especially the method of copying to a mirror subdomain, doing all the testing on the mirror, and then migrating it back, a method that has worked very well for me in J***** upgrades and testing).

    --
    Bart Lidofsky
  • OK, I am a bit late, but there were some technical problems. One problem I see immediately: Is it possible to have more than one instance of Zikula in the same domain? The reason I ask is that I had intended to create a site mirror.xxx.com, using a copy of the Zikula databases, pointing the config file at the copies, and then testing out the upgrades on that. Problem is, there is a database, information_schema, which is not mentioned in config.php. I am afraid that I can't point the mirror instance at a copy of the information_schema database, which means that upgrading the mirror may (or may not) screw up the regular copy.

    Can anybody tell me what the information_schema database did in 1.0x, and what will happen to it in the upgrades?



    Edited by bartl on Nov 17, 2011 - 05:56 PM.

    --
    Bart Lidofsky
  • Quote

    Problem is, there is a database, information_schema, which is not mentioned in config.php. I am afraid that I can't point the mirror instance at a copy of the information_schema database, which means that upgrading the mirror may (or may not) screw up the regular copy.


    Unless I'm seriously mistaken (and I don't think I am) the information_schema database is an internal MySql DB which has nothing to do with your Zikula DB. So you can have multiple Zikula instances without any issues (I do this all the time).

    There are 2 options you have:
    1) Create a separate Zikula DB for your test instance
    2) Use the same database you're already using and for your test instance use a set of Zikula tables with a different table prefix and set this table prefix accordingly in your config.php

    Greetings
    R
  • You are correct, that database isn't relevant, I don't know what's in it, but it's not tied to Zikula, it's a creation/used by CPanel.
  • rgasch


    There are 2 options you have:
    1) Create a separate Zikula DB for your test instance
    2) Use the same database you're already using and for your test instance use a set of Zikula tables with a different table prefix and set this table prefix accordingly in your config.php


    Thanks to you and Halbrooktech.

    I'm going with my original plan and make a mirror copy on a subdomain, making the changes in config.php. I will, however, backup the informaton_schema, JUST in case.

    My biggest problem is that my theme is based off of Seabreeze, and, like an idiot, I did not take notes as to the changes I made, so I suspect it will take me a couple of days to rebuild my theme. I'm hoping that I can just upgrade the main site in the same way I upgrade the mirror site, copying over the new theme, but 3rd to worst case, I'll delete the main site and copy the mirror site over (2nd to worst: reinstall Zikula, manually rebuilding everything, worst case, dropping Zikula entirely and rebuilding with Joomla or Drupal).

    In any case, I'm going to have to go with 1.2.8 until my ISP upgrades PHP.

    I will continue to post progress reports, for those who may have the same situation.



    Edited by bartl on Nov 18, 2011 - 11:55 AM.

    --
    Bart Lidofsky
  • Good luck and keep your patience when things don't go immediately ok. Make sure you keep backups along the way so you can always make a step back in the theme adjustments.

    --
    campertoday.nl, Module development, Dutch Zikula Community
  • OK, at this point, it appears that it will be easier for me to do a new install rather than an upgrade; at least I have a good handle on how long it will take (I've tried about 4-5 times to upgrade, and it just doesn't seem to work). Looking through my site, I see that everything should be rather straightforward; I'm going to put the site on a subdomain, and then overwrite my main domain when I am satisfied (at least that part seemed to work well, albeit in the other direction). I'm going to go with 1.28 (as my ISP is still on PHP 5.29).

    But, there are two things which, if true, will make my transfer a lot easier:

    1) How much has the user's list changed? Ideally, can I just copy the data over from the existing zk_users table?
    2) How much has news changed? Can I just copy the zk_stories data over and tweak a few fields, or do I have to reenter (and redate) all the articles?

    The rest of the data I can reenter in a matter of half a day.

    --
    Bart Lidofsky
  • Hi, sometimes it is easier indeed to just start over.
    I have upgraded from 112 recently to have all the users and categories etc in place.

    1) To be honest I dont know how much the user table has changed. Did you try an upgrade without any modules to have just the Core like users and permissions updated?
    2) News has changed quite a lot since early version that were on 102, what version are you using now? You can just copy over zk_stories and install the files of the latest zk12 version of News (262). In the modules list after regeneration you will see that there is a new version and you should be able to update News seperately. If you changed the prefix (zk_) you have to update that also on zk_stories. BTW the table will be renamed to zk_news during the update. And also there make a backup of the News table so that if something goes wrong you can just remove the new table and try with the old one once again.
    If it really doesnt succeed you can also send me the table and I can update it for you. But 1st try yourself of course icon_wink

    --
    campertoday.nl, Module development, Dutch Zikula Community

Go to page 1 - 2 [+1]:

  • 0 users

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