Can

MarkupCookieConsent

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 ;)

Quote

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

Share this post


Link to post
Share on other sites

@Can

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

Share this post


Link to post
Share on other sites

Perhaps this new config field could be a field for entering a selector, that would allow more flexibility.

  • Like 3

Share this post


Link to post
Share on other sites

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

//in MarkupCookieConsentConfig

                    array(
                        '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

Share this post


Link to post
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

Share this post


Link to post
Share on other sites

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!

Michael

Share this post


Link to post
Share on other sites

Could you solve it?

Have you tried disabling ajax?

I'm really short on time at the moment :/

Share this post


Link to post
Share on other sites

hi @Can

i installed the module. it's working at the back-end but doesn's show up on front-end.
do i have to embed it manually in templates?

PW 2.8.35

Share this post


Link to post
Share on other sites

 @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

Share this post


Link to post
Share on other sites

Thanks for this module!

I seem to have a problem with it though...

I accept the cookie on my homepage, but then on other pages it asks for cookie consent again.

I tried with and without ajax, still this message keeps coming back.

How can I fix this?

Thanks

Share this post


Link to post
Share on other sites

Hello,

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!

Share this post


Link to post
Share on other sites

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'>";

to 

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

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

Share this post


Link to post
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!)

greets

  • Like 1

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

Hello,

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.

Regards
Bacelo

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
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.

1264856490_Bildschirmfoto2018-05-18um19_48_30.thumb.jpg.85ad6cc8befeb6e2edd6b97a1bc55bc7.jpg

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.

Share this post


Link to post
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!

Share this post


Link to post
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!
 

Share this post


Link to post
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.

Share this post


Link to post
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.

Share this post


Link to post
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.

Share this post


Link to post
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 Macrura
      Field Descriptions Extended
      This module enables you to extend field descriptions by dividing short descriptions with a longer text that is revealed in a toggle.
      Modules Directory: http://modules.processwire.com/modules/field-descriptions-extended/
      Github: https://github.com/outflux3/FieldDescriptionsExtended
      Extending your field descriptions using the standard field's description field.
      Once this module is installed, it will automatically search your description field for the presence of 5 dashes (-----).
      Any content above the 5 dashes will be visible and the content below the dashes will be hidden. A 'More...' link will appear at the end of the short description which when clicked will reveal the rest of the description.
      Using Simple Markdown Editor with the description field
      If you have Simple Markdown Editor (InputfieldSimpleMDE) installed, you can enable the field description to have that editor.
      *When using Simple MDE, you can use the button (Insert Horizontal Line) instead of typing 5 dashes. More about SimpleMDE.
      Extending your field descriptions using content from a ProcessWire Page for the field description.
      You may use the content from a ProcessWire page as a field description. This would allow you to easily insert images, links, and use hanna codes.
      To use page content for your field descriptions, please follow these instructions:
      Install Select Fields module (FieldtypeFields) http://modules.processwire.com/modules/fieldtype-fields/ Create a new field using this field type, e.g. field_select. Add the field to any template you will be using for your field descriptions. Setup your help pages (for example under a settings branch) where you will store the field description content,using the template containing the Field Select. Add content to a page and select the field where that content should show. To show a short text before the link to the longer content, separate them with 5 dashes Be sure to update your settings on this page, first enable page content descriptions,then specify the name of the Select Fields field, template to search, and content field. If you create a field description using this method, please note that the description field must be blank for contexts where you want the page content to appear.
      You can freely use template context for field descriptions, but the Page Content method is not context sensitive and will display under all contexts where the description is blank.
      ----
      original post:
      This is a new module, hope to release soon, which allows extended field descriptions, in currently 2 ways.
      The main feature of the module is that you can have a short description and then a 'more...' link which drops down a longer block of text.
      This is achieved by separating the intro/visible text and the rest with 5 dashes.

      Example setup:

      the 2nd way is if you are using AdminThemeUiKit, you can show extended field instructions in a panel. The content of the panel is edited on a regular PW page. This use case would probably not be that common, but if you had a field that required some extended instructions for how to use, this could be useful; Also, since this allows you to target information and instructions down at the field level, it could reduce the amount of documentation needed on a global level, since it is a lot more context targeted.

    • By Robin S
      Breadcrumb Dropdowns
      Adds dropdown menus of page edit links to the breadcrumbs in Page Edit.

      Installation
      Install the Breadcrumb Dropdowns module. The module requires ProcessWire >= v3.0.83 and AdminThemeUikit.
      There is a checkbox option in the module config that determines if the breadcrumb dropdowns will include pages that the user does not have permission to edit.
      Features/details
      The module adds an additional breadcrumb item at the end for the currently edited page. That's because I think it's more intuitive for the dropdown under each breadcrumb item to show the item's sibling pages rather than the item's child pages. In the dropdown menus the current page and the current page's parents are highlighted in a crimson colour to make it easier to quickly locate them in case you want to edit the next or previous sibling page. If the option to include uneditable pages is selected then those pages are indicated by a reduced text opacity and the "not-allowed" cursor is shown on hover. There is a limit of 25 sibling pages per dropdown for performance reasons and to avoid the dropdown becoming unwieldy. Incompatibilities
      This module replaces the AdminThemeUikit::renderBreadcrumbs method so will potentially be incompatible with other modules that hook the same method.
       
      https://modules.processwire.com/modules/breadcrumb-dropdowns/
      https://github.com/Toutouwai/BreadcrumbDropdowns
    • By joshuag
      Hey guys, 
      Thought I would share a quick preview of Designme. A module we (Eduardo @elabx and I) are building for visually laying out your templates/edit screens. 🙂
      This is a really quick, zero polish screen grab. FYI. 
      Video #2 - UPDATE
      This new video shows the following features in Designme:
      Re-arranging fields via Drag & Drop Re-sizing fields via Dragging. Adjusting field settings - with live refresh. Working on "hidden" fields while Designme is active. Creating New fields. Deleting fields. Creating/Deleting Tabs. Dragging fields between tabs. Creating fieldsets. Tagging/Un-tagging fields. Fields without headers expand when hovered (like checkboxes). Live filtering of fields in the sidebar. Ability to adjust (all) Template settings without leaving Designme. Template File Tree Editing Template files source code with ACE Editor. Editing Multiple files with ACE Editor. (New Tabs) Saving files. Techie stuff Fields load their own js/css dependancies. *ready to use on creation (*most fields)  Everything happens via Ajax to ProcessPageEdit (via module + hooks). Designme has a JS api that you can use.  All actions trigger events.  We would love any detailed feedback on what you see so far. If you are interested in testing Designme. Let me know below. 🙂
       
       
      Video #1. 
       
    • By dreerr
      TemplateEnginePug (formally TemplateEngineJade)
       
      This module adds Pug templates to the TemplateEngineFactory. It uses https://github.com/pug-php/pug to render templates.
      doctype html html(lang='en') head meta(http-equiv='content-type', content='text/html; charset=utf-8') title= $page->title link(rel='stylesheet', type='text/css', href=$config->urls->templates . 'styles/main.css') body include header.pug h1= $page->title if $page->editable() p: a(href=$page->editURL) Edit Project on GitHub: github.com/dreerr/TemplateEnginePug
      Project in modules directory: modules.processwire.com/modules/template-engine-pug/
       
      For common problems/features/questions about the Factory, use the TemplateEngineFactory thread.
       
    • By tpr
      ProcessNetteTester
      Run Nette Tester tests within ProcessWire admin.
      (continued from here)

      Features
      AJAX interface for running Nette Tester tests, in bulk or manually display counter, error message and execution time in a table run all tests at once or launch single tests show formatted test error messages and report PHP syntax errors stop on first failed test (optional) hide passed tests (optional) display failed/total instead passed/total (optional) re-run failed tests only (optional) auto scroll (optional) include or exclude tests based on query parameters start/stop all tests with the spacebar reset one test or all tests (ctrl+click) https://modules.processwire.com/modules/process-nette-tester/
      https://github.com/rolandtoth/ProcessNetteTester