Problem: You are trying to preview certificates in different languages using WPML, but the preview shows a blank page. The known fix does not resolve your issue. Solution: We recommend adding the necessary code to the
functions.php
file of your theme. To ensure that this modification persists through updates, consider creating a child theme or using a snippets plugin to manage the code. This approach prevents the need to reinsert the modification after each update.
If this solution does not apply to your case, or if it becomes 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client wanted to remove the automatic translation feature in WPML to avoid using credits unintentionally and requested a refund for credits used due to accidental automatic translations. Solution: 1. We explained that the 'Translate Automatically' button cannot be removed from the Advanced Translation Editor (ATE) as it is loaded from an external server and is the same for all users. 2. We clarified that once credits are used, they are non-refundable as the payment goes to the selected translation engine. For more details, please refer to this link. 3. We suggested switching to the Classic Translation Editor via WPML->Settings, which does not use automatic translation. More information can be found here: this link. 4. As a one-time courtesy, we attempted to refund the 1000 credits mistakenly used. After locating the correct account, we refunded 1050 credits.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if needed.
Problem: The client needed to remove an old development website and manage credits associated with WPML that were still assigned to a non-existent site. Solution: We located the credits assigned to the old site and moved them back to the client's WPML.org account. You can verify this by checking your account here: http://wpml.org/account/. If your site no longer exists and the automatic translation account was not disabled while the site was active, this could cause the credits to still appear. We have taken action to resolve this issue, and you should no longer see the old site listed.
If this solution does not apply to your situation, 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client has a custom post type called 'Projects' with 78 posts, 10 of which are 'featured' and translated into all languages. The remaining posts need to appear in the original language, English, when not translated. However, only the translated projects are currently displaying. Solution: We recommend using the duplication option in WPML. Here's how you can do it: 1. Go to WPML -> Translation Management -> Dashboard. 2. Duplicate all the projects into the desired language (e.g., French). 3. Translate only the projects that need translation. This method ensures that all projects show up in all languages, with untranslated ones displaying in English. You can also use filtering options to display specific types of projects.
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 further assistance is needed, please open a new support ticket at WPML support forum.
