Provides extensible support for EU/UK compliance of the EC Cookie Directive (2009/136/EC), based on a visitor's location.
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.
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.
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
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:
AddHandler x-mapp-php6 .phpto the
SetEnv PHP_VER 5_3or
SetEnv PHP_VER 5_TESTto the
AddHandler x-httpd-php5-3 .phpto the
Action application/x-hg-php53 /cgi-sys/php53and
AddHandler application/x-hg-php53 .phpto the
AddHandler application/x-httpd-php53 .phpto the
.htaccessfile (Note: may require a support request/ticket to enable PHP 5.3)
The plugin is to assist with compliance, but it may not be a full-stop solution.
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.
You can reset your preference by adding
?cookillian_resp=2 to any URL of your website, such as
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.
The alert is not shown if:
If the alert is still not being displayed, enable the Debug Mode as described above.
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.
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-no respectively. If your CSS styling does not appear, you may need to add
!important to your styling.
On the Settings page, you will need to modify the Alert Text by replacing the hash sign (#) within the
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.
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 email@example.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.1
Last Updated: 2013-11-4
0 of 4 support threads in the last two months have been resolved.
Got something to say? Need help?