Problem: The client has custom HTML added to their blog for an author box, which is not translating in the Advanced Translation Editor (ATE).
Solution: Firstly, we advised the client that it is not necessary to include meta tags and font links within the custom HTML block, as WordPress adds this information to the site. Instead, we recommended enqueuing the fonts file in the functions.php file of the child theme and adding CSS rules to the style.css file of the child theme.
We then instructed the client to simplify the custom HTML block to only include the necessary divs and paragraphs, which will allow the strings to be automatically translated in the ATE. The client should remove unnecessary HTML tags and structure, leaving only the content that needs translation.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, please contact our support forum.
Problem: The client has translated their categories but the URLs are not translated as desired. The issue is that the translated category slugs are appending a language code at the end, which the client wants to remove.
Solution: We explained that WordPress requires each taxonomy term's slug to be globally unique, which means one taxonomy term cannot have a matching slug with another taxonomy term across all taxonomies. To allow for duplicate slugs in different languages, we recommended checking out a post that provides a solution for allowing duplicate taxonomy slugs in WordPress. Here is the link to the post: https://stackoverflow.com/questions/12806409/allow-duplicate-taxonomy-slugs-wordpress
Please note that the solution provided might be outdated or not applicable to your case. If after checking the known issues and confirming that you have the latest versions of themes and plugins installed, the problem persists, we highly recommend opening a new support ticket. For further assistance, please visit our support forum.
Problem: The client has translated their pricing page, but the FAQ section did not translate along with it. Even after manually translating the content in Elementor, it reverted back to the default language. Additionally, the advanced translator did not show the text. Solution: 1. We recommended installing the Multilingual Tools Plugin. 2. We identified a server permission issue that prevented the installation of the plugin, which was indicated by the error message "Could not create directory. /var/www/html/wp-content/plugins/multilingual-1/". 3. After resolving the server permission issue, we added the correct custom XML configuration for Elementor, which should allow the client to translate the content properly. 4. We provided a link to the page where the client can translate the contents using the options in the sidebar: WPML Compatibility Test Tools Plugin.
If this solution doesn't look relevant, please open a new support ticket in the WPML support forum.
Problem: The client was experiencing issues with some pages still opening in the Classic Translation Editor instead of the Advanced Translation Editor after switching back to the Advanced Translation Editor in the settings. Solution: 1. We accessed the WPML settings. 2. We changed the option under WPML --> Settings --> Editor for translations previously created using Classic Translation Editor from "Classic Translation Editor (recommended)" to "Advanced Translation Editor". 3. We advised the client to delete any translation jobs that were in progress with the Classic Translation Editor from WPML --> Translation Management --> Jobs. 4. We provided a video tutorial for further assistance: https://komododecks.com/recordings/Mx0Gt88nPAgGvmfj0QDO.
Problem: The client was experiencing issues with WPML's automatic translation where the translation status keeps refreshing and the progress bar rotates continuously. The translation still doesn't appear, and not all language flags are visible for editing on the post. Solution: We recommend you try the following steps: 1. Ensure you have a full backup of your site and database. 2. Navigate to WPML > Support > Troubleshooting and click on "Synchronize local job ids with ATE jobs". 3. Go to WPML > Translation Management and resend the page to translation.
