Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
27 Aug 2011 at 22:43 UTC
Updated:
10 Sep 2018 at 09:58 UTC
Jump to comment: Most recent
Comments
Comment #1
sreynen commentedI reviewed this module and found no problems.
Comment #2
tim.plunkettvariable_get() should take two parameters, since NULL isn't really valid in this case.
array(NULL) is redundant
List files[] in the .info only when they contain OO classes or interfaces, and never the .module file
Implements hook_help().No "of", always parentheses.Use single quotes unless needed, and be consistent. In one place you have single quotes with apostrophes escaped, other places you use double quotes.
"Provide to deny field access" is not a sentence.
Lines of documentation should end with a full stop, you're missing them on the lines below @param
Comment #3
misc commentedThe applicant has been contacted to ask if the application is abandoned.
Comment #4
misc commented@tulvit says that the application is not abandoned.
Comment #5
tulvit commentedSorry it took so long.
@tim.plunkett
Fixed.
Fixed.
Fixed.
Changed to "Provide ability to deny fields' access.".
Changed to
It seems like the only right option in this case.
Comment #6
rudiedirkx commentedWhy is this module better than Field Permissions? What does it add that FP doesn't?
Comment #7
tulvit commented@rudiedirkx
Thanks for the reply.
Now Field Permissions works just fine, but last summer it didn't, that's why I decided to write my own module (I can't remember what exactly those problems with FP were).
For now, the only two differences are:
- My module denies fields' access for all users, including user/1.
- This issue is still open.
But I think it's not enough to publish module with the same functionality. So, changed status to "close (duplicate)".
Comment #8
avpaderno