Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 JavaScript translation workaround issue | Event Espresso - Staging Server
since EE does not support multiple languages registration forms, I implemented a simple (though dirty, please don’t judgde me ;) JavaScript workaround.
Let’s say I have two different languages, English and German. When Setting up a dropdown question I name it “Color / Farbe” and set the values to “Blue / Blau” and “Red / Rot”. As a result I get the following (simplified) HTML structure:
Users now only see labels and values in their language. Great. But a problem emerges, I guess, on form submit. Let’s say the user selects “Blue”: In the database the value “Blue / Blau” gets stored, which is perfectly fine but on the admin panel when looking at the attendee data, the dropdown “Color / Farbe” has no option selected.
If I turn off JavaScript everything works fine.
Do you have any idea what could cause this issue?
Thanks.
Are you turning off JavaScript in the admin only, or in the registration form as well? I tried putting answers in for a question with slashes in it, and it seems to work fine.
It might. It should only take a little debugging code on the attendee admin page. You can fill out the form here and be sure to include ftp credentials.
I found that if a question value has double spaces in it, then it is changed to a single space in the registration form or the value in the edit attendee screen. Then when the answer is compared, it does not match the value. I put a fix in on your site, in includes/functions/form_build.php changing line 304 and 305 to:
The support post ‘JavaScript translation workaround issue’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.