Closed (fixed)
Project:
Project Issue File Review
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
9 Jan 2010 at 00:04 UTC
Updated:
13 Feb 2010 at 00:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
jhodgdonTo be consistent with other perms in Drupal, shouldn't it be "Administer PIFR"?
Comment #2
boombatower commentedYea, that makes sense.
Comment #3
jhodgdonIt looks like some of the other permissions in that module are more similar to your previous permission name?
From the patch:
Hmmm. I guess those are in a different module?
Comment #4
boombatower commentedThat is in the test "pifr_server.test".
Comment #5
jhodgdonYes, but presumably those are other permmissions that the test is using, that come from PIFR or a related module? I'm just saying that those other permissions are using the format "pifr whatever" rather than "whatever pifr". Also, I think most permissions don't abbreviate the module name, so it would be even better to be "administer project issue file review".
But it's your module. :)
Comment #6
boombatower commentedUpdate the rest of the permissions the same way, and provided update path.
Comment #7
boombatower commentedI think for now I'll stick with abbreviation like code user pifr.module, pifr_server.module. At somepoint I'm thinking about renaming.
Comment #8
boombatower commentedCopy-paste fail, pifr_update_6204 in pifr_server.install should be pifr_server_update_6204().
Comment #9
boombatower commentedCommitted.