Dieses Thema ist gelöst. Hier finden Sie eine Beschreibung des Problems und der Lösung.
Problem: Der Kunde hatte Schwierigkeiten, die Zwischenüberschriften in Blogbeiträgen zu übersetzen, was dazu führte, dass das Inhaltsverzeichnis (Table of Contents) diese noch in der Ursprungssprache anzeigte. Lösung: Wir haben die Einstellung 'RAW HTML-Inhalte zur Übersetzung senden' unter 'WPML > Einstellungen' deaktiviert. Anschließend haben wir eine kleine Änderung auf der Seite vorgenommen und diese gespeichert. Da die automatische Übersetzung auf der Seite aktiv war, wurde die Übersetzung automatisch abgeschlossen. Nachdem wir die Übersetzung überprüft und gespeichert hatten, wurde die Zwischenüberschrift korrekt ins Englische übersetzt und das Inhaltsverzeichnis entsprechend aktualisiert.
Bitte beachten Sie, dass diese Lösung möglicherweise nicht mehr relevant ist, da sie veraltet sein könnte oder nicht auf Ihr Problem zutrifft. Wir empfehlen Ihnen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollte das Problem weiterhin bestehen, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Hier ist der Link zum WPML-Supportforum.
Dies ist das technische Support-Forum für WPML – das mehrsprachige WordPress-Plugin.
Mitlesen können alle, doch nur WPML-Kunden können hier Fragen veröffentlichen. Das WPML-Team antwortet im Forum an 6 Tagen pro Woche, 22 Stunden am Tag.
To reduce the waiting time, I took this ticket and responded in English. Please let me know if you're okay with it or if you prefer to continue the conversation in German. Based on your preference, I will forward this ticket to one of our German-speaking colleagues to assist you further.
I have reviewed the entire conversation you had with my colleague Bruno to understand the issue better. As you provided access to your site, I navigated to "WPML > Settings" and turned off the option to send RAW HTML content for translation under "Page builder options." After this, I made a minor edit to the "hundehaftpflichtversicherung-in-spanien" page and saved these changes.
Given that Automatic translation is active on your site, the translation was completed automatically. Once I finished reviewing the translation and saved it, the Heading was correctly translated into English. Additionally, the Table of Contents section was also updated to reflect the English Heading. For your reference, please check this screenshot demonstrating the changes: versteckter Link
I hope the issue has been addressed properly. Feel free to let me know if you need further assistance in this matter. I will be happy to help.
I have another question: The site must be trilingual, but entries written in English or Spanish must also be translated into the other languages. Is that possible?
And where can I find the translation options for the tabs: versteckter Link
Using the method I outlined in my previous message, you should be able to effectively translate the page into other languages. Given that the option to send raw HTML data to the translation editor is already disabled, you can translate the content by following these steps:
1. Make a minor modification in the title of the default page and save these changes.
2. Immediately after, a translation update icon should appear. Click on the update button to proceed with updating the translation.
In answer to your query, yes, you can indeed translate content from both the default and secondary languages. Although it is our general recommendation to translate content from the default language to others, if your need is to initially create content in a secondary language and then translate it into other languages, this is also feasible. Just make sure that your site is running the latest versions of WPML (4.6.9) and String Translation (3.2.9).
However, while checking the link you've shared, I found a 404 error and also noticed that you've switched to a different plugin.
While I respect your decision, I genuinely want to ensure that you have the best experience with WPML. We are committed to helping you solve any issues you encounter while using our plugin. If you reconsider and decide to use WPML again, please know that we will be more than happy to address and resolve any concerns you may have. Your satisfaction is our priority, and we're always here to assist you. Remember, WPML is continually improving, and we'd love to have you back to experience these enhancements firsthand.
Feel free to reach us if you need further assistance with WPML, I will be happy to help.
Hi Prosenjit, , thanks for your reply. I use WPML on a lot of other sites, but on this site it doesn't really work well with the automatic translation of Geodirectory.
I have to translate each entry manually, which is very time-consuming. Irrespective of this, can I change the default language afterwards or does this confuse the system?
If you have the automatic translation feature enabled, it should seamlessly translate all posts across all the post types on your site. To better assist you, could you please specify which Geodirectory plugin you're using? This information will help me understand how the content is stored and provide you with a tailored solution.
As for changing the default language, you can indeed change the default language. Everything should continue to function properly. However, depending on the translation settings for your post types, you might need to make some adjustments to ensure that the archive listings work as expected.
The Geodirectory plugin that you're using is compatible with WPML. Please check the guide below.
- versteckter Link
As per the documentation-
All GD pages and templates will need to duplicated and translated with the WPML settings found in pages. They must be recreate for in each language that you configure via WPML. This includes the Search, Archive, Listing Details, Add listing, Location and other such pages.
This indicates that content within the Geodirectory plugin must be translated manually, as there is no support for automatic translation of its contents. For a more comprehensive understanding of this constraint, it would be advisable to contact the support team for the Geodirectory plugin. They should be able to provide a more detailed explanation on this matter. I hope you can understand.
Regarding the query about changing the default language, it's generally straightforward and doesn't require adjustments. However, it's a good idea to refer to the guide to ensure your site is configured correctly after the change.
I checked the page and can confirm that all the headings are showing correctly translated. I haven't noticed any untranslated headings on that page. For a clearer view, please refer to this comprehensive screenshot: versteckter Link
As everything appears to be working fine, could you please clear the caches from your site and browser and then check again?
I also have checked the English version and it seems the English translation is not fully completed yet. Please complete the translation first and hopefully, the Heading will appear translated in the English version as well.
Please let me know the update. I will be happy to help if you need further assistance in this matter.
[For clarity and to keep our discussions organized, we are allowed to discuss one issue per thread. Let's continue focusing on the Heading translation issue in this conversation. Should you require assistance on any other matter, don't hesitate to open a new ticket, and we'll be glad to assist you further.]
