Add permission to mod - explain

[Jotade29]

Hi.

I have a question about how adding permissions to a mod works...

To explain my doubt, i am going to take the glossary mod as an example (https://custom.simplemachines.org/index.php?mod=1525;sa=parse)

According to the code in the mod, it has been added to managepermission.php...

Code Select Expand

'view_glossary' => array(false, 'glossary', 'view_basic_info'),
'admin_glossary' => array(false, 'glossary', 'administrate'),
'suggest_glossary' => array(false, 'glossary', 'view_basic_info'),
I understand that this is where the permission is created, but i don't understand how it works, for example with 'view glossary' what does the false, 'glossary' and 'view_basic_info' refer to? Also, nowhere do i see mention of the permission text, and yet it shows its name, in this case it would be $txt['permissionname_view_glossary'] = 'See glossary';

Thank you so much.

[Jotade29]

Pls, any know? 

[Doug Heffernan]

for example with 'view glossary' what does the false, 'glossary' and 'view_basic_info' refer to?

False in this case means that said permission doesn't have multiple options. Whereas view_basic_info is the permission group/area where the aforementioned permission is added to by the mod.

Also, nowhere do i see mention of the permission text, and yet it shows its name, in this case it would be $txt['permissionname_view_glossary'] = 'See glossary';

This is handled/defined in the language file of the mod. Hope it helps.

[Jotade29]

for example with 'view glossary' what does the false, 'glossary' and 'view_basic_info' refer to?

False in this case means that said permission doesn't have multiple options. Whereas view_basic_info is the permission group/area where the aforementioned permission is added to by the mod.

Also, nowhere do i see mention of the permission text, and yet it shows its name, in this case it would be $txt['permissionname_view_glossary'] = 'See glossary';

This is handled/defined in the language file of the mod. Hope it helps.

Thnx for yur answer, Doug!!

I think i understand, thank you very much for the explanation. However, there is one thing ii can't understand. In the case of the example, what's the point of putting 'glossary'? That is: 'view_glossary' => array(false, 'glossary', 'view_basic_info'). With 'view_basic_info' I add it to the forum's basic permissions category, but is the 'glossary' after 'false' to mention the permission category?

I wud also like you to tell me about the txt issue of permissions. Do they have to mention the managepermission or do they simply have to follow the txt format in the forum language files $txt['permissionname_view_glossary'] ;$txt['permissionhelp_view_glossary']?

Thank you

[Jotade29]

for example with 'view glossary' what does the false, 'glossary' and 'view_basic_info' refer to?

False in this case means that said permission doesn't have multiple options. Whereas view_basic_info is the permission group/area where the aforementioned permission is added to by the mod.

Also, nowhere do i see mention of the permission text, and yet it shows its name, in this case it would be $txt['permissionname_view_glossary'] = 'See glossary';

This is handled/defined in the language file of the mod. Hope it helps.

Another question, and sorry for the double post, but it won't let me modify it. To check the permission with isallowedto, do we need to put it only in the code of the source that we want to check, or do we also have to put it in the template?

[Arantor]

Following the structure of the language string is enough - it's what the rest of SMF does.

As for allowedTo/isAllowedTo checks, they should only be in sources. (The difference is that allowedTo returns true/false so you can show/hide options etc., while isAllowedTo pushes the user to an error page if not allowed)

[Steve]

As @Jotade29 has been here 12 days after his last post in this topic without further input, I'm assuming this is resolved and marking it so.