Thibault Delavallée
269ff99f24
proposal. Instead of posting a chatter message with the post data + storing a blob on the track store directly the various data on the track object itself. Post a message on the event to warn a new track has been created. Updated the track website view. Instead of storing a blob, rebuild a correct and editable track view on the website.
28 lines
997 B
XML
28 lines
997 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<openerp>
|
|
<data noupdate="1">
|
|
|
|
<record id="event_sponsor_type1" model="event.sponsor.type">
|
|
<field name="name">Bronze</field>
|
|
<field name="sequence">3</field>
|
|
</record>
|
|
<record id="event_sponsor_type2" model="event.sponsor.type">
|
|
<field name="name">Silver</field>
|
|
<field name="sequence">2</field>
|
|
</record>
|
|
<record id="event_sponsor_type3" model="event.sponsor.type">
|
|
<field name="name">Gold</field>
|
|
<field name="sequence">1</field>
|
|
</record>
|
|
|
|
<!-- Event-related subtypes for new track / Chatter -->
|
|
<record id="mt_event_track" model="mail.message.subtype">
|
|
<field name="name">New Track</field>
|
|
<field name="res_model">event.event</field>
|
|
<field name="description">New Track Created</field>
|
|
<field name="default" eval="False"/>
|
|
</record>
|
|
|
|
</data>
|
|
</openerp>
|