|
Martijn Siemes
|
August 3, 2015 at 7:36 am
I now have downgraded from EE4 to EE3 and now I would like to use the dutch version? How do I activate that? I know it’s a po-file, but how do I tell wordpress that?
|
|
Lorenzo Orlando Caum
|
August 3, 2015 at 9:46 am
Hi Martijn,
You can download the language files from the link at the end of the page (mo and po files):
http://translate.eventespresso.com/projects/event-espresso/nl/event-espresso-nl_NL
Then upload to this location:
/wp-content/uploads/espresso/languages
If needed, create the language folder as shown above.
Then rename the files to event_espresso-nl_NL.mo and event_espresso-nl_NL.po.
Your site should then start to use the translations.
Notes that certain content like the email notifications and the questions and question groups are translated through the WP dashboard.
For example, if you wanted to change the name for a question group, then you could go to Event Espresso –> Questions. Then click on an existing question, rename it, and then save changes.
—
Lorenzo
|
|
Martijn Siemes
|
August 5, 2015 at 6:09 am
Does it take effect immidiately? I just did what you said, but it’s still in English. Do I have to refresh anything?
|
|
Lorenzo Orlando Caum
|
August 5, 2015 at 9:00 am
Hi Martijn, it should activate right away. Is your WordPress site currently set to Dutch through the wp-config.php file or through the general settings screen?
Also, could you share the exact file names for the language files? The software looks for a specific formatting for the name.
Thanks
—
Lorenzo
|
|
Martijn Siemes
|
August 5, 2015 at 10:08 am
Through the general settings screen of wordpress it self.
The names are:
– event_espresso-nl_NL.po
– event_espresso-nl_NL.mo
And I got them by exporting them from the link you gave here above. Seperately a po and a mo file.
|
|
Tony
|
August 5, 2015 at 11:40 am
Hi Martijn,
Within Settings -> General -> Site Language what is that currently set to?
|
|
Martijn Siemes
|
August 5, 2015 at 12:41 pm
Site language is in Dutch (Nederlands) and my wordpress is entirely in Dutch (except for EE3). I checked the wp-config.php but it doesn’t seem to contain a WP-LANG definition at all. Don’t know what that means. I saw that sometimes it should be changed if your wordpress general settings don’t work.
I’m using WordPress 4.2.4 by the way.
And so far I also tried changing the language settings in WordPress and changing it back in Dutch, but it didn’t help.
|
|
Tony
|
August 5, 2015 at 12:51 pm
WP-LANG should no longer be needed with the latest versions of WordPress.
Can you try using these translation files – http://take.ms/XoDJs
Upload those to /wp-content/uploads/espresso/languages/
Then check you EE menu – http://take.ms/ouNdR
Has it been translated?
|
|
Martijn Siemes
|
August 5, 2015 at 1:03 pm
No, it hasn’t.
What can it be?
|
|
Martijn Siemes
|
August 5, 2015 at 1:05 pm
Could it be something related to EE4? I deinstalled it before I installed EE3. Or can it be a conflict with our theme (WP-clear). We also use Jetpack and something called Project Manager.
|
|
Martijn Siemes
|
August 5, 2015 at 1:06 pm
This should be the registration form. As you can see it’s bilingual…
http://www.puur-fair.nl/event-registration/?ee=1
|
|
Martijn Siemes
|
August 5, 2015 at 1:07 pm
Come to think of it. Should I delete all event information before changing the language?
|
|
Tony
|
August 5, 2015 at 1:24 pm
Come to think of it. Should I delete all event information before changing the language?
No you should not need to.
Can you try adding this:
define('WPLANG', 'nl_NL');
Anywhere above this line:
/* That’s all, stop editing! Happy blogging. */
Within wp-config.php.
|
|
Martijn Siemes
|
August 5, 2015 at 1:38 pm
YES!
Thank you! I was getting desperate but you saved the day.
|
|
Tony
|
August 5, 2015 at 2:01 pm
You’re most welcome, glad I could help.
I can see why this didn’t work previously and have issued a ticket to have this updated in the next version of Event Espresso.
It shouldn’t cause you any further problems (apart from the notice that WPLANG is depreciated) but we’ll add a fix so we can prevent this in the future.
|
