Support

February 21, 2024 at 1:35 pm

Hi there,

This: EED_WP_Users_Ticket_Selector.module.php

Is the wrong file, but close 🙂 That’s for showing a notice on the ticket selector when a waitlist form is available but login is required.

Your screenshot is from the Attendee information of the Single Page CheckOut, the code that adds that is in EED_WP_Users_SPCO.module.php

Within the loginAndRegisterButtonsHtml method: https://monosnap.com/file/HtM771iaFnRqAUftVjGYx72LI099zF

You can see there is no filter for that specific string in EE however, any strings that are translatable (and we try to make sure EVent Espresso is 100% translatable) is passed through the gettext filter, which I know from your other thread your already using.

Adding 'Register' => 'Create account', to your strings array will change that string to ‘Create account’ so change to whatever you prefer to use there.

Something important to note here!

gettext is a filter applied within WordPress core to ALL strings used on the site, which means by using it to translate ‘Register’ to something else, you are changing ALL instances of that string across the site.

One wa to prevent that is to use:

if ( 'event_espresso' !== $domain ) {
    return $translated;
}

As the first line of your signuperror_filter_gettext function… so it now only applies to strings with the event_espresso text domain (so only strings from us) and otherwise just returns the string as is.

February 21, 2024 at 4:22 pm

So, it would be possible to replace the file EED_WP_Users_SPCO.module.php by copying the file into the Avada child theme….

No, you can’t replace entire class files like that. We allow it for template files (which will usually end .template.php) but not others.

To be sure I understand, using the method you’ve described, the word ‘Register’ would be translated to ‘Create account’ everywhere in Event Espresso.

Yes, but to be clear its only the specific string that you target, in this case ‘Register’, for ‘Register Now’ wouldn’t change to be ‘Create account Now’ with this example. Its only an exact ‘Register’ match that will change.

There’s no way to limit the scope to a particular page, or a particular

, in this case the

with id=”ee_reg_qstn-5959-email-input-dv”.

Not as it stands, I can request a filter is added to allow targeting the strings a little better but there isn’t another available right now.

Along these lines, can you help me understand what this bit of code means?:
‘event_espresso’ !== $domain

I don’t see ‘event_espresso’ in the URL for this page:

Its not that kind of domain, its the text_domain.

When you pass strings to be translateable its done like this:

esc_html__('Register', 'event_espresso')

esc_html__() is a function that translates the string (that’s the __() part) and then escapes it for safe HTML output.

‘Register’ is the string to be translated.

‘event_espresso’ is the ‘text_domain’ for the string…. so all strings in Event Espresso use the event_espresso text domain. The idea is that everyone uses their own text domain so the strings can be identified for a specific domain. A plugin called ‘My Super Plugin’ may use ‘my_super_plugin’ as the text domain:

esc_html__('Register', 'my_super_plugin')

gettext on its own filters both of those and would change both to be ‘Create account’, but because the text domain is passed to the filter with each string, we can use it to check specifically for the ‘right’ string to translate (the one(s) with a text_domain of ‘espresso_events’).

Make sense?