[18.0][ADD] oca_search_engine, oca_vcp, oca_membership, oca_sponsor and [DEL] oca_custom, website_oca_sponsor#130
[18.0][ADD] oca_search_engine, oca_vcp, oca_membership, oca_sponsor and [DEL] oca_custom, website_oca_sponsor#130arnaudlayec wants to merge 72 commits into
Conversation
|
Hi @petrus-v, |
d38a75c to
ec3e833
Compare
f6e6e7b to
cb232a9
Compare
[18.0][MIG] Move sponsors mgt from 'website_oca_integrator' to 'oca_sponsor' [FIX] Request validation if blog post are updated by the sponsor itself
Rename "community" to "working gorup"
…or oca_sponsor and oca_membership [FIX] Add dependency shopinvader_base_url SE adaptation: avoid pushing "None" to search engine [FIX] Add/remove persons & company from index + clean code technical fixes
remove computation of industry_id from industry_ids Replace custom activity type with Teams activity (module 'mail_activity_team') + override the module to display the count of both Team & Personal activities in the Systray
[FIX] Finish fixing schema + fix all tests Last fixes (test & schemas)
- Small fix suggested in Sebastien's review - Fix some sync issue on ParentCompany & Country format - Switch of 'shopinvader_base_url' to 'base_url' [IMP] Simplify "can_be_published", and raise on bindings instead
[IMP] Change review logics based on Tasks mixin `html.field.history.mixin` [IMP] Add portal self-service for sponsor data update [IMP] Affiliated sponsorship
b991a85 to
0e092ce
Compare
|
|
||
|
|
||
| { | ||
| "name": "Membership Account Cut-Off", |
There was a problem hiding this comment.
start and end dates will be use for cutoff but this module has nothing related to cutoff, those date could be use for other purpose as well. I would suggest to rename it membership_start_end_date.
Why not to contribute it directly in vertical association repo ?
There was a problem hiding this comment.
Hello Pierre, you are right, I will do this in coming days
| @@ -68,6 +68,6 @@ WORKDIR /app | |||
| RUN python -m compileall . | |||
| ARG DISTRO | |||
| RUN --mount=type=cache,target=/root/.cache/uv,id=uv-${DISTRO} \ | |||
| uv sync --locked --no-dev | |||
| uv sync --no-dev | |||
There was a problem hiding this comment.
Why those change ?
As we build this images on test server and production server we want to ensure uv.lock est satify, use uv sync and versioned change in uv.lock should be a better approch
There was a problem hiding this comment.
It's just temporary and must be remove before going in production (to avoir conflict with the main branch we do not use the lock file in order to simplify the rebase).
|
@sebastienbeau : Will you create a new PR to install only oca_vcp? |
I am going to do it today |
This reverts commit 91794e6.
…nt_cutoff to OCA/vertical-association/membership_start_end_date
88c10c8 to
9673212
Compare
9673212 to
9bfb5e6
Compare
DRAFT
This big PR is part of RFQs 2 & 3 submitted by the OCA in ~Sept 2026.
It is a 1st "big" PR, focused on collecting the data for the website in Odoo and synchronizing it to a Search Engine (here, Typesense).
In more details:
oca_vcp:
oca_sponsor
oca_membership
oca_search_engine
oca_custom
website_oca_sponsor
Ping @sebastienbeau @bguillot @TumbaoJu