The European Court of Justice (ECJ) has ruled that cookie banners, which do not expressly require the consent of the website visitor, are not lawful under the DSGVO. To make it easier for TYPO3 developers to implement this new requirement, we have developed the sgalinski Cookie Opt-In, an easy-to-integrate module that enables embedding for cookies and tracking scripts that is compliant with GDPR (DSGVO) and ePrivacy. You can find further information in the german blog article from Dr. Schwenke.
| TYPO3 Versions | 8.7.X | 9.5.X | 10.4.X | 11.5.X TYPO3 versions 6 and 7, are supported up to version 3 of our product. |
| PHP Versions | 7.0.X | 7.1.X | 7.2.X | 7.3.X | 7.4.X | 8.0.X |
| Tested Browsers | Internet Explorer 11 and Evergreen Browsers |
We are looking forward to support you with the integration of our Cookie Opt-In Extension into your TYPO3 instance. Just contact us with your support request! – Everyone else who integrates and configures our Cookie Consent Tool on their own will find a Cookie Opt-In documentation on this page as support.
Cookies may be loaded due to the DSGVO (GDPR) and the ePrivacy regulation only if the respective side visitor agrees this expressly (cookie consent). This also eliminates the need for opt-out solutions in which the user must actively object in order to no longer receive cookies. For this reason, the sgalinski Cookie Consent only embeds cookies that you define as essential.
Non-essential cookies are sorted into any number of groups in the supplied backend module of the extension. These cookies are listed transparently and clearly to the visitors of your site with information such as origin, description and duration. The user can then decide which cookie groups he wants to accept and which cookies should not be loaded.
You install the extension via Composer or the TER and include it with a few lines of TypoScript in your instance. Thanks to the clearly arranged backend module and an intelligent pre-configuration, your cookie opt-in banner is ready for use with just a few clicks. Any tracking scripts can also be added in no time at all, but will only be loaded once the user has agreed to it.
In the backend module of the cookie consent extension, the color design of the cookie pop-up can be configured so that the banner integrates seamlessly into the frontend of your website. This gives you full control over the appearance of the cookie opt-in hint.
The cookie banner of the TYPO3 extension can be translated into any number of different languages and is played out accordingly on each language of your website.
In addition, different cookie groups can be configured for different language versions of your website. This ensures transparent, flexible data protection for all users.
You can insert any scripts in the settings of the sgalinski Cookie OptIn. They will be loaded as soon as the user has agreed. We have taken special care to ensure that no tracking information is lost through the OptIn consent.
Sgalinski Cookie OptIn for TYPO3 is the simplest solution to play out tracking scripts and tags as well as cookies in compliance with data protection laws. With the clear opt-in banner you create trust and transparency with your users.
The backend module helps you to quickly divide all your cookies, tags and scripts into groups that users can freely accept. Thanks to our licensing model, you will receive all updates for sgalinski Cookie OptIn as soon as they are available.
Our TYPO3-based website base is a comprehensive package for creating and managing websites of all kinds. The sgalinski Cookie Consent extension is contained in the Website-Base. Basically there is the option to create a Website at a fixed Price or to choose a Website as a Service package, which does not incur any additional costs for hosting or security and function updates. All information about the available editions of the Website-Base can be found on the pages linked below.
After the successful installation and configuration of the sgalinski Cookie Consent Extension, each new visitor to your website will be shown a window with the cookie consent. The user decides which cookies he chooses to allow and which not.
The following cookie groups are visible in the cookie banner (essential cookies are always accepted as they are important for the function of a website):
The user can save the individual selection or accept 'only essential cookies' or 'all cookies' with just one click. If a site visitor closes the window without making a selection, only essential cookies are automatically loaded.
You also have the possibility to integrate the Cookie Consent into a page after configuration by inserting the corresponding content element.
The Tracking / Cookies module is organized into three functional areas:
By default, you enter the Settings functional area as soon as you select the module Tracking / Cookies. To switch between the functional areas, simply click in the box above the content area where 'Settings' can be seen. In the drop-down menu you can see all three functional areas, then click on the one you need.
In the statistics you can see how many people have accepted or rejected your cookies. You can filter the results by the time period or by the version number. The module shows you pie charts for the different groups and represents how big the percentages of people are who have accepted or rejected the respective group. The essential cookie group is always 100% accepted, which is why it does not appear in the statistics.
If you filter by the version number, you will see only the data for the specific version. This allows you to compare different versions with each other. You can draw conclusions from this as to whether certain changes have contributed to more visitors accepting non-essential groups.
If visitors complain that they have received cookies to which they have not consented, this can be checked in Consent Management. There you can access the OptIn logs and check whether unwanted cookies were actually played.
For this purpose, visitors receive a user hash, which they can find at the bottom of the cookie banners. In Consent Management, the user hashes are listed and it shows when which cookie groups were accepted or rejected. A new user hash is assigned when browser data has been deleted.
The list can be filtered by user hash, time period or the cookie groups.
Starting with TYPO3 9. we have implemented a handy export and import function for agencies or customers who have multiple TYPO3 instances with our Cookie Opt-In Extension. It allows to configure the cookie consent once and to transfer all settings to further instances.
When importing, you must ensure that at least the default language is present in the exported file, or that the original configuration contains the main language of the page into which the file is to be imported. If other languages do not match completely, this is not a problem. If there are too many languages in the file, they will simply not be included in the new instance. In the opposite case, if languages (other than the default language) are missing, you just need to add a new translation for the cookie opt-in in this instance.
You will be informed during the import process if the default language is missing or if the number of cookies and scripts does not match in the translations. The latter can lead to the translations not being adapted correctly. Problems that occur as a result can be fixed afterwards.
Proceed as follows when exporting & importing:
If you have already created an entry in this instance, you must delete it in order to use the imported configurations. To delete an entry, go to the Tracking / Cookies module and use the Paper Bin icon to remove the entry you don't need.
The TYPO3 extension can be easily obtained from the TER or installed via Composer. To install the extension with Composer, you need to execute composer require sgalinski/sg-cookie-optin. In both cases, the extension must then be added using the Template module and configured via the Tracking / Cookies module. Both steps are described below.
For the integration to work smoothly, you need to configure a so-called siteroot. You can see if you have already configured a siteroot for your website by the small globe icon next to the name of the page in the page tree. If you don't see a globe there, the checkbox has not been activated yet.
To configure a siteroot, open the properties of the desired page in the backend via right-click -> Edit and activate the checkbox "Use as root page", which can be found in the tab "Behaviour".
After the installation you have to add the static TypoScript named Cookie Opt-In to your instance. To do this, proceed as follows:
Should your TYPO3 installation be located in a subdirectory e.g. www.example.com/subdirectory, you should adjust the value general.folder in your extension settings in the TYPO3 backend.
In the technical documentation for our Cookie OptIn Extension, developers in particular will find further useful information on the installation of our TYPO3 Cookie Extension.
Before you set up your Cookie Opt-In Extension in the backend, you should check your website for cookies. To do this, use the following tool, which is best opened in a new tab or window.
As shown below, enter your homepage address and confirm your entry with Scan Now.
In addition to the tool, you also have the possibility to manually check your page for cookies. To do this, follow these instructions.
The result is a clearly arranged table, as shown below. This table contains most of the information required for configuring the extension. The section on the group of essential scripts & cookies describes which data you have to enter where.
Note that this list may not be complete.
Furthermore, it is not enough to check only the Website URL for cookies. It is important that the other main and sub pages of the website are also scanned.
Only if all cookies and tracking scripts are loaded exclusively via the Cookie Opt-In/Consent Extension is it possible to create a GDPR-compliant website. If this is the case, the tool will not be able to deliver any results after the complete configuration when re-examined. In this case you will receive the message: No Cookies Found. You must insert cookies and scripts into our Cookie Consent until the tool cannot find cookies on any of your pages.
Before you start editing the Cookie Consent, you should activate the test mode in the Settings tab! - This way, no Cookie OptIn window will be displayed to the page visitors during the editing process. However, you can always display the Cookie OptIn dialog with ?showOptin=1 at the end of the address bar in the frontend to check appearance and functionality.
If you have made critical changes and want to ensure that visitors have to accept cookie groups again, even if they have already accepted them, enter a higher version number at this point and place a check mark before saving your changes. When the form reloads, you should see your current version number in the box on the right.
You can then track the preferences of visitors in the statistics.
You can see in the figures below which fields will be visible at which positions in the frontend. Fill in the fields Title of Opt-In Window to Link to Display Information of a Cookie Group.
Fill in the cookie information text fields. All cookies used are broken down according to these four pieces of information. Here you only specify the label.
In the last step you link the imprint and the privacy policy declaration. Proceed as follows:
IMPORTANT On the page of your privacy policy you should also add a button or link to the cookie settings OR insert the Cookie Consent content element in the data protection declaration.
If you decide to use the button/link variant, the user must access the cookie settings with a click on the button. To do this, you create an external link with the URL of your privacy policy additionally with the parameter ?showOptIn=1. The link on our site looks like this: sgalinski.de/datenschutz/?showOptIn=1. If a user has already decided which cookies he wants to load and at a later point in time reaches a page with the parameter ?showOptIn=1, the checkboxes he selected will be displayed again.
In the first part of the Template tab, you first choose between two basic design templates. In our example, this is the comprehensive variant. You also can choose the compact design.
Alternatively, you can check the box Overwrite Template and adapt the template to your requirements.
The template can be displayed in the frontend at any time by clicking on the Template Preview button (below the template code). In a new tab you will then see your website with the current design of the Cookie Content.
When the template is selected, the colors of the individual components are adjusted. First you define the colors of the upper area and the heading as well as the text.
The template can be customized for each language. To apply a different template in a translated language, you need to select the corresponding language and choose the custom translation behavior in the Template tab. Then customize the template according to your needs. In order for the changes to be applied, you also need to enable the Overwrite Template option (as in the default language).
This is followed by the colors of the window where most of the content is shown.
The group checkboxes are located in our basic template to the left of the cookie group name. Essential cookies and scripts can get a different color than all other groups.
For each button in the Cookie-Opt-In you have the possibility to change the background, the button-hover (mouseover effect to show an available interaction) and the text color.
Finally, you can adjust the colors of the group details list and the cookie description tables.
To activate the Cookie Consent for Iframes, simply check the box in the External Content tab and fill in the Title or Description fields and specify the text for the button labels.
Similar to essential cookies you can specify all cookies coming from external scripts under the field Description. The information can be seen in the cookie information part of the Opt-In field in the frontend.
In the Text fields you define the button labels for external content. Furthermore, you can assign an additional text under the button to load the external content (see screenshot below).
The column Colors is located under the column Texts (button labels). Here you can adjust the color of the box and the buttons.
It is also possible to adjust or change the design templates directly in the backend.
To do so, set a checkmark at Override Template of the Settings Window to rework the code for the design for the settings of external content and checkmark at Override iFrame Replacement Template to change the template that is displayed instead of the iFrame.
Overwritten code will not automatically apply future updates. If the option is deactivated again, the template is reset.
If your website requires certain external content for its functionality or for other reasons, content may be loaded without the prior consent of the user. For this purpose, the extension has a whitelisting function. The list automatically contains reCAPTCHA, a service that allows to distinguish between humans and bots. If you set a checkmark at overwrite template, you can add further exceptions. The external content (iFrame, objects, audio and video HTML tags) are then excluded from external protection.
Each content element can be individually protected as external content. This can be useful, for example, if the external content was added by a complex JavaScript or if the content itself represents only a small part of a large block containing text headers, controls, etc. It may then be more convenient for you to mark the entire block as protected. There are three ways to mark a content element as an external element.
Add the attribute data-external-content-protection to the HTML tag.
<div class="test-content-protection" data-external-content-protection="1">
This content would have not been protected
<iframe src=”some/external/page” />
</div>
Or enter the class frame-external-content-protection in the HTML tag.
<div class="test-content-protection frame-external-content-protection">
Content comes here
</div>
It may happen that you do not want to protect individual external content. This may be necessary, for example, if the function of your website depends on the external content, if iFrames of whitelist domains belonging to your company are involved or if the external content does not contain cookies. You should therefore always ensure that your website remains GDPR-compliant.
There are three ways to load a content element that would not automatically appear on the page as an external element without the user's consent.
Add an attribute data-iframe-allow-always or data-external-content-no-protection to the HTML tag.
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/XYZ" data-iframe-allow-always="1">
</iframe>
Or enter the class frame-external-content-protection in the HTML tag.
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/XYZ" class="frame-external-content-no-protection">
</iframe>
Just add the data attribute data-consent-button-text to an iframe HTML tag, like in the example below.
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/XYZ" data-consent-button-text="Custom text here"></iframe>
You can insert a description to the external content. To do so, you need to add a corresponding attribute to the HTML code of the iFrame: data-consent-description. The iFrame tag in the HTML content element may then look like this:
<iframe
width="560" height="315"
src="https://www.youtube-nocookie.com/XYZ" allowfullscreen
data-consent-description="Some additional description"
data-iframe-allow-always="1">
</iframe>When a user does not accept external content, Iframes are not loaded and are displayed as a box. The visitor now has the option to load only one iframe. When clicking on the Open settings button, a small Cookie Consent window appears (see screenshot below), where all external content or only one iframe can be accepted.
If you check the box for the less noticeable banner in this column, only a small banner will be displayed instead of the detailed variant. However, you can also set a certain width of the browser window up to which the small banner will be displayed, otherwise the large, detailed banner will be visible. Even if the user does not click on Accept, the website remains fully functional. You can set the position of the banner at the bottom or top. In our example the banner is at the bottom. Even in this form of cookie content, a text is intended to inform the site visitor about cookies. You insert the explanatory text in the field provided.
Banner colors can be set individually for the various components: Banner with background and text, button for Settings and Accept button. The settings button should be activated with the check mark if your site uses cookies.
As in the External Content or Template tabs, changes to the design can be made directly in the backend. To do this, set a check mark for Overwrite Template.
By activating this option, future updates will no longer be applied automatically. As soon as the setting is deactivated, the template is reset to the original template design.
When a site visitor opens the Cookie Consent in the frontend, information about the cookies used can be seen there. In this tab you have to add all essential scripts & cookies.
The individual scripts & cookies, you can create afterwards. Click on the button Add new and fill in all fields.
You will find the necessary information about the cookies in the listing of the tool from the first step. The names of the cookies are in the Cookies column. Under Description you will find the purpose and usually also the provider/provider of the cookies. The lifetime corresponds to the Duration column.
And finally, the last column tells you how to group your cookies: If a cookie is categorized as Necessary, it belongs to the essential cookies, so it is needed for the functionality of the website.
The Name field is a regular expression. These are used to check if a given text matches a certain pattern. The value you enter in the text field is the pattern against which each cookie name is checked. Cookies that match this pattern will be deleted if a user does not agree to the cookie group. You can test the syntax, for example, on the page: regex101.com. After saving, you should clear the cache and reload your page in the frontend. Then try to give consent for a cookie and remove it. Check the browser console to see if cookies are being deleted or if JavaScript errors are occurring.
All non-essential cookie and script groups can be added in the tab Other Script & Cookie Groups. When dividing cookies into groups, you can use the table from the first step of the configuration.
Create a group and enter the associated cookies and scripts. Three sub-tabs are available for editing each group. In the General tab simply enter the group title, the group key for GTM and the description. Title and description are already visible in the frontend in the unfolded state of the Cookie Consent.
In the Cookies tab you add all other cookies in the same way as the essential cookies.
You can implement scripts as HTML code or as JavaScript. The scripts can be added to your created groups under Scripts. You decide whether you implement the script as HTML or as JavaScript in the Cookie OptIn Extension. Depending on this, you simply use the box provided for this purpose. The tab Scripts and the fields for entering the code you can see here in the screenshot. In a multi-domain environment, you can use a different procedure that allows you to set the ID via TypoScript.
All cookie-related scripts must be added to the configuration and must not be loaded anywhere else!
For example, the Google Tag Manager can be integrated as follows:
document.TagManagerLoaded = document.TagManagerLoaded || 0;
if (!document.TagManagerLoaded) {
document.TagManagerLoaded = 1;
(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='//www.googletagmanager.com/gtag/js?id='+i+dl;f.parentNode.insertBefore(j,f);})(window,document,'script','dataLayer','YOUR GTM-CODE');
}This looks like this in the Scripts tab of a cookie and script group:
In a multi-domain system, the method described above can lead to complications that you can avoid with the procedures presented below. Among other things, these alternatives allow you to set the ID (variable) directly in TypoScript.
For the first variant, enter the following code in the HTML field (again, the Google Tag Manager is used as an example):
<!-- Google Tag Manager -->
<script type="text/javascript">
document.TagManagerLoaded = document.TagManagerLoaded || false;
if (!document.TagManagerLoaded) {
document.TagManagerLoaded = true;
(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);})(window,document,'script','dataLayer', document.googleTagManagerId);
}
</script>
<!-- End Google Tag Manager -->The ID/variable is then set via TypoScript in the TS template of the instance and can be overwritten with conditions:
page.headerData.14414 = TEXT
page.headerData.14414.value (
<script type="text/javascript">
document.googleTagManagerId = '<MY_ID>';
</script>
)Alternatively you can integrate the script completely via TypoScript:
<!-- Google Tag Manager -->
<script type="text/javascript">
function addTagManager () {
document.TagManagerLoaded = document.TagManagerLoaded || 0;
if (!document.TagManagerLoaded) {
document.TagManagerLoaded = 1;
(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new
Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='//
www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);})
(window,document,'script','dataLayer','{$settings.gtm.id}');
}
}
</script>
<!-- End Google Tag Manager -->The parameter settings.gtm.id can then be set dynamically via TypoScript Conditions. You then only have to enter the line addTagManager(); in the extension.
With the latter variant the variable/ID can be set via TypoScript and at the same time it is no longer necessary to copy the code to the different domains.
In Settings tab of the Cookie OptIn Extension you can adjust the runtime of our cookie. After this time has elapsed, users will be prompted again to enter the Cookie Consent. The default setting is 12 months; however, you can adjust this period. Furthermore, in the checkbox next to it, you can specify that for visitors who accept only essential cookies, the lifetime of our cookie is limited to the current session only.
Our cookie is essential for the function of the OptIn Extension cookie. It must be saved so that the tool knows which cookie groups the user has accepted. The structure of our cookie looks like this:
This means: The user has accepted the essential and performance groups, but not the analytics one.
All CSS and JavaScript files are compressed. If you don't want this, you have to uncheck the box Minify generated files.
You should activate the test mode if you are still setting up the cookie consent on an existing page. If you enable this mode, the Cookie OptIn window will not be displayed to the site visitors. To check the appearance and functionality, the dialog can be opened at any time with ?showOptin=1 at the end of the address bar in the frontend.
You can hide the text Powered by sgalinski Cookie OptIn in the frontend by activating the checkbox under Disable Powered by.
If you are in a subdomain, e.g. subdomain.example.com, but want to save the user settings for the whole domain example.com, you can do so here. Just enter the domain for which the cookie Consent should be valid. This does not work with external domains. You should always make sure that your settings are still DSGVO-compliant.
Not all users of your site come from the EU area? - Then they also do not have to deal with a cookie banner. Put a check mark in the appropriate translation to remove the banner there.
If you enable this option, all the JavaScript and CSS content of the Cookie OptIn is rendered directly in the head element. This improves the page load time because it contains fewer blocking HTTP requests (which includes CSS and JavaScript content).
If users have activated the 'DoNotTrack' option in their browser, they can use this checkbox to decide whether they want to take this setting into account or whether the Cookie Consent window should be displayed to them anyway.
Please note that this is not normally GDPR compliant. You use this option at your own risk!
Without this setting, this configuration applies only to the domain where it is stored. With this setting you can use the cookie configuration for multiple domains, for example by writing example.com so that the configuration is used for both dev.example.com and www.example.com.
On your privacy page, you will certainly place the cookie opt-in content element. Therefore, the banner does not need to appear there again. For that, paste the page URI into the field. Each new line will be interpreted as a new regular expression. Check if your regular expression matches the URL of your page, for example by using this page. Also, after saving, check on the frontend in the browser console (to open with F12) that there are no JavaScript errors.
Set the days after which the cookie banner should be displayed again if not all groups were selected.
If you want to translate the content, simply select the language for which you want to create a translation above the content area. Easily adapt all content to the corresponding language and save the changes with the Save button above the content area.
An individual template can also be applied for each language. You can find more about this in the Template tab section.
If you use the Google Tag Manager (GTM) you have to make adjustments in the GTM after integration & configuration of the Cookie Consent Extension.
The first requirement is to create the tracking groups in the Cookie OptIn Extension and add the GTM script in all relevant groups. This avoids double loading. Also note alternative procedures when using multi-domain systems.
The following explanations are based on the exemplary script and cookie groups Analytics and Marketing. The corresponding group keys, which you enter in the tab General of a group, are marketing and analytics in our example.
The script for the Google Tag Manager and the tab Scripts is shown in the figures below.
After the configuration of the Cookies Consent on your website, you must now carry out several actions in the GTM for a complete and successful integration.
Now you have to set the new triggers in your Google Analytics tags. Depending on which cookie group you have assigned a tag to, you adjust the corresponding trigger in the tag. To change the trigger, proceed as follows:
More complex triggers are not executed on every page. In the GTM these must be converted as a trigger group. To create a trigger group, proceed as follows:
You add trigger groups to a tag in the same way as other triggers. In our example you can see that the created trigger group Trigger Group Event can be found in the tag UA - Event. This tag is only activated if both triggers of the group are fulfilled.
You are now ready with the installation & configuration of the sgalinski Cookie Consent!
For some use cases we have enabled developers to interact with our Cookie OptIn system. You can see the use cases in our demo.
The function opens the Cookie OptIn dialog.
In 99% of the cases you will call the function without parameters and the dialog will open:
SgCookieOptin.openCookieOptin();
This parameter adds a trigger function to all protected elements. It is triggered if the respective element has received the approval. You can filter the elements by a CSS selector.
This is very handy if you want to apply a special logic after adding an element to the DOM (e.g. resizing the element or using a highlight effect).
callback {function} – Represents the callback function that is triggered in case of the event.
selector {string} (optional) – A CSS selector is used to filter unaccepted external content elements. Please note that at this point in the runtime, these elements are extracted from the DOM and replaced by the consent elements. So you cannot use parent selectors in this string. These selectors can only be used to check the external element itself for attributes – id, class, src etc.
The example uses the predefined resizeIframeAfterAccept function to resize the element with the ID rce-event:
SgCookieOptin.addAcceptHandlerToProtectedElements(resizeIframeAfterAccept, '#rce-event');
With this function you can programmatically replace each element on the page with a consent box. Try to execute the command below in the developer tools for testing purposes.
This function can be used for external elements that are loaded with AJAX.
externalContent {dom}: Represents the DOM element to be replaced.
SgCookieOptin.replaceExternalContentWithConsent(document.getElementById('c20534'));
We have introduced some JavaScript events to give developers more ways to programmatically influence the behavior of the Cookie OptIn. These are bubbling events that can be attached to the document.body or any other DOM element that is at a higher level than the element itself. The elements are JavaScript CustomEvent objects that you can work with just like any other JavaScript event. The following events are available.
The event can be used to add additional logic and scripts that will be run after the Cookie OptIn dialog is displayed.
Fired when: The Cookie OptIn Dialog has been displayed.
Event target: document.body
Event detail: {}
The event can be used to add additional logic and scripts that will be run after the Cookie OptIn dialog is hidden or closed.
Fired when: The Cookie Optin Dialog has been hidden or closed.
Event Target: the parent of the cookie optin
Event Detail: {}
The event can be used to add additional logic and scripts that will be run after the OptIn dialog for external content is displayed.
Fired when: The details for an external content have been displayed.
Event Target: the wrapper element of the external content itself
Event Detail: {}
The event helps to read users' settings and add additional custom logic. It can be used when you want to add your own statistics tracking or set the cookie on other domains and subdomains, etc.
Fired when: The user has selected his preferences and the cookie has been set (Accept or Accept all).
Event Target: document.body
Event Detail: {cookieValue: String}
Tip: To extract the cookieValue information, you can then pass it to the method SgCookieOptin.readCookieValues(event.detail.cookieValue).
With this event you can change this HTML or add more HTML in specific cases.
Fired when: A custom script’s loadingHTML has been added.
Event Target: document.head
Event Detail: {src: String}
The event can be used to add more logic to the JavaScript or change it in some particular context.
Fired when: A custom script’s loadingScript has been added.
Event Target: the script itself
Event Detail: {src: String}
document.body.addEventListener('cookieOptinShown', function() {
console.log(‘We just opened the cookie optin dialog! We can now change the styling of some elements dynamically at this point.’);
});
document.body.addEventListener('cookieOptinHidden', function() {
console.log(‘We just closed the optin dialog! We can now revert those stylings back to how they were initially.’);
});
Below is a list of commands that you can use on your web server or add as scheduler tasks. You use them in your shell as follows.
./vendor/bin/typo3 sg_cookie_optin:command_name arg1 arg2 ...
sg_cookie_optin:generate_static_files [siteRootId] – Generates the static JavaScript, JSON and CSS files in your fileadmin directory. It replicates the same function as when you save your configuration. It comes in handy, for example, for deployment, unit tests or similar CI/CD tasks. int siteRootId is required – This is the PID of the site root. If you are in a (inconsistent) state that contains more than one configuration entry for the site root, note that the script will export only the first one it finds, assuming it is the correct one.Only the standard layout is currently available. However, it is possible to overwrite the CSS of the cookie window.
In the long term, it is planned to offer different layouts for selection.
We assume that it is possible to create a DSGVO-compliant website with the sgalinski Cookie OptIn Extension. For this it is, however, necessary to load all cookies and tracking scripts exclusively via the extension. As this is the responsibility of the individual website administrator, we cannot assume any responsibility for the legal security of the software.
In addition, the DSGVO conformity of a website includes other aspects that are not covered by sgalinski Cookie OptIn.
You are very welcome to report any suggestions for improvement and feedback about bugs in our tracker to our internal Gitlab. You can also send this directly to our support team via our email address support@sgalinski.de.
This is made possible by the new content element, which has been integrated since version 2.0. This can be found in the backend with the name "Cookie-Opt-In" within the tab "Plugins". Once you have created this, the modular OptIn is no longer displayed on this page.
[1] There is no guarantee for permanent availability or support of the software. Licensees may use the software during the license period as long as it is officially supported and available.
Our cookie consent extension have convinced you, and you would like to realize your next web project or your individual software idea together with us? – Then get in touch for a non-binding offer!
You have an interesting project idea, would like to engage our agency for your TYPO3 / Shopware or Symfony project or contact us about another topic? We look forward to receiving your enquiry via our form or via one of the other contact channels.