Support

December 10, 2024 at 3:40 pm

Hi there,

However it doesn’t and after inspecting the html, there is actually no html element on the page with the id of checkout.

So the issue here is more that, at this point… there should be.

Changing the anchor to something else is indeed possible (although you’ll need to jump through a few hoops to get them all), but…. if the #checkout element isn’t loading on the page its an indication of other problems so I would advise figuring out why rather than patching EE to use another anchor.

The code used to load the checkout element runs on the loop_start hook:

add_action('loop_start', [$this, 'set_checkout_anchor'], 1);

So if its not loading on the page, is the theme doing something unexpected to load the page?

Are you running your own custom theme? If so does it follow the WP theme standards?

Can you link me to an event I can take a look at to view this?

And then the other issue is, once the user has filled out the Registration Form and gone to the payment stage, they can never go back to the registration stage (in case they want to update something on there). There is no button to go back and seemingly no way to return them there. Surely there is a way to allow them to go back and change things before they have paid?

I assume you have the Multi Event Registration add-on enabled based on your post? Currently we don’t hae an option to go back to the attendee information step once they proceed to payment unless the ticket selection is changed.

Althught, the user does have the option to change the attendee information after registrations is complete.

December 11, 2024 at 8:02 am

Ok, so you have this:

It is indeed a custom theme but it isn’t doing anythign weird in that regard.

And then…

So the page that outputs the checkout stuff is page-registration-checkout.php and it is using

Whilst not ‘weird’, why are you processing the shortcode via the template using do_shortcode()?

Does the_loop run on that output? loop_start runs as the beginning of the loop… no loop (or the loop running outside of the expected location) means no loop_start hook to add the code.

Within the area that is populated by that shortcode, there is no id=”checkout”, either on the first stage (registration) or the second (payment).

This makes sense with the context given so far.

Are you not running the_loop?

As far as not being able to go back, that’s a shame! Is that something planned for the future at all? It seems like a strange thing to lock people out of just for clicking proceed as they havent altered anything or paid at that point.

It’s not that we are intentionally locking people out, the attendee progressed through the checkout steps and made it to payment options. With Multi Event Registration enabled, we keep the session open so navigating away from the page doesn’t change the session’s ‘completed steps’, meaning when you go back to SPCO, it knows your current step is ‘payment_options’ and loads that.

We have discussed this previously and do have a feature request ticket to add the ability to go back to attendee info. However, it has had a relatively low number of requests from users, so it isn’t considered a priority feature at this time.