tags in your XLIFF file show empty CDATA[] instead of the actual text, this might be due to an issue with HTML sanitization in your theme's code. Solution: We recommend modifying the
1
wp_kses_allowed_html
filter in your theme. Specifically, avoid using a wildcard for attributes and instead, explicitly apply the
1
style
attribute to each allowed tag. Here is a corrected version of the code you can use:
// Properly allow inline styles on a per-tag basis
foreach($allowedas$tag=> &$attributes) {
if(is_array($attributes)) {
$attributes['style'] = true;
}
}
}
return$allowed;
}, 10, 2);
Please try this solution and let us know if it resolves the issue.
If this solution does not apply to your case, or if it seems outdated, 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. If the problem persists, please open a new support ticket.
Problem: After updating to WPML version 4.7.0, you are unable to import your old XLIFF file, and you receive an error during the import process. Solution: This issue might be related to a known problem discussed in another support ticket. We recommend checking if your situation matches the one described in the following support forum thread: https://wpml.org/forums/topic/the-uploaded-xliff-file-does-not-seem-to-be-properly-formed-3/. If it does, please mark this ticket as solved and continue the discussion in the existing thread to avoid duplicates.
If the solution provided in the other ticket does not resolve your issue or if the details differ, 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. If the problem persists, please do not hesitate to open a new support ticket for further assistance. You can do so here: WPML Support Forum.
Problem: The client was experiencing an issue where a page in Urdu was redirecting to the main English page upon the first load in a private window, but subsequent loads did not redirect. Solution: We suggested checking if the translation of the page was published and if the WPML setting for automatic redirection based on browser language was enabled. It turned out that the automatic redirection was not enabled, which was confirmed by the debug information provided by the client. After ensuring the translation was published and the settings were correctly configured, the issue was resolved, and the page no longer redirected on the first load.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also 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 https://wpml.org/forums/forum/english-support/.
Problem: You are trying to convert your pages to other languages, but the page URL is not translating correctly. Solution: We recommend checking your WPML settings. Specifically, you should navigate to WPML > Settings > Translated documents options and set Page URL to
1
Translate
. This setting will allow the slug in the translation to be included and not automatically created from the title.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket.
