Skip to content

[FP][IMP] website_cookiefirst: Replace deprecated Cookiefirst functionality #1113

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 1 commit into
base: 18.0
Choose a base branch
from

Conversation

NICO-SOLUTIONS
Copy link
Member

@NICO-SOLUTIONS NICO-SOLUTIONS marked this pull request as ready for review July 1, 2025 14:47
@NICO-SOLUTIONS
Copy link
Member Author

@eugenios73
@matteoopenf
hey. sorry for bothering again.
we needed to cover www domains as well, which was considered up to now.
Are you willing to review the changes again?

@NICO-SOLUTIONS
Copy link
Member Author

@ioans73 added the fix in this existing fowardport.

Copy link
Contributor

@eugenios73 eugenios73 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@NICO-SOLUTIONS
Copy link
Member Author

@OCA/website-maintainers
can we merge this one please?

@pedrobaeza pedrobaeza added this to the 18.0 milestone Jul 10, 2025
@pedrobaeza
Copy link
Member

You have to squash commits and use proper commit message:

https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#commit-message

@pedrobaeza
Copy link
Member

And next time, it's better that you do only a pull request for one version, and when merged, then do the fw-ports, as if not, any change have to be propagated to each of the PRs, giving you more work, and adding noise to the email subscribers.

Copy link

@matteoopenf matteoopenf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

technical review is ok

@NICO-SOLUTIONS
Copy link
Member Author

NICO-SOLUTIONS commented Jul 10, 2025

And next time, it's better that you do only a pull request for one version, and when merged, then do the fw-ports, as if not, any change have to be propagated to each of the PRs, giving you more work, and adding noise to the email subscribers.

@pedrobaeza
ok. thanks for the hint. i am not 100% aware of the forward and backport mechanism. I will get into it...
Concerning the squashing. you mean the two commits inhere? The imp commit is already merged into 17.. thats why i ask.
and sorry for the noise.

@pedrobaeza
Copy link
Member

Yes, in this version 18, there's no need to keep both things as separated, as I understand that both belongs to the same concept: replace deprecated functionality. In 17, as one patch was already merged, there's no other solution than to add an extra commit, but here, we can keep the commit history clean.

@NICO-SOLUTIONS NICO-SOLUTIONS force-pushed the 18.0-fp-imp-website_cookiefirst_consent_js branch from f60f8bd to 0ea9a86 Compare July 10, 2025 09:49
- replace banner.js with new consent.js script using domain and identifier
- remove www. prefix from domain in cookiefirst script URL
- forward ported from V17 PR (OCA#1110 & OCA#1117)
@NICO-SOLUTIONS NICO-SOLUTIONS force-pushed the 18.0-fp-imp-website_cookiefirst_consent_js branch from 0ea9a86 to f746c2d Compare July 10, 2025 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants