I updated an existing v7.4 Drupal installation to the newest v7.8

After running update.php Drupal told me the following message (see bottom).
Is this an error or warning or only information?

Is this an event because of Drupal or because if an outdated PHP or perl or MySQL installation?

When I click throught the pages of Drupal everything seems to be ok so far. Maybe I have not detect the malfunction yet.

Peter

"Notice: unserialize() [function.unserialize]: Error at offset 34 of 40 bytes in variable_initialize() (line 916 of /mnt/web2/20/29/5143334/htdocs/Drupal_01/includes/bootstrap.inc)

Updates were attempted. If you see no failures below, you may proceed happily to the administration pages. Otherwise, you may need to update your database manually. All errors have been logged.

•Front page
•Administration pages"

:

Comments

Kiadolakas’s picture

This interested me. Does anyone know the answer?

pstein’s picture

Has someone found an answer?

Leo.dil@gmail.com’s picture

I've updated my Drupal from 7.4 to 7.8 and get this error!

Anyone??

hullabaloo’s picture

Downloading the module http://drupal.org/project/variablecheck and running the invalid variables-check at admin/reports/variablecheck fixed the problem for me!

no longer here 1151244’s picture

Hi

I just installed fresh D7.8 and after restoring data of http://vision4life.in, same error found. Luckily found your reply, downloded, installed and deleted 2 arrays (colorbox next, previous), and the problem solved. Thanks a lot.

sbrunthaler’s picture

After upgrading from 7.17 to 7.19, I have the same problem (Notice: unserialize() [function.unserialize]: Error at offset 0 of 1 bytes in variable_initialize() (line 916 of /mnt/webf/a3/87/518587/htdocs/Drupal_01/includes/bootstrap.inc)).

I installed the module variablecheck and ran it, but the delete does not work: The wrong values stay.
There is no error message, they just dont go away...

Thanks for any help,
Stefan

web 17.2 will not come before the universe collapses.

sbrunthaler’s picture

Update - no solution?

web 17.2 will not come before the universe collapses.

knalstaaf’s picture

Try diving into your database and locate the (table and) record that's being mentionned.

Once you've found it, check in the BLOB if the number of characters after the "s:" is correct.

markosaurus’s picture

You might find that the error your seeing still appears because it's in the page cache.

Once you've done as suggested above, go through your database and empty any cache-related tables.

That should empty your page cache and get rid of the error for you :)