Hi,
I get this error when I try to submit an issue for a project:
warning: Invalid argument supplied for foreach() in E:\website\htdocs\modules\project\issue.inc on line 365.
Also, the "project" drop-down list doesn't contain any projects even thought I've just created a project.
Also, if I go to the "projects" menu item then it says there are no projects available. I can only access the newly created project by going to "my projects".
Here's the exact recepie for re-creating this problem:
1) Install the project module (no errors are created)
2) Create a new project (no errors are created)
3) Try to submit an issue for the new project.
I am using the latest project module code from CVS (downloaded today). I have tried installing project on two separate Drupal installations and I get exactly the same error on both installations. Both installations are made from the latest CVS Drupal code (i.e. a code base that's more mature than 4.7-beta3). The details of the two installs are:
Linux install
PHP 4.4.1
MySQL 4.1.14
Windows install
PHP 5.5.1
MySQL 4.1.16
I installed the project module by copying all the project files into modules/project, then I setup the MySQL tables, then I enabled the project module, then I enabled permissions for the project module, then I created the directory files/issues.
Many thanks,
Jack
Comments
Comment #1
dan_aka_jack commentedI just updated to today's copy of project.module from CVS but I'm afraid the problem remains.
Comment #2
dan_aka_jack commentedJust to be clear...
...I've marked this bug as "critical" because it breaks what I see as the most important part of the "project" module: the ability to report bugs and feature requests and I get this bug on two totally separate installations of Drupal-4.7-Beta3 so I'm pretty sure it's a real bug and not just me being useless.
And ideas at all would be a help.
Thanks,
Jack
Comment #3
dan_aka_jack commentedTypo...
...Ooops! I meant:
"Any ideas at all would be a help.
Thanks,
Jack"
Comment #4
nedjoDo your projects have releases? It sounds like the module is looking for projects and not finding them. Perhaps try turning off "browse by version" in project settings.
Comment #5
nedjoThis error seems to be a result of the Components field not saving correctly, see http://drupal.org/node/38120.
Comment #6
dan_aka_jack commentedHi,
Many thanks for your reply.
I tried both the things you mentioned but I'm afraid that didn't fix it.
Many thanks for the link to the "Components field doesn't save to database correctly" issue. Yes, you're right... I believe my issue is a product of the "Components field doesn't save to database correctly" bug.
Many thanks,
Jack