Problem: The client needs guidance on how to manually add translated blog posts and link them correctly to their respective language versions and domains in WPML. Solution: If you're experiencing this, we recommend using the manual translation method available at Using Different Translation Editors for Different Pages. Alternatively, if you have already created the pages with the translated content, you can follow these steps to connect a translation in the WordPress backend for each language. This can be done by selecting a different language backend from the top black bar while in the site backend. Detailed steps can be found at How to Link Already Translated Pages.
Please note that the solution might be irrelevant if it's outdated or not applicable to your case. 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 issue persists, please open a new support ticket at WPML Support Forum.
Problem: The client is trying to configure WPML for multiple domains (models118.de, models118.at, models118.ch) that share the same German language. The issue is that models118.at and models118.ch are treated as separate language domains instead of sharing the German content from models118.de. Solution: 1. Navigate to WPML-> Languages-> Edit Languages. 2. Ensure you have different locales set up, for example: * German (Germany): de_DE * German (Austria): de_AT * German (Switzerland): de_CH 3. Map these locales accordingly. 4. Click 'Save'. 5. Verify that the domains are added correctly. 6. Resave the permalinks. After these steps, the domains and languages should work correctly. To display the main domain content on the secondary domains without translating, you will need to either duplicate the content or use the fallback function.
If this solution does not resolve your issue or seems outdated, please check the related known issues and verify you have the latest versions of themes and plugins installed. If further assistance is needed, we recommend opening a new support ticket at WPML support forum.
Problem: You are trying to resolve an issue where the updated PLN prices via BaseLinker's API are visible in the WooCommerce product backend but do not reflect on the frontend without manual updates. This behavior differs from EUR prices, which update immediately. Solution: Firstly, BaseLinker is not officially compatible with WPML, which might be causing the issue. We recommend contacting BaseLinker's authors to consider joining our GoGlobal program to work towards compatibility: https://wpml.org/documentation/support/go-global-program/ If PLN is your second currency and you are updating it, WPML synchronizes changes when the post is saved. You might need to trigger a re-save of the post using hooks like
save_post
or
update_post
. This approach may require additional custom coding. For custom coding, consider hiring a contractor from WPML: https://wpml.org/contractors/
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 issues persist, please open a new support ticket for further assistance.
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 https://wpml.org/forums/forum/english-support/.
Problem: The client is using WPML for their website and has questions regarding the costs of translating sentences with variable attributes, the automation of translations for new content, and whether numerical values are excluded from translation costs. Solution: 1. WPML utilizes a translation memory, which means you won't be charged for sentences that are identical to those already translated. For more details, visit how WPML keeps track of your translations. 2. If you use the "Translate everything automatically" option in WPML > Settings, WPML will translate any new content when changes occur. However, this might consume many credits if there's a lot of new or final content. Alternatively, the "Translate what you choose" setting allows more control, letting you select specific content for translation. 3. For sentences with variable attributes like [Scale], each unique sentence is considered new and will be charged unless it matches an existing entry in the translation memory. Sentences need to be 100% identical to be reused from memory without charge. 4. WPML does not translate or charge for numerical values like years or dimensions, as these are recognized as non-translatable and reused from the translation memory.
If this solution does not fully address your issue or seems outdated, we recommend checking related known issues at WPML 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.
Problem: You are trying to manage product translations on your site using WPML and want to prevent certain product titles from being translated while ensuring that all product details, especially colors, are translated accurately. However, WPML sometimes leaves product colors and certain details untranslated, causing inconsistencies in product descriptions. Solution: If the WooCommerce Multilingual plugin is active on your site, all product data, including taxonomies and variations, should translate easily and remain consistent. To keep the product title consistent across languages, when translating the product, copy the title from the default product into the translation. In the translation editor, translate the rest of the content and save the translation. This way, the product title will stay the same in all languages, while other data like taxonomies and variations will be translated properly. Ensure that the WooCommerce Multilingual plugin is installed and activated on your site, as it handles the translation of all product data, including variations, correctly. For more details on translating products and their data, please refer to this guide: https://wpml.org/documentation/related-projects/woocommerce-multilingual/
If this solution does not apply to your case, or if it seems outdated, we 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 you still need assistance, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
