I am still getting my sea legs here. So please bear this in mind. I installed 6.10 just a couple weeks ago. I went to install 6.11 following the instructions. Or at least I thought so. After backing up everything on the site, database included. I copied my /modules, /themes, /profiles, /sites directories on to my computer. I then installed these on the folder created when I expanded the 6.11 tarball. So it overwrote those directories with the old info. I then reinstalled all of these over what was originally in my root folder. Then I ran the updata.php and it didn't do much.

Oh... i should also mentioned that I shut off all added modules.... but I did not shut off modules listed as part of the base system. Is this where I went wrong... ie ... I should have deselected every module before I ran update.php.

Anyway.... any help would be greatly appreciated. This may be a simple question to answer for you more experienced users. BTW... this is a very cool CMS... so glad I chose it over Jumba(sp?).

Thanks...

Comments

GreyHawk’s picture

GreyHawk commented

I'm tired, so not sure I'm following you correctly, but did you say you overwrote the new with the old...?

I did the upgrade by unpacking the tarball, then copying the entire contents up to overwrite the existing core Drupal (old) files.

Any custom modules or themes should be located under sites/all by my understanding, so wouldn't have been touched.

The only file I had to watch for was .htaccess, which had been customized so I had to incorporate the changes/additions from the old into the new (and therefore had to have a copy of the old handy).

I then ran update.php, w/o shutting off any modules.

Seemed to work.

zap-admin’s picture

zap-admin commented

Hi GreyHawk,
Yes.... I unpacked the tarball..... then replaced the /profiles, /themes, /modules, /sites directories..... Then with that entire folder... I uploaded the entire thing. it did give me one error that said it couldn't replace the settings.php file. But the sites folder/directory I had used was from the original site.... so I figured it was the same thing that the FTP program wouldn't replace anyway.

So to sum it all up..... I took some of the files from the original installation... stuffed them into the 6.11 folder of stuff to install.... then installed that whole thing..... then voila.... Nothin....LOL

I hope that's making some sense. I know what you mean by tired.... think I'm going to call it a night here.

Just for the record... I copied the profiles and sites folders to keep some profile information created by one of the modules I was using and for the XML sitemap data that another module had generated. But I can't seem to get that darn thing to updated itself like it's supposed to. Every time I check the file it only shows 2 pages/nodes from the web site... instead of the 20 some odd nodes/pages that there are. I'm playing with those settings to see if I can figure out what in the heck i'm doing wrong.

Thanks...

maxiorel’s picture

maxiorel
Location Brno
commented

I have the same problem. Sucessfully updated about 10 websites, but one of them is problematic. When running update.php there is no 6055 update for system module.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Fixed

http://drupal.org/node/390448

If after following the instructions on this page you still have an issue reset the Status to active.

GreyHawk’s picture

GreyHawk commented

Check out earnie's comment and the link provided; essentially, you should unpack a fresh tarball and copy the entire contents (minus settings.php, .htaccess and the sites folder) up to your existing site, overwriting old stuff, after putting the site into offline mode of course. ...do you have a lot of add-on modules...? If not, you can manually turn 'em off; don't mess with the core modules. Leave 'em alone. If you want to be sure that you won't have a theme issue, set your administration theme to a default field like Garland or something, so that you can at least work with it once the update it done; ideally, if you're working a with heavily modified add-on theme, you'll switch the primary site theme to a default core theme before the upgrade to minimize potential problems, in case the modifications to the add-on cause you issues.

Nodes are stored in the database -- overwriting old core files and folders shouldn't impact 'em.

Add-on modules should be in the sites/all/modules directory and add-on themes in the sites/all/themes; if you'd added 'em to the regular "modules" and "themes" folder, or modified the existing core modules and themes (i.e., not those in the sites/all folders), then you've kinda boxed yourself in.

Once you've got the new fresh files copied up, run update.php. If that completes successfully, go back and enable the add-on modules and themes.

...hope the above makes sense. Again, use the link specified by earnie as your primary guideline; my babble above is simply an attempt to summarize, but shouldn't be used as "the" guideline. This is the online doc that ernie references. Follow it as the recommended procedure...should come out ok...

Good luck!

maxiorel’s picture

maxiorel
Location Brno
commented
Status: Fixed » Active

Thanks for the guideline, however it doesn't solve my problem. The new files from Drupal 6.11 are here, but the update.php doesn't see the new database structures, for example, there is not the 6050 version for the system.module. And yes, again: I overwrite all older files with new files from Drupal 6.11.

I did the same update way like many times before and like ten times today with other websites... Only one seems to be problematic and I don't know why.

GreyHawk’s picture

GreyHawk commented

Hi max -- sorry, I should've been specific; my comment was responding to zap's...I am at a loss for why your update isn't working.

:/

Do you have any errors in your log file?

Anonymous’s picture

Anonymous (not verified) commented

Do you find a update function numbered 6050 in the system.install file? What VERSION do you find in system.module?

maxiorel’s picture

maxiorel
Location Brno
commented

Hi there. The log file seems to be OK, only the record "themes/misc/watchdog-ok.png not found" is there.

And yes, there is a function 6050 in system.install file. The system.module begins with this:

// $Id: system.module,v 1.585.2.34 2009/04/30 00:13:31 goba Exp $

and with this:

define('VERSION', '6.11');

Anonymous’s picture

Anonymous (not verified) commented

What is the schema_version listed in the system table for the system module?

zap-admin’s picture

zap-admin commented

Hi Ernie..... I'll check it out and report back.... thank you for your help..... Z

zap-admin’s picture

zap-admin commented

GreyHawk.... I will give what you suggest another try and look at Earnie's notes.... When I did do the last install I don't think I reused the old .htaccess file.... but I know I used most everything from the original sites file... this was because one of the modules I've got... I think the XML sitemap module.... dumps a bunch of files, including the XML sitemap it was generating until I hit the "Clear Cache" button...LOL. into the sites/default/files directory. Maybe I just need to scrap that module and reinstall it after I do this again... since it's still in development and I read another post in there that said they were still working out the kinks. Anyway.... I'll report back after I make these adjustments and reattempt this.... probably tomorrow night. But I wanted to thank you again for your help. I really appreciate it.

Okay... I tried it again.... and still the same issue.... in the list that appears in update.php there's nothing showing for a core update. The latest one in the list is the 6049..... Now I do have another question. When I look at the sites/default folder it has all the "write" permissions unchecked. I thought I had turned this on and off during the installation. But could this be at all part of my problem? Because it won't transfer anything from the sites folder... but i think you said I shouldn't update that anyway.... I'm thinking my only next step is changing something I saw in the settings.php file..... mentioned someplace else... Anyway any other suggestions would be greatly appreciated. Thank you to everyone for your help ..... tried changing settings.php file from FALSE to TRUE as indicated in link.... but still no difference. I must be missing something....

maxiorel’s picture

maxiorel
Location Brno
commented

Ernie, the schema_version in the system table for the system module is 6049.

Anonymous’s picture

Anonymous (not verified) commented

Ok, it seems that maybe you're having some environment issue. Would there be a mod rewrite happening you're unaware of? Or perhaps a symlink (junction point on Windows) that puts you in a different version.

Try moving the modules directory completely out of the sites into a temporary holding directory. Does that help the situation? The move of the directory is effectively disabling the modules without disturbing any of their data.

Good luck. BTW, I'm working to get the kinks out of xmlsitemap by hopefully today.

maxiorel’s picture

maxiorel
Location Brno
commented

Disabling the clean URLs, cleaning the cache tables, disabling the modules as above, nothing helps. There is not any symlink too. Very strange.

jkkcolburn’s picture

jkkcolburn commented
Priority: Normal » Critical

Hello folks!

I had a smooth running 6.10 site that is now down after attempting to updating to 6.11.

I have been successfully using drupal for about a year. I am not a pro, and avoid changing code in any way, but I usually can update without an issue until today.

http://everydaype.com

Fatal error: Call to undefined function user_access() in /hermes/web07/b2314/pow.everydaypeco/htdocs/epe2009drupal/includes/menu.inc on line 449

Fatal error: Call to undefined function user_access() in /hermes/web07/b2314/pow.everydaypeco/htdocs/epe2009drupal/includes/theme.inc on line 934

Thanks for any help you may have.

JC

***I do not know how to edit the htaccess file, but I think that is my culprit as my main directory is in a subdirectory on the server. Word pad just gives me a head ache looking at the mishmash of code...is there a better way to view this type of file?
***anyone available to help me with this for a fee?

jkkcolburn’s picture

jkkcolburn commented
Assigned: zap-admin » Unassigned
GreyHawk’s picture

GreyHawk commented

Post your .htaccess -- did you overwrite it? Do you have a backup of the original one, or can you pull the original from the backup?

I use wordpad to edit mine -- it looks mishmashed in notepad for me. (Did you tell it to use wordwrap in notepad? That might help.)

zap-admin’s picture

zap-admin commented

Earnie,
I guess I can try that. Just so you know... I'm using a Linux host.... not windows.. and working on site via an OS X Mac. Look forward to seeing how the XML sitemap module works. It deleted his XML map file in sites/default/files/xmlsitemaps/ and I just checked it and it's still not there... this happened when I hit the "Clear Cache" button in the tool box. BTW... it's shaping up to be a kick butt module you've created there..... once I figure out what exactly in the heck I'm doing...LOL

Oh.... there's one other issue. The ISP is supposed to reinitialize or reinstall the database. When I was screwing with it's settings I changed a selection on PHP version... and the server is a myPHPadmin 5.0.51a.... while the MySQL database library is 4.1.21 Do you think this could be the source of these problems? I just checked and they still haven't fixed it. I may need to go back to my old ISP.... but what a PIA. Anyway... it's giving me an error message that says this mismatch may cause "erratic behavior".

GreyHawk,
I haven't messed with the .htaccess file at all. I think I overwrote it the first time I tried to do the update but I'm not entirely positive about that. Any of the files that I've messed with... which I think has only been the one mentioned in one of the links above...I used dreamweaver .... or maybe textedit... then replaced it. If I post a copy of the .htaccess file in here.... This may be a completely stupid question... but I'm not opening myself up too much putting this up here am I? I'm guessing no since you should be able to pull it yourself since it's on my main site folder......Or have I missed the boat and you were replying to the other person with a complete site crash...LOL... laughing at my ashen-blonde moment and not that guys problem....

I can't say this enough Ya'll (Texas thing) but thanks for your help....J

zap-admin’s picture

zap-admin commented

Okay... here's the latest....

1) I renamed the themes and modules folders.... then uploaded all the stock files from the 6.11 tar ball and viola... or so I thought. I ran updata.php and for the first time I actually saw the 6050 update. And told it to install.... I also deactivated all the modules before I did this. Okay... so then I delete the modules and themes folders and renamed the originals back to their original names. I then when back into the admin and the dang thing thought it was still on 6.10. I Here are some of the error messages I got....

first on upon coming back into the admin...

user warning: Unknown column 'status' in 'where clause' query: SELECT COUNT(*) FROM xmlsitemap WHERE status = 1 in /usr/local/pem/vhosts/191920/webspace/httpdocs/zaphodsplanet/modules/xmlsitemap/xmlsitemap.module on line 302

The next one I got was was after I turned all my modules back on:
• user warning: Unknown column 'status' in 'where clause' query: SELECT COUNT(*) FROM xmlsitemap WHERE status = 1 in /usr/local/pem/vhosts/191920/webspace/httpdocs/zaphodsplanet/modules/xmlsitemap/xmlsitemap.module on line 302.
• user warning: Unknown column 'status' in 'where clause' query: SELECT COUNT(*) FROM xmlsitemap WHERE status = 1 in /usr/local/pem/vhosts/191920/webspace/httpdocs/zaphodsplanet/modules/xmlsitemap/xmlsitemap.module on line 302.

Then the fun began... I ran installed updates to the xmlsitemap module and another called tweet.... but I forgot to turn them off in modules..... anyway... I installed the new versions and then ran update.php again....

When I tried to shut off the xmlsitemap module(s) the system would give me a blank screen after I hit the update.... I finally broke down... went into FTP and deleted the whole folder for XMLsitemaps. I'm at least no longer getting the weird errors when I go back into admin... just the typical "Not Secure"... need to update to 6.11.

Now... I'm going to run update PHP one more time with the xmlsitemaps module completely gone.....Okay... it doesn't see anything to update although I notice now that it did take the tweet module update

Next... I'm going to try uploading all the files again w/o turning off the modules... and w/o copying the modules or themes from the original tar-ball.... Uploading... I'm suddenly glad that I haven't quit smoking again...LOL... Oh... the site is in Maint. mode.
Okay... son of a you know what... nothing listed to update. I'm assuming that some other modules must be causing this...

So Next... I will shut off all non-core modules, upload once again... all files except for modules and themes and run update.php again to see what I see. Still the same result... it isn't seeing any updates at all.

My sudden, out of the blue hypothesis is that there's something wrong with one of the modules from the original installation... so... I'm going to look at the modules in the new 6.11 modules directory.... and I'm going to install them one at a time over the old modules with the same name to see if we can figure out which one of these buggers is getting wonky on us. I'll run update.php between each update and report below:
-Aggregator...survey says.....no difference
-Block..... Okay.... Success.... on the second try.... hell... I am sorry but I didn't go back to the status reports after updating Aggregator.... so I don't know if that did it... but after I updated block I got the same thing in update.php.... showed no updates available.. ran it anyway.. then went back into admin.... and I was suddenly showing that I was 6.11... FINALLY... and not 6.10

Next.....since we're all up to date... I'm going to reinstall the newest version of the XML Sitemap module..... to see if we get anything super freaky....Well... I turned everything back on and all seemed well... however... after running update.PHP after the install of XML Sitemaps I'm getting this error again.....

user warning: Unknown column 'status' in 'where clause' query: SELECT COUNT(*) FROM xmlsitemap WHERE status = 1 in /usr/local/pem/vhosts/191920/webspace/httpdocs/zaphodsplanet/modules/xmlsitemap/xmlsitemap.module on line 302.
user warning: Unknown column 'status' in 'where clause' query: SELECT COUNT(*) FROM xmlsitemap WHERE status = 1 in /usr/local/pem/vhosts/191920/webspace/httpdocs/zaphodsplanet/modules/xmlsitemap/xmlsitemap.module on line 302.

Sorry this post is so freakin long. Somewhere in here one of you module developers might see something I'm completely oblivious to... I'm going to see if the majority of my news stories are still in tact now... And I'll report back with anything of interest...

zap-admin’s picture

zap-admin commented

I have temporarily shut down XML site maps module.... total bummer.... will try next rendition of it..... I ran the update XML Sitemaps for entire site.... got about 2 pages full of errors... followed by a green "update successful" message. Wish I could understand what's happening.... J

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Fixed

Follow up on the xmlsitemap issue queue for your issues with that module. A contrib module isn't a Drupal issue.

zap-admin’s picture

zap-admin commented

Okay.... I'll come back to it in the next few days.... I need to make more site updates. Thanks again for your help Earnie... BTW... it sounded like you were doing the XMLsitemap module.... true? Going to be fantastic when the kinks are all worked out. Wish I knew.... or more accurately... had the patience to code like that....Thanks again.... So glad I chose Drupal over Jumba.....J

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

maxiorel’s picture

maxiorel
Location Brno
commented

Just a note for the others. I finally solved my problem. I looked to the system table and see a strange filepath like modules/modules/... for all core modules. So I went to the modules folder and find that the modules are doubled in modules/modules folder for an unknown reason. I deleted the modules/modules folder and edited the database providing the right path. Finally I was able to run the update.php correctly.