Active
Project:
Leech
Version:
5.x-1.6
Component:
leech_yahoo_terms
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
22 Mar 2007 at 15:34 UTC
Updated:
17 Apr 2007 at 13:23 UTC
I have an issue with the leech_yahoo_terms module that happens when cron is run. I am running leech 5.x-1.6 with the patch from http://drupal.org/node/125004. Drupal 5.1, PHP 5.2.1, MYSQL 5.0.24a
The error is a whole bunch of these:
# : Object of class stdClass could not be converted to string in /path/to/drupal/sites/all/modules/leech/leech_yahoo_terms/leech_yahoo_terms.module on line 119.
On this error I did come googling and came up with two issues with other modules running into the same error:
Those errors seem to be PHP 5.2+ related.
The first set is followed by this:
# warning: Illegal offset type in isset or empty in /home/.pegs/atalk/atalk1/modules/taxonomy/taxonomy.module on line 1150.
# warning: Illegal offset type in /home/.pegs/atalk/atalk1/modules/taxonomy/taxonomy.module on line 1151.
# warning: Illegal offset type in /home/.pegs/atalk/atalk1/modules/taxonomy/taxonomy.module on line 1154.
# : Object of class stdClass could not be converted to string in /home/.pegs/atalk/atalk1/sites/all/modules/pathauto/pathauto_node.inc on line 221.
# warning: Illegal offset type in isset or empty in /home/.pegs/atalk/atalk1/modules/taxonomy/taxonomy.module on line 1150.
# warning: Illegal offset type in /home/.pegs/atalk/atalk1/modules/taxonomy/taxonomy.module on line 1151.
# warning: Illegal offset type in /home/.pegs/atalk/atalk1/modules/taxonomy/taxonomy.module on line 115
I am on the most current versions of these modules, (the released version, not dev). I noticed this http://drupal.org/node/92900 for pathauto but it seems old.
Thank for the help.
Comments
Comment #1
designerbrent commentedClarified subject
Comment #2
aron novakThe problem is that array_unique PHP function tries to apply this:
(string) $elem1 === (string) $elem2And it became invalid in your PHP version.Thanks for the report, I'm aware of the problem.
It will be fixed soon.