Now, PLEASE NOTE that, whenever you add a new attribute, it 'll be added in the language set in your user profile. For example, if you switch your user profile language to Site Default (i.e. Turkish) and now if you add an attribute, its default language 'll be Turkish.
Please also note this is a temporary workaround and isn't recommended. But can help fixing the problem where Product Attributes are always added in English.
Problem: The client is experiencing issues after pushing their site from the productive environment to the live site, resulting in an error message related to WPML's Advanced Translation Editor : This site has been moved to a new location . Solution: If you're encountering a similar problem where you see an error message after moving your site, we recommend using the new "Force-enable WPML’s Advanced Translation Editor" button. This feature was introduced in WPML version 4.6.7 to help resolve such issues. You can find this button on the Troubleshooting page. For detailed steps, please refer to our documentation:
Problem:
I am experiencing an issue with the WPML plugin on our website, where updates made to the original German pages are inadvertently overwriting the English content, despite setting pages to 'Translate independently'. I have tried activating the 'Translate independently' button, checking Elementor settings, and looking for relevant updates or documentation without success.
Solution:
Please follow these steps carefully:
-Clear the caches from your caching plugin.
-Reconfirm that the translated pages are set to 'Translate independently'.
-Navigate to "WPML > Support > Troubleshooting".
-Click on the buttons provided in the provided screenshot link.
-Make a minor edit to the default page title and save, to prompt a translation update.
-Update the translation and check if the issue of overwritten content persists.
-Additionally, ensure any previously duplicated pages are set to translate independently, and if any duplicates were deleted, permanently remove them from 'Trash' to avoid conflicts.
Problem:
Having trouble translating my WP Job Manager/Woocommerce shop page.
Solution:
When using custom template based on page slug (i.e. page-pricing.php), all you needed to create one for the translated slug also (i.e. page-prix.php for French) by simply copying that template into a new file.
Problem:
The customer is concerned about the compatibility of WPML with PHP 8.2, which has been out for almost a year. They have noticed PHP 8.2-related issues and expect WPML to keep up with the latest PHP version.
Solution:
The support agent acknowledged the concern and mentioned that both WordPress and WPML are working on becoming fully compatible with PHP 8.2. They assured the customer that their feedback would be shared with the development team.
Problem: The client reported that category thumbnails were missing on the Finnish (FI) version of their website's homepage and that the left menu did not match the original page. They also mentioned that after manually adding some missing translations for categories, the thumbnails disappeared again. The troubleshooting section indicated '0 left' for 'Sync products categories (display type, thumbnail)', preventing the regeneration of thumbnails. Solution: We recommended that the client resave the categories to fix the issue with the missing thumbnails. We provided a screen recording to guide them through the process. If you're experiencing similar issues with missing category thumbnails on your multilingual site, we suggest you try resaving the categories as well. If this solution doesn't seem relevant to your problem, please open a new support ticket with us.
Problem: The client is running a WooCommerce shop with thousands of products and dozens of attributes, and after installing WPML, the products do not appear in the shop unless they are translated. The client is looking for a way to mark products as translated without having to go through each one individually. Solution: If you're experiencing an issue where your products are not appearing in your shop because they are not translated, and you want to focus on translating attributes while leaving product information like titles and descriptions for later, we recommend duplicating your products in the secondary language. This will allow your products to appear in the shop and enable you to translate them fully at a later time. For detailed steps on how to duplicate content, please refer to our documentation on Displaying Untranslated Content on Pages in Secondary Languages.
If this solution doesn't look relevant to your situation, please open a new support ticket and we will be happy to assist you further.
Problem: After switching servers, the client's credits are missing on the same domain. Solution: Removing a Site’s Registration from WPML.org account returned the missing credits to WPML.org account to use any of the registered site.
Problem: The client is looking for a way to automatically send new or edited content to a translation service and to ensure that all new Pages/Posts are saved in Draft mode until they are translated.
Solution: 1. To automate the translation process, we recommend switching from "Translate Some" to "Translate Everything" mode in WPML -> Settings. This will automatically send content for translation.
However, for the specific workflow where content is automatically sent to a translation service and both the source and translated content are published after translation, this would require custom development. For such custom work, we suggest reaching out to one of our recommended contractors: WPML Contractors.
If this solution doesn't look relevant to your situation, please open a new support ticket so we can assist you further.
**Problem:**
I am having this issue where, after changing the product category layout, the English page displays correctly, but the Arabic page still shows the previous layout, resulting in unsuccessful translation. Additionally, when copying the homepage layout to the product page, the Arabic content does not translate, and there is an issue with blog cards not displaying images.
**Solution:**
To address the layout issue, I created a backup of the website and worked on resolving the product page problem. Specifically, I disabled the image title function and added a title element below the image to ensure successful translation. After these adjustments, the Arabic version of the product category layout on the product page was updated. The problem was resolved by recreating the products page for the Arabic language.
Problem: The client needed guidance on adjusting the character amount for their website when creating a key for automatic translation in WordPress and whether this key can be recreated with a different amount. Solution: If you're experiencing confusion about the automatic translation process and how we charge per number of words, we recommend you review our documentation on automatic translation pricing.
Should you have available credits, you can select a specific number or create a key with zero credits and add credits later. You maintain full control to add or remove credits as needed. For further details, please refer to our documentation on how to assign automatic translation credits to your sites.
Additionally, you can use the calculator found in the FAQ section titled "How much does automatic translation cost?" on our automatic translation pricing page to estimate the cost of credits.
If this solution doesn't seem relevant to your issue, please feel free to open a new support ticket in our support forum.
Problem:
I am having an issue where updating a page or post in any language only shows the live page without visible changes in the preview. This problem occurs only with pages or posts that are already published; drafts preview correctly. The issue started after upgrading to the newest WordPress and updating my theme. It wasn't present on a staging site but appeared on the live site. Deactivating WPML resolves this issue, indicating a relation to WPML. I've already tried deactivating caching plugins, clearing my cache, clearing cache in WPML, and switching themes, but none resolved the issue.
Problem: The client is seeing a message from WPML indicating that a new address for the site has been detected, which is a non-existent URL. Solution: We suspect that the URL might have been associated with a staging/testing environment or an alias created by the hosting panel during the initial WordPress setup. This can occasionally happen due to server changes or updates. We recommend the following steps: 1. Create a full backup of your website. 2. Select "NO" when prompted by the WPML notice regarding the new address. This should resolve the issue and the notice should no longer appear.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem:
I am having this issue where I moved my website to a new URL, and now I can't update the plugin because the key product is no longer valid.
Solution:
The issue was resolved by generating a new key for the new domain from the WPML account's sites page and then registering WPML with the new key in the site's backend.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive