Closed (fixed)
Project:
Localizer
Version:
4.7.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
17 Jan 2007 at 12:39 UTC
Updated:
22 Jan 2007 at 07:50 UTC
Jump to comment: Most recent file
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 ;-)
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | localizer_0.module | 33.29 KB | Roberto Gerola |
Comments
Comment #1
Roberto Gerola commented> Which is rather easy to fix ;-)
Absolutely, of course :-)
Thanks.
Fixed in CVS.
Comment #2
Rand HOPPE commentedAnd 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...!
Comment #3
Roberto Gerola commentedIt 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....
Comment #4
Rand HOPPE commentedThat seems to have taken care of it. Thank you!
Comment #5
Rand HOPPE commentedI'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!
Comment #6
Roberto Gerola commentedNo.
It is only the default value that is wrong if the settings are never been saved.
Comment #7
Rand HOPPE commentedThanks 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??
Comment #8
Roberto Gerola commentedIt 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
Comment #9
Rand HOPPE commentedI used Beyond Compare to compare the localizer.module on my server to the localizer_0.module you attached and they are the same. :(
Comment #10
Roberto Gerola commentedOk.
Can you post here the lines 899 and 904 of you localizer.module ?
So I can take a look at them.
Roberto
Comment #11
Rand HOPPE commented899: $nodeslocale = _localizer_clearnodeslocale(unserialize(variable_get('localizer_usernodeslocale', '')));
904: $nodeslocale = _localizer_clearnodeslocale(unserialize(variable_get('localizer_anonymousnodeslocale', '')));
Comment #12
Roberto Gerola commentedThe 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.
Comment #13
Rand HOPPE commentedI 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.
??
Comment #14
Roberto Gerola commentedOk.
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
Comment #15
Rand HOPPE commentedLooks like that took care of it, Roberto. Thanks!
Comment #16
Roberto Gerola commentedClosed in release x.6