We're Moving to a New Support Platform – Starting June 1st!

We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.

You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.

While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.

We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.

Thanks for your continued support and trust – we’re excited to bring you an even better support experience!

Okay
  Public Ticket #2886552
Event display
Closed

Comments

  • Shelley Upton started the conversation

    Hi,

    Is there a way to automatically hide events when they are closed?

  • [deleted] replied

    Hi Shelley

    Thank you for reaching out to us.

    Please try to add this CSS to the Events page in order to hide Closed Events:

    .am-event-list .closed {display: none !important;}

    This only hides the events with the status "closed" from the page. They are, however, still present. So, if the page displays 12 events, and 9 of those are "closed", the page will hide them, so only 3 events will appear on the page.

    PS If you need help with adding custom CSS to the page, please take a look at this article.


  • Shelley Upton replied

    Hi,  I tried hiding with CSS however it leaves the pagination on screen, so the customer has to click to page 2 to find the latest and open courses they can book.  

  • [deleted] replied

    Hi Shelley

    Unfortunately this is a known limitation. There is nothing we can do about it I'm afraid as this is the only workaround we can offer currently.