When changing the label of a field, all corresponding permissions are being dropped.
This kind of update is not understood as reason to check access permissions again and fields got hidden accidentally...
Why not use the field naming for permission dataset?
This is a major issue in productivity. I see no reason to use Label in this context and therefore file this as a bugreport (due to loss of information in case of a minor update).
Thanks for your opinion.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | cck_field_perms.module.gz | 3.24 KB | halstead |
| #1 | cck_field_perms.patch | 2.69 KB | halstead |
Comments
Comment #1
halstead commentedThis fixes the issue by storing the field_name in the permissions table and form_altering the access page to display the field label.
Comment #2
webchickConfirmed that this patch fixed the problem for me.
To reproduce, I created a text field called "Moose" and assigned view permissions to authenticated users. Before the patch, renaming this field to "Moosesd87s8sd45" caused the checkbox at admin/user/access to clear. After the patch, on subsequent rename, it stayed checked. :)
Comment #3
webchickAlso, I would call this critical. Taking away your permissions you worked so hard to setup is not nice.
Comment #4
halstead commentedHere is a pre-patched module file for people not familiar with CVS and patch.
(The patch above was done against CVS. This module file is the version in the 5.x-1.10 download.)
Comment #5
webchickOops. I'm pretty sure halstead didn't mean to reset the status here, so switching it back.
Comment #6
halstead commentedThis is in 5.x-1.x-dev which should appear soon.
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.