[Resolved] something like this happend $28.36 [English] ($23.06, netto)
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues where the name of the current language appears next to the currency numbers when switching currencies, or if you need to auto-translate custom Elementor widgets, follow these steps. Solution: For the currency display issue, it appears that a string was incorrectly translated. We recommend you navigate to WPML-> String Translation and delete the translation of the problematic string. This should resolve the currency display problem. For translating custom Elementor widgets, please check our documentation on how to manage translations for Elementor widgets using WPML. If these steps do not resolve your issues or if the solution 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am trying to fix an issue on my site hidden link where after translation, the name of the language has been added to the price. WordPress indicates it's a problem with the taxonomy of product_type.
Symptoms:
After translation, the name of the language is added to the price.
Questions:
How can I fix the issue with the language name being added to the price after translation?
I'm affraid that my problem stil exists... I'm guessing it's something wrong with translations.
Where I can find this place to remove tranlation?
I've noticed that after reset all translated content hasn't been removed from my site so I'm cleaning up myself
Thank you I've rosolved that on but having one more problem
admin_texts_woocommerce_gateways bacs_gateway_title
Przelew bankowy
won't translate to english or german, it says is waiting for translation but its been a long time and nothing happed. It is from checkout information about payment
Please delete these stuck strings, search for them, and translate them.
If you can't find them after deleting them, please try the following steps:
1- Go to WPML-> Theme and plugins localization, select your theme/plugin, and scan
2- Go to WPML-> String Translation
3- Scroll down and click on the "Translate texts in admin screens »" link
4- Search for the needed strings
5- Select the strings
6- Click on the "Add to String Translation" button
7- Then click on the "« Return to String Translation" link
8- Translate the strings, clear the cache, and check the front end
Thanks for your reply. I would need to look closely at your site, so I would need to request temporary access (WP-Admin and FTP) Preferably to a test site where the problem has been replicated.
Your answer will be private, meaning only you and I can access it.
❌ Please backup your database and website ❌
✙ I need your permission to deactivate and reactivate the plugins and themes and change site configurations. This is also why the backup is critical.
✙ I also need your permission to take a local copy of your site to debug the issue without affecting your live site.
Thanks for that 🙂 There is one more problem, when I choose language like German or English and switch currency to Polish zloty I can seen name of current language next to the numbers. How to fix it?
And finally last one I promise. How to translate custom elementor widgets? I mean autotranslate them
New threads created by Osama Mersal and linked to this one are listed below:
1) Please let me know how this cart widget is added to the header.
2) We try to keep one issue per ticket in our forum. Continuing with one ticket per issue helps supporters focus on one issue at once and enables other users to find solutions to their questions faster.
Therefore, I've split the other issue and created a new ticket with this issue.