Closed (fixed)
Project:
Drupal core
Version:
6.15
Component:
update system
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
18 Dec 2009 at 04:58 UTC
Updated:
27 Jan 2010 at 12:26 UTC
Jump to comment: Most recent file
Comments
Comment #1
pasquallewe need to understand your problem first.
can you write the steps what you did and also what is the problem, the error message?
Comment #2
quikone commentedNo error message, but the websites still indicate that they are at 6.14. The steps I followed were basically the steps included in the file. But, I did a system backup, downloaded the new file, unpacked the file into its own folder, moved all but the themes and modules folders over to the /var/www directory. I then went to my main website and performed update.php. The first time I noticed that the system was still at 6.14 I thought I must have done something incorrectly. So at that point I went back to the update directions and I am pretty sure I followed them. Should I have moved any of the file in themes and modules, so far with all previous updates I have not.
Thanks again,
Ron
Comment #3
quikone commentedComment #4
heine commentedThe directories modules and themes contain core Drupal elements and need to be transferred.
Comment #5
quikone commentedThat was it, sorry I did not recognize that before posting.
Comment #6
ingopingo commentedSorry to reopen this issue, but same problem here.
After multiple "update.php" and "Available updates" runs the site still shows 6.14 and "Security update required!"
I fear that I'll finally give up.... At the moment I simply don't feel like working any further with drupal... :-(((
Comment #7
ingopingo commentedSeemes that I'm not the only one who ran in big troubles with this update.
If I could turn back time (just back to this morning) I would give a damn on this security update... :-(
Comment #8
heine commented@ingopingo, while I can understand how you feel, your emotional state doesn't give us much to work with.
What steps did you take to upgrade?
Comment #9
pasquallewhat do you see in /modules/system/system.module on line 12?
Comment #10
ingopingo commentedHeine,
thx for your reply.
I used the upgrade.txt as guidance and did all the steps as described (as I did before when I upgraded from 6.13 to 6.14).
- made a backup of files and database
- put site in maintanace mode
- deactivated all modules except the core ones
- deleted all the content within the drupal installation
- copied the drupal 6.15 data in the installation folder
- copied the sites folder in theinstallation folder
- run update.php (which was a problem cause I forgot to upload the www.example.com/modules fiolder during the first step). this result was that the update. php only leaded to WSoD.
- copied the missing modeules folder in the drupal directory
- rerun update.php which now worked as it should.
- began to re-activate some basic modules asi18n, cck, views, poormanscron, etc.
- poormanscron was then fired up which leads my attention to the fact that drupal still wanted to upgrade to 6.15
- made several update.php runs since then and reupped the 6.15 files again and again but with no success.
- status report still mention that 6.15 upgrade is necessary.
Simply frustrated I dunno what I can do except dropping database tables and start from scratch. But this is not really an option either...
For Drupal is at version 6.15 now it is hard to believe that it is incapable to update automatically.
How can it happen that an minor core update (with not even a single new feature!) causes such an amount of work and contents such a bunch of risks to destroy the installation?
At this moment it seems to me that having a drupal community is a bit like playing russion roulette...
Basically these points could make Drupal a No-Go for one who isn't interested in dealing with disasters every couple of weeks :-(
Comment #11
ingopingo commented@Pasqualle
define('VERSION', '6.15');as you stated.
Cleared all caches for several times, too..
Comment #12
pasquallepossible problems:
1. you must have a module (or old system.module copy) which redefine the VERSION number. try:
find . | xargs grep "'VERSION'" -sfrom the Drupal root folder
2. you are not working with the correct installation folder. the site points to a different folder than what you are trying to upgrade.
Drupal upgrade is plain easy.. don't blame the system..
Comment #13
ingopingo commentedfind . | xargs grep "'VERSION'" -show can I do this? is this a console command? I didn't worked with console yet...
Comment #14
heine commentedYour modules folder still contains files from Drupal 6.14. The update status module takes the version information from the .info files there.
Comment #15
ingopingo commentedThat would be logical. But I already deleted all within the www.example.com/modules folder and upped the 6.15 folders in there. So I wonder what file this could be.
Could it be possible that any file within the /sites/all/modules causes such errors? From all what I learned till now this couldn't be?!?
I think I'll check those files within the modules folder once again. Perhaps I've overlooked anything. Thx for your help so far....
Comment #16
ingopingo commentedWell... I did it again... Deleted all folders and files except the /sites folder and reupped all from a clean & fresh downloaded drupal 6.15 copy.
To me this means that there can't any old files left.
Update.php was executed once more (no changed files) and the result is the same again...
If nothing within the /sites folder can cause these problems than it has to be the database.
Really dont know what to do else if not to delete the whole installation. I want to say thx for your time and the attempts to help.
I'll have to think about rebuilding (again!) all from scratch on a 6.15 version or to try out a different CMS (littering over 6 month of learning and the books I bought). I don't know if I simply had a lot of bad luck during the past months or if it is just that I'm as dumb as a doorknob. I can't believe that it is normal that one risks crashing the system everytime when installing /deinstalling contributed modules. At the end I want a system I can count on while running my sites...
Comment #17
heine commentedIf you are sure you deleted everything except sites, it means there's a module in sites that claims to be core and of version 6.14.
Possible causes:
- you did "override" a core module with a copy in sites/all/modules or sites/[site]/modules.
- you copied a .info file from core to a module in sites/all/modules and forgot to remove the version & core claims.
- you store a backup of older core modules inside sites/all/modules or sites/[site]/modules.
BTW: If you open modules/block/block.info, what VERSION does it have?
Comment #18
heine commentedIf you have access to your sites' database (eg via phpmyadmin), please post the results of the following query:
(If you use a database prefix, use [prefix]system)
Comment #19
pasqualleare you sure you are working with the live Drupal directory?
rename the index.php file to noindex.php (or something), then check the site from the browser.
Comment #20
ingopingo commented@Heine,
thx a lot for your help. It's much appreciated!
The modules/block/block.info shows
version = "6.15"Should I try to delete the complete content of sites/all (the modules & themes folder within) to see if anything in there interferes with the core modules?
Comment #21
ingopingo commented@ Heine,
this is the result of the database query
SELECT filename, info FROM systemComment #22
ingopingo commented@Pasqualle,
Thx a lot for your help, too
Renaming the index.php to noindex.php leads to a file not found
Comment #23
heine commentedPlease execute the query instead of searching for it :)
PHPMyadmin should have something called "Execute query" or "Execute SQL" or somesuch.
Comment #24
ingopingo commentedOh sorry... :-/
This is a big one... phew!
Comment #25
ingopingo commentedOh sorry... :-/
This is a big one... phew!
Had to make an Attachment. Perhaps too big...
Comment #26
heine commentedThanks!
You have a copy of Drupal 6.14 inside sites/all/modules/drupal6-14. Better remove it :)
Drupal will pick those modules over the ones in /modules
Comment #27
ingopingo commentedOh my goodness!!!
I've searched for core modules in this folder over and over... But I didn't notice this Drupal-6.14 folder... Don't even know how it has find its way in this folder...
I'm somewhat painfully embarassed... :-/
I' try it out and reply...
Comment #28
ingopingo commentedSometimes I'm such a blockhead...
Must have had this folder in sites/all/modules for a while...
After deleting it I now face some major trouble:
Fatal error: Call to undefined function user_access() in /var/www/web84/html/sites/all/modules/admin_menu/admin_menu.module on line 82if I reload http://www.example.com/en/admin/reports/updates...Have to figure out now how to tell drupal to use the www.example.com/modules folder instead... Hmmm
Comment #29
ingopingo commentedWhen I try to run www.example.com/update.php I get
http://www.example.com/update.php?op=infowith a blank screenand trying to run www.example.com/en/update.php leads to
, too..
In this line of admin_menu (line 82ff) I found the following:
Comment #30
pasqualleyou need to clean up your system table now.
Comment #31
ingopingo commented@Pasqualle,
thx again. Now running update.php was possible :-)
Comment #32
ingopingo commentedBut nevertheless a lot have been messed during my upgrade attempts to 6.15 (maybe earlier) cause everything runs horrible sloooow now and there are a lot of other issues as far as I can see.
Parts of my menus are totally gone.
Translations seem to be messed up cause content is shown in mixed languages now.
Don't know if I'll be able to fix these things up... but that's another story.
But at this point I want to say thanks a million to Heine and Pasqualle for your time and your patience :-)
Your help was / is much appreciated!
Comment #33
int commentedComment #34
int commentedSorry, cross post
Comment #35
CarbonPig commentedHi Pasqualle,
I had the exact same issue - I accidentally left a drupal-6.14 file in my sites/all/modules directory.
When I ran the command to clean the system tables like you suggested I adjusted the value from 43 to 31 so that modules/.. directory would be referenced instead of the sites/all/modules/drupal-6.14/modules/.. directory.
Now all the admin pages show up blank - the site still shows offline for anonymous users, but for the admin, I just see blank pages and can't run cron.php or update.
Any suggestions would be greatly appreciated, as I'm totally stuck.
Thanks,
Matt
Comment #36
pasqualle@CarbonPig: check the core (required) modules in the system table. make sure they are enabled (status = 1) and the module path (filename) is correct