1b473a78737009326da66b45002dba04233bfc24
Two bugs caught by entech battle test on first deploy: 1. Manifest entry landed in the 'demo' list instead of 'data' because my anchor (fp_demo_shopfloor_data.xml) was already in 'demo' — the entry pattern-matched into the wrong section. Demo data doesn't load on entech (no --load demo), so the mail.template never existed. Moved fp_tablet_pin_reset_template.xml to 'data'. 2. The fp.notification.template wrapper record referenced a model that doesn't exist until fusion_plating_notifications loads; fusion_plating_shopfloor doesn't depend on notifications, so the data load ParseError'd. Removed the wrapper — the controller calls mail_template.send_mail() directly anyway, not via the notification dispatcher. Added an inline comment explaining why the wrapper isn't here. Battle test updated to drop the (now removed) wrapper xmlid check. Battle test ALL PASS on entech after fixes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Description
Odoo 19 custom modules
Languages
Python
56.7%
HTML
25.2%
JavaScript
14.8%
SCSS
2.1%
CSS
0.8%
Other
0.3%