<a class="reference external image-reference" href="https://itpp.dev"><img alt="Tested and maintained by IT Projects Labs" src="https://itpp.dev/images/infinity-readme.png" /></a> <a name="customer-event-portal"></a> <h2>Customer Event Portal</h2> <p>Allows to customers see tickets for events at Portal.</p> <ul class="simple"> <li>Only confirmed tickets with attendee_partner_id as current user are shown</li> </ul> <p>Additional features:</p> <ul class="simple"> <li>Ticket transferring feature<ul> <li>To decrease chance of transferring to a wrong email, partner with the email must exist before transferring.</li> <li>New <em>When to Run</em> values for Email Schedule:<ul> <li>transferring_started</li> <li>transferring_finished</li> </ul> </li> <li>New attendee receives email with a link to finish ticket transferring</li> </ul> </li> <li>Tracks changes in key registration fields (via <code>track_visibility='onchange'</code>)</li> <li>Tickets can be changed to other products (including other tickets)<ul> <li>When old ticket is canceled, a message with a reference to new Sale Order is posted</li> </ul> </li> </ul> <a name="relation-to-other-modules"></a> <h3>Relation to other modules</h3> <a name="website-event-refund"></a> <h4>website_event_refund</h4> <p>Ticket refunding feature based on <code>website_event_refund</code> module</p> <a name="website-event-attendee-signup"></a> <h4>website_event_attendee_signup</h4> <p>It's recommended to use the module with <code>website_event_attendee_signup</code> which creates user for each attendee on registration.</p> <a name="website-event-attendee-fields"></a> <h4>website_event_attendee_fields</h4> <p>We need this modules for autofill feature. Other features of the modules are optional.</p> <a name="website"></a> <h4>website</h4> <p>The module is not splitted in two where one doesn't depend on website how it's usually done (e.g. <code>portal_event_tickets</code> and <code>website_portal_event_tickets</code>), because since 11.0 there is no such separation.</p> <a name="event-sale"></a> <h4>event_sale</h4> <p>We don't split module in two where one doesn't depend on <code>event_sale</code> (e.g. <code>portal_event_tickets</code> and <code>portal_event_tickets_sale</code>) for following reasons:</p> <ul class="simple"> <li>it simplifies development and maintainance</li> <li>we don't consider portal module without <code>event_sale</code> as popular</li> <li>free events are still usable even if <code>event_sale</code> module is installed</li> </ul> <a name="portal-event"></a> <h3>portal_event</h3> <p><code>portal_event</code> should be more proper name for this module, but it's occupied by repository odoo/odoo and which makes it impossible to use it in odoo apps store.</p> <a name="questions"></a> <h3>Questions?</h3> <p>To get an assistance on this module contact us by email :arrow_right: <a class="reference external" href="mailto:help&#64;itpp.dev">help&#64;itpp.dev</a></p> <a name="contributors"></a> <h3>Contributors</h3> <ul class="simple"> <li><a class="reference external" href="https://it-projects.info/team/yelizariev">Ivan Yelizariev</a></li> </ul> <a name="further-information"></a> <h3>Further information</h3> <p>Odoo Apps Store: <a class="reference external" href="https://apps.odoo.com/apps/modules/10.0/portal_event_tickets/">https://apps.odoo.com/apps/modules/10.0/portal_event_tickets/</a></p> <p>Tested on <a class="reference external" href="https://github.com/odoo/odoo/commit/6c1c1f6e9e03322771169b920d3c14c5e33111e9">Odoo 10.0</a></p>