Support

July 17, 2015 at 11:28 am

Hello, the registration checkout flow is different in Event Espresso 4.

A registrant/attendees starts their registration on a single event page by clicking on Register and this takes them to registration checkout. Registration checkout cannot be combined with the single event pages.

—
Lorenzo

July 19, 2015 at 4:30 pm

Hello, that isn’t available out of the box but maybe possible with some custom coding. We do not have any tutorials as this would require more than a few lines of coding so please check with an Event Espresso professional here:

https://eventespresso.com/developers/event-espresso-pros/

—
Lorenzo

July 20, 2015 at 5:43 am

Hi mpurse,

The image you linked to looks like an event within EE3.

As Lorenzo mentioned the registration flow within EE4 is different than EE3. At the registration checkout page, the registrant should have already viewed the single event page which would have displayed all of the Event details, venue details etc, the user would have then selected a ticket there and then been re-directed to the registration checkout page.

Can you link me to one of you events so I can see how this currently works on your site please?

July 20, 2015 at 7:28 am

Your EE3 site is using the Multi Event Registration Add-on to add the events to the cart from the main event list, then directing the user to the cart to input the registration detail.

Your EE4 site does not have Multi Event Registration, so you attendee view the single event, select the tickets and proceed to the registration form from there.

Is the table used to display the EE4 events a custom table or a modified version of one of the EE4 templates?

July 20, 2015 at 9:07 am

Apologies, looks like we have our wires crossed.

Based on this image – http://prntscr.com/7toacc

I looks like you want the registration to work in a similar way to EE3 and show the registration form within the single event, is that right?

Currently there isn’t a way to do that, so your looking to add the same details to the espresso checkout template and dynamically display the event details shown in the image on that page?

Right now you looking at editing the template within core to allow you to do this and want to load a custom template in its place. The template is loaded from within core, so if core doesn’t provide a filter to allow loading of a custom template, we can’t provide a snippet/plugin to do so.

Can you provide further details on exactly what it is you want to display and where you want it to display it? There may be another hook available to do what you need without completely overriding the template.

July 20, 2015 at 10:18 am

Then I thought of adding information like Description, Venue, Dates to that Registration/Checkout page,

So basically you want the ability to include any of the details from the single events page within the checkout page.

We can create feature request tickets to add hooks within the registration checkout page so information like this can be included, however to try and explain a little more from comments above.

The single event registration page includes this information already, so…

With your current set up all of your registrants click to view the event, then view the single event page, select a ticket, then go through to the registration checkout page which would display the same (or similar) details (just an example).

Meaning the details will be displayed twice, is that how you are expecting this to work?

This will also become much more complicated when/if you introduce EE4 Multi Event Registration and allow users to register onto multiple events at once, the checkout page could include multiple sets event details making it rather long.

July 21, 2015 at 9:45 am

@Josh found a way to use existing hooks within SPCO to allow you to output various info within that page.

For example:

function jf_ee_display_selected_datetimes_on_spco(){
    $checkout = EE_Registry::instance()->SSN->checkout();
    if ( $checkout instanceof EE_Checkout ) {
        $transaction = $checkout->transaction;
        if ( $transaction instanceof EE_Transaction ) {
            foreach ( $transaction->registrations() as $registration ) {
                if ( $registration instanceof EE_Registration ) {
                    $ticket = $registration->ticket();
                    if ( $ticket instanceof EE_Ticket ) {
                        $datetime = $ticket->datetimes();
                        $datetime = reset($datetime);
                        if ( $datetime instanceof EE_Datetime ) {
                            $event = $datetime->event();
                            $event_name = $event->get('EVT_name');
                            echo '' . $event_name . ' starts on ';
                            $datetime->e_start_date();
                            echo '
';
                        }
                    }
                }
            }
        }
    }
}

add_action(  'AHEE__SPCO__before_registration_steps', 'jf_ee_display_selected_datetimes_on_spco'  );

That function will output the start date for the first datetime assign to the ticket your registrant has selected.

Which is done within this section of code:

//First check that the ticket we have is an EE_Ticket.
if ( $ticket instanceof EE_Ticket ) {
	
	//Call the datetimes() method on the EE_Ticket object to pull in all of the tickets datetime.
    $datetime = $ticket->datetimes();

    //Grab the first datetime object
    $datetime = reset($datetime);

    //Check is is actually a EE_Datetime object
    if ( $datetime instanceof EE_Datetime ) {

    	//Grab the EE_Event object from the datetime
        $event = $datetime->event();
        //Now the event name from $event
        $event_name = $event->get('EVT_name');

        //Some output to the SPCO checkout page
        echo '' . $event_name . ' starts on ';
        $datetime->e_start_date();
        echo '
';
    }
}

I’ve added some comments so you can follow along with what is happening although if you need further help you may need to contact a developer to help work through these customisations.