After installation of the current dev release the following PHP warnings are displayed when the Storm page is navigated to:

Warning: scandir(sites/all/modules/storm/icons) [<a href='function.scandir'>function.scandir</a>]: >failed to open dir: No such file or directory in scandir() (line 1230 of /var/www/html/cm7/sites/all/modules/pm/storm.module). => 

Warning: scandir() [<a href='function.scandir'>function.scandir</a>]: (errno 0): Success in scandir() (line 1230 of /var/www/html/cm7/sites/all/modules/pm/storm.module). => 

Warning: Invalid argument supplied for foreach() in storm_icon_recache() (line 1231 of /var/www/html/cm7/sites/all/modules/pm/storm.module). => 

Before installing "PM" module I fully deinstalled all Storm modules, deleted the storm directory and cleared all caches. Are there still references into the storm module directory?

Comments

GStegemann’s picture

Found the reason for this: the "wrong" path was taken from the Storm configuration. I changed the icon folder to the new locationm and the warnings are gone.

GStegemann’s picture

Status: Active » Fixed
juliangb’s picture

@GStegemann, I'm keen for others to avoid these errors.

Do you remember what path was shown, and what you changed it to in order to fix the problem?

juliangb’s picture

Status: Fixed » Active

Reopening to see if there are changes we can make to fix this.

GStegemann’s picture

Yes. It was "sites/all/modules/storm/icons".

juliangb’s picture

Title: scandir(sites/all/modules/storm/icons) failed to open dir » Migration: Refresh icons location
Project: Drupal PM (Project Management) » Storm Project Management
Component: Code » Storm.module

I see - this is due to the renaming to pm.

I assume you had previously been tried the module when we had it in the Storm module.

I will move this issue back to the Storm project, as there will be a module to assist in migration there, and this would be a useful thing to fix.

juliangb’s picture

Status: Active » Fixed

Done in new module committed to Storm 7.x-1.x branch.

Please follow instructions in the README.txt carefully when testing.

Status: Fixed » Closed (fixed)

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