$ 53.43
Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Website (website)
• Discuss (mail) |
Lines of code | 120 |
Technical Name |
manatec_consent_manager_base |
License | OPL-1 |
Website | https://www.manatec.de |
Versions | 17.0 15.0 16.0 |
Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Website (website)
• Discuss (mail) |
Lines of code | 120 |
Technical Name |
manatec_consent_manager_base |
License | OPL-1 |
Website | https://www.manatec.de |
Versions | 17.0 15.0 16.0 |
Cookie Consent Manager Base
GDPR-compliant privacy settings for your website.
Consent Manager Interface
The main interface (see image below) gives your customers an overview of which personal information is processed. All non-essential settings can be approved or rejected here with a single click.
Consent Manager Settings
In the settings interface your customers can manage individual options.
Configuration
The web page settings in Odoo can be used to configure basic settings. These include the path to the privacy policy and the domain for the cookies. Both parameters can be set per website, making the module multi-webpage compatible. Furthermore, they can also be used in the context of customizing the module.
Please check after configuration if your cookies are really deleted and adjust your configuration again if necessary. You can use the developer console of your browser to find out which domain your cookies are stored with.
Customization
In the configuration file (static/src/js/klaro.config.js) the Consent Manager can be adjusted and customized.
Here you can, among other things, ...
- ... adjust the link to the privacy information.
- ... configure the consent to one or more additional cookie(s).
- ... adjust existing consent configurations for cookies.
- ... change all texts and descriptions.
- ... add or change a (new) language.
- ... add custom css classes for an individual look.
If the settings here are incorrect, it can happen that the Consent Manager is not displayed correctly and/or the cookies are not deleted correctly.
To support the individual configuration you can use the additional website dependent parameters "cookie domain" and "privacy url" from the website configuration in Odoo. These parameters can be accessed in the "klaro.config.js" file, making the consent manager multi website compatible.
A more detailed documentation of the settings and possibilities can be found in the Klaro-Documentation: .
FAQ
Do you provide free support for this module?
Support for installation, configuration or adjustment is not included in the purchase, only errors of the module will be fixed by us. If you need support please contact us and we will be happy to record and discuss your requirements as well as provide you with an individual offer.
Why are there different modules?
The "Consent Manager Base" module adds ony the basic functionality like the consent popup and the backend configuration menu. All other modules extend the basi module with specific functionality
Somethings is not working or cookies are not blocked as expected, what can I do?
Most problems are caused by a faulty configuration. Please check yours accordingly. Otherwise, please note the answer to the question "Do you provide free support for this module?".
I need to change the texts/consents/messages/styles/languages/… of the manager/banner/button/…, does this module allow me to do this?
Yes, see the section "Customization" and specifically the Klaro-Documentation for more details.
Is there a limit of questions or consents?
There is no limit. You can add or configure as many cookie consents as you like.
Is the module multi-website capable?
Yes, see the section "Customization" for more details.
Is it possible to block all cookies first and configure them later?
The module can only block cookies that are configured. Not configured cookies are allowed by default.
Which "Klaro" version are you using?
Currently version 0.7.18
Can I upgrade "Klaro" myself?
We only provide error and bug fixes for the provided version. If you upgrade "Klaro", you do so at your own risk.
Changelog
- Restructuring and Refactoring
- Migration to odoo 15 and Klaro version 0.7.18
- Fixed loading of klaro on specific sites that do not provide klaroDefault
- Fixed display of cookie consent manager settings if no website is selected
- Fixed inheritance implementation to prevent odoo unit tests from failing
- Fixed a problem where web pages could not be translated anymore.
- Module description improved.
- Klaro updated to version 0.6.3.
- Basic configuration added to website settings to enable multi website support.
- Initial release.
Contact & Support
Do you like this module?
Try out our other apps!
Challenges with this module, wishes for more functions or questions about Odoo? Contact us!
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module