community_membership:
- Tiers get a fixed-term period (term_years), minimum age, a
proof-document flag, a family-member flag and a signup description.
- Members get first/last name (composing the contact name), month and
year of birth with computed age, board approval state with
approve/reject buttons, terms acceptance, a proof-of-eligibility upload
and an inline family members list. Birth date and proof document are
restricted to Membership Managers.
- Constraints: plausible birth year; a tier's minimum age is enforced
when the birth year is known.
- Fix pre-existing tests that collided with deployment-seeded tier codes
and member ID format.
tncsc_deployment:
- Five Yes/No eligibility questions from the tncsc.com registration form
(manager-only), shown in an Eligibility section of the member form.
- Tiers now match tncsc.com/membership-registration: Annual/Family $30,
Long-Term (10 yr) $250, Life $500, Senior Annual (65+) $15, Senior Life
(60+) $250, Student Annual $10 (CAD).
- 19.0.1.1.0 post-migrate rewrites existing tiers (noupdate data) and
archives the unused Individual tier.
scripts/migrate_wp_members.py maps WordPress levels to the new LONG and
SENLIFE tiers. .mcp.json (holds credentials) is now gitignored.
Verified on the local Docker stack: -u on tncsc_site ran the migration
cleanly, and a fresh install with --test-enable passed 32/32 tests for
community_membership and tncsc_deployment.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds the membership foundation: community.membership.tier (admin-configurable
tiers, each auto-creating a linked invoicing product), res.partner membership
fields (member ID, tier, state, family grouping, volunteer tracking), and a
res.config.settings page (org name, member-ID format, renewal offsets, portal
toggle) - all backed by ir.config_parameter so nothing is hardcoded.
Member IDs are generated on activation via a configurable format string
({year}/{seq}) resolved against an ir.sequence. Adds the Membership Manager
group/menu and views (tier list/form, partner form tab, list columns, search
filters, settings page).
Along the way, hit two real Odoo 19 API changes vs. older tutorials/docs:
res.groups.category_id was replaced by privilege_id -> res.groups.privilege,
and module settings pages now use the <app>/<block>/<setting> pattern
inherited from base.res_config_settings_view_form rather than raw divs.
Verified by upgrading the module against a live Odoo 19 + Postgres 16
container: installs clean, all 4 tests pass (tier->product creation, member
ID generation on activation, one-time/lifetime tiers never expire,
configurable ID format), and the module still installs cleanly for its
dependents (community_benefits, tncsc_deployment).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
