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
- mercromina responded to »error when i try to upgrade to the last version of dizkus module (3.1)« 08:01 PM
- craigh responded to »TagIt 3.0 for Zikula« 03:58 PM
- localrags responded to »Remove contents of nuke_sc_anticracker from Database« 11:30 AM
- jmvaughn responded to »Shoutit for zikula 1.3?« 09:31 AM
- mdee responded to »Different page content under one template (tpl file) based on URL« 07:17 AM
- espaan responded to »Categories disappear when editing ...« 08. Feb
- eledril responded to »How decrease zikula cpu usage« 08. Feb
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
Minor issue upgrading from 1.2.1 to 1.2.2
-
- Rank: Registered User
- Registered: Feb 08, 2010
- Last visit: Feb 24, 2010
- Posts: 7
-
- Rank: Software Foundation
- Registered: Jul 21, 2001
- Last visit: May 31, 2010
- Posts: 604
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 -
- Rank: Registered User
- Registered: Feb 08, 2010
- Last visit: Feb 24, 2010
- Posts: 7
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. -
- Rank: Developer
- Registered: Dec 31, 1969
- Last visit: Jun 01, 2010
- Posts: 6840
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
-
- Rank: Developer
- Registered: Aug 23, 2003
- Last visit: May 31, 2010
- Posts: 1401
There is a 120 -> 122 patch also in the downloads
--
campertoday.nl, Module development, Dutch Zikula Community -
- Rank: Developer
- Registered: Dec 31, 1969
- Last visit: Jun 01, 2010
- Posts: 6840
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
-
- Rank: Softmore
- Registered: Dec 31, 1969
- Last visit: May 25, 2010
- Posts: 306
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 -
- Rank: Helper
- Registered: Sep 19, 2003
- Last visit: May 25, 2010
- Posts: 585
-
- Rank: Software Foundation
- Registered: Jul 21, 2001
- Last visit: May 31, 2010
- Posts: 604
Yup.
--
Zikula Lead Developer
Board Member of the Zikula Foundation
Follow me on twitter.com/zikuladrak -
- Rank: Helper
- Registered: Sep 19, 2003
- Last visit: May 25, 2010
- Posts: 585
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 -
- Rank: Developer
- Registered: Dec 31, 1969
- Last visit: Jun 01, 2010
- Posts: 6840
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
-
- Rank: Registered User
- Registered: May 19, 2007
- Last visit: Apr 23, 2010
- Posts: 19
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. -
- Rank: Softmore
- Registered: Dec 31, 1969
- Last visit: May 25, 2010
- Posts: 306
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 -
- Rank: Helper
- Registered: Sep 19, 2003
- Last visit: May 25, 2010
- Posts: 585
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. -
- Rank: Developer
- Registered: Dec 31, 1969
- Last visit: Jun 01, 2010
- Posts: 6840
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
- Moderated by:
- Support
