George Botsev
Forum Replies Created
-
@bruno.marques @rodrigocoragem96 are you getting the exact same error?
Perhaps you should temporary switch off WooCommerce Multilingual, change the value in the database for ‘_wcml_version’ to 4.0.0 and then re-enable the WooCommerce Multilingual plugin again.Regular price in EUR is empty
While EUR is your default currency it is not correct to leave it empty.
What happens if you fill the EUR regular price?
Is it behaving the same way?Hello, usually such field should be set to “translate” in WPML > Translation Management > Multilingual Content Setup > Custom Term Meta Translation (because they are assigned to terms).
Once this is done, it should be visible when you create a new translation job or re-send already translated element to translation again.
You could also check in WPML > Taxonomy Translation – if it is shown there as well.
If this is not happening, perhaps it would be a good idea to open a new ticket in our support forum at wpml.org so that we can investigate more in-depth of the cause of this.As far as I see, Storefront adds overflow:hidden in /wp-content/themes/storefront/assets/sass/woocommerce/woocommerce.css?ver=4.7.3
and this makes the currency switcher not behave properly when set as dropdown or dropdown click.
A temporary fix should be if you set.single-product, div.product { overflow: visible !important; }- This reply was modified 9 years, 2 months ago by George Botsev.
Thank you for reporting this.
We are investigating the issue.
I will let you know when we have some progress there.
For now I can confirm that the issue is happening and I am going to escalate to our developers.Hello, in WooCommerce Multilingual we introduced much improvements to the currency switcher – including templates.
Perhaps if you go to your widgets and edit the currency switcher – this error may be gone.
Another possible solution is to remove the widget and add it again.Please let me know how it goes.
Hello,
Previous versions are available here: https://wordpress.org/plugins/woocommerce-multilingual/developers/Did you disable all currency switchers from the multi-currency page in WooCommerce Multilingual?
Well I got one bug that I have just escalated to our developers.
To work-around the issue, you need to create a new template as of ver. 4.1 WooCommerce Multilingual allows language switcher templates: https://wpml.org/documentation/related-projects/woocommerce-multilingual/designing-custom-currency-switchers-using-template-files/
So you need to create a template without css file in your theme folder:
\wpml\templates\currency-switchers\my-template
config.json{ "name": "My custom switcher", }template.twig
<div class="{{ css_classes }} your-custom-class" > <ul> {% for currency in currencies %} <li {% if( currency == selected_currency) %} class="wcml-cs-active-currency" {% endif %} > <a rel="{{ currency }}">{{ get_formatted_price( currency, format )|raw }}</a> </li> {% endfor %} </ul> </div>Then you need to go to MultiCurrency tab in WooCommerce Multilingual and temporary enable Show a currency selector on the product page template and select your new custom template from the list. After this you can disable the option: Show a currency selector on the product page template
This should make the style.css for the legacy-dropdown be disabled – because you are loading a template without .css fileHello,
You are using WPML 3.5.0, however the class WPML_File was introduced in WPML 3.6.0 and above.
Please make sure that you are using that version and if not – please update.Hello,
Could you please paste here the error that you are getting?If you are not using the currency switcher you could remove leagacy-dropdown/style.css
However, I would not advise you to remove cart_widget.js because it is related to cart fragments functions in WooCommerce and this might prevent the correct ajax updates to your cartForum: Plugins
In reply to: [WPML Multilingual & Multicurrency for WooCommerce] error warningsLatest version of WPML is 3.6.3 and the class WPML_File is introduced (if I recall correctly) in WPML 3.6.0
Error 500 is completely different thing and you have to enable debugging so that I can try to think of some reason why this is happening.
The error could be in the server log or in the debug.log from WordPress.
To enable debug logging in WordPress you need to set this options in wp-config.php
above the line that says:
/* That’s all, stop editing! Happy blogging. */
// Turn debugging on
define('WP_DEBUG', true);// Tell WordPress to log everything to /wp-content/debug.log
define('WP_DEBUG_LOG', true);// Turn off the display of error messages on your site
define('WP_DEBUG_DISPLAY', false);// For good measure, you can also add the follow code, which will hide errors from being displayed on-screen
@ini_set('display_errors', 0);
Please do note to remove any other instances of this code if you have it in the file:
define('WP_DEBUG', false);
Forum: Plugins
In reply to: [WPML Multilingual & Multicurrency for WooCommerce] error warningsI am not sure if it is the best solution to downgrade WooCommerce Multilingual, since you obviously have older WPML than 3.6.3
Forum: Plugins
In reply to: [WPML Multilingual & Multicurrency for WooCommerce] Order QuestionWell, I see in our tracking system that this exact problem is scheduled for the next version – so still no workaround for this.
Of course once I have a viable solution I will get back to you here.Forum: Plugins
In reply to: [WPML Multilingual & Multicurrency for WooCommerce] Woocommerce 2.7 betaA very crude method would be to use something like this:
add_filter( 'wc_product_has_unique_sku', false, false, false );
in your functions.php file in your theme until this is fixed in WooCommerce Multilingual.