The plugin automatically adds the iubenda code to all the pages of a site (to the HEAD section);
Simplifies the management of the iubenda Cookie Solution for multilingual sites.
Google Site Search
Google Tag Manager
Installation and activation
Log in and open the admin section to get to your main PrestaShop dashboard;
Click on Modules > Modules & Services in the sidebar menu;
Click on Upload a module in the header section;
To install the module upload the “iubenda_cookie_prestashop_plugin.zip” file (click here to download) – you must point to the module’s zip archive, and not its folder or any of its unpacked files.
If the installation is successful, you’ll get this message:
The module will then appear in your list of modules under “Modules & Services”.
Now it’s time to go configure the settings of the module.
How to add the cookie banner and modify settings
Now that the module is ready, we need to feed it the necessary information from your iubenda account.
If you haven’t clicked on the Configure button inside the “Module installed!” pop-up message, navigate to the Modules & Services page and find the iubenda module:
Click on Configure to go to the module configuration settings.
Add the code from your iubenda account to the extension (this is what the embedding code looks like in your iubenda dashboard): (If you haven’t already generated your cookie banner and code, you can do so here or for in-depth information, you can read the introduction to the iubenda Cookie Solution guide. )
Paste that code into the plugin form and save: (Being PHP native, we recommend the primary, faster option for the parsing engine. If you’re experiencing some issues, try with the alternative based on a custom HTML DOM class)
These scripts can be blocked by entering the source into the Custom Script boxes in the plugin console or by using the manual wrapping method illustrated in the example below and (in more detail) in this help post
Blocking custom scripts from within the console
The Custom Scripts field makes it easy for you to block scripts inserted into the page directly from within the plugin console. This greatly reduces the need for direct edits to the site’s code.
Here’s how to do it:
On the left menu in your admin panel, go to the Improve section and click Extensions > Plugins.
Next, search “iubenda”, and when the plugin appears, click on the Configure button.
Scroll down to find the Custom scripts and Custom iframes fields at the bottom of the page.
Enter your script or iframe sources as needed, and click the Save button at the bottom-right of the page.
Using these fields are pretty straightforward. Simply enter the script or iframe src attribute you’d like to block.
Let’s say you wanted to block scripts inserted into the page via the following iframe
What you’ll need to enter into the iframe field would be videowebsite.com/embed/ as this is the actual source of the scripts. Be careful NOT to enter the component id (videowebsite.com/embed/xxFhMChxx) to ensure that all scripts coming from the actual source are blocked.
Manual Use (wrapping method)
This method requires you to directly modify your site’s code. You’ll need to go into the relevant section of your site’s code and add the scripts to be blocked as explained below.
For API calls and xmlrpc we suggest the parameter ?iub_no_parse=1.
PrestaShop “Forbidden” error
Always remember to back up your website before attempting any fix.
In some rare cases, the system may return a “forbidden” error when you enter the Cookie Solution script, or any other script, into the Cookie Solution module and click “Save”.
This is likely related to a ModSecurity property of Apache activated in the PrestaShop backend. To solve the issue, you’ll need to disable the mod_security module. You can do this using the following procedure:
Click on Shop Parameters -> Click on Traffic&Seo -> Find the “Disable Apache ModSecurity Module” and set to “Yes”.
If for some reason the procedure doesn’t work, it may be necessary to contact your web hosting provider regarding your particular site restrictions.
Changelog and current version
Tweak: Simple HTML Dom PHP class update to 1.9 Tweak: Code handled with official code validator
New: Introducing a way to skip specific script parsing Fix: Improved handling of iubenda script HTML Tweak: Support links update
Tweak: Adjust the iubenda PHP class handling Tweak: Update iubenda logo
New: Option to block custom scripts and iframes Tweak: Update and extend the list of blocked scripts including Google Site Search, Google oAuth, LinkedIn widgets, PayPal widgets, Freshchat, UserVoice, AdRoll, Olark, Segment, Kissmetrics, Mixpanel, Pingdom, Bing and Elevio
Tweak: Update and extend the list of blocked scripts including Pinterest, AddThis, Disqus, Optimizely, Neodata, Criteo, Outbrain, Headway and CodePen Tweak: Interface improvements
Fix: Invalid iubenda parser implementation
Tweak: Update and unify iubenda parsing engine
Fix: Eage output empty if script blocking disabled