Posted: February 15, 2021 at 7:29 am
I have been trying to use events expresso but have found the way its displays things, events, the table, the calendar, etc to not be useful for my purposes because it does not make sense and is not aesthetically pleasing. I cannot write PHP which is why I bought this product.
I looked at the Hide and EE consultant and it gave me a price of 1500 to just make the displays of your product look decent.
How come there is no control of how the elements of an event are shown? I cannot really change anything except in the antiquated and nearly useless WYSIWYG editor…. Why is the featured image of an event not displayed on the event page? Why is the price not displayed in the table? Why do the tickets show at the bottom of the page? Why Cant I just put the tickets remaining on the page instead of a ton of info no customer needs…
The backend seems to work fine but the layout of the events and the display is impossible to customize without coding in php….The things I want to do are not major customizations and other people on these forums are repeatedly asking for the same things…
Event Espresso was designed to output events to be as consistent as we could across multiple themes and we don’t integrate with any types of page builder/template plugin if that’s the type of control you are looking for. One of the reasons we don’t use a builder is you then become locked into our choice of builder.
You do have some control over the order and what is displayed within Event Espresso -> Events -> Templates (tab)
There you’ll see a section for Single Event Pages and Event List Pages to change some of what is shown and alter the order of elements but failing that you’ll need a custom template for your theme.
That editor is for the event description rather than the event layout as a whole.
In short, because your theme’s template has been set not to, it’s the theme that controls the output of the feature image rather than Event Espresso.
There are a few reasons, one of which is to keep the table lean. It wasn’t designed with the intention of being a full event details list but simply a list of events.
For a full event list we use the /events/ list (which is an archive of Events) and that includes all of the information, including the ticket selector showing all of the prices if needed.
Another issue is which single price do we display on that table? An event can have multiple datetimes and each of those datetimes can have individual tickets assigned to it or tickets assigned to multiple datetimes. Each of those tickets within the event then has a price assigned to it, so displaying a price for an event with a single ticket is simple enough but which ticket do we use when you have say 10 tickets with different prices assigned to a datetime? The highest? Lowest? A range?
Whichever of those we chose the next person will prefer something else. We know from past experience with EE3 that adding multiple options within the shortcode parameters then causes more confusion which is one of the reasons we created that table as a simple list. The templates are all customizable within Event Espresso and that is very intentional as it allows for customizations, yes it requires PHP knowledge but providing a multitude of options for users to customize everything also comes with its own pro and cons, as do page/template builders.
You can alter the order using the settings I mentioned above.
I assume you mean the info included in the ‘ticket details’ section? You can hide various sections using CSS but the data included in that section was taken from feedback received within EE3, whilst I understand your customers may not need it, we had multiple requests for a lot of that info previously.
You’ve had a quote of 1500 for those customizations which shows they aren’t just basic changes. Without creating a front end editor specifically for Event Espresso (which is not something we are currently in a position to create) whatever we do will require PHP at some point, user A wants X, user B wants Y, its all very subjective which is why we chose to follow the current site’s theme output rather than what EE3 did with its own template system (which required much more EE specific knowledge than EE4 does).
In short, if your looking for a front end editor with control over each individual EE element similar to a page builder type setup then Event Espresso is not the right fit. Even if we dropped everything we are working on right now and switched over to developing a solution for it, it is not something that can be pushed out the door quickly. As much as I’d love to say we could, it simply isn’t possible.