745e147de9
Only community_membership and community_school had application: True;
the other 6 product modules (community_benefits, community_classifieds,
community_interac, community_portal, community_theme_base,
event_qr_ticketing) had application: False despite being fully installed
and functional. Odoo's Apps screen filters to application=True by
default, so they were invisible there even though Technical > Installed
Modules showed them correctly - looked like they weren't installed.
Per the plan's own resellability rule ("each module is independently
installable and independently sellable"), every community_* product
module should be a discoverable Apps-grid entry. tncsc_deployment stays
application: False - it's the hidden client-config layer, not something
anyone browses to install on its own.
Verified on tncsc_site: -u upgrade picked up the flag for all 6, and the
site still serves every page (/, /about, /membership, /tamil-school,
/contact, /event) after the upgrade.
====================== Community OS Benefits ====================== Benefit centres / partner vendors offering member benefits, entitled per membership tier, with a redemption log. Installation ============ Install as any Odoo module. Usage ===== * Admins register benefit centres/vendors (``community.benefit.partner``) and the benefits they offer (``community.benefit``), each entitled to one or more membership tiers. * Members see the benefits their tier entitles them to at ``/my/benefits``; the public directory of participating centres is at ``/benefits``. * A benefit centre logs a redemption (``community.benefit.redemption``) after confirming the member is active via the membership QR-verify endpoint, giving a verifiable usage trail per member/benefit. Credits ======= Authors ------- * Metatroncube Software Solutions LLP