Rev 7 | Blame | Compare with Previous | Last modification | View Log | Download
# Changelog of PrivacyWire## 1.1.2- Added: Config option to activate / deactivate PrivacyWire## 1.1.1- Merged PR #19 and #22- Changed: Switched `innerText` to `textContent` for accuracy in `updateAllowedElementScript()`- Changed: form layout and fields definitions syntax- Updated dependencies## 1.1.0- Added: Config option and feature to detect bots (per User-agent) and hide the banner to them## 1.0.11- Fixed: Bug, when multiple page()->render() methods are called. Now PrivacyWire only loads on the main call of page()->render()## 1.0.10- Added: Config option to replace the original consent blueprint template (located in site/modules/PrivacyWire/PrivacyWireConsentBlueprint.php) with an alternative consent blueprint## 1.0.9- Changed: Reduced priority of Page::render hook to allow easier override of settings## 1.0.8- Added: Add class to body "has-privacywire-window-opened" while PrivacyWire windows are visible## 1.0.7- Added: Function to re-handle external button trigger via `window.PrivacyWire.reHandleExternalButtons()`## 1.0.6- Fixed: Legacy IE11 Bug with Array.from Polyfill (Also for not-inline mode)## 1.0.5- Fixed: Legacy Support for IE11 with Array.from Polyfill## 1.0.4- Fixed: removed console.log() debugger from DNT-method## 1.0.3- Changed: Order of Buttons in Options window## 1.0.2- Changed: Removed ProCache Output method as there is no real improvement over enabling JS minification in the ProCache settings.- Changed: Load modern ES6 version of JavaScript via `<script type="module" ...>` and legacy version of Javascript via `<script nomodule ...>` to support both modern and legacy browsers with the best possible result.- Fixed: The Imprint and Privacy links markup is now equal between banner and option view.- Fixed: After upgrading from 0.4.5 (and below) to 1.0 (and up) require new consent from the user, as syntax has changed.## 1.0.1b (beta)- Changed: Return value of PrivacyWire methods for better extensibility- Added: method `getPrivacyWireCore` which returns the path and url to the PrivacyWire Core JS file- Added: more comments to explain how you can bundle the PrivacyWire Core JS with your other scripts## 1.0.0a (alpha)**Major Refactoring**. Rewritten both the JS and PHP parts.- Added: Config option for output mode (regular script tag, ProCache script tag, inline script)- Added: Config option to choose elements which require consent by class `require-consent` instead of data-attribute (better performance). **WARNING**: Enabling this needs adding the css class `require-consent` to every element (also script tags!) you want to be processed by PrivacyWire- Added: Config option to choose ES6 JavaScript instead of a _Babel_ transpiled version (Faster and smaller but no Internet Explorer support)- Changed: Module methods refactored. Hookable methods changed. Take a look into [PrivacyWire.module](PrivacyWire.module) to see the difference- Added: Possibility to manually refresh detection of elements (e.g. after loading content via AJAX). Just call `window.PrivacyWire.refresh();` after adding new content to the DOM which could require consent- Changed: Split markup from Banner and Consent Blueprint in two different files for better separation of concerns and easier hook management.## 0.4.5- Added: JS function to manually trigger the update of DOM elements: `window.updatePrivacyWireElements`## 0.4.4- Added methods: getInlineJavaScriptTag & getPathToCssFile- Added: CSS file instead of SCSS for improved manual rendering options## 0.4.3- Fixed: Textformatter support for TextformatterVideoEmbed now also works for YouTube no-cookie mode## 0.4.2- Fixed: Bug during cloning allowed script elements after giving consent## 0.4.1- Changed: Optimized "priw_updateAllowedElement"## 0.4.0- Fixed: Bug during cloning allowed elements after giving consent## 0.3.9- Added: Textformatter support for TextformatterVideoEmbed (Thank you @teppokoivula !)## 0.3.8- Fixed: Bug with ask consent window when cookies get accepted via the main banner## 0.3.7- Added: Config options to show alternative headline and text elements within the options banner## 0.3.6- Added: Config option to prevent automatic rendering.- Added: New methods renderHeadContent() and renderBodyContent().## 0.3.4- Fixed: sanitize alternative banner template path to ignore leading slash## 0.3.3- Added: Config option to replace the original banner template (located in site/modules/PrivacyWire/PrivacyWireBanner.php) with an alternative banner template- Added: hookable method to get JS file- Added: hookable method to get inline JS- Added: hookable method to get (alternative) banner template file- Changed: Optimized CSS (even smaller - 458 bytes instead of 554 bytes)- Changed: Re-arranged the config options to provide better structure## 0.3.2- Fixed: Bug with "Accept all" Button to load elements- Added: Config option to choose the banner header tag between `<header>` and `<div>`## 0.3.1- Added: Config option within Textformatter to choose open and close tag## 0.3.0- Added Feature: When the user hasn't given consent to a specific cookie category, show an alternative element with asking for consent. To enable this feature, add following data-attribute to the element ``` data-ask-consent="1"```. In the module configuration you can choose, what text should be in that window. Example: ``` <iframe src="" data-src="https://www.example.com/" data-category="marketing" data-ask-consent="1" frameborder="0" height="400" width="400"></iframe>```## 0.2.7- Fixed: Updates more attributes of elements (srcset, height, width) - important for responsive images or iFrames## 0.2.6- Added: Config option to show an "Accept All" instead of "Toggle" Button within the "Choose Cookies" window.## 0.2.5- Fixed: Changing version number now works as expected## 0.2.4- Fixed: Typo in consent of external_media## 0.2.3- Added: Config option for message timeout## 0.2.2- Added: Config option to output unstyled (no css) PrivacyWire## 0.2.1- Added: New cookie category "functional"## 0.2.0- Changed: Major rewrite of PrivacyWire.js -> now around half the size (main reason was babel with usage of js classes (ES6))- Added: New possibility to add a custom js function name which is triggered after saving options## 0.1.2- Added: Config option for using ProCache minification or not## 0.1.1- Fixed: Error during uninstall## 0.1.0- Changed: Script detection now uses the data-category attribute instead of type="optin" (W3C validation)## 0.0.7- Fixed: Multi-lang privacy & imprint link## 0.0.6- Fixed: CSS-Debugging for hiding unused buttons, added ProCache support for the JavaScript tag## 0.0.5- Added: Multi-language support included completely (also in TextFormatter).- Added: Possibility to async load other assets (e.g. ``<img type="optin" data-category="marketing" data-src="https://via.placeholder.com/300x300">``)## 0.0.4- Added: Possibility to add an imprint link to the banner## 0.0.3- Added: Multi-language support for module config (still in development)## 0.0.2- First release## 0.0.1- Early development state (ALPHA)