Request consent the next visit

What you could do is set the cookie expiration in the banner settings to one day. Then, when a user consents, use a jquery hook to set the expiry to a higher value when the consent level is ‘all’ (marketing level). This will basically set all functional accepted users to an expiration of one day, after which the cookie is gone. But users that accept a higher level, get a longer expiration.

jQuery(document).ready(function($) {
    $(document).on("cmplzEnableScripts", myScriptHandler);
    function myScriptHandler(consentData) {
        //your code here
        console.log(consentData.consentLevel);
        if (consentData.consentLevel==='all'){
           var expiryDays = 365;
           cmplzSetCookie('complianz_consent_status', 'allow', expiryDays);
        }
    }
});

As for your second question: this can be done with some css, but will included in the plugin in one of the future releases.

To do this right now, you’ll need a minor tweak in the cookiebanner js files to wrap a div around the cookiebanner window
https://github.com/rlankhorst/complianz-gdpr/tree/add-window-wrap-html-for-cookiebanner
You only need the complianz-gdpr.php file to up the version number, and the new js files in core/assets/js

When you increase the version number, your browser will use the new javascript files instead of the old, cached ones.

Then you can add this custom css to grey out the area around the banner:

.cmplz-banner-wrap{
    position: fixed;
    width: 100%;
    height: 100%;
    top: 0;
    left: 0;
    right: 0;
    bottom: 0;
    background-color: rgba(0, 0, 0, 0.7);
    z-index: 99;
}

• This reply was modified 4 years, 7 months ago by Rogier Lankhorst.

I’m sorry, the cmplzSetCookie function is out of scope here, you’ll need to add the code for setting the cookie:

jQuery(document).ready(function($) {
    $(document).on("cmplzEnableScripts", myScriptHandler);
    function myScriptHandler(consentData) {
        if (consentData.consentLevel==='all'){
            var expiryDays = 365;
            var secure = ";secure";

            var date = new Date();
            date.setTime(date.getTime() + (expiryDays * 24 * 60 * 60 * 1000));
            var expires = ";expires=" + date.toGMTString();
            if (window.location.protocol !== "https:") secure = '';

            document.cookie = 'complianz_consent_status' + "=" + 'deny' + secure + expires + ";path=/";
        }
    }
});

I noticed there is a bug in the original cookieconsent.js file that we used to build the plugin on. I have fixed this in the same branche. But when you override the complianz_consent_status like above, this does not really matter.

The reason the expirydays is not changing is that this is cached. If you change something in the cookiebanner, like the color or something, the cache will be cleared.

I’ve just tested it, and this now works fine. If you open it in an anonymous window you should see it working.

As for going to production: I’ll see what I can do. We’ll have to add this as a new theme, then test it. Won’t be in a few days, but maybe in a week or 2.

Yes, in your setup you’d need allow.

I can’t reproduce your issue with the date. This works fine for me.

As for the grey out background: I have made some additional changes, which allows you to enable the soft cookie wall option in the cookie banner settings.
https://github.com/rlankhorst/complianz-gdpr/tree/add-window-wrap-html-for-cookiebanner

@beeriz just made some last changes to this branche for the soft cookie wall: minified files weren’t changed yet.

Hi @beeriz,

3.1.0 will be released somewhere next week. With the current release candidate, the 3.1.0 version on github, I do not see the issue. Do you have the expiry date issue with the default code (without hooks to alter the expiry date)?

Is it possible the cookieconsent.min.js file is still a cached file in your browser cache?