bd9b449ded
shared/DEMO_SCRIPT.md's cast table names six logins. Two - the parent and student portal accounts - were created in mc_education_portal. The other four (Principal, Front Office, Teacher, Accountant) were explicitly punted to O9: mc_education_base's demo/mc_teacher_demo.xml says outright "res.users/login creation is O9's job (demo rehearsal), not this base module." That job was never actually done - found only now, while writing a demo handbook that needed to print real, working credentials and I checked them against a live container before printing anything. Concretely this means a from-scratch rehearsal of the demo script would have stalled at Scene 1: there was no way to log in as Rekha Nair, Sunitha R, or David Fernandes at all, and logging in as "Arun Prakash" would have meant either sharing the admin account or creating an unlinked user that fails Scene 4's actual point - a teacher seeing only their own batch, which the attendance record rule resolves through batch_id.class_teacher_id.user_id. Arun's login is now attached to the same hr.employee record mc_education_base's own demo data already made Grade 8-A's class teacher, not a fresh one. Real Odoo behaviour learned fixing this, worth recording since it will bite again: demo data loads with noupdate=True so a school's own edits survive a later module update, and that guard is checked by xmlid, not by which file is doing the writing - a <record> in this module trying to set an existing mc_education_base demo record's field was silently skipped, no error, nothing in the log. <function> calls the ORM directly and is the correct tool, but carries the same guard one level up in Odoo's loader (convert.py's _tag_function skips entirely unless the module is being freshly installed, mode == 'init' - an update on an already-installed database is a no-op). That is exactly the real story this product cares about (a clean machine, installing the whole suite once), so it's the right fix going forward - verified on a from-scratch install of all nine modules together. The one already-running database that had this module installed before this fix existed needed a one-off manual correction outside the codebase, not a workaround inside it. Added a regression test asserting all four logins exist in the right group and that Arun's employee record and Grade 8-A's class_teacher_id actually resolve to the same person - not just "a teacher login exists somewhere." Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
25 lines
936 B
Python
25 lines
936 B
Python
{
|
|
"name": "School ERP - Theme",
|
|
"version": "19.0.1.0.0",
|
|
"category": "Education",
|
|
"summary": "Per-company branding; hides Odoo/ERPNext branding the demo audience would see.",
|
|
"author": "Metatroncube Software Solutions LLP",
|
|
"license": "Other proprietary",
|
|
# portal is a real, necessary dependency this module's own spec line
|
|
# ("Depends: mc_education_base") missed: hiding the "Powered by Odoo"
|
|
# text (views/portal_branding_templates.xml) means inheriting
|
|
# portal.portal_record_sidebar, which requires the portal module to
|
|
# be loaded. Flagging per CLAUDE.md's closing instruction rather than
|
|
# silently working around it.
|
|
"depends": ["mc_education_base", "portal"],
|
|
"data": [
|
|
"views/portal_branding_templates.xml",
|
|
],
|
|
"demo": [
|
|
"demo/mc_theme_demo.xml",
|
|
"demo/mc_cast_users_demo.xml",
|
|
],
|
|
"installable": True,
|
|
"application": False,
|
|
}
|