Support

September 9, 2014 at 9:14 am

I’ve been informed by my client that we cannot use Event Espresso for events on her site. She thinks that displaying payment information when someone is only registering for a free event is extremely confusing and will likely result in people not completing the registration. In an election where every vote counts, she does not want a registration process that is confusing or off-putting to potential voters.

I’ve been looking at the Step 1 Attendee Information page. Two things would make this acceptable and less confusing:

1. Change the “Proceed to Payment Options” button to simply say, “Proceed” or “Continue”

2. Either not display the <h2> “Step 1 – Attendee Information” and the <h2> “Step 2 – Payment Options”

OR Change the <h2> “Step 2 – Payment Options” to say “Step 2 – Finalize Registration”

It would be better (but not required) to add some logic which changed the Step 2 language from “Payment Options” to “Finalize Registration” depending on whether or not the balance due is $0.00 or greater than $0.00.

I’ll settle for simply making the language a little more generic so that it fits both the free and payment due situation.

Any assistance in locating the proper code and perhaps accomplishing this without hacking EE4 and making it no longer updateable would be very helpful.

I’m using Version 4.4.0.beta.011.

September 9, 2014 at 2:01 pm

Thank you.

As I understand, the plugin deactivates all payments, so it would not work for me. Is that correct?

So, I changed the button “Proceed to Payment Options” to simply the word “Register”.

That still leaves me with a problem: The <h2> text which says “Proceed to Payment Options”. I had to hack the the registration_page_payment_options_template.php file to change that text to “Register”.

IS THERE A WAY TO OVERRIDE THAT TEXT WITHOUT HAVING TO HACK THE TEMPLATE? Especially since I’m using a beta version of EE4 and I don’t want to clobber it when I switch back into the normal update channel in a week or two!

September 9, 2014 at 3:14 pm

If you look at registration_page_payment_options_template.php on line 3, you will see that the text is hard coded as and is not in a string or array.

You did give me an idea. I couldn’t make Quick Localization work, but I was able to use “Real-Time Find and Replace” to do it – but, it filters every page rendered, so it seems like it is grossly inefficient and could affect site rendering speed.

BUT, at least I have something works without hacking EE.