Closed (fixed)
Project:
Project
Version:
5.x-1.x-dev
Component:
Releases
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Dec 2006 at 02:24 UTC
Updated:
21 Mar 2008 at 17:52 UTC
Jump to comment: Most recent file
Comments
Comment #1
dwwi tried *very* hard for #1, and various drupal menu limitations, hook_access() behavior, and other woes made it impossible to get it right. :(
#2 is fairly reasonable in the short term.
but #3 would be even better: add another page to the N-page form. if you don't know the project, present page #0 to just select that. if you already know the project, skip to page #1 for the "start" of the release add wizard. very similar to creating a new issue.
/me waits for FAPI multi-step stuff to get more functional. ;)
Comment #2
hunmonk commentedlooks like #2 was implemented. postponing until we have a menu system that allows a more elegant solution.
Comment #3
dwwAs I wrote in (duplicate) http://drupal.org/node/199182 :
"Inspired and emboldened by what I learned over at http://drupal.org/node/199138 removing the evil multipage form for project_issues, we should do the same thing for release nodes.
Instead of converting the release node form into a true multipage form, all we need to do is stick a simple form directly at node/add/project-release with a project selector (restricted to the projects the current user has permission to create release nodes for), and then redirect to the full URL."
Comment #4
hunmonk commentedattached patch does it, i think. tested and seems to work perfectly. i'm *pretty* sure the menu access checks are right, but please check them for me :)
Comment #5
aclight commentedThe code looks good to me and the functionality works well. I checked this using test users with different permissions and only got redirected to the add a release page when I had the appropriate permissions.
Comment #6
hunmonk commentedcommitted to 5.x-1.x. setting back to active until this is deployed on d.o et. all.
Comment #7
dwwXSS on content type name:
Not *really* a big deal, but it's potential priv escalation and we don't do that. ;) You want '@' not '!' to be safe.
Comment #8
dwwCommitted to HEAD for 5.x-1.x.
Comment #9
hunmonk commentedfixed, deployed on d.o
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.