439
edits
Module CustomFields Dev: Difference between revisions
Jump to navigation
Jump to search
→Preliminary test: Adding another case
(→Preliminary test: Adding another case) |
|||
| Line 134: | Line 134: | ||
* If there is no '''$user->rights''': there is either no standard security implemented in this module, or either the variable is called with another name. If there is no security, you don't need to configure it in CustomFields, but if there is a security, you need to find how the variable is called (like $object can get another name sometimes). | * If there is no '''$user->rights''': there is either no standard security implemented in this module, or either the variable is called with another name. If there is no security, you don't need to configure it in CustomFields, but if there is a security, you need to find how the variable is called (like $object can get another name sometimes). | ||
* If there is '''$user->rights''' but the module can't be found in the list: either the name for the rights is different (this often happens, the rights array is not yet standardized), or either the rights are hardcoded into the module's code (rights should be announced to the $user->rights array, but sometimes it happens that the dev forgot to do so, and thus the right is entirely hardcoded and you can't find it in the dynamic rights array). In any of these two cases, you will have to manually read the module's code to find the right. Also, maybe there is no security implemented, but since $user->rights is declared this is less probable. | |||
When you are finished with implementing the support of CustomFields in the module, you should delete these debug lines. | When you are finished with implementing the support of CustomFields in the module, you should delete these debug lines. | ||