Data-only deployment layer seeding TNCSC's branding (navy/orange/electric-
blue from the plan), 5 membership tiers in CAD (Individual $50, Family $80,
Student $20, Senior $30, Life $500 - the plan's own example figures;
update via Settings once TNCSC confirms real pricing), the
'TNCSC-{year}-{seq}' member-ID format, a Canadian (Ontario/HST) chart of
accounts via l10n_ca plus non-profit-specific accounts (Membership Dues/
Event/Sponsorship/School Fees/Donations Revenue, Deferred Event Revenue
liability, a Stripe clearing account) and a Donations journal, bilingual
EN/Tamil overrides of two membership email templates (Tamil text is a
best-effort draft only, explicitly flagged as needing native-speaker
review before go-live), five placeholder website pages (Home/About/Tamil
School/Sponsors/Contact), and TNCSC-named role groups (Board Admin,
Treasurer, Events Officer, School Coordinator, Teacher, Classifieds
Moderator) that imply the existing generic product-layer groups rather
than defining new permission logic.
Chasing the chart-of-accounts setup down to a genuinely working state
took real digging: setting company.country_id on a brand-new company
auto-schedules this Odoo build's own chart-template installer via a
precommit hook (res.company.install_l10n_modules), which races an
explicit try_loading('ca_2023', ...) call made in the same install
transaction and silently replaces its result afterwards (reverting
currency to USD, chart_template to 'generic_coa', and deleting the custom
accounts) - confirmed via raw SQL checks that the correct state exists
right up until the post_init_hook transaction commits, and is gone by the
time the install process exits. Since the precommit auto-trigger only
ever fires once per company (guarded by chart_template being unset), a
second call from a separate transaction is immune to the race. The fix:
the actual setup logic lives in an idempotent res.company._tncsc_setup_
accounting() method (models/res_company.py - a narrow, documented
exception to "no models" in the deployment layer, since cramming this
into a sandboxed ir.cron code string wasn't practical), called as a
best-effort from post_init_hook and guaranteed by a daily safety-net cron
que runs in its own transaction. Also hit two smaller, separate bugs on
the way: ir.cron code execution forbids direct attribute assignment
(STORE_ATTR) in its sandbox, and Html config_parameter fields must not be
wrapped in CDATA in data XML.
Verified end-to-end on a genuinely fresh database (not the long-lived dev
DB, which already has posted entries and correctly refuses a currency
change): installed tncsc_deployment alone, pulling in all 8 product
modules plus l10n_ca as dependencies, confirmed the post-install state via
raw SQL, manually triggered the safety-net cron and confirmed it reached
the fully-correct state (CAD, ca_2023, 355 accounts including all 7
custom ones, the Donations journal, tier products linked to the dues
account), confirmed the cron is idempotent on a second run, and ran the
full test suite (9/9 passing) with the same deterministic setup called
from the test transaction directly.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
53 lines
1.6 KiB
Python
53 lines
1.6 KiB
Python
{
|
|
'name': 'TNCSC Deployment',
|
|
'version': '19.0.1.0.0',
|
|
'category': 'Hidden',
|
|
'summary': 'Tamil Nadu Cultural Society of Canada - client configuration for the Community OS suite',
|
|
'description': """
|
|
TNCSC Deployment
|
|
==================
|
|
|
|
Deployment layer for the Tamil Nadu Cultural Society of Canada (TNCSC).
|
|
|
|
This module contains DATA ONLY - no models, no business logic. It seeds:
|
|
|
|
* Branding (Community OS Theme Base settings)
|
|
* Membership tiers and prices
|
|
* Chart of accounts and journals for a Canadian non-profit
|
|
* Bilingual (EN/Tamil) email template overrides
|
|
* Website pages
|
|
* User groups and access rules
|
|
|
|
All client-specific values (names, prices, colours, account codes, email
|
|
copy) live only in this module. It is exempt from the brand-leak CI check
|
|
that applies to the community_* product modules.
|
|
""",
|
|
'author': 'Metatroncube Software Solutions LLP',
|
|
'website': 'https://www.metatroncube.com',
|
|
'license': 'LGPL-3',
|
|
'depends': [
|
|
'community_theme_base',
|
|
'community_membership',
|
|
'event_qr_ticketing',
|
|
'community_school',
|
|
'community_classifieds',
|
|
'community_benefits',
|
|
'community_interac',
|
|
'community_portal',
|
|
'l10n_ca',
|
|
],
|
|
'data': [
|
|
'security/tncsc_roles.xml',
|
|
'data/res_company_data.xml',
|
|
'data/theme_data.xml',
|
|
'data/membership_data.xml',
|
|
'data/mail_template_overrides.xml',
|
|
'data/ir_cron.xml',
|
|
'views/website_pages.xml',
|
|
],
|
|
'demo': [],
|
|
'application': False,
|
|
'installable': True,
|
|
'post_init_hook': 'post_init_hook',
|
|
}
|