This thread is resolved. Here is a description of the problem and solution.
Problem: You are trying to save a translation in WPML but encounter an error. Specifically, you struggle with translating the footer despite following the process of selecting and translating the necessary string. Solution: To resolve the issue with saving translations, ensure that you apply all formatting markers on your translated content. Highlight the words that require formatting and click on the button labeled "Strong Alt - 1" or "Strong Alt - 2". This action should allow you to save the translation correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. Additionally, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am trying to save a translation in WPML, but I encounter an error.
Symptoms:
I get an error: "The original sentence includes formatting markers. However, not all markers are applied to the translation" and I cannot complete it.
Questions:
How to solve the error related to formatting markers in translations?
Thank you for contacting WPML support. While you are waiting for one of my colleagues to take this ticket and work on it, let me try to help with the issue quickly.
Based on the screenshot that you shared, you need to apply all formatting markers on your translated content before you can save the translation. To do that, highlight the words that require formatting and click on the button that says "Strong Alt - 1" or "Strong Alt - 2".
Based on the screenshot you shared, it looks like you've not highlighted the words and assigned the format markers.
I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.
Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.
Your upcoming reply will be treated with confidentiality and will only be visible to you and me.
✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.
I wanted to let you know that the text highlighting worked. I'm currently translating the product pages, but I can't translate some of them. I'll see which ones are problematic and let you know. Best regards!
Hello Mr. Kor,
I managed to translate the products, thank you for the advice. But now I am struggling with translating the footer. I do the following:
1. I find the necessary string from String translation and select Translate;
2. I find it in Translations and translate it.
3. I check it on the site if the translation is successful.
I'm wrong somewhere in the process. Can you please give me exact instructions for translating the footer?
Yes, I need help translating the queries. I added a query plugin (ELEX Request a Quote) which adds a button below the product image. Unfortunately, this query button is not visible in the English version of the site, even though I translated the page with WPML. How can I get this button on the English version of the site?
New threads created by Kor and linked to this one are listed below:
I'd like you to know that our support policy allows us to take care of only one issue per ticket.
Continuing with one issue per ticket helps not only supporters to focus on one issue at once, but also enables other users to find solutions to their questions faster.