Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By lion123 on
Hi,
I'm trying to update drupal 6.12 to 6.13. I tried everything, from instructions in upgrade.txt, then instructions in handbook, but nothing works. I hoped this one will work, but also no luck - http://drupal.org/node/390448
Briefly, I did this in the last attempt (which followed instructions in http://drupal.org/node/390448):
- backup sql database and the whole drupals directory
- set the theme to garland and disabled all the contributed modules
- then I copied all of the files from 6.13 in drupals directory. These new files have overwriten all of the existing files with the same name. Ofcourse, setting.php wasn't changed and all the info inside is correct.
- run the update.php
- after that I log on as administrator, but it still says I should upgrade to 6.13
I have also tried the longer way, with deleting the whole directory with old files, it also didn't work.
Please help, I'm desperate, I have lost whole day trying to solve this :(
Comments
I just did this upgrade last
I just did this upgrade last night and know I, too, would have been frustrated if I had experienced your situation. No error messages, right? Stoopid question: but are you absolutely positive you uploaded 6.13? Is it a browser cache issue? Did you check?
The 6.13 files are, of course, stored in a 6.13 folder and depending on how you uploaded, you could have sent the entire 6.13 folder into your original Drupal directory. I'm just exploring every option here... Look at your drupal site on your server and see if there's a 6.13 folder there... or, if not, double check one of the Drupal files to see if it's in fact 6.13 that's up there.
When I do the updates from just something like 6.12 to 6.13 (one step up) , I don't disable contrib. modules. Haven't had any hiccups. I also delete the Drupal core files, which I never modify, rather than writing over. I know one can write over but I prefer the clean way. Just my method. I don't delete sites/htaccess/robots as that's where all of my custom "stuff" is...
No error messages, that's
No error messages, that's right.
Yes, I have uploaded correct files :) I uploaded only the files from "drupal" folder in my root directory, I didn't upload them in "Drupal" folder. I really don't know what's wrong. Can you please describe in detail how you updated?
Thank you in advance and thank you for this reply too!
Well, the steps in the
Well, the steps in the "install.txt" in your drupal 6x folder are the one's I use. The exception is that I don't disable my contributed modules for a security update like you are doing -- a 6.12 to 6.13 update where it's a tiny leap up. I do delete my Drupal core files rather than writing over them.
But, what's bugging me about your problem is that you say that you have no error messages; you are absolutely positive you have the right version uploaded to your server; you can log in to your admin site with no hiccups... And the only problem is that when you click on "Status Report" it still says 6.12, rather than 6.13. Right???
That just screams, at least to me, that your browser is displaying cached info....cause everything else is right. Just makes sense. So, did you run cron? Did you go into your browser settings and clear cache? Did you clear cache under performance within Drupal?
All caches are cleared. I can
All caches are cleared. I can log in normally, the only error I see is
"One or more problems were detected with your Drupal installation. Check the status report for more information."
And when I see that report, the only errors are
"Drupal core update status: Not secure! (version 6.13 available)" and "Cron maintenance tasks: Never run".
But I haven't seen that I have to run cron. Now I started cron manually, but still nothing changed.
I also forgot to mention that I have tried to update twice on web server and 4-5 times on xampp, but the result is the same.
Hmmm. How about humoring
Hmmm. How about humoring me? Open the changelog.txt that you copied/installed into the Drupal folder on your local dev server. Does it read as follows:
// $Id: CHANGELOG.txt,v 1.253.2.31 2009/07/01 20:51:55 goba Exp $
Drupal 6.13, 2009-07-01
----------------------
- Fixed security issues (Cross site scripting, Input format access bypass and
Password leakage in URL), see SA-CORE-2009-007.
- Fixed a variety of small bugs.
Yes, exactly the same code.
Yes, exactly the same code.
1. Well........ I'm stuck,
1. Well........ I'm stuck, then. My head still says it's a browser display issue -- hey, have you tried a diff. browser? might be worth a shot.
2. Are you running admin menu? If you are running admin menu and haven't done today's update... then disable it. see if that helps.... (See: http://drupal.org/node/507746)
3. Post to this Drupal queu, which has a similar problem...http://drupal.org/node/507760
My attempted upgrade
This is a quick note on my attempted upgrade.
I have been with Dupal since 4.15 and have upgraded many sites countless times.
I tried upgrading on one of my dev sites.
I uploaded all of the files overwriting the existing ones like I have done countless times before.
I tried to run update script. The result was a white screen with no error messages.
I went back to the main page. Everything was OK.
I went to the status report page and it indicated that I had Drupal 6.13 installed and that I need to run update.php.
Just for the hell of it I tried to flush all the caches and got the WSOD and an error message indicating pointing to the menu module. Pretty scary
I put the Drupal 6.12 files back up and restored the DB using the Backup/Migrate module (Thanks for this lifesaver module)
All is good now.
I will try the upgrade on a local install to try to figure out what happened.
Interesting. The only dif
Interesting. The only dif betwn what u did and what I did is I didn't overwrite any core files; deleted 'em and then punched the new files in.
Hey Dougzilla --- You running
Hey Dougzilla ---
You running the admin menu? I am and just got an update announcement and went snooping... found there's a problem in the admin menu caused by an api change in d.6.13 .. sun has done the fix and released it.....see this thread: http://drupal.org/node/505820
Yup it looks like admin menu is the culprit
I read the threads mentioned http://drupal.org/node/505820 and http://drupal.org/node/507746 and I am sure that is what is going on.
I love admin menu and use it everywhere even though one of the last dev versions was a bit wacky. So am I correct in assuming that adminmenu 6.x-1.5 plays nice with Drupal 6.13? I will give it a whirl on a sandbox somewhere.
I haven't really had a chance to digest all of this yet, but I think I am a little cheesed that the older version of adminmenu is so problematic. I know that the the module is always in flux and that the developers are constantly improving it and I thank them for their efforts, but I had a scary situation this morning. If I didn't back up right before the upgrade, I would have had a pretty serious problem
I am having a similar
I am having a similar problem. I updated Drupal like I have always done all through since D4.7 but have never encountered such a problem.
The only difference this time is I decided to take advantage of the site being offline to move the contributed modules & themes from modules/contrib & themes/contrib to sites/default/modules/modules & sites/default/themes respectively.
That caused no problem as everything loaded normally. I feared if any problem came up it would be here but not related to updating to 6.13 from 6.12.
Before that, the update seemed to run normally, including update.php, where the system db table was updated.
I did disable contributed but not system modules (first time I did so), which I had read would not affect the update.
Anyway, the site looks normal only that whatever I do, it shows I still have 6.12. The contributed modules update run with no problem.
I even at one time deleted all system folders except the sites folder & some non Drupal folders + files, but those does not help.
the subsequent runs of update.php are making 0 changes.
I am quite confused.
What could be causing this & how do I get rid of this error without going back & using the pre-update back-up?
.
If any of you are running
If any of you are running admin menu, you should see:
http://drupal.org/node/505820; and
http://drupal.org/node/507746
I'm having the same issue
I upgraded to 6.13 from 6.9, but my site still thinks I am at 6.9. I have done many upgrades without problems. I am not using AdminMenu. My Changelog knows the truth, but for some reason the site thinks it's still at 6.9.
I appreciate any help!
FWIW I have a few other
FWIW I have a few other modules that Drupal thinks are outdated, too. For some reason Drupal is not seeing that the new files are there, even though they are right where their predecessors were.
In fact, it thinks some modules are present that are not even in the Modules folder! I deleted Gallery hours ago. Something's fishy here, but I'm no icthyologist!
I have the same thing as well
I did not upgrade from 6.10 as it was not a production site, but I updates this week and deleted the directories bringing in new 6.14 files. No issues, no errors, cleared caches, tried on another browser, ran update.php way too many times and have drupal 6.10 as the current version. I also have 2 wysiwyg 's on the navigation menu incidentally.
The solution to my problem
I discovered what was causing what seemed to be some strange update failure mentioned above. I had explained it in another post (http://drupal.org/node/519198) but will quote the part addressing this:
Thank you lionheart8
Thank you lionheart8, this was my problem as well (upgrading from 6.14 to 6.15). I just uploaded the individual modules from a fresh 6.15 download, overwriting those I had backed up from my 6.14 install, and upgrade.php ran successfully. I spent hours looking for a solution, and you certainly saved me many more wasted days.