Skip to content

[19.0][ADD] sale_portal_debranding: Remove Odoo branding from sale portal page#120

Merged
OCA-git-bot merged 1 commit intoOCA:19.0from
havmedia:19-add-sale-portal-debranding
Jan 17, 2026
Merged

[19.0][ADD] sale_portal_debranding: Remove Odoo branding from sale portal page#120
OCA-git-bot merged 1 commit intoOCA:19.0from
havmedia:19-add-sale-portal-debranding

Conversation

@jappi00
Copy link
Copy Markdown

@jappi00 jappi00 commented Jan 6, 2026

Created my first module for this issue #115 . I tried to follow all guidelines and I hope I did everything right.

What it does?

Replace all references, except to the docs for integrations, from the "Connect youre System" Modal on the sale portal page

@jappi00 jappi00 changed the title [ADD] sale_portal_debranding: Remove Odoo branding from sale portal page [19.0][ADD] sale_portal_debranding: Remove Odoo branding from sale portal page Jan 6, 2026
@jappi00 jappi00 force-pushed the 19-add-sale-portal-debranding branch from cb959a8 to 2067a19 Compare January 6, 2026 21:14
@jappi00
Copy link
Copy Markdown
Author

jappi00 commented Jan 6, 2026

Hello @pedrobaeza,

I'am not sure if I did anything wrong here and how I can progress from here. Maybe you can give me a hint?

Have a nice evening,

Jappi00

@pedrobaeza pedrobaeza added this to the 19.0 milestone Jan 7, 2026
@pedrobaeza
Copy link
Copy Markdown
Member

Hello @jappi00 it seems correct. Now, you have to find reviewers

https://odoo-community.org/page/review

You can review other PRs, and ask in exchange that they review yours.

Copy link
Copy Markdown
Member

@ljmnoonan ljmnoonan left a comment

Choose a reason for hiding this comment

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

Thank you for your work!

Honestly, I do think this should be a part of portal_debranding as it is already doing stuff similar to what this module does, so I would suggest opening a new PR as such.

Comment thread sale_portal_debranding/readmes/CONTRIBUTORS.md Outdated
Comment thread sale_portal_debranding/readmes/DESCRIPTION.md Outdated
Comment thread sale_portal_debranding/views/sale_portal_templates.xml Outdated
Comment thread sale_portal_debranding/views/sale_portal_templates.xml
Comment thread sale_portal_debranding/__manifest__.py Outdated
Comment thread sale_portal_debranding/__manifest__.py Outdated
Comment thread sale_portal_debranding/__manifest__.py Outdated
@jappi00
Copy link
Copy Markdown
Author

jappi00 commented Jan 14, 2026

Thank you for your work!

Honestly, I do think this should be a part of portal_debranding as it is already doing stuff similar to what this module does, so I would suggest opening a new PR as such.

Was my first idea too. But that module do not depend on sale. We would take away the possibility to use the portal debranding module for users which only use purchase and not the sale module.

@jappi00
Copy link
Copy Markdown
Author

jappi00 commented Jan 14, 2026

And @ljmnoonan, thanks for the review. I appreciate it! I’ll update it shortly.

@ljmnoonan
Copy link
Copy Markdown
Member

But that module do not depend on sale. We would take away the possibility to use the portal debranding module for users which only use purchase and not the sale module.

Ahh, I see. I wonder if there is a way to make a view "optional" and not crash everything if it does not find its parent. I'll have to look into it

@jappi00 jappi00 force-pushed the 19-add-sale-portal-debranding branch 3 times, most recently from 9d25f99 to a7deb37 Compare January 14, 2026 23:56
@jappi00
Copy link
Copy Markdown
Author

jappi00 commented Jan 15, 2026

But that module do not depend on sale. We would take away the possibility to use the portal debranding module for users which only use purchase and not the sale module.

Ahh, I see. I wonder if there is a way to make a view "optional" and not crash everything if it does not find its parent. I'll have to look into it

I don't think so but it would be a good thing since we have the exact same modal on purchase and this would mean we would need one more module. Maybe we could autoinstall those modules with the portal debranding?

@jappi00 jappi00 force-pushed the 19-add-sale-portal-debranding branch 2 times, most recently from bc4a7b8 to 3fe02b5 Compare January 15, 2026 00:04
@pedrobaeza
Copy link
Copy Markdown
Member

This module should be an extra one, as the base one can't depend on sale.

@jappi00 jappi00 force-pushed the 19-add-sale-portal-debranding branch from 3fe02b5 to 6b9c85a Compare January 15, 2026 00:19
@jappi00
Copy link
Copy Markdown
Author

jappi00 commented Jan 15, 2026

@ljmnoonan Sorry, I strugeled a little bit with pre-commit. I hope I solved everything. Not sure if the more defined xpath / view is good. Was a little bit hard to find a good way for targeting the right elements.

@jappi00 jappi00 requested a review from ljmnoonan January 15, 2026 00:22
Copy link
Copy Markdown
Member

@ljmnoonan ljmnoonan left a comment

Choose a reason for hiding this comment

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

Functional test is good!
A few nitpicks which you can ignore if you want :)

Comment thread sale_portal_debranding/readme/CONTRIBUTORS.md Outdated
Comment thread sale_portal_debranding/readme/DESCRIPTION.md
@jappi00 jappi00 force-pushed the 19-add-sale-portal-debranding branch 2 times, most recently from 650bf0b to 2d0b2d6 Compare January 15, 2026 21:18
@jappi00 jappi00 force-pushed the 19-add-sale-portal-debranding branch from 2d0b2d6 to 3512889 Compare January 15, 2026 22:07
@jappi00
Copy link
Copy Markdown
Author

jappi00 commented Jan 15, 2026

Functional test is good!
A few nitpicks which you can ignore if you want :)

Fixed those. 🫡

@jappi00 jappi00 requested a review from pedrobaeza January 16, 2026 09:48
Copy link
Copy Markdown
Member

@pedrobaeza pedrobaeza left a comment

Choose a reason for hiding this comment

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

Congratulations on your first module!

/ocabot merge nobump

@OCA-git-bot
Copy link
Copy Markdown
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 19.0-ocabot-merge-pr-120-by-pedrobaeza-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 3148c5f into OCA:19.0 Jan 17, 2026
7 checks passed
@OCA-git-bot
Copy link
Copy Markdown
Contributor

Congratulations, your PR was merged at fd201e1. Thanks a lot for contributing to OCA. ❤️

@jappi00
Copy link
Copy Markdown
Author

jappi00 commented Jan 17, 2026

Yeah! Thanks @pedrobaeza @ljmnoonan for helping and fixing my stupid misstakes! <3

Have a nice weekend.

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.

4 participants