190e51a7da
Adds a QWeb PDF "Membership Card" report (85x54mm landscape, custom report.paperformat) showing the company logo, member name/ID, tier, and a QR code generated with the qrcode library (embedded as a base64 PNG via a non-stored res.partner.membership_card_qr compute field). The QR encodes a public verification URL built from ir.config_parameter's web.base.url. Adds the public GET /membership/verify/<member_id> controller: shows valid/expired/not-found with no personal data beyond name (and tier, for valid members) - internal states like 'invoiced'/'none' are deliberately reported as not-found so partial signup state isn't leaked. Adds the member portal: /my/membership (status/tier/expiry), /my/membership/ renew (finds or creates a draft renewal invoice, redirects to the existing portal invoice page), and /my/membership/card (PDF download) - plus a "Membership" entry card on the main /my portal home page. Since community_theme_base doesn't exist yet (that's Phase 6), the card uses res.company.logo rather than a theme setting - still brand-neutral, just resolved from the standard company record for now. Verified against a live Odoo 19 + Postgres 16 container, both via the test suite (12/12 tests: unit tests, HttpCase tests hitting the real verify endpoint for valid/expired/unknown IDs) and by hand end-to-end - created a tier and member over JSON-RPC, activated the membership, fetched the live /membership/verify/ page, and rendered the actual PDF card via /report/pdf/... (11.7KB single-page PDF, confirmed non-blank). Along the way, hit a third real Odoo 19 API change: res.users.groups_id was renamed to group_ids. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
3 lines
47 B
Python
3 lines
47 B
Python
from . import models
|
|
from . import controllers
|