Minor issue upgrading from 1.2.1 to 1.2.2  Bottom

Go to page 1 - 2 [+1]:

  • I downloaded the 1.2.1-to-1.2.2 patch and overlaid the files, then downloaded the full install, and uploaded upgrade.php, install.php and the install directory. I cleaned out all the caches, unprotected config.php and ran upgrade.php. I then regenerated the module list and upgraded the Profile module, after deleting the aforementioned files.

    The site still reports that it is running 1.2.1 and is informing me that an upgrade is available. What am i doing wrong?



    edited by: sk8rs_dad, datetimebrief
  • It would appear the patch files are missing the upgrade.php file which should be run. You can download the upgrade.php from here.

    We'll get the patches updated shortly.

    Drak

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak
  • Thanks for looking into this, Drak.

    I found my problem. I use BeyondCompare (http://scootersoftware.com) as an ftp client and it failed to catch a difference due to an optimization setting that I shouldn't have been using. As a consequence it had failed to upload the latest pnAPI.php.
  • Did we ever do patches for 1.2.0 to 1.2.1? I've got 3 sites that I need to update that are 1.20 still. Plus a legacy PN site I need to get the client on the ball to upgrade before it becomes a more costly venture for him.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • There is a 120 -> 122 patch also in the downloads icon_smile

    --
    campertoday.nl, Module development, Dutch Zikula Community
  • Ah when I looked at the annoucnement there were 2 for 1.2.1 I presumed one was a zip and the other a tar.gzGuess it's a moot point to do one of

    --
    Home Page | Find on Facebook | Follow on Twitter
  • upgrade.php won't be able to run without the install directory right? The install directory isn't in the patch either.

    I've uploaded the patch to a 1.2.1 site and admin is showing 1.2.2 but I don't want to run into problems later if I should have uploaded the /install directory and upgrade.php from the full download.

    It's great that patch file(s) were provided, less to upload, but please consider including an upgrade.html file in the docs directory of the patch that gives instructions for how the patch should be installed. The current upgrade.html included with the patch zip file doesn't even mention a patch, it's the standard upgrade instructions.

    When I see the word patch I figure it's a simple file overwrite, different from an upgrade that may include database changes and need to run an upgrade script.



    edited by: damon, datetimebrief

    --
    Damon
    Catamaran Sailing at TheBeachcats.com
  • Going from 1.2.1 to 1.2.2; do we need to run the upgrade patch?
  • Yup.

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak
  • Ok, I failed to run the upgrade module. Is it safe to run it now or should I revert back to 1.2.1 and then upgrade again?

    Does the upgrade script only make changes to the database, as I could setup my 1.2.1 on my development site and then upgrade, and then transfer the database to my live site?

    I also noticed that files become obsolete. Will the upgrade script take care of these obsolete files to keep the file structure clean?



    edited by: mesteele101, datetimebrief
  • Should still be safe, I had the same problem and running after the fact didn't cause any problems. As to the obsolete files, no, it won't get rid of them, because it only uploads new files, doesn't delete old ones.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • Sorry, but I'm a bit confused after reading all this. Is it better to just upload the patch files, upgrade.php file, and install directory or should I just download the full zip, delete the old files and upload the new ones then run the upgrade.php? It would seem alot easier to just do the patch, but I don't want obsolete files hanging around since I'm doing major customization to my site.
  • When I went to download the core 1.2.2 to get the latest /install directory I noticed that the notice at the top of this page
    http://code.zikula.org/core/wiki/downloads
    "don't know what to download?" points to Zikula 1.2.1

    --
    Damon
    Catamaran Sailing at TheBeachcats.com
  • HalbrookTech

    As to the obsolete files, no, it won't get rid of them, because it only uploads new files, doesn't delete old ones.


    I noticed in the 1.2.1 changelog:

    Code

    Removed behaviour.js from release.

    The above looks like an obsolite file. Are they being removed as part of running the update.php?

    I just remember back in the Postnuke days where there were a LOT of files in folders that were obsolite.

    I would think that running an update on Zikula or even a module should remove any file that is no longer of use.
  • Quote

    Sorry, but I'm a bit confused after reading all this. Is it better to just upload the patch files, upgrade.php file, and install directory or should I just download the full zip, delete the old files and upload the new ones then run the upgrade.php? It would seem alot easier to just do the patch, but I don't want obsolete files hanging around since I'm doing major customization to my site.

    Well, first off, none of your customizations should be done to any files effected by the upgrades, so you shouldn't have to worry about wasting time on Obsolete files. It's just a matter of taking up space. If you want to keep the file system clean, then yes, delete files and upload the new distribution.

    Quote


    The above looks like an obsolite file. Are they being removed as part of running the update.php?

    As I said, all the patches do is update new things, it does not delete anything.

    --
    Home Page | Find on Facebook | Follow on Twitter

Go to page 1 - 2 [+1]:

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