Cookillian 1.1 released

on May 31, 2012 in WordPress with 1 comment by

Cookillian version 1.1 has been released today, bringing with it a large number of additions and changes based on the input of David Artiss at, and suggestions by e-mail and the WordPress support forum.

Cached content

One of the show-stoppers for Cookillian was the lack of support for caching plugins, such as WP Super Cache and W3 Total Cache. This was due to the dynamic nature of the alert. In 1.1 this has been incorporated in AJAX code, which effectively bypasses the static content returned by caching plugins.

Whilst it sounds simple, it was a little more involved behind the scenes, but also gave me an opportunity to work on how the statistics are updated. They should now be more accurate, and avoid the “trigger happy” visitors that tend to double-click on links (effectively doubling opt-in/out statistics, causing negative numbers for the “Ignored” alerts).

Implied Consent

Newspapers reported that at the 11th hour, the ICO had a change of heart about implied consent. This allows the visitor to ignore the alert, provided the alert clearly states that continued use will imply consent. Cookillian now support the option to add “implied consent”, where ignoring the alert on subsequent visits, it’ll opt the user in.


The Cookies page was very simplistic in the previous version, and has been updated to easily select from existing groups and remove entries. A new WordPress Dashboard widget has been provided, that gives a quick overview of newly detected cookies – along with a link to edit them – and a few of the top statistics reported to Cookillian for the current month.



The shortcode for displaying the cookies on a page or post has been altered slightly. It now allows for more than one group to be specified using a comma-separated list, like so:

[ cookillian cookies="WordPress, Website"]

Alternatively, instead of specifying a large number of groups, you could also display all groups with the exception of those you exclude, like so:

[ cookillian cookies exclude="Unknown, Deprecated"]

This would especially be useful of excluding newly detected cookies, which may sometimes include “false positives”. And by that, I mean malfunctioning browsers or those with too much spare time, trying to break things.

[mt_label type=”info” text=”Heads up!”] There’s a space in between the left opening bracket and “cookillian” to prevent it from running on this page.

More features

One of the most asked questions, as well as feature request, was regarding the styling of the alert. The default alert is quite, shall we say “in your face”? Some prefer a little more subtle alerts. Now, Cookillian’s alert styling could already be modified from when it was released, but an additional field has been provided where this can be done without having to modify the WordPress theme in use. I will be providing some sample styles in later posts – keep an eye out on them.

Cookillian now also has the ability to use a backup geolocation service,, in case it did not receive a valid or empty response from the chosen default geolocation service. has a limit of 1000 requests per hour, hence that it is only available as a backup service.

Geolocation data is also cached, which helps reduce the amount of requests sent to a geolocation service. With version 1.1, this cache time can be changed. For CloudFlare and MaxMind, it should be fine to change the cache time lower than the default, however, using geoPlugin, the longer it stays in cache, the better. The cache can be purged at any time from the Settings page.

Furthermore, the API has been enhanced based on the input found on the WordPress support forum. Instead of filters, regular PHP functions can now be used, and introduces the ability to check for implied consent, delete cookies, opt a user in or out and reset the opt in/out preference. Because caching plugins interfere with this API, JavaScript equivalents have been provided, all of which are explained in the Help tabs.



One comment

  1. posted on May 31, 2012 at 9:40 AM  |  reply

    […] the Cookillian version 1.1 release post, I had promised to show how to style an alert. With the following styling, I have taken example of […]

Join the discussion

Your email address will not be published. Required fields are marked *