Jump to content



Recommended Posts

Maybe some javascript messages could work or you add a query string like ?comment=success which shows the message?

nice addition, I'll look into it as soon as possible ;)


Good to have the option to limit the cookie consent to a special path/ tree. But in this case the banner shouldn't be shown for pages not residing under this tree.
It would also be nice to store the page id and not the path, to stay multilanguage compatible and to avoid problems if the page name has been changed. A page-field (instead of text) would be the simplest solution here.

@kixe, think I need your help. I'm standing on the hose about your suggestions..

I replace the "cookie path" config input with an page select like used on "privacy page" right?
Then I'm getting an id. But I can't use that id as $path in setcookie or am I missing something?
So I would then find the page by this id, and store the page path?
But then how to be "multilanguage compatible"?

Edited by Can
Link to comment
Share on other sites

  • 3 weeks later...


Sorry if I didn't speak clearly. I was talking about the banner, not the cookie itself. I don't need an option to modify the path of the consent cookie itself, so I would hardcode it to '/'. (To stay complete leave it as is.)

Much more interesting is to limit the display of the banner to a selectable page tree. Therefore an additional pagefield in the config could be useful. Lets call it pageTree.
You just need to add one line at the beginning of the renderCookieForm()  function.

 if($page->id != $this->pageTree && $page->parents->has(wire('pages')->get($this->pageTree)) == false) return;

An additional checkbox to include or exclude the parent page would complete this option.

  • Like 1
Link to comment
Share on other sites

Perhaps this new config field could be a Selector field ... :rolleyes:

//in MarkupCookieConsentConfig

                        'type' => 'Selector',
                        'name' => 'pageSelector',
                        'label' => __('Banner display limit'),
                        'description' => __('Define selectors, which limits the display of the banner to selected pages.'),
                        'columnWidth' => 100

// in function renderCookieForm()
    // we stop here when on admin pages except this modules config page (for demonstration) or out of pageSelector
        if(($page->template != 'admin' && wire('pages')->find($this->pageSelector)->has($page) == false) || ($page->template == 'admin' && $this->wire('input')->get->name != $this)) return;


  • Like 1
Link to comment
Share on other sites

Finally pushed version 0.3.0

which includes your code snippets @kixe thanks for that and a button to remove the cookie for easier development..

Please tell me if all is clear, especially about the new selector, I added a little note on how to include tree parent using just the selector inputfield..
Let me know how you guys like it.

Should I still keep both branches? master for legacy (without namespace) and devns for namespace?

  • Like 2
Link to comment
Share on other sites

  • 6 months later...

Hi all,

I'm using the current version of MarkupCookieConsent on PW 3.0.62, but it doesn't seem to work anymore (used to work fine a while ago). No error message whatsoever is displayed, but still no cookie is set (checked it in browser as well as on module's config page). The consent message isn't displayed either. I've already deleted/reinstalled the module two times.

Is anyone else experiencing the same problem? Suggestions?

Thanks a lot!


Link to comment
Share on other sites

  • 2 weeks later...

 @ngrmm just bumped the version to 0.3.2 including a little fix so it show up again, please let me know if it works :) 

@CalleRosa40 Just checked on pw 2.8.62 and 3.0.62, cookies are created as expected..have you checked console in dev tools? it should show something..and it could be interesting to check network tab in dev tools, too, to see if it actually sends the ajax request

  • Like 2
Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...


Does anyone have problems with the ProCache module? What happens is ProCache ignores the user choice when pressing the button "I have accept etc" and keeps popping up in every other page and in the page reload itself. I have asked on the ProCache forum and they redirect me here

Thanks for any help!

Link to comment
Share on other sites

  • 4 months later...

Hi. Nice module, seems to work pretty well.

A few suggestions about configuring/customising. I like to keep my css files to a minimum, so I'd like to move the styles to my site css file (rather than inserting it after the first <link>). But when I untick the 'inject modules stylesheet?' option, it removes classes from the markup and hides the top/bottom, dark/light options. How about keeping these options available and just letting the user know that the css must then be manually added to a stylesheet?
I've done modified my installation to do that and it works well.

Also, when I've changed the class prefix in the config file, I had to still manually change one class:
I changed Line 104 of the module.php file from

    $cookieConsentForm .= "<p class='mCCF__message'>";


    $cookieConsentForm .= "<p class='{$classPrefix}__message'>";

You may want to update that. Thanks again for the module.

Link to comment
Share on other sites

hey guys I'm sorry for being away for such a long time and am unfortunate to say that I'm not able to maintain any of my modules at the moment
as I'm not doing any php / pw at the moment myself and don't have a working php/mysql environment locally right now to do anything "quickly"

but I would be open and happy if someone else wants to take over any of my processwire modules, by any way, for example by transferring the repo to a new home to have it redirect old links, or you could just upload yourself and i'll include a message in my repo readme and here in the thread

@strandoo maybe you are interested in taking over? than you could easily include your suggestions which sound good :) or just publish yourself and I'll link yours (just a thought, no pressure of cause!)


  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...
  • 2 weeks later...


I just added this module (on ProcessWire 2.8.62), but somehow it ony shows up on the config page of the module.

I can't get it display at the front-end. Is there anything else then installing it?

Hope someone can help me on this.


Link to comment
Share on other sites

  • 4 weeks later...

I had a play with this last night ahead of the GDPR coming into effect and all looked good, except…

It appends the cookie to all forms on the site, so for example I have a Mailchimp sign up form and a contact form, they both get the cookie message appended, as well as at the bottom of the page. Is there a quick fix for this in the backend without having to dig into the templates/css?

Link to comment
Share on other sites

The banner is always displayed at the bottom of the page. You can limit the appearance to certain pages via module settings. e. g.


Do you use iframes for your forms? If yes, each iframe has its own body tag. The banner is prepended to each closing body tag. Disable the banner by module settings (using selectors) for the framed pages.

Link to comment
Share on other sites

On 4/11/2018 at 12:13 PM, Pete said:

I'm having similar issues to @palacios000 - it seems that ProCache sometimes messes with this. Seems fine on desktop at the moment but can't make the cookie stick on mobile?

At the end I used the cookie script from Iubenda... It works well and the client pays for it anyway!

Link to comment
Share on other sites

@Can first off; thanks for the awesome module, as Simon mentioned a few comments back, with the GDPR up and running now, it's been a great help in setting up cookies across multiple websites 🙂 cheers!

I have one specific question though – perhaps I'm not looking hard enough – but I have some domains set to internal forwarding. So these URLs will show the exact same at referdomain.com as on maindomain.com. But, as the cookieDomain field is set to maindomain.com, it keeps showing up on referdomain.com even after you accept. Is there a way to make an Array (or add multiple domains ins some other way), so all the referral domains are included for the cookieDomain? Or should I be looking in a different direction to fix this?

Curious to hear anyone's thoughts on this!

Link to comment
Share on other sites

For security reasons, a cookie can not be set for a different domain. There may be ways to trigger this, but this could open security holes. The cookie set by this module also applies to subdomains.

Link to comment
Share on other sites

@kixe thanks for the reply! Makes sense – I hadn't really thought about security holes before.

Do you have any idea how I could go about doing this? I guess I can't really set a Cookie for a URL that's forwarding right...if it was a hard redirect there wouldn't even be an issue. But as the URL will remain, I guess the Cookie-pop-up will stay put then, as it's actually asking to set a cookie for a different 'domain' (url) :s If anyone has tips...I would be very grateful.

Link to comment
Share on other sites

Set up a page which just return the cookie banner, put it in an iframe and add it to the other sites. You would have to change (loosen) the x-frame options in your .htaccess file of the framed page to get this work. All-in-all not the best solution.

Link to comment
Share on other sites

  • 4 months later...


and thank you for the plugin. I have just tested it and I have a few questions.

1. There seems to be an option to show a link to privacy policy. However, the link is not shown, only text and the button.

2. I've read that upcoming laws will require the website to set no cookies until the user accepts cookies in the banner. However, a wire cookie is set either way. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      Link to github.com:
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
  • Create New...