Support

October 31, 2016 at 7:12 am

Hi Atharveda,

The ticket details are output using the ticket selector template, its possible to load a custom version of the template however there is a lot of logic within the ticket selector so loading your own template means you will need to make sure you keep up to do with any changes we make within the default template in your own template.

Because loading your own template you could hide some details using CSS, or there is also some options within:

Event Espresso -> Events -> Templates -> Ticket Selector Template Settings

That allows you to remove some sections.

Can you let us know what it is your trying to change within the details section?

November 1, 2016 at 3:34 pm

I think “Ticket Selector Template Settings” will apply on all the events. Is there some way to control it per event basis?

Currently you can not control this per event without some custom development.

Is there someway to show just the ticket description & hide everything else?

You could hide the sections using some CSS, for example:

.tckt-slctr-tkt-price-sctn, 
.tckt-slctr-tkt-sale-dates-sctn, 
.tckt-slctr-tkt-datetimes-sctn {
    display: none;
}

Will hide all of the other sections.

Would that work?

To give you an idea of the how complex the ticket selector template is you can take a look within:

\event-espresso-core-reg\modules\ticket_selector\templates\ticket_selector_chart.template.php

The template location is filterable which mean you can load your own version of the template, it is also passed the EE_Event object meaning you could also change this depending on the event it needed (although it would likely be better to add the logic within the template).

The filter that allows you to change the ticket selector template location is:

apply_filters( 'FHEE__EE_Ticket_Selector__display_ticket_selector__template_path', $templates['ticket_selector'], self::$_event );

A developer can use that the above to add any additional details you need, note that we do not provide support for custom templates, if you use a custom template you will need to make sure it is kept up to date with any changes we make to the default template.

November 2, 2016 at 6:02 am

Because this is the only part that doesn’t fit very well with the modern wordpress event themes in terms of look & feel.

We simply can not integrate ‘well’ with all themes due to the amount of different themes available. We need to display the data in a way that fits in with most themes, many users do not use ‘Event’ based themes with EE so we can not focus development on any single theme type.

Any future plan for this?

Not currently but I can create a ticket to discuss this further.

Do you have any example we can use of how the data could be displayed?

Or if you prefer you could open up a pull request with the suggested changes for the dev team to review.