Closed (fixed)
Project:
Acquia Marina
Version:
6.x-3.0-alpha1
Component:
Miscellaneous
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Dec 2009 at 09:25 UTC
Updated:
15 Jan 2010 at 07:50 UTC
This morning I have adjourned the theme to the new version 3 alpha and they have appeared the following errors:
# warning: Invalid argument supplied for foreach() in /home/hopfrog/public_html/sites/all/modules/skinr/skinr.module on line 297.
# warning: Invalid argument supplied for foreach() in /home/hopfrog/public_html/sites/all/modules/skinr/skinr.module on line 309.I have eliminated and then installed again skinr without any result
I have changed the theme from Acquia to Fusion and the problems they have disappeared therefore I think that the problems depend on Acquia and not from skirn.
Comments
Comment #1
sociotech commentedhopfrog,
Did you get apply this patch: http://drupal.org/node/648816#comment-2345038 or use the most recent revision of Skinr from CVS (which includes the patch)?
That patch should fix the issue. Post back here whether or not it works.
Comment #2
enzo de simone commentedOK. It's work
Thanks
Comment #3
enzo de simone commentedAnd instead doesn't work! When I am administrator the errors they disappear but as user (anonymous or recorded) all the errors reappear. I leave selected the theme so that the errors can be seen: http://www.hopfrog.it
Comment #4
jwolf commentedDisable caching via the Performance section in Drupal admin land
Comment #5
sociotech commentedhopfrog,
If disabling/clearing cache doesn't work, it may require clearing out the variable data entry for Skinr in your database. Depending on your familiarity with phpmyadmin, I can walk you through that. Unfortunately, it looks like Skinr doesn't implement uninstallation, which would also clear the variable data.
In the meantime, of course, you can set your error reporting to send errors to the log only in order to prevent the warnings from showing on the screen.
I'll also look more into what is causing this.
Comment #6
enzo de simone commentedI have cancelled the voices related to Skinr created in the database. The errors are disappeared and all work fine. Thanks
Comment #7
sociotech commentedIt looks like the latest version of Skinr from cvs has improvements to both eliminate this issue by not saving empty values and to correct it by exporting, editing, and then importing your Skinr settings:
http://drupal.org/node/648816#comment-2418792