Planner is like web Tips : a data in a module. - Rename planner.planner to web.planner - Rename files according to guidelines - Remove planner_crm module - Make CRM depends on web_planner, and add its planner as crm data - Remove duplicate less style - Add 'active' boolean field on planner (to disabled them), and create planner backend views
11 lines
535 B
XML
11 lines
535 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<!-- Ensure that the portal user doesn't have access to any planner that is not designed for him -->
|
|
<record id="web_planner_rule_portal" model="ir.rule">
|
|
<field name="name">Portal Planner</field>
|
|
<field name="model_id" ref="model_web_planner"/>
|
|
<field name="perm_read" eval="1" />
|
|
<field name="domain_force">[('planner_application', '=', 'portal')]</field>
|
|
<field name="groups" eval="[(4, ref('base.group_public'))]"/>
|
|
</record>
|
|
</odoo> |