Posted by dalin on July 20, 2011 at 6:17am
5 followers
| Project: | Signup |
| Version: | 7.x-1.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
| Issue tags: | Usability |
Issue Summary
Signups don't really have anything to do with content, or anything else in the content menu (nodes/comments/media). And since the settings form is under admin/config/people, it would be a better admin experience if the signups were moved under admin/people.
Comments
#1
patch attached.
#2
#3
Sounds fair. Can you post before/after screenshots? Would help review this.
#4
I'm assuming you know what the before state looks like. Here's shots of the after.
#5
Well, I'd have to install the module first, that's why we ask for after *and* before screenies :)
#6
I'm totally confused. How can you comment on an issue for a module that you've never installed before?
#7
Because you're only suggesting a change in information architecture (where), not functionality (what). I know what Signup module does in general.
Either way, this change makes total sense, I'd say go ahead.
#8
I agree that this menu item is on the wrong place. The patch in #1 applies fine and fixes the issue.
#9
Committed, thanks!
#10
I dont agree they are two different things one is for viewing signups and the other is for managing the signup (content) node.
Also there is no way that I've found where you can manage the limit for each event outside for the default/catch all method via the admin/configuration/signup page. If you need a more granular approach you need either :
1) a full list of all the signup nodes with access to manage the event limit
2) or add the limit functionality to the content editing page, not sure what the area is called but its the area where the menu settings, comment setting etc are.
3) or make it a field that can be used when building a content type.
#11
Automatically closed -- issue fixed for 2 weeks with no activity.