Support

October 28, 2024 at 4:53 pm

Hi Matt,

May I ask why this is much more time consuming within the new editor?

It may be a case of us needing to highlight how to edit sections a little better as the new editor should be quicker rather than slower.

—

To answer your question, it is currently possible to switch back to the ‘legacy editor’ within Event Espresso:

Event Espresso -> Events -> Default Settings (tabs across the tob of the list table)

Set ‘Activate Advanced Editor?’ to Legacy Editor and save.

Now that eventually that legacy editor will stop working so I’d like to understand the pain points you are facing with the new editor to see what we can do about those.

October 29, 2024 at 1:24 pm

In the Legacy editor it was all located in a single page – now as I try and learn the new editor there seems to be pop ups and click throughs to each instance which makes it much more time consuming.

Ok, so this I’m not sure is correct and I assume is part of where I mentioned that we need to make it clearer what is editable.

Most of the details shown on the card output (the default output for the new editor) are directly editable from the card. Some have additional popups (like the date/time selectors) but most are directly editable.

Here’s a quick example with editing datetimes and tickets.

Datetimes: https://monosnap.com/file/3JN4Z32sswS8TS69uFx6oxOj7kxyH0

Tickets: https://monosnap.com/file/GuQwjrTDtoPJv2AIdIweY1t1hQX38f

I agree some sections have new modals, but most of the information you would/should need to edit most of should be quickly accessible. Datetime/ticket assignment is the only one I can think of that could currently be considered to have an ‘additional’ modal.

I had another discussion on the editor with another user having a similar issue HERE and we are aware that we need to make some changes to improve the how the editor works for some people.

But know the above data is accessible from the card itself, does that help with your situation at all?

it also seems if I make a change to a ticket now that the ticket gets unassigned and is then “hidden” from view so I need to adjust the filters to see it etc…

Tickets should never be unassigned from datetimes unless explicitly changed by yourself, although they can be removed from view based on the current editor filters.

For example, if you expire a datetime then the default filters will hide the datetime and with the LINK filter (again on by default) that would also hide the tickets assigned to that datetime (because the datetime is expired).

Originally the filters were intended as a method to keep the editor ‘clean’ from ‘unneeded’ datetimes times when you have many (say you have multiple ‘old’ datetimes and tickets for those within a single event) the default filters keep those hidden by default as most people don’t want them all shown all the time. BUT we have been taking note of the feedback given by our customers and the filters seems to be causing more confusion for users so we are looking into changing how those would work.

—-

Side note – I/we do listen to all of the feedback given by our customers, so if anything above sounds like I’m simply dismissing your pain points here that’s not intentional.