|
Emoni
|
July 7, 2014 at 9:00 am
Hi
Just testing EE4 for a new licence purchase.
I need to make a few changes, like removing this:” “Print it, download it, cherish it” on the confirmation, and words like ‘Finalize’ to British English. There is also a mistake in the English when not requiring additional attendees:
“This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for it’s registration purposes.”
It should just read: “This ticket type does not require any information for additional attendees, so attendee #1’s information will be used for registration purposes.”
Where can I make these various changes – I saw something about POedit but wanted to check before I start up the wrong path…
Thanks
|
|
Tony
|
July 7, 2014 at 10:08 am
Hi Nicholas,
Regarding: “Print it, download it, cherish it”
We have a filter to allow changing that text.
add_filter ('FHEE__payment_overview_template__order_conf_desc', 'override_confirmation_text');
function override_confirmation_text() {
return 'Change this message to new instructions';
}
Would change that text to ‘Change this message to new instructions’.
Changing ‘Finalize’ depends on where exactly this is located. The registration checkout button can be altered using the guide available here:
https://eventespresso.com/wiki/customize-checkout-registration-button-text/
The phrase ‘This ticket type does not require any information for additional attendees, so attendee #1?s information will be used for it’s registration purposes.’
Can be altered using either POEdit or a translation plugin such as Quick Localization, the string you would need to translate would be:
‘This ticket type does not require any information for additional attendees, so attendee #1\’s information will be used for it\’s registration purposes.’
Within the event_espresso text domain.
We have a guide for doing so available here:
https://eventespresso.com/wiki/how-to-change-wording-with-poedit/
However I will include your feedback regarding this phrase within a ticket to have this fixed within a future version of Event Espresso.
Does that help?
|
