History: Cookie Consent
Source of version: 5
Copy to clipboard
! Cookie Consent New in ((Tiki10)), to comply with "EU Privacy and Electronic Communications Regulations." To allow a site to comply with the European regulation that a user must give positive (not passive) informed consent before a web site loads cookies onto their accessing device (PC, phone etc) a new optional Cookie Consent feature has been added to the Login set of admin screens. When set 'on' this enables the prevention of any cookies (except the session cookie) from being set and also lets the following be defined: - the name of a new cookie that is loaded when consent has been given - the duration of the consent cookie - various parameters so that warning text and 'consent giving' dialogue can be displayed, and - an Id can be defined so that the dialogue can be styled as required using css The session cookie can be prevented for Anonymous users by configuiring the 'Silent session' option in the 'Sessions' section of the 'Performance' admin screen - but as this means users will only have a session if they log in, this also means that anonymous users will lose the capacity to have things like Switch Language, since a session is needed for this. You therefore need to decide whether this additional cookie suppression make sesne for you. It should be noted however that some actions by admins and users with edit permissions can bypass the cookie prevention e.g. setting Google Analytics or some social media functions with plugins, etc.; so admin/editor user education is required. If some action like using Google Analytics is set by an admin in (say) the 'Customization' section of the 'Look & Feel' admin screen, then a check on the state of the custom consent cookie should be added as a wrap around the code used, like this: ~np~{if $smarty.cookies.your_custom_cookie_consent_name eq 'y'} ~/np~ your code that might set a cookie ~np~{/if} ~/np~ For any editor that might use some code in a Wiki page etc., that could set a cookie then they need to use a new 'wrap around' plugin called COOKIECONSENT which will prevent anything in the body of this new plugin from being executed if the user has not set the consent cookie eg ~np~{COOKIECONSENT()}~/np~ any content that could set a cookie ~np~{CONSENTCOOKIE}~/np~