wpbft
Forum Replies Created
-
Ok. That does not work for me, but I’m glad it helps for you. Please don’t consider it a general solution to the 3.0.x problems yet, as there seems to be other issues with this update.
fwkart, I have tried to replicate your suggestion by switching the Optimized DOM Output on/off. That does not solve the issues I’m experiencing with 3.0.1 (mainly issues with font and colors).
Can you explain what problems switching on/off the optimized DOM output solves on your install(s)?
- This reply was modified 5 years, 9 months ago by wpbft.
I marked this as resolved but unfortunately there are still problems with #1 on several sites. Editor displaying something else than live site, no matter if cache is cleared, css reset and so on.
While I’m also experiencing similar problems and slightly shocked that 3.0 has passed quality control, I think we’ll all benefit from explaining to Elementor so they can be solved. What problems exactly are you experiencing?
Also, the global fonts can’t be applied to theme settings. Replicate this way (in any order):
* Add a heading to page
* Define a custom global font
* Apply to any header (for example H1) in theme settings–> No change on live site
This is also tested with a clean install with only WP 5.5, Elementor 3.0.1 and Hello Theme. Refresh CSS is tried. Also tried to “Disable default fonts” and refreshing css.
- This reply was modified 5 years, 9 months ago by wpbft.
#1 is solved in 3.0.1
#2, see a better and updated post here: https://ww.wp.xz.cn/support/topic/3-0-1-headings-global-font-size-problem/Hi David!
I just tested this with a fresh install without upgrading anything at all, starting with 3.0 straight away.
So I think this is not related to upgrades/data migration.
Forum: Plugins
In reply to: [ECS - Ele Custom Skin for Elementor] Upgrading to 3.0.0 broke my siteAfter doing some more research it seems that I have been wrong about the source of the error. It seems that it is actually caused by another plugin (Dynamic Content For Elementor – dynamic.ooo). When disabling the “Template” and “Token” extensions in that plugin, errors are gone.
I’m still not sure though if it’s caused by a conflict between these plugins, so I will leave the question open. It seems like others here are experiencing similar issues. I still believe it happened after upgrading to 3.0.0, but I could be wrong.
Forum: Plugins
In reply to: [ECS - Ele Custom Skin for Elementor] 3.0.0 Fatal Error con Elementor 2.9Can you explain that fix? How do you revert back to use ElementorPro\Classes\Utils?
Including the sales price should be default behavior.
Forum: Plugins
In reply to: [WPC Fly Cart for WooCommerce] SpeedHi,
Thanks for the feedback.
How long time does it take on your test setups to add/remove?
Is 2.5 seconds normal or above expected?I am hosting with Kinsta (Google Cloud) which is a fast Premium-host.
Best regards.
Thanks.
Surely there must be a way to modify the template? If you decide to include it as a Pro version feature in the future, let me know.
Hi Auke,
Thank you. I can confirm this solution works.
I found that the best way to go about it is to use a space (” “) as the thousand separator instead of “.”
I tested this by uploading the feed again to Google Merchant Center, and it seems like Google accepts this.
Perhaps a solution for this would be good for the future. For those (Italy, Spain, Norway, Netherlands(?)) who use “.” as thousand separator, this can easily go unnoticed when you have a large product catalogue, leading to incorrect pricing in Google. After all, (to the best of my knowledge) it is the default setting in Woocommerce when your language is set to one of the above.
Hi,
I have the same problem as the gentleman above.
The thousand separator in my country is a period (.)Product price is 1305 kr, and is entered into Woocommerce without any comma or period.
Ends up as 1.3 kr in Google Merchant Center.
Price in the feed is 1.305: https://ibb.co/JnpQKjT- This reply was modified 6 years, 4 months ago by wpbft.