Closed (fixed)
Project:
Signup
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
18 Dec 2008 at 07:20 UTC
Updated:
3 Jan 2009 at 01:00 UTC
Jump to comment: Most recent file
Canceling signups is a destructive operation. Especially if the signup form has fields, you're losing data entered by the user. Now that #55168: tracking actual attendance is in, I can easily see situations where a site might want to empower a role to be able to record attendance at events, but not necessarily give them power to destroy signup data by canceling signups. So, it seems like splitting the cancel powers off of the usual "adminster signups" permission into a separate "cancel signups" perm.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 348559_cancel_signups_perm.1.patch | 3.84 KB | dww |
Comments
Comment #1
dwwThe final two hunks of this patch against includes/node_admin.inc might be overkill, but I figured in the land of tamperdata and the like, it can't hurt to be a little extra paranoid, and chx couldn't give me a straight answer on if this was needed or not. Better safe than sorry. ;)
Comment #2
dwwCommitted to HEAD and DRUPAL-6--1, along with a bunch of updates to the docs (UPGRADE.txt, INSTALL.txt, etc).