summaryrefslogtreecommitdiff
path: root/addons/event/security/ir.model.access.csv
diff options
context:
space:
mode:
authorThibault Delavallée <tde@odoo.com>2020-01-17 12:57:52 +0000
committerThibault Delavallée <tde@odoo.com>2020-01-30 15:18:08 +0000
commit6b09c1b8c62fc8b5bbd210d4759561ec67269155 (patch)
treedc94f8c1f2922bf05762a7a4cfadb5dd1214195d /addons/event/security/ir.model.access.csv
parentec121565ccc5b9ab42bf381db15a08c98e76afba (diff)
[REF] event: move ticket definition from event_sale to event and use ticket templates
PURPOSE Integration between event and eCommerce is required only when users handle the entire selling process online. However users may require ticketing support while managing payments outside of Odoo. Purpose of this commit is to support tickets directly in event application without need of sales. RATIONALE Remove the need to have event_sale installed to manage basic multi ticket event type. Integration with eCommerce is needed only when one wants to handle the entire selling flow online, i.e. order, payment, ... Integration with Sales is needed only when one wants to create sale orders linked to attendees. Many event users do not need all of this. Their attendees pay through bank transfers or they simply manage payments outside of Odoo while still requiring tickets management. SPECIFICATIONS Remove the need to have event_sale installed to manage basic ticketing on events. Move ticket model (event.event.ticket) directly into event, copying most fields from event_sale. Only sale specific fields and behavior should be kept in event_sale : * keep product_id and price information in event_sale; * keep sales analysis in event_sale; We also split tickets model used for event type (event.type.ticket) and events (event.event.ticket). Indeed previously to this commit both are modeled in the same table, with the following issues : * tickets on templates use only a subset of fields: name, seats availability, product, price; * a ticket has either an event_id, either an event_type_id, and there are constraints to try to avoid having lost tickets. This leads to a strange model where m2o fields are required only in some cases with a dual behavior; * tickets are not shared between event.type and event.event. They are copied and having a single model is therefore not necessary; We therefore choose to have a light model for event.type.ticket. It is linked to event.type when configuring template tickets. They are copied in the onchange copying event template configuration to the event itself, leading to event.event.ticket creation. Some tests are moved / completed accordingly. Access rights are copied from website_event_sale to website_even concerning ticket access for public / portal. Currently they are kept as they are with some rewording as it is not the purpose of this commit to rewrite them. LINKS Task ID 2177281 Community PR odoo/odoo#43488
Diffstat (limited to 'addons/event/security/ir.model.access.csv')
-rw-r--r--addons/event/security/ir.model.access.csv4
1 files changed, 4 insertions, 0 deletions
diff --git a/addons/event/security/ir.model.access.csv b/addons/event/security/ir.model.access.csv
index d00f94350cc..9d680924f5d 100644
--- a/addons/event/security/ir.model.access.csv
+++ b/addons/event/security/ir.model.access.csv
@@ -1,9 +1,13 @@
id,name,model_id:id,group_id:id,perm_read,perm_write,perm_create,perm_unlink
access_event_type,event.type,model_event_type,event.group_event_user,1,0,0,0
access_event_type_manager,event.type manager,model_event_type,event.group_event_manager,1,1,1,1
+access_event_type_ticket,event.type.ticket.user,model_event_type_ticket,event.group_event_user,1,0,0,0
+access_event_type_ticket_manager,event.type.ticket.manager,model_event_type_ticket,event.group_event_manager,1,1,1,1
access_event_event_portal,event.event.portal,model_event_event,,1,0,0,0
access_event_event_user,event.event.user,model_event_event,event.group_event_user,1,0,0,0
access_event_event_manager,event.event.manager,model_event_event,event.group_event_manager,1,1,1,1
+access_event_event_ticket_user,event.event.ticket.user,model_event_event_ticket,event.group_event_user,1,0,0,0
+access_event_event_ticket_manager,event.event.ticket.manager,model_event_event_ticket,event.group_event_manager,1,1,1,1
access_event_registration,event.registration,model_event_registration,event.group_event_user,1,1,1,1
access_event_registration_employee,event.registration,model_event_registration,base.group_user,1,0,0,0
access_event_registration_portal,event.registration,model_event_registration,base.group_portal,1,0,0,0