I get this after running update.php:

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://www.twinz.gr/update.php?op=selection&token=[some_token]&id=16&op=do StatusText: OK ResponseText: Fatal error: Call to undefined function variable_store_list_all() in /var/www/mysite/sites/all/modules/i18n/i18n_variable/i18n_variable.install on line 66

The update process was aborted prematurely while running update #7003 in i18n_variable.module

Comments

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Priority: Normal » Major

...I cannot update my drupal installation anymore. Any other pending db updates won't run because of this. Can someone please take a look at this and help me troubleshoot it?

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Priority: Major » Normal

...OK, I gave this a bit of thought and decided to try to disable and then re-enable the module for which the 7003 update is meant for. That module was i18n_variable:

i18n_variable module

* 7003 - Update list of realm variables.
* 7004 - Delete obsoleted variable realm variables.

...so I navigated to my modules page to disable it and guess what? It was already disabled (???). I thought that you are not meant to be offered db updates for disabled modules(?). Anyways, I enabled the module and tried running the db updates. This time it finished without any errors. Still this remains a WTF for me.

jose reyero’s picture

jose reyero commented

Yes, that's the problem, you can do db updates for disabled (but installed) modules :-(

I don't think we are fixing this.

mediameriquat’s picture

mediameriquat commented

I got this message right after uploading the files, after trying to refresh the Available Updates page:

Fatal error: Call to undefined function variable_realm_initialize() in [path]/sites/all/modules/i18n/i18n_variable/i18n_variable.module on line 17

The site appeared to be broken, so I had to revert to the previous version.

Ramaniks’s picture

Ramaniks commented
Version: 7.x-1.x-dev » 7.x-1.6
Priority: Normal » Critical

Here also occurred the following error:

Fatal error: Call to undefined function variable_realm_initialize() in [path]/sites/all/modules/i18n/i18n_variable/i18n_variable.module on line 17

It was after updating the i18n module with version 7.x-1.6.
If I delete it the site back to normal, but can not launch content.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Version: 7.x-1.6 » 7.x-1.x-dev
Priority: Critical » Normal

@Jose Reyero: yeah, a more graceful error pointing to the solution would definitely be UX-friendlier though - just so to give people a hint as to what the problem might be before they rush to the issue queue and create noise I mean. A check before trying to apply/run update #7003 if the module is enabled perhaps?

If this is a generic thing that could happen to any module, perhaps I should file an issue in the core update.module queue so that a generic solution can be found. Perhaps an issue is already filed for that(?) - errors trying to update previously enabled but currently disabled (not fully uninstalled) modules I mean.

@paradiso: You're on the wrong issue Pierre-Etienne. #1619106: Call to undefined function variable_realm_initialize() is what you're looking for. It seems that you'll have to upgrade your Variable module to the 7.x-2.x version.

@Ramaniks: Same as above Valdecir. The issue you need to follow is #1652564: Fatal error: Call to undefined function variable_realm_initialize() in [path]/18n/i18n_variable/i18n_variable.module, line 17

jose reyero’s picture

jose reyero commented
Status: Active » Fixed

Added some module loading for variable store. However, if the module is not there it will still crash, and I think better crashing than losing data.

@klonos: yeah, a more graceful error pointing to the solution would definitely be UX-friendlier though

If we need to do that for each module dependency I'll quit software development and start growing vegetables...

I think a PHP error is actually better. Otherwise users could ignore it and end up with a really dirty site.

Now please, if you want to discuss how this should be, move on to Drupal core issue queue. I am sure there are plenty of other modules hat have similar issues.

(Talking about user friendly, in D7, they removed the option to individually select updates from the update page, now if one of them doesn't work, you're stuck with all the rest... good, right? )

Also see #1666670: Create a new release fixing multiple update issues [Meta issue]

Status: Fixed » Closed (fixed)

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