George Botsev
Forum Replies Created
-
Hello!
I am unable to reproduce the scenario that you report.
Could you please check if you have the string that matches your product base translated in WPML > Strings – perhaps more than once?
Also, it would be great if you can remove all instances of that string in there in WPML > String Translation and then re-translate and check if this happens again.If this happens again, I would ask you kindly to open a new ticket, but in our forum at wpml.org so that we can ask you for access and attempt to trace the problem in your site.
I provided you with a solution.
It seems that your theme and one another plugin are not compatible and quite outdated, thus creating the issue with the option “Language as parameter” in WPML > Languages.Hello!
I am sorry that you are upset and you have difficulties in setting-up correctly our plugin.
The forum at wpml.org sometimes is overloaded, and you might receive a response with up to 24 hours of delay – depending on the load.
However, we also offer initial support here in the Support Threads for WooCommerce Multilingual – where you can also ask for help, and if you have a ticket in wpml.org to point us to that ticket so that we can prioritize it (if possible).If you wish for me to help you – please let me know, provide more details about the issue and your wpml.org ticket link and let’s work on the problem.
Hello and thank you for contacting us.
The issue that you are describing is a very strange one and I have not seen it yet.Do you have an idea how this can be reproduced?
Have you tested with a standard theme like StoreFront or TwentySeventeen – if you can reproduce the problem?
Can you provide exact steps that I can follow in order to reproduce the problem, and if you have a site where I can see this in action?
Hello Anita,
I suggest first going to WPML > String Translation and removing the old string, then re-saving the page in Woocommerce – Settings – Payments – Direct Bank Transfer, so that the string in question is re-registered once more and re-translating that string.
It is possible that this helps in your case.Please let me know how it goes.
If it is not working, I suggest that you open a new ticket in our forum at wpml.org where we can ask you for credentials and see the problem more closely and debug it.When you delete a string – its entry is removed in the icl_strings and icl_string_translations tables. Then if the strings is in a .mo file – after a check for new .mo files/updates of .mo files it is re-added. If the string is displayed somewhere, then it is automatically re-registered (if it does not exist) and the translation is added from .mo file if present. The settings that are good to be enabled are the auto-registering of strings in WPML > String Translation.
“Following string translations”? Do you mean the options to not load the .mo files in WPML > Theme and plugin localization?
That option improves performance because by default WordPress loads the .mo files contents and translations and WPML String Translation does the same – so double the load without that option.
If you check the option that “original language of string is English” this is known to increase the performance, but it is only available if your default language of the site is English – as this saves loading of strings in the memory instead of loading another set of strings for the language and uses the string from the source instead – which is faster than querying the database.
However, if you have defined strings in French in an example, and you have that option enabled – then the French strings will be considered to be in English.I hope I have explained it well and that I have understood your question accurately.
Please excuse me if it is not so and let me know.Okay, I see the screenshots and everything looks right and as it should be.
It is possible perhaps if you remove these strings and try and re-translate them?
*You might have to re-save the payment method titles.If this does not help, then I suggest that you open a new ticket in our forum at wpml.org where we can ask you for access and check the site and try to debug the issue.
Hello
I need more details in order to provide a viable path to follow for resolving this problem.Could you provide some screenshots of the string in question and of the code that generates this string?
In order to be translated properly, a string needs to be wrapped correctly in a gettext call.
Perhaps our documentation here: https://wpml.org/documentation/support/troubleshooting-string-localization/ might help?Hello!
For now, in our plugin, it is not possible to set a manual price for the shipping price.
If I understand correctly, you want another layer of complexity – setting the price manually for a country that uses certain currency, and that is something that is also not a feature that we offer. Perhaps everything that you want could be achieved by custom coding and manually overriding the shipping price when you detect the shipping country with the hooks that WooCommerce offers, but it is a huge project.I reproduced the problem that you are reporting.
However, I am not sure if this qualifies really as a problem, because it happens only when WPML setup has not been completed.In order for WooCommerce Multilingual to work, you need to have WPML, WPML String Translation and WPML Translation Management plugins running as well.
WooCommerce Multilingual depends on classes, methods and API calls from these plugins.
Completing the WPML setup fixes this issue for me.
I will report that to our developers, but I suggest you install WPML and complete the setup, or simply remove WooCommerce Multilingual plugin because it is ineffective without the other above-mentioned plugins.
I am very much certain that if you update to a more current version – preferably the latest one, then the problem will be resolved.
WPML 3.5.0 is a very old version. Perhaps maybe more than 2 years old.Of course, always make a backup before doing such big upgrades.
You can use a plugin like Duplicator – as it is a fast and secure solution for 1:1 backups.Hello and thank you for contacting us.
Which version of WooCommerce Multilingual are you using?
Which version of WPML plugins are you using?
I would like to recommend you to upgrade to the latest version of WPML 4.0.8, as the error that you mention here looks like a class that we expect to be there is missing and creating the problem.Thank you for the information.
I tried to set up the same environment and to reproduce the problem.
However, after setting up the environment, I am unable to reproduce the exact issue that you report.For me, there is no change in the elements.
Are you using some other plugins?
Could you test in a minimal setup – running only WPML, WPML String Translation, WPML Translation Management, WooCommerce Multilingual and WooCommerce?
Hello and thank you for contacting us.
This is a very atypical problem.Could you tell me please which theme are you using?
Have you tried with a default theme like TwentySeventeen or Storefront?
Do you use some kind of resource optimization like CSS minification and concatenation? – it is possible that you might be loading some CSS that should be used only on the admin side.Actually, in this case it was the theme (flatastic).
I assume that you fixed the problem then?
The .mo file for themes should go to a separate folder – /wp-content/languages/themes/
and should be named by the theme domain name that is used – in example “twentyseventeen” for Twenty Seventeen and then suffixed by the language code- in example: twentyseventeen-es_ES.mo for Spanish