updating from 6.26 to 6.27 (security update)

Posted by laz0rama on December 21, 2012 at 6:34pm

i have searched all over, google and drupal.org, and i cannot seem to find reference to this specific issue.

i am trying to update to 6.27 for the security fixes. i am following the standard update procedure, and my installation has no custom code (other than theme files). although it appears to go fine, one i have completed running update.php, i get the wsod. forcing on error reporting, i see that the error is:

Fatal error: Call to undefined function _system_theme_data() ... /includes/theme.inc on line 493

the undefined function is in /modules/system/system.module. by adding debug code, i see that the module is being loaded. but that function is unavailable when theme.inc tries to call it.

i see tons of other errors and discussion around this error (undefined function _system_theme_data() ), but none seem to apply to this particular update.

has noone else seen this issue when updating to 6.27? am i missing something obvious?

any help much appreciated.

thanks!

Comments

I updated one site today to

Posted by sadashiv on December 21, 2012 at 7:04pm

I updated one site today to 6.27 from 6.26 and faced no problems in it. Make sure that you change your default theme to garland before updating, flush all cache after the update and then reenable your previous theme.

Hth,
Sadashiv.

I have two different stes,

Posted by ajriddin on December 23, 2012 at 2:05pm

I have two different stes, currently running Drupal 6.26.

I attempted to update from 6.26 to 6.27 when the security notice came out. I put the sites off-line, selected the default themes and performed backups. After installation, when I navigate to /update.php, I get a WSOD. I type in other urls, but get the same.

I've cleared the cache via phpMyadmin, installed Dtools, and tried a number of options listed in various articles on this webste, all to no avail.

I am now forced to revert to 6.26, which concerns me, because of the security issues identified.

Can anyone please suggest any fixes?

I cannot even force error reporting (although perhaps I'm doing it wrong?)

I don't think their are any

Posted by sadashiv on December 23, 2012 at 4:40pm

I don't think their are any database updates required in upgrading from 6.26 to 6.27 as it shows nothing pending. Can you try using drush to clear all cache (drush cc) and check if it works or you get the same error on drush run too.

Thanks,
Sadashiv.

Revert to default themes

Posted by county_bg on January 2, 2013 at 4:23pm

Hi,
I had exactly the same problem. You need to switch both Site Theme and Administration Theme to the default (Garland). Disable all contributed (non-core) modules and run update.php
And most important of all: never update a live site without testing the update in a testbed.
Good luck!
/B

Upgrade D6.26 to 6.27

Posted by kaybee57 on January 15, 2013 at 11:27pm

Did my stock standard regular upgrade one V6 version to another, (6.26-6.27) having done the same process many times on previous versions - major fail - crashed my site, reverted back to D6.26 and all good again.
Haven't got time right now to go check what 'really' needs doing (other than what I've always done) so will report back later.
Meantime am not touching D6.27. There's obviously something different going on for the quick upgrade path!

And yes, time to upgrade that site to D7 - just done my first major 6-7 upgrade on another - whew!!! It's all working. All of my new sites now are on D7 but still have lots on D6.26 - luv D7 so much better than 6.

6.27

Posted by niki v on January 17, 2013 at 3:23pm

I upgraded a live site in December and all seemed fine until I attempted to install new modules/ update existing modules - nothing happens.
I tested a fresh install of 6.27 on WAMP and found that I could upload new modules but not update any older versions of modules that I installed to test. The update manager also doesn't recognise the core as being 6.27, it reads it as 6.22, even though it's a clean install of 6.27 so there is a major flaw somewhere. Bug reports have not been replied to - I'm going to test 6.28 which mention some bugfixes and will report back but I don't recommend trying to upgrade, even though it's a security fix :( :(

Time to get porting to 7...

Is it a module problem?

Posted by Tarim on January 19, 2013 at 10:19pm

I had the same problem upgrading to 6.27 (and also to 6.28).

Turns out it's because I'm using a module which contains a copy of the 6.26 core modules - in my case:
cod-6.x-1.0-rc2-core.tar.gz

The clue (which I missed at first) is in the naming. Have you installed any modules which have "core" in the name? "grep -r '6\.26' sites/all/modules" might help you track this down.

I guess I shouldn't really be using cod as a standard modules in sites/all/modules in this way. Though I thought I grabbed it from the Drupal modules pages same as any other module and didn't see any warnings about this.

At the moment I've kludged it by deleting the directory sites/all/modules/cod-6.x-1.0-rc2-core/modules and creating a soft link to ../../../../modules in its place. Not a very pleasing fix.

Any hints on the proper way to do this gratefully received.

Cheers,
Tarim