Support

March 4, 2024 at 6:36 am

Hi there,

That is an issue with the translation files in use on the site.

Do you have FTP/File Manager access to the site?

If so look in /wp-content/uploads/espresso/languages/

You will likely find (at least) 2 translation files for Event Espresso named event_espresso-nl_NL (A .po and .mo file)

If you have those they are considered ‘custom’ translations, have you alrered any of the translations on the site using those?

You have 2 options, rename them (just change the MO file to be event_espresso-nl_NL-temp.mo for example), that will stop them loading and EE will use its default translations…. does the page work then?

(You could just remove them, but if you have custom translations within those files they will then be lost)

Or… download the PO file, open it up in POEdit

Search for:

Below are message types that are currently %sactive%s with this messenger. Drag them over to the "Inactive Message Types" box to deactivate them.

Then you look at the translation, it will have a missing s on %sactive%

Update the translation to have the s, save and generate a MO file, replace the MO file you are currently using above with the one you just generated (I’d recommend also uploading the PO file for any future use).

The reason you are getting an error is PHP8 (which your server likely updated to recently) does not allow for any errors within the original/translated string, it not throws a fatal error with them when PHP7 would not.

—-

If you are NOT using custom translations through that file, my recommendation s to remove it and use the default files built into Event Espresso.

https://monosnap.com/file/zEADkBrSbyDqacPEAirC9MO111i4eA

March 5, 2024 at 4:25 am

You like got them from here:

https://translate.eventespresso.com/projects/event-espresso-4/

That is were all of our our current translations are stored 🙂