Fatal error: Call to a member function getDefaultWeight() on a non-object in variable_realm.module on line 548

Just encountered the exact same error

.

Same error here after updating from 1.2 to 2.0.

Same error here...

Same here: Same error here after updating from 1.2 to 2.0.

Same here

same here

If it helps, I found that clearing the caches (I used the devel module's "empty cache" option) cleared up the errors, as I could also not access the Multilingual Variables settings after this and got white screens. (and I had to manually put the site back on-line since the update didn't finish cleanly.)

Clearing caches seems to have worked. Hope there is nothing left behind ...

Same with my sites

Still not working after clearing caches...

I realize now that I missed the update to variable v 2 (before updating i18n) because it was not suggested in the list of available updates.
Why was variable 2 it not listed as an update to v 1?

Confirmed, you have to upgrade variable to 2.x (and run update.php) before updating i18n module.

Thanks!

@jordiserra, you have to upgrade Variable and i18n simultaneously, otherwise there can be even more serious problems.

Exact same problem here. Variable module didn't notify the new 2.x version before I upgraded i18n. Then I downloaded the variable 2.x, copying and overwriting all previous version. Before I run update.php, I got the Fata error message above, and I couldn't open some module administration screens (for example Google Analytics). But after running update.php, everything is working fine now..

I encountered the same error (during a run of update.php) and after clearing the caches update.php would run fine.

@renat (#13): updating simultaneously exactly run me into that error. Took me several approaches with different module order to overcome that hurdle.
I'd recommend first upgrade to Variable 2.x and run database update twice.

Yes, it may be wrong i18n version or that it needs a cache refresh. However, these errors shouldn't happen even when classes are not available, this one should be fixed now in latest dev.

Just in case it helps someone, I had to proceed to a complete registry rebuild in order to recover from the wrecked upgrade.

Change $i18n_string_object->cache_reset();

to

if ($i18n_string_object = i18n_string_get_by_lid($lid)) {
$i18n_string_object->cache_reset();
}

on line no 402, all\modules\i18n\i18n_string\i18n_string.pages.inc