Skip to content

[18.0][MIG] website_cookiebot: Migration to 18.0 #1093

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 12 commits into
base: 18.0
Choose a base branch
from

Conversation

StefanRijnhart
Copy link
Member

  • Align config layout with similar settings on the same page
  • Renew screenshot in description

antonio-trey and others added 12 commits March 10, 2025 14:00
- Reorganize templates.
- Make templates noupdate=0, because if user edits them, it will be in the COW'd, website-specific version, so no problem on that.
- Rename `cookiebot_id` to `cookiebot_dgid` to avoid confusion with X2many fields.
- Remove ICP support, as the DGID should be per website.
- Add ID placeholders to Cookie Declaration page editable sections.
- Ensure Google Analytic script is blocked before consenting statistics. FTR it wasn't actually being blocked.
- Improve instructions.
- Split README.
- Apply pre-commit.

@Tecnativa TT32828
Currently translated at 100.0% (13 of 13 strings)

Translation: website-16.0/website-16.0-website_cookiebot
Translate-URL: https://translation.odoo-community.org/projects/website-16-0/website-16-0-website_cookiebot/es/
If we don't remove the key the assets will keep trying to load, which
isn't what we'd expect.

TT50520
* Align config layout with similar settings on the same page
* Renew screenshot in description
@StefanRijnhart StefanRijnhart force-pushed the 18.0-mig-website_cookiebot branch from 6ba9bf6 to ce77ae6 Compare March 10, 2025 14:52
@pedrobaeza
Copy link
Member

/ocabot migration website_cookiebot

@OCA-git-bot OCA-git-bot added this to the 18.0 milestone Mar 10, 2025
@OCA-git-bot OCA-git-bot mentioned this pull request Mar 10, 2025
8 tasks
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.