Plugin Directory

!This plugin hasn’t been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.


Provides extensible support for EU/UK compliance of the EC Cookie Directive (2009/136/EC), based on a visitor's location.

Help, it's broken! What do I do now?

If something does not appear to be working as it should, search the support forum or write a new topic that describes the problem(s) you are experiencing. I will do my best to provide a solution as soon as possible.

I have a PHP version older than 5.3, can I make it work?

This plugin makes use of many features introduced in PHP version 5.3, and an attempt to make it work with older versions of PHP is equivalent to a complete rewrtie of the plugin.

Many hosting providers are already providing PHP 5.3+ to their customers, and others allow for an easy upgrade. Also consider that PHP 5.3 was first released in 2009 and fixes many bugs and security issues, and support for PHP 5.2 was stopped in 2010.

How can I upgrade to PHP version 5.3?

This depends. If you have your very own server, then this is Operating System specific and you will need to consult its documentation on how to upgrade. Most commonly in Linux environments this consists of running apt-get, yum or pacman from the CLI.

If you are using a web hosting provider, then you need to contact the provider regarding this. Some can move your website to a different server with a newer version of PHP 5.3, while others make it as simple as adding/changing a line in the .htaccess file or a setting in the control panel. For example:

  • 1&1 Webhosting: Add AddHandler x-mapp-php6 .php to the .htaccess file
  • OVH: Add SetEnv PHP_VER 5_3 or SetEnv PHP_VER 5_TEST to the .htaccess file
  • GoDaddy Linux Shared Hosting: Add AddHandler x-httpd-php5-3 .php to the .htaccess file
  • GoDaddy 4GH Hosting: Visit GoDaddy's Hosting Control Center -> Content -> Programming Languages
  • HostGator: Add Action application/x-hg-php53 /cgi-sys/php53 and AddHandler application/x-hg-php53 .php to the .htaccess file
  • Bluehost: Add AddHandler application/x-httpd-php53 .php to the .htaccess file (Note: may require a support request/ticket to enable PHP 5.3)

Will this plugin make my website entirely compliant?

The plugin is to assist with compliance, but it may not be a full-stop solution.

For example, this plugin will stop WordPress and any other WordPress plugins you've installed from setting a cookie. But, if there's Javascript used on your website, they may still set cookies that are beyond the control of Cookillian. Google Analytics is probably the most common one, but other things like Share on Facebook or Share on Twitter buttons could set their own cookies.

That's why there's the option within the plugin to include JavaScript in the header/footer if the visitor has agreed to receiving cookies - you'd need to remove that JavaScript from your website, and add it to the plugin option instead.

Cookillian will also list which cookies it has detected (including ones set by JavaScript). There are also extensions for browsers that will help you see which cookies have managed to get past Cookillian. Google Chrome users can use the Developer Tools from the Menu bar as well.

If you have any cookie that are required for your website to operate, ie., a cookie that stores products placed in a shopping cart, you can set these in the plugin's Cookies page as well.

The alert has disappeared after I clicked "No", how do I get it back?

You can reset your preference by adding ?cookillian_resp=2 to any URL of your website, such as http://www.example.co.uk/?cookillian_resp=2. Naturally, you can add this as a link on, for example, the Privacy Policy page to make it easier for visitors.

How do I know if it is working?

On the Settings page, under the heading Advanced Options near the bottom, you have the option to enable Debug Mode. For logged-in users, this will cause the alert to be displayed at all times, which allows you to see where it will be located.

Enabling the Debug Mode also provides you with extra information when using the JavaScript console. The console can be viewed with Firebug, or the browser's Developer Tools.

The alert is not displaying at all, help!

The alert is not shown if:

  • The visitor is logged in as a WordPress user (with any role), or
  • The visitor is not in one of the defined countries, or
  • The visitor already explicitly opted in/out, or
  • The browser support the "Do Not Track" (see donotrack.us) option, and enabled it.

If the alert is still not being displayed, enable the Debug Mode as described above.

How do I change where the alert is displayed?

First you need to set Show Alert to Manually on the Settings page. In its simplest form, you can use a WordPress shortcode [cookillian alert] in a post or page, which will be replaced by the alert if neccesary.

For slightly more complex use, you insert <?php cookillian_insert_alert_block(); ?> in the desired location of your theme.

How do I change the appearance of the alert?

You can use your own CSS styling through by choosing Custom for the Alert Styling on the Settings page. The alert is wrapped in a .cookillian-alert class (also when added manually), providing the background and border colors. The alert heading is in an .alert-heading class and the Yes and No buttons in .btn-ok and .btn-no respectively. If your CSS styling does not appear, you may need to add !important to your styling.

When I click on "Privacy Policy", nothing happens

On the Settings page, you will need to modify the Alert Text by replacing the hash sign (#) within the <a href="#"> HTML tags to the actual URL of your Privacy Policy (and the "More Information" link).

I'm using a caching plugin and after a while the alert stops showing. Why?

Cookillian uses a security token for its AJAX requests, which are valid for up to 24 hours. If a page is cached beyond this time, the security token (stored on the cached page) will be invalid and Cookillian can no longer perform AJAX requests. For this reason, it is recommended to cache pages for less than 24 hours.

WP Super Cache includes a Garbage Collector, checking cached pages at set intervals for cached pages that have expired. It has a minor issue, where the Garbage Collector will be reset when saving other settings, so you may have to double-check the Garbage Collector is still called at the correct intervals.

How can I translate Cookillian to my own language?

A generated .PO (.POT) file called default.po is included in the plugin's resources directory, generally wp-content/plugins/cookillian/resources/l10n. It can be translated using tools such as POEdit or manually in a text editor. Simply save the translated .PO and generated .MO file using the locale code (ie., nl_NL.mo) within the same directory, and Cookillian will automatically use it if the WordPress language is set to that locale.

If you wish to share the translations with other users of Cookillian, feel free to e-mail the translation to hello@myatus.com and I'll be happy to include it with the next release, along with a credit by-line for your hard work.

Requires: 3.3 or higher
Compatible up to: 3.7.11
Last Updated: 2 years ago
Active Installs: 1,000+


4 out of 5 stars


Got something to say? Need help?


Not enough data

0 people say it works.
0 people say it's broken.

100,2,2 100,1,1 50,2,1 100,1,1 100,1,1 100,1,1 100,1,1
100,1,1 100,1,1