Problem:
I have set up a bunch of custom fields for a post type using ACF. These will be translated using the translation editor. However, the custom fields appear in the order that they were added to the database, which does not match the order they are in when editing the posts. The order of custom fields in the posts follows that of the ACF field group and this order can be re-arranged, for example after adding more custom fields.
Solution:
WPML is not made to update based on the order changes that you made on the field group. This is gonna work only on the WordPress editor, but the WPML translation editor has no logic implemented for this.
Problem:
I am trying to translate a page from English to Chinese. I expected to see the masonry gallery exactly the same both on the original and translated page.
Solution:
Edit each image of the Masonry Gallery through Dashboard → Media library (in list view). Open one of the images, and check the value of the Masonry Image Layout option at the bottom of the page. Now, change the language using the top admin language selector and make sure that this custom field has the same value. Once you did this, just simply update the image and that's all.
Just make sure that you did this for all the images of the masonry gallery.
Problem: Got an alert that the site moved or Copied - Action required.
I used duplicator site to copy this site to another test/staging site. Why does it show on my production site this message and not on staging site?
Solution: Moving or copying your site has implications for the Advanced Translation Editor. You need to tell WPML if your site has moved or is a copy so it knows how to treat your translations and translation memory.
Problem:
When I translate a website in a new language, I don't want my URL(slug) to be translated into the new language. I want to keep the same.
Solution:
- Go to WPML=>Settings => Translated documents options=> and select "Translate (this will include the slug in the translation and not create it automatically from the title)".
- Now when you translate just confirm and save the same URL slug. You can also go to your secondary language post/page and within quick edit settings, edit the slug.
Problem: The client wants to set different pricing policies for the same product based on the customer's location, using the same currency (Euro) but with different prices in different countries (e.g., France 100 EUR, Netherlands 80 EUR). Solution: From WooCommerce Multilingual version 4.10 onwards, it is possible to set currencies based on the user's location using the MaxMind Geolocation API. For more details on setting this up, please refer to the MaxMind Geolocation Integration documentation.
Currently, WooCommerce Multilingual does not support different prices for the same currency based solely on location without changing the currency. However, we are considering adding this feature in future versions. In the meantime, we recommend trying the WooCommerce Product Price Based on Countries plugin, though it has not been tested by our team. Please ensure to back up your site fully before using this plugin.
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 further assistance is needed, please open a new support ticket.
This was an issue with the currency symbol in the mini cart widget in the header. It didn't change to the current symbol when the cart was empty.
Solution:
We checked this issue on our side and found it was not an issue with WPML or WooCommerce Multilingual & Multicurrency. It was an issue with the custom code by the user.
Problem: The client wanted to translate the currency symbol from 'EGP' to 'جنيه' using string translation, but it was not working. Solution: We informed the client that currency symbols are managed by WooCommerce and there are limitations to translating them directly through string translation. However, we provided a solution using WooCommerce hooks to change the currency code. We directed the client to the WooCommerce documentation on how to change a currency symbol and provided sample code to be placed in the
functions.php
file of their theme after ensuring a full site backup.
We asked the client to try this solution and provide feedback.
If this solution does not apply to your situation, 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 further assistance is needed, please contact us through the WPML support forum.
- Add a new Footer using the builder and name it English Footer.
- In the screen of the Section Builder disable the Use WPML's Translation Editor option.
- On the pop up choose This Section Builder.
- Click the + or pencil icon there for the other language translation.
- You will be redirected to the other language version and you can either add the footer from scratch or copy it from the original language by clicking the Copy content from ... button.
- From the address bar of your browser check the URL when you are in the second language of the Section Builder and write down the post ID for later use. For our example, it was 25.
- Go to "Appearance > Customize > Header and Footer > Footer > Footer Section" and select the English Footer and publish the settings.
- Go to "WPML > String Translation > admin_texts_theme_mods_hongo" and translate the page ID there.
For example the current page ID there is 20 for English. We need to add 25 (The one that we wrote down) here for Spanish.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
