I am unable to create issues for projects. I have created several projects and can not access them to create issues. In fact the projects do not show up in the "Project navigation (drop-down select)" block unless i "rebuild permissions". but as soon as i clear the cache or the cache clears on its own the projects are gone from the "Project navigation (drop-down select)" block. As for the "Project navigation (text field)" block they never show up. they also never show up in "Issues for all projects" or "Search issues for all projects".
The projects do show up if i access them via the http://kb1pro.com/project/projects/sapb1.
i do not have any node role modules installed.
I have tried single and multiple "Project categories" so that there is a "Project Type:" and a "projects categories:"
Nothing seems to work and can not find any info on the problem.
Thank you,
Comments
Comment #1
joseph.guagenti@kb1pro.com commentedI have tried this on 6.x-1.0-alpha4 and on 6.x-1.x-dev. I am having the same problem on both versions.
I am unable to create issues for projects. I have created several projects and can not access them to create issues. In fact the projects do not show up in the "Project navigation (drop-down select)" block unless i "rebuild permissions". but as soon as i clear the cache or the cache clears on its own the projects are gone from the "Project navigation (drop-down select)" block. As for the "Project navigation (text field)" block they never show up. they also never show up in "Issues for all projects" or "Search issues for all projects".
The projects do show up if i access them via the http://kb1pro.com/project/projects/sapb1.
i do not have any node role modules installed.
I have tried single and multiple "Project categories" so that there is a "Project Type:" and a "projects categories:"
Nothing seems to work and can not find any info on the problem.
Thank you,
Comment #2
mikey_p commentedIt sounds like you're using some kind of node access module, or the 'rebuild permissions' option wouldn't have any effect on the content visibility, could you post a list of all the modules that you are using?
Comment #3
joseph.guagenti@kb1pro.com commentedmikey_p
I was not using any node access module. I have since tried using one (og) but still having the same issue. this is making me goofy(er).
"Project navigation (drop-down select)" block works but the "Project navigation (text field)" block never works.
i have access to
http://kb1pro.com/project/issues
http://kb1pro.com/project/issues/search
http://kb1pro.com/project/issues/user
http://kb1pro.com/project/issues/statistics
i can also see the projects
http://kb1pro.com/project/projects/sapb1
and
http://kb1pro.com/project/b1ubercart
http://kb1pro.com/project/b1sugarcrm
I have also enabled Node_access_summary on the site and here is the output for my account when accessing the create content issue.
username create view update delete
xx.xx YES: administer nodes YES: administer nodes YES: administer nodes YES: administer nodes
the error is still
You do not have access to any projects.
Any ideas are welcome
Comment #4
Anonymous (not verified) commentedSame error for me.
Super Administrator can't even create an issue.
Comment #5
Anonymous (not verified) commentedI've done some investigations and found that the error message is displayed where no project is found. In my case website is multilingual and I've created a first project having "language neutral" as language configuration. No project were found because SQL request was looking for project with language set as fr. I then changed the project language to fr and now it works.
In others words I had this problem due to multilingual configuration.
Comment #6
izkreny commentedI had this error too.
Easy way to reproduce it:
1) Fresh install (project, project_issue, comment_upload)
2) Create one test project and create one (or more) test issues
3) Go to list of vocabularies (/admin/content/taxonomy/list) and add at least one term to "Project types" vocabulary (important: there was none terms before!!!)
4) Try to create issue -> Error! :(
Solution (kind of workaround):
1) Go to your test project and edit it
2) Add / assing at least one (created) term to your test project
3) Try again to create issue -> no more error. ;)
Hope this will help..cheers..
Comment #7
develcuy commentedI confirm #6, worked like a charm :)
Comment #8
alberto56 commentedNote that this can also happen if you have converted a node from another node type to a project node type using node_convert.
The issue system seems to only recognize projects which were actually created from scratch.