Error:

* warning: Invalid argument supplied for foreach() in /includes/common.inc on line 874.
* warning: strtr() [function.strtr]: The second argument is not an array in /includes/common.inc on line 891.

Occured when updating an attribute.

CommentFileSizeAuthor
storm-error-screenshot.PNG9.06 KBMagnity

Comments

adam_b’s picture

I'm getting this also. Standard PHP5/MySQL5/Apache2 installation with everything up to date.

Magnity’s picture

Priority: Normal » Critical

Changing priority as per #435504: TODO BEFORE STORM 1.22

Magnity’s picture

Status: Active » Fixed

http://drupal.org/cvs?commit=199248

Removal of excess argument in t(), line 161.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Magnity’s picture

Component: Code » Storm.module
Status: Closed (fixed) » Active
Tabecka’s picture

I am having the same issue.
PHP5/Postgres/Apache2
I removed the t(), updated and i still have this issue.
No apparent conflicts with other modules.

Magnity’s picture

Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

Would it be possible to run a backtrace on the error using the Devel module? I cannot see this error on any of my installations anymore. Also, please could you confirm the version of Storm that you are using?

Magnity’s picture

Status: Postponed (maintainer needs more info) » Fixed

Assuming this is no longer an issue - please reopen if it is.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

bluecafe’s picture

I have removed the t() and everything seems to be ok but I am still having this issue if calling adminster by module: admin/by-module
Then I am getting

* warning: Invalid argument supplied for foreach() in /www/htdocs/w00ae2d7/templates/includes/common.inc on line 884.
* warning: strtr() [function.strtr]: The second argument is not an array in /www/htdocs/w00ae2d7/templates/includes/common.inc on line 901.

Magnity’s picture

@bluecafe - This problem could have been caused by a number of modules - so I would recommend that you use the Devel module to backtrace the error. If you get a Storm related function - then reopen this issue stating the function name.

bluecafe’s picture

Hi Magnity, I deactivated the storm modules one by one and after deactivating the module storm knowledgebase the error was gone. When I reactivated knowledgebase, the error was there again. Tried to locate the error using devel but don't know how (?)

bluescarni’s picture

Just for the record, I'm getting the same behaviour described by bluecafe.

Magnity’s picture

Status: Closed (fixed) » Active

Reactivating issue.

bluecafe’s picture

It's a great module, thanks for all the work you have put into it!

Magnity’s picture

Status: Active » Fixed

I'm pretty sure i've got this one now - on line 13 of stormknowledgebase.module, the t() should not have the second argument.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.