Event Submission Form is not using translation files

[Murat]

Hi,

I am using qTranslate-X (and its language chooser) for translations,

But my event submission form (“Submit an Event”) is not making use of all the translations in the translation files,
it stays always in the same language (when I use the language switcher). Same goes for the community tab in the admin panel, it either stays english, or german, but I have not figured out why and when it stays with one language.

For example:
I translated my “Event” wording to “Class”, and when I switch languages on the form “page” (community/add),
the “Event” wording changes from “Class” to “Kurs”, but most of the other stuff doesn’t change (like “Submit an Event” headline). And I read that “add” and “list” should also be translated, but they are not translated in the URL either.

What can I do?

[Murat]

I can tell now that
if I go to Settings -> General,
and change my Site language to German and SAVE,
the Submission form will use German translations.
But if I SAVE it as English, it will turn to English.

The Community tab in Settings of TEC also applies to this,
it stays in the language SAVED in Settings -> General.

All other TEC pages work fine with translations.

[Murat]

I fixed it 🙂

In Main.php
the plugin text domain has to be loaded during “init”,
so I replaced

$this->loadTextDomain (like 264 or sth)
with
add_action(‘init’, array($this, ‘loadTextDomain’));

works now!

[Brian]

Hi,

Thanks for bringing this up.

It looks like your fix maybe the proper way to go.

I will see if we can make this change.

Thanks

[Brian]

Hi,

Thanks for bring this up with have a ticket in the system to fix for our next release 4.0

Keep your fix in the plugin for now and the 4.0 version will have it included.

I am going to close this ticket to new replies, but the issue is still open and we will update this ticket once we release a fix released.

If you have any new questions or issues please create a new ticket and reference this one.

Thanks

[Geoff]

Hey there!

Just poking in to let you know that this issue has been resolved and a patch will be included in Version 4.0. We expect that to release sometime today so please do keep you eyes peeled and feel free to let us know if have any other questions after updating.

Thanks for your patience while we figured this out!

Geoff

[Author]

Posts