Maybe someone out there have a better understandable explanation.
/Joe
]]>Is it safe to assume you verify the contributed extensions have unique numbers before posting them on the website?
If I create a new extension from an existing one and forget to change the number, we could have two with the same number.
tom
]]>Maybe set a range for local use and any others need to be allocated by the core development team?
tom
]]>Janusz
]]>barney
]]>barney
]]>5. Example access control configuration file
--------------------------------------------
This is content of sample access control file for CRM extension module:
<?php
/*
Define security section codes
*/
define('SS_CRM_C', 101<<8);
define('SS_CRM', 102<<8);
define('SS_CRM_A', 103<<8);
/*
Additional security sections for CRM module
*/
$security_sections[SS_CRM_C] = _("CRM configuration");
$security_sections[SS_CRM] = _("CRM transactions");
$security_sections[SS_CRM_A] = _("CRM analytics");
/*
Additional security areas for CRM module
*/
$security_areas['SA_CRMSETUP'] = array(SS_CRM_C|1, _("CRM module setup"));
$security_areas['SA_CRMCONTACTENTRY'] = array(SS_CRM|1, _("Customer contact entry"));
$security_areas['SA_CRMANALYITCS'] = array(SS_CRM|1, _("Pre-sale contact analytics"));
?>
The exact values used for security section codes are not very important,
as they are rewritten by access control system during integration of
access extensions. Therefore numeric values of security sections/areas should
never be used directly in the extensions source. Use string representations
instead when needed, or values retrieved from $security_areas array.The exact values used for security section codes are not very important,
as they are rewritten by access control system during integration of
access extensions.
Though I never try to confirm this.
]]>I think a more important question is: Does the 105 have to be unique across all add-on modules?
Are we granted security permissions based upon that bit mask?
If two modules have the same SS_ value won't they be controlled together in the security settings?
Tom
]]>kuro
]]>thanks a lot,
barney
]]>define('SS_ASSETREGISTER', 101<<8);What I realize is that every time there is that, there is this:
function install_access()
{
$security_sections[SS_ASSETREGISTER] = _("Asset Register");
$security_areas['SA_ASSETTYPE'] = array(SS_ASSETREGISTER|1, _("Asset Type Entries"));
$security_areas['SA_ASSETS'] = array(SS_ASSETREGISTER|2, _("Assets Entries"));
$security_areas['SA_AMORTISATION'] = array(SS_ASSETREGISTER|3, _("Amortisation Posting"));
return array($security_areas, $security_sections);
}(source taken from asset_register extension)
So I conclude that prefix SS_ means Security Section, the "define" statement above is used to define some kind of unique security level identifier, and that this defined constant will be used to define the security areas used by the extension.
Hope that helps.
]]>Maybe someone out there have a better understandable explanation.
/Joe
]]>Could you tell me, what is the meaning of '105<<8' in 'define ('SS_IMPORTCUSTOMERS', 105<<8);' .
Or is some kind of description available?
Bernd
]]>/Joe
]]>