Support

June 29, 2024 at 12:03 am

Thanks for understanding, No worries, if you need anything, feel free to reach us again.

Thanks

June 29, 2024 at 1:20 am

I did try 50 and it works on my end. But depending on the recurring and intervals, the system makes a limit.

It is expected that it will be quite messy in the front-end as there’s a lot of ticket and event date. But how do you plan to show it? Let’s see if there’s css we can use to customize its look.

We also suggest to read the documentation for REM https://eventespresso.com/wiki/eea-recurring-events-manager/

thanks

June 30, 2024 at 9:48 pm

In the example you shared, they did not use Recurring Event Manager. Recurring Event Manager will create tickets and Datetime in one event page.

What i think was done here was using Duplicate Option. You can do that by going to Event you want to duplicate then https://monosnap.com/file/qGpQjEpPVe8vdDoSNbstocVa9pZSKb

then share the link for Event List, or create a page with filtered events.

thanks

July 11, 2024 at 4:37 am

You can try CSS code to hide that.

You can save the CSS code by going to your Appearance -> Customize -> Additional CSS

.spco-ticket-info-dv span {
    display: none;
}

thanks

July 20, 2024 at 7:01 am

A.
This URL https://firstaidwinnipeg.ca/standard-first-aid-courses/ is using this add-on https://eventespresso.com/product/eea-events-table-view-template/

Recurring add-on will create Tickets and Datetime but it is only created in one event page. Though you have lots of datetime and ticket on one event page, there will be only one registration button on it. Here’s example
https://lethbridgefirstaid.ca/events/basic-life-support-bls-cpr-and-aed-courses-in-lethbridge/

B. If you plan to hide the ticket information, then you can just go to EE dashboard -> Event -> Templates -> Then find the Show Ticket Details setting. https://monosnap.com/file/2EXk9cQlnxwuOyXPsRSoPLXpXAKMKU
Then set it to NO.

If you just want to hide the specific part you shared, you can use CSS to do that.

.tkt-slctr-tbl section.tckt-slctr-tkt-sale-dates-sctn {
    display: none;
}

you can also use different Selector if you want to do that in particular event page.

C. That site you shared is using The table add-on. then they did create a page and enter the shortcode for that plugin.

Are you planning to show the Class Remaining on your event page?
you can use snippet here https://eventespresso.com/wiki/useful-php-code-snippets/

We recommend creating a custom plugin for easy maintenance and debugging. here’s the guide.
https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/

Thanks

July 30, 2024 at 11:06 am

Hi Mark,

A. just to confirm are you referring to showing the active date at the top?

C. the link is not working for me there might be some issue with the site.
https://prnt.sc/l1a0P-xXGVMB

Please fix that so that we can check the issue for you.

August 3, 2024 at 8:44 am

Currently, users have to click on each individual ticket to find the registration link. I’d like to display a registration link directly next to each ticket, so users can easily register without having to open each ticket’s details.

You need to use this add-on https://eventespresso.com/product/eea-events-table-view-template/ and not recurring. Recurring will only create ticket/datetime. But the register button will be just one.

Check this thread.
https://eventespresso.com/topic/custom-ticket-selector/

C.
The reason why it didn’t work because the filter is not correctly called.
FHEE_espresso_list_of_event_dates_datetime_html should have more underscore.

Check the code here.

add_filter(
    'FHEE__espresso_list_of_event_dates__datetime_html',
    'my_add_total_spaces_display',
    20,
    2
    );
    function my_add_total_spaces_display( $html, $datetime ) {
    $html .= '<br><span class=space-remain>Total spaces remaining: ';
    $html .= $datetime->total_tickets_available_at_this_datetime();
    $html .= '</span>';
     return $html;
    }

it is a good practice to put it in the plugin.
https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/

thanks

August 5, 2024 at 2:41 am

Hi Mark,

Sorry for the confusion.

A. Regarding the registration button, in the screenshot you are showing the single event page: https://lethbridgefirstaid.ca/events/basic-life-support-bls-cpr-and-aed-courses-in-lethbridge-ne/

Here you can see the register button at the bottom of the page: https://tinyurl.com/23rxw4s6
That’s not a drawback there should be one register button per event. Due to this, you can select your required tickets (one or many) and then proceed with registration.

C. Regarding the “remaining space” amount you can see that within the ticket details section itself, you do not need to scroll down to the “Upcoming Datetime” table

https://tinyurl.com/2cmqxhsr

However, if you still want to add that to the “Remaining Space” column to the table that needs custom modifications.

August 6, 2024 at 8:01 am

Hi there,

Customizations are not something we provide support for and the problem with the section you are trying to edit is the amount of logic used in the ticket selector makes things… difficult and error-prone when you start making modifications. We seen it in the past, users make customizations to the ticket selector and then get caught when they don’t pot over any changes made within core to ‘their’ ticket selector… often when the developers of that custom solution has moved on/no longer available.

Adding a register button to each line would basically just be a copy of the current register/submit button and the user would still need to select the relevant Qty for the ticket(s) they are wanting to submit.

There’s no dates on your ticket names which means when your users land on the ticket selector and hit the register button you are looking to add… which date are they attending? How do the users know which date they are attending?

For example the page loads and they see this row: https://monosnap.com/file/JtXU9djYwl8GNfIqiM2XZmTtyxt79S

They click register but don’t know which date they are attending unless they went into the more details section to view the details.

I gues what I’m trying to so here is that adding a register to each row in the ticket selector sounds great here but still has its own issues and you going to need to work through a bunch of logic (both within the ticket selector and possibly SPCO depending on the specifics of how you want this to work) for this.

—

If you are using the Recurring Events Manager to use a single event then what about adding a datetime selector above the ticket selector so they user can select the Date they want to view tickets for using that, then select the relevant ticket?

Go to Event Espresso -> Events -> Templates (tab above the events list)

Find the ‘Ticket Selector Template Settings’ section.

There you’ll find a “Show Date & Time Filter?”, set that to ‘Maybe show….’

(Its ‘maybe’ becuase it depends on the number of unique datetimes you have on the event, which you set on the option below)

Then set the ‘Date & Time Filter Threshold’ to say 3… that means the datetime selector will show when the event has 3 or more unique (different dates) datetimes on it.

Then go back to your single event page and view it again, does that help?

—

How are you directing users to that single event page? There may be another solution from there. It’s possible to add a query parameter to filter the tickets shown on the single event page (where the ticket selector is) for a specific datetime. So if you’re listing all of your event dates you can have a link from each date which then directs the users to the single event page showing only the tickets for the specific date they click for. That will still require custom development, but not within the ticket selecotr itself.

August 8, 2024 at 6:34 am

I’ll jump in at the beginning of this and state that I’m not dismissing any of your feedback/issues here, if any of my replies come across that way it’s not intended to be. I understand and acknowledge all of the issues you’ve raised here and will be opening up a discussion on this with the team to see what we can do. Your feedback is appreciated and heard.

What I am trying to do right now, is work out a possible way for this to work for you as it stands rather than having to duplicate events. Even if we look into changing this right now, it’s not going to be a quick fix as there’s multiple use cases we cover here so many moving parts to work through.

Unfortunately, the recurring functionality in EE4/5 has been useless for us.

So far it’s sounding more like an issue with how the recurring events are displayed for your use case rather than the EE4 Recurring Events Manager (REM for short) itself. REM is allowing you to create multiple instances of the event but the display on the single event page doesn’t suit your needs.

To explain that a little, within EE4+ rather than having individual copies of an event as a recurring series (like EE3 does), it uses a single event and creates the datetimes (you can think of those as an instance of event) and the tickets associated with those datetimes. The problem you’re running into currently is the event outputs we have then display events, so when it links back to the event as a whole you see all of the datetimes/tickets for that event which (understandably) doesn’t work for your use case here.

So whilst it may sound like I’m splitting hairs on this, that sounds more like an issue of how the events are handled when output rather than REM itself, right?

—

So, if I work on that assumption for this reply… it sounds like having an output that displayed datetimes would work better for you here.

If this:

https://app.screencast.com/GTlJ8xYDVgWPN?conversation=HgFF20ywOTMH0cKNiTbIsA

Was creating a table based on datetimes (and then displaying the event data related to that datetime), providing a link for the single event based on the datetime display this would work better for you?

To give you an example of how that would work…

Single event as a whole:
https://lethbridgefirstaid.ca/events/basic-life-support-bls-cpr-and-aed-courses-in-lethbridge-ne/

But then if you were displaying datetimes in the table mentioned above and wanted to display only the datetime/tickets for one of those, you pass the datetime ID as a query param, so your September 16th datetime ID is 739, the link would be:

https://lethbridgefirstaid.ca/events/basic-life-support-bls-cpr-and-aed-courses-in-lethbridge-ne/?datetime=739

That’s still the single event output, but now it’s filtered directly to a specific datetime and only displays the ticket and datetime info for that specific datetime.

For your use case I think trying to funnel users to the single event page to then make their date selection is ‘too late’ which is then causing confusion here. The single event displays ALL options and you’re trying to then come up with a solution to narrow down from there. The datetime filter I referred to above was added to try and help with that for some use cases but when you have long recurring events that can also be confusing for users IMO.

—

While I appreciate your suggested options, they still don’t bring the call to action to the forefront. The small + button that needs to be clicked doesn’t work for us, especially given the number of events we have on a single page. The date and time are shown at the bottom, but with so many events, a longer page simply isn’t practical for us.

This I’m a little confused about, I didn’t mention the + button?

Is this relating to showing which datetime the ticket relates to?

If so, that’s not how I would advise doing it, it doesn’t work well for your us case as there are too many tickets to expect users to go through each one checking the dates. Which I think is what you are saying here and I agree with.