About Markup Cookie Consent
Renders cookie consent information for EU-Cookie-Law
|Category 1||Markup Generation|
Markup modules that are called upon to generate or parse markup (like HTML). Markup modules are most often used on the front-end of a site (rather than admin).
Modules designed to help site accessibility, standards compliance and SEO.
Close to stable, but users are advised to be cautious and test thoroughly.*
|Date Added||February 21, 2016|
|Last Updated||January 10, 2019|
This module's files should be placed in /site/modules/MarkupCookieConsent/
How to install or uninstall modules
ProcessWire >= 2.8.15Haven't tested it myself on pw 2.8, and actually don't even know if there is 2.8.15. Thing is, it depends on this fix which was applied right before pw 3.0.16.
This repo now includes a devns branch. Which is not a development version of this module, but rather meant to be used with Processwire 3.x devns as the only difference is the added namespace and therefore the requires flag in module info.
Not widely tested, and config inputs already look like they're translatable but they're actually not yet saving! Thanks to Ryan the newest PW 3.0.15 devns fixes this issue
Make sure to remember any settings! Please remove module and then install fresh copy of newest version. Or update to latest version, then disable and enable module.
The module only checks for minified style and script so if you make any changes either minify yourself and name file MarkupCookieConsent.min.css / MarkupCookieConsent.min.js or disable auto injection in settings and include them yourselfSo the non-minified versions are only for development. Minified CSS & JS have been added in version 0.1.2.
If you want to use your own stylesheet or merge MarkupCookieConsent styles with another stylesheet just uncheck moduleStyles.If you want to use a custom CSS class prefix you can modify it by adding the following code line to your ready.php.
$modules->get('MarkupCookieConsent')->classPrefix = 'CSSCustomPrefix';
This module is intended to add a little cookie notice to your front-end. It's doing this by hooking into page render and altering the output to include the form at the end of the page (right before </body>).
- AJAX (deactivatable, JS disabled users will fall back to normal form submit with page reload, so fully functional without JS)
- 2 themes (dark/light)
- 2 positions (top/bottom)
- customizable texts, message and button label
- prepend / append custom text/markup to the button e.g. Font Awesome Icon like in the screenshot
- selector field to limit banner to certain pages
- fully customizable cookie settings (name, lifetime, domain, path, secure, HTTPonly)
- you wanna roll your own design? Just disable default stylesheet
You can enter the class name MarkupCookieConsent in your back-ends module configs and it will download automaticallyor get from Processwires module directory or Github and install it by unzipping and moving into your /site/modules/ folder or selecting the zip from your back-ends modules page.
- 0.3.3 - CSS class prefix sustainably implemented,removed dependence between stylesheet-autoinjection and CSS classes
- 0.3.2 - fix banner not showing on front end if no page selector provided
- 0.3.0 - add display limit selector field to define limit the banner to certain pages, added "remove cookie" button, removed cookie path setting
- 0.2.0 - fixed version issue and misleading cookie expiration setting
- 0.1.6 - added custom privacy url as requested by kixe, fixed custom link target, appended query string "accept=cookies" to form action for cached non ajax requests
- 0.1.5 - fixed issue on single language installations
- 0.1.4 - Cookie notification now completely translatable in front-end
- 0.1.2 - Added minified CSS & JS files
- 0.1.1 - Fixed issue with cookie not being set, two strings wouldn't recognize translation, default cookie expire now 1 year, updated readme, removed deprecated branch
- 0.1.0 - Missing strings now translatable
- 0.0.9 - Changed style injection, now prepends to first in head makes it easier to add custom css tweaks without the need for !important because of the cascading order
No comments yet. Be the first to post!
Your e-mail is kept confidential and not included with your comment. Website is optional.
- Admin Helpers
- Core Modules
- Development Tools
- Field Types
- Input Fields
- Language Modules
- Language Packs
- Markup Generation
- Premium Modules
- Process Modules
- Proof of Concept
- Site Profiles
- Social, Feeds, Services
- Text Formatters
- Other Modules
- Users and Access
*Use modules at your own risk. There are no guarantees or warranties. It is recommended that you backup your site and database before installing new modules.