I just downloaded the latest snapshop and got the following error:
Fatal error: Call to undefined function: userialize() in .../httpdocs/sites/all/modules/localizer/localizer.module on line 879

Which is rather easy to fix ;-)

CommentFileSizeAuthor
#8 localizer_0.module33.29 KBRoberto Gerola

Comments

Roberto Gerola’s picture

Status: Active » Fixed

> Which is rather easy to fix ;-)
Absolutely, of course :-)

Thanks.
Fixed in CVS.

Rand HOPPE’s picture

And I just downloaded and am getting:

warning: unserialize() expects parameter 1 to be string, array given in /usr/local/apache2/htdocs/drupal47/modules/localizer/localizer.module on line 902.

??

Thanks for any help...!

Roberto Gerola’s picture

It seems to me that you are using Drupal 4. Correct ?

For the latest bugs fixing you should use the development version :
http://ftp.osuosl.org/pub/drupal/files/projects/localizer-4.7.x-2.x-dev....

Rand HOPPE’s picture

That seems to have taken care of it. Thank you!

Rand HOPPE’s picture

Title: userialize -> unserialize » unserialize
Version: 5.x-1.x-dev » 4.7.x-2.x-dev

I'm using the correct module now. The unseriualize message went away when just having installed the module. But now, when I initialize the settings, the

warning: unserialize() expects parameter 1 to be string, array given in /usr/local/apache2/htdocs/drupal47/modules/localizer/localizer.module on line 899.

error re-appeared.

.....

and now, after having placed tye language blocks and switched, the error is gone.

Will this be some kind of re-curring error?

-Thanks!

Roberto Gerola’s picture

No.
It is only the default value that is wrong if the settings are never been saved.

Rand HOPPE’s picture

Thanks for the quick response, Roberto! Unfortunately, I am still having problems with this error message. It seems to be attached to the "Select Content Languages" block. If I enable the block and check a language, the error goes away. But if I leave a language un-checked the error returns. If I disable the block, the error returns, as well. There are cases where it mentioned line 904, rather than 899, as well. Is there some more info that I can provide to help??

Roberto Gerola’s picture

StatusFileSize
new33.29 KB

It seems to me that you are not using the corrected version of the module.
The errors at the lines we are mentioning are already fixed.

Please, try with the localizer.module that I've attached to this post.
(It is the same version extracted from the dev tarbal)

Let me know.

Roberto

Rand HOPPE’s picture

I used Beyond Compare to compare the localizer.module on my server to the localizer_0.module you attached and they are the same. :(

Roberto Gerola’s picture

Ok.
Can you post here the lines 899 and 904 of you localizer.module ?
So I can take a look at them.

Roberto

Rand HOPPE’s picture

899: $nodeslocale = _localizer_clearnodeslocale(unserialize(variable_get('localizer_usernodeslocale', '')));

904: $nodeslocale = _localizer_clearnodeslocale(unserialize(variable_get('localizer_anonymousnodeslocale', '')));

Roberto Gerola’s picture

The code is correct.
Can you try to execute this SQL instructions on you dataabse ?

DELETE FROM variable WHERE name LIKE 'localizer%'

and then save again you localizer settings ?

Let me know.

Rand HOPPE’s picture

I ran the delete query.
The error message no longer appeared.
I went into administer|settings|localizer
Deselected the "Show Flags" box under "Locale switch block".
Clicked save configuration.
The flags in the left sidebar went away and the error:
warning: unserialize() expects parameter 1 to be string, array given in /usr/local/apache2/htdocs/drupal47/modules/localizer/localizer.module on line 899.
appeared.

??

Roberto Gerola’s picture

Ok.
It is my fault. Sorry.

Change the two lines in localizer.module as follow.
New official release in on the way.

899: $nodeslocale = _localizer_clearnodeslocale(variable_get('localizer_usernodeslocale', array()));
904: $nodeslocale = _localizer_clearnodeslocale(variable_get('localizer_anonymousnodeslocale', array()));

Let me know.

Thanks

Roberto

Rand HOPPE’s picture

Looks like that took care of it, Roberto. Thanks!

Roberto Gerola’s picture

Assigned: Unassigned » Roberto Gerola
Status: Fixed » Closed (fixed)

Closed in release x.6