Submit issues cannot find projects

i doubt this is a criticial bug, since this code all works fine on drupal.org.

did you create any projects?
did you set the access control properly? (i.e. grant the respective users 'access projects' permissions, etc)

thanks for including the version numbers, but can you provide more info about the steps you took to set things up, what you tried, and what you're seeing?

thanks,
-derek

Same here.

Installed from scratch, made projects, but project_issue doesn't have anything in the 'project' dropdown when attempting to add issues

i just tried (again) on a totally clean 4.7.x test site. indeed, things are broken if you use 4.7.x-2.1 in quite a few ways. that's why 4.7.x-2.3 is the current download. ;)

with 4.7.x-2.3, i can't reproduce any of these bugs on a clean site.

4.7.6 core
4.7.x-2.3 project
4.7.x-2.3 project_issue
no other contribs
install as usual
assign "access projects" and "create project issues" permissions to the "authenticated user" role
create a project (as uid 1, or just give "maintain projects" permissions to auth user and do it as another user).
create an issue (the project drop-down works here, for both uid 1, and other, non-admin users).

solution: use the latest official releases, and everything should be fine. therefore, i'm marking this closed. only re-open if you a) are using the current official release and b) you provide a similar list of steps you took, exactly what non-core modules you have installed, etc.

thanks,
-derek

A few different people report this is still a bug in 5.x over at http://drupal.org/node/134159 (now marked duplicate).

However, I think the real problem is what's described here: http://drupal.org/node/145452

Did you all create the project nodes before you enabled project_issue module? If so, I think that would describe the problem, given the bug report at #145452.

correct me if i'm wrong, but can't we simply check on module install for node type 'project_project', and copy the relevant data into the {project_issue_projects} table?

attached checks the {project_issue_projects} table for missing project nids anytime the module is installed fresh, or anytime it's already been installed and is being re-enabled. tested on postgres in both situations, and it works perfectly -- projects added w/o project_issue installed/enabled are correctly discovered and added.

better naming conventions.

Tested on MySQL -- works great. Reviewed: can't find any problems. ;) Please commit to all branches.

fixed in HEAD. since 4.7 doesn't include a hook_enable(), i'm leaving this issue as 'to be ported', in case somebody wants to come along and use some fancy form_alter magic to take care of the disable/enable case.

What Must I do with this file?

project_issue_new_projects.patch 1.44 KB

Please don't change the version number, since this issue has been fixed in the 5.x series and still needs to be ported for the 4.7.x-2.x branch. The most recent official release in the 5.x-1.x branch (5.x-1.3) should not have this problem. If that's not the version you're running on your site, you may need to upgrade your project issue module or apply the patch from comment #7 to whatever version you are using. For information on patches, see http://drupal.org/patch/apply

Since we're no longer supporting the 4.7.x version of project issue, I'm setting this to closed.