We have change the main language and have big problems whit some parts. We had Swedish as the default language and changed to English because Directorist didn't work in some parts for our clients.
Directorist listing that was not translated when we change the default language
Directorist Directory which was translated before we change the default language
Woocommerce products which was translated before we change the default language
I have gone and updated "Update internal links"
I have gone to support and "troubleshot" all things that I read about in your documentation
Please can you have a look and help us
Thanks,
Annika
thanks for the patience, I have found what was missing.
In directory builder you are using custom template page, but that was not set for EN side. From directory builder I edited Nightlife and under custom template set correct translate page (that you are using as template - Natliv template).
I see that the Hassapiko bar now is in English but the Swedish doesn't show now and when I go to update the translation of the Swedish it doesn't open your Translator, instead it open the ordinary wp editor.
Also we have problem with the woocommerce products, not the free once but the other that we sell so can you please have a look at that also
please let’s focus on the main issue, as we limit one issue per ticket to keep things clear. If needed, we can always open a new ticket later and continue from there.
Regarding the template, I’ve set it again and it’s working correctly now. You can see it here:
- hidden link;
From what I can see, the issue is likely caused by mixing default languages between pages and templates, along with using manual translation methods.
Also, you currently have the page set to use the WordPress editor instead of the WPML Translation Editor (see attached image).
I would suggest deleting the template (or ensuring its default language is also English), then recreating/saving it and translating again. Additionally, switch to using the WPML Translation Editor for more consistent results.
Just to alert you on other issues that occured;
Translating listings on our regular site doesn't work correctly, Parts of translations (done today) from swedish to english in the "Free Shop" category comes up twice on the same page,
and sites with english translations in the "Nightlife" category doesn't show at all, Since there is a mismacth in both of these categories, can this be a global issue ??
We've debugged the website and it comes up with errors for the wpml-plugin.
I’m referring to the template used for that page/listings: Nattliv template hidden link
If you didn’t build the website, it would be best to check with the original developers, as there are many interconnected elements and some complexity, which could explain why this was missed.
You don’t have to use the WordPress editor—you can use the WPML editor. However, please note that any manual changes made in the WordPress editor may be overwritten, and you would need to translate that content again. Since mixing methods is not recomanded.
I would not say this is global issue, I would say that mixing default languages and correct settings missing is causing the issue, as it was with template settings missing.
As we keep one issue per ticket to maintain clarity, please open a new chat for any additional issues and we’ll be happy to help further.
Hi again,
I built the website and everything worked fine until we change the default language. I get a bit lost in your expanation, what did you do with the template? And just to clearify
1. Is the problem caused by the change of main language
2. Is it possible to change the main language with this complex structure? For us it's important to change because of the payment gateway etc. But I thought maybe instead delete all directories, templates, listings etc and use import export instead. If we do that shall we start to import all in English and then change to Swedish up in the top menu and import everything in Swedish and so on?
thank you for your message, I understand the confusion here.
The main issue is that changing the default language does not update the language of already existing content. All content, templates, and listings created before the change remain tied to the original default language, while any new content is created in the new default language. This leads to a mixed setup, which is likely what you are experiencing now.
Technically it is possible to continue working with this setup, but with a complex structure (templates, listings, etc.), it requires careful manual checking. You would need to review all templates, assignments, and settings to ensure they match the correct language, since some are still tied to the old default language and others to the new one.
Regarding your proposed approach, the safest recommended way would be:
- create a fresh staging site
- remove existing content and reset WPML
- build the site completely in the intended default language without WPML
- once everything works correctly, enable WPML and translate into the secondary language (e.g. Swedish)
This avoids mixing languages and ensures a clean and predictable setup.
Thank you very much for your explanation and this was the way I was thought I will do. But one last question.
For instance the Directorist plugin: Here I can export and import both Directories and listing. Can I for instance when I after your point "build the site completely in the intended default language without WPML" import Directories and listing in English?
After that you point "once everything works correctly, enable WPML and translate into the secondary language (e.g. Swedish)" import Directories and listing in Swedish?
This would be fantastic but maybe not possible, we have loads of listings and it will take us a lot of time and do everything manual.
I’m not entirely sure which Import/Export option you are referring to. If you mean the Directory import/export tool, I’m not certain how it works or if it would be correctly in this case, as WPML requires its own data structure to properly connect listings and translations.
However, even with that approach, the content (posts, listings, etc.) would still retain the original default language, which is why I didn’t recommend it earlier and instead suggested starting with a clean setup.
