Journal des modifications

03/10/2024
  • ERROR RESOLVED When using domain mapping (e.g., with WPML or Polylang), the consent history on the mapped domain may not have been retrievable, but it remained accessible on the main domain.
02/10/2024
  • NEW The filter hook borlabsCookie/scriptBuilder/modifyConfigBeforeSaving has been added.
  • IMPROVED Multilingual plugin support has been improved when the domain mapping feature (Polylang & WPML) is used.
  • IMPROVED The "Cookie Domain is set correctly" test in the debug console has been improved.
  • ERROR RESOLVED The URL for cross-cookie domain article has been fixed and now points to the correct article in the knowledge base.
26/09/2024
  • NEW Legacy Importer added. Import settings from Borlabs Cookie Legacy (version 2.x). This requires Borlabs Cookie version 2.3.0. For more details, visit https://borlabs.io/kb/upgrade-2-3-to-3-2/.
  • NEW Debug Console added to help identify misconfigurations and common issues with Google Tag Manager integration.
  • NEW PHP API for third-party developers is available and can be accessed through borlabsCookieApi() after the WordPress init action hook is executed. For more details, visit https://borlabs.io/kb/php-api-v3/.
  • IMPROVED Handling of Borlabs Service requests has been improved.
17/09/2024
  • ATTENTION: This update requires Borlabs Cookie 2.2.68! Do NOT install this update if your current version of Borlabs Cookie is not 2.2.68!
  • NEW All tables and option names of borlabs_cookie or BorlabsCookie renamed to borlabs_cookie_legacy or BorlabsCookieLegacy.
  • NEW Option to upgrade to Borlabs Cookie 3.0. For more details, visit https://borlabs.io/kb/upgrade-2-3-to-3-2/.
04/09/2024
  • IMPROVED Cookie handling has been improved. The borlabs-cookie and TCF_COOKIE cookies are no longer created twice when the "Automatic Domain and Path Detection" setting is changed in live mode. Previously, these duplicate cookies could cause the dialog to reappear each time a page was loaded. This issue has now been resolved.
  • IMPROVED The automatic update process has been improved.
  • IMPROVED Handling of Borlabs Service requests has been improved.
28/08/2024
  • IMPROVED Support for PHP 8.2 has been improved.
  • IMPROVED The automatic update process has been improved. In earlier versions, there was a possibility that WordPress did not recognize that Borlabs Cookie should be updated automatically.
  • IMPROVED The Service Shortcode now supports third-party Shortcodes.
  • IMPROVED Multilingual plugin support has been improved. Borlabs Cookie now ensures that all default entries for Content Blockers, Providers, Services, and Service Groups are available in every language.
07/08/2024
  • NEW A new setting has been added to disable email notifications for packages that are updated automatically. Although we believe it's important to receive notifications for automatic updates, we have made this feature available due to popular customer demand. This feature is enabled (true) by default and must be manually disabled. Future updates will not change this default setting to false.
  • IMPROVED The handling of regex in Script Blockers and Style Blockers was improved.
07/08/2024
  • ERROR RESOLVED The error message if the REST API is blocked (which should not be the case!) is now catched correctly.
07/08/2024
  • IMPROVED The logging of regex in Script Blockers and Style Blockers without delimiters and the associated fallback have been removed. If you have manually added a blocker and are using a regex, make sure that your delimiters are set. If you use our Facebook package, make sure it is up to date.
05/08/2024
  • IMPROVED Email notifications for packages that are updated manually are now disabled by default.
  • IMPROVED The handling of regex in Script Blockers and Style Blockers was improved. If you have manually added a blocker and are using a regex, make sure that your delimiters are set.
  • IMPROVED Replaced static white color with a CSS variable for the dialog background gradient. This change ensures better theming support and flexibility in styling.
  • ERROR RESOLVED An error could occur when synchronizing Services with other languages.
  • ERROR RESOLVED If invalid data was entered when adding a Provider, the error was not handled correctly and all the data entered had to be re-entered. Kudos to Christian for finding the error.