The cookie consent module in Signocore Toolkit will be removed in Toolkit 5.0, and Signocore Consent takes over the job. You can switch whenever it suits you. The two plugins never show two banners at once, so there is no gap and no overlap.
Switch in five steps
- Install and activate Signocore Consent.
- Leave Toolkit as it is. While Cookie consent is on in Signocore Consent, Toolkit's banner and its Consent Mode defaults stay off on their own.
- Go to Settings → Cookie consent and copy your settings across, using the table below. Toolkit 5.0 does not move them for you.
- Replace the shortcodes, links and code that point to Toolkit's banner, as listed further down.
- Open your site in a private browser window and check the banner and the Consent Mode signals, as described in Check the setup.
Settings
| Signocore Toolkit (Signocore Toolkit → General) | Signocore Consent (Settings → Cookie consent) |
|---|---|
| Enable Cookie Consent | Cookie consent |
| Banner Position: Bottom Right, Bottom Left or Full Width Bottom | Banner position: Bottom right, Bottom left or Full width at the bottom |
| Banner Message | Banner text |
| Consent Duration (Days) | Remember the choice for, in days |
| Show Preferences Button | Settings button |
Both plugins keep a choice for 30 to 730 days, 365 by default, and both add a link to your privacy policy page when one is set under Settings → Privacy.
Links and shortcodes
| Signocore Toolkit | Signocore Consent |
|---|---|
[cookie-settings], with an optional text attribute |
[consent-settings], with the same text attribute |
A menu link to #sctk-cookie-settings |
A menu link to #consent-settings |
The data-sctk-open-preferences attribute on your own link or button |
The data-scc-open attribute |
Categories and Consent Mode
| Signocore Toolkit | Signocore Consent |
|---|---|
| Necessary | Necessary |
| Preferences, new | |
| Analytics | Statistics |
| Marketing | Marketing |
Toolkit grants functionality_storage to every visitor and leaves personalization_storage unset. Signocore Consent denies both until the visitor allows Preferences, so Google tags that use them wait for that choice. See Google Consent Mode v2 for the full mapping.
Scripts that wait for consent
With Toolkit, holding a script back meant writing your own loader that read the sctk_consent cookie and listened for the sctk:consent:updated event. Signocore Consent does this with an attribute: change the script's type to text/plain and name its category in data-scc-consent. Replace your own loaders as described in Load scripts after consent, and remove the old ones, or they will keep waiting for a cookie that is no longer written.
Code
| Signocore Toolkit | Signocore Consent |
|---|---|
The signocore_toolkit_consent_categories filter |
The signocore_consent_categories filter. Add signals to a category to grant Consent Mode signals. |
The signocore_toolkit_consent_banner_html filter |
No equivalent. Change the text with Banner text and the colors with the plugin's CSS custom properties. |
The sctk:consent:updated event |
signocore-consent:updated |
The sctk:consent:banner:shown event |
signocore-consent:banner-shown |
The sctk:consent:preferences:opened event |
signocore-consent:preferences-opened |
The sctk:consent:preferences:closed event |
signocore-consent:preferences-closed |
The sctk_consent cookie |
The signocore_consent cookie. The analytics key is now statistics. |
What visitors notice
The two plugins store the choice in different cookies, so every visitor sees the banner once more after you switch. Choices made in Toolkit's banner are not carried over, which also means nobody is treated as having agreed to something they were never asked about.