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 Event QR Ticketing =========================== Signed QR ticket per event registration, with a staff check-in and verification screen. Works standalone on a stock Community Edition event. Installation ============ Install as any Odoo module. Usage ===== * Every ``event.registration`` gets a unique ``ticket_ref`` and a QR code encoding a per-database-signed token, attached automatically to the standard CE registration confirmation email as a PDF ticket. * Staff check attendees in at ``/event/checkin/<event_id>`` (camera scan or manual ticket-ref entry, restricted to the Event User group). The scan endpoint verifies the token signature and rejects forged or already used tickets. * A per-event dashboard on the same page shows registered vs. checked-in counts in real time. Credits ======= Authors ------- * Metatroncube Software Solutions LLP