Smart Cookie Kit

2.3.2

• Fixed a XSS vulnerability (thanks to patchstack.com )

2.3.1

• Minor bug fix

2.3.0

• Added a compatibility mode for Facebook Pixel (for official and unofficial plugins – EXPERIMENTAL).
• Google reCaptcha block can be optionally disabled.
• SCK now manages the AutomateWoo “Session tracking” feature.
• It is now possible to know server side if current user accepted cookies (more details in the backend help page).
• Minor bug fix

2.2.4

• SCK was not blocking cookies on wp-login.php page. Fixed (thanks to @delbono72).
• SCK was not blocking some ShareThis cookies. Fixed.
• SCK is now compatible with Polylang PRO
• SCK is now compatible with GAinWP Google Analytics Integration for WordPress

2.2.3

• Autoptimize’s author changed a filter in its code in version 2.6.0. Updated SCK to reflect this change
• Corrected a bug to remove all SCK data from the database on uninstall

2.2.2

• SCK is now compatible with Async Javascript
• Bridge theme changed its shortcode for adding Google Maps. SCK updated to correctly manage them.
• Added the Instagram embed script to the block of SCK.
• It is now possibile to INCLUDE additional Javascripts scripts to the block

2.2.1

• Minor bugs fix

2.2.0

• Smart Cookie Kit is officially compatible with Gutenberg (even if it is not used to manage translations)
• Updated the “Simple HTML Dom” Library to version 1.8.1 for compatibility with PHP 7.3.1
• Smart Cookie Kit now fires standard Javascript events to let you able to manage custom functionalities (more details in the “Help and support” page of the plugin)
• It is now possible to EXCLUDE some Javascripts from the block
• Added a security check for NGINX web servers
• Minor bugs fix

2.1.3

• SCK was blocking “Google Tag Manager by DuracellTomi” even if the option to block Google Tag Manager was disabled. Solved.
• Version 2.1.2 caused some graphic issues. Solved.
• Smart Cookie Kit did not show a placeholder for Google reCAPTCHA. Solved.
• Added native support for Google Maps added through the shortcode of Bridge theme.

2.1.2

• Fixed a minor bug for the maximized banner in the policy page.
• Added the possibility to unlock services when users scroll the page (implicit consent).

2.1.1

• Fixed a bug between Cache Enabler plugin and Customizr theme.

2.1.0

• Banner translations can be now easily managed like page and post translations via WPML and Polylang.
• Added a field to customize the placeholder text.
• The banner content and the placeholder text fields are now “rich text fields”, so you can format the content and add links.
• If present, the link to the page that contains the cookie policy has been inserted automatically in the “Banner text” field.
• Changed the settings section of the plugin. Settings are available now on the main menù of the backend.
• Avada was adding Google Map directly in “contact” pages (not only through the Fusion Builder element): blocked!
• Enfold theme 4.4 was improved for better performance and changed how maps are handled: solved!
• Added an option to reload the web page when user disables cookies.
• Solved a compatibility problem with plugins that use “Simple HTML Dom” library.
• Solved a compatibility problem with “Google Tag Manager by DuracellTomi” plugin.

2.0.6

• Added native support for Google Maps added by Divi Builder, Avia Builder (Enfold theme), Fusion Builder (Avada theme), Visual Composer (Jupiter and others themes) and Cornerstone builder.
• Added some integrations with cache plugins (W3 Total Cache, Fastest Cache, WP-Rocket, Litespeed Cache) for optimizations with DEFER scripts attribute.
• Added compatibility with Divi and Cornerstone frontend builder.
• Solved minor bugs for compatibility with Microsoft Edge and Mozilla Firefox.

2.0.5

• Solved a minor bug related to the minimized banner.

2.0.4

• Added an option to show a “Content not available” placeholder where elements have been blocked in the page.
• Added an option to choose whether or not to show the minimized button to open the banner.
• Added a shortcode to get a link that opens the banner.
• Smart Cookie Kit is now compatibile with Autoptimize.
• Restored the backlayer option.

2.0.3

• The log directory has been moved from “/wp-content/plugins/smart-cookie-kit/logs/” to “/wp-content/cookie-preferences-log/”.
• The log directory has been protected to avoid browser access to its content.
• Log files has been converted to a csv format.
• Minor compatibility issues has been fixed.
• Solved minor translations related bugs.
• Javascript code has been improved.

2.0.2

• Solved minor bugs.

2.0.1

• Solved warning: “The first argument should be either a string or an integer” in plugin_options.php on line 42
• Sometimes Google Tag Manager was not blocked.
• Sometimes Google Analytics was blocked even if anonymized.
• Solved minor bugs.

2.0.0

• Plugin was modified to be full GDPR compliant!
• Cookie name to save user preference is changed in “CookiePreferences-[wp_install_dir]”
• Scroll and click consent deprecated.
• Added in cookie and in server log informations about first cookie acceptance and following updates.
• It is possible now to handle Google Tag Manager.
• Client side code rewrited in pure Javascript: plugin now does NOT require jQuery.
• Solved minor bugs.

1.2.7

• Solves an error of the previous update.

1.2.6

• Yoast SEO compatibility. Solved a compatibility bug with Yoast on “application/ld+json” scripts.

1.2.5

• W3 Total Cache compatibility. SCK replaces known js scripts with its empty.js but W3TC minification minifies the empty script removing the reference to the original script, so SCK can’t run the original script. Now SCK integrates a filter to exlude it’s empty.js from the W3TC minification.

1.2.4

• Minor bug fix.

1.2.3

• Minor bug fix.

1.2.2

• Smart Cookie Kit blocks now scripts from tawk.to chat system.

1.2.1

• Smart Cookie Kit blocks now pixels from PixelYourSite plugin too.

1.2.0

• Made optional (even if it is active by default) the policy when user scrolls the page (thanks to Angelo for the suggestion).
• Added an offset to permit to the user to make a little scroll before trigger the implicit consent (thanks to @diegocanal for the suggestion – https://wordpress.org/support/topic/great-concept-beautifully-implemented).
• Added (optionally) option to implicit accept the policy when the user clicks on some elements of the page (it is possible to exclude some).
• It is now possible to save on the server (as well as on the user browser) a log of users that accept the policy (included the way of acceptance) – thanks to @woodypad for the suggestion, https://wordpress.org/support/topic/registra-i-consensi-records-consents)
• Added a debug mode

1.1.1

• Solved a bug: some themes don’t print scripts in the footer. Added an option to insert scripts in the header of the page.

1.1.0

The previous version of the plugin was adding a layer to the page content to avoid clicks on any element in the page, so the user had to accept the cookie policy to get the content “available”.
On this version I made that layer optional and disabled for default, thinking that this is a better choice for the search engine spiders.
Also added others options to customize the layout of the banner.

1.0.4

• Minor bug fix.

1.0.3

• Minor bug fix.

1.0.2

• IT Cookie law tutorial added.
• Minor bug fix (translations related).
• English translation added.

1.0.1

• Minor bug fix.

1.0.0

• Option page added.
• Plugin is ready for translations.

0.1.0

• Test version.