No count and no add to cart button

@frankhmila, I’m sorry for the delay in response, but we are not getting any reports of this from others nor I am seeing this on my test site tough, I have just tested with Divi theme and its showing it without any problem. So I can suggest 2 things here as basic debugging steps.

1- Switch to basic twenty theme and see if you get things working as expected. If so then your theme may be the reason for that .
2- Otherwise, disable all extra plugins then check again and see if you get this working as expected then one of the installed plugins might be conflicting. Just activate them one by one to catch the culprit.

Also, look for your server error logs for any error reported there?
Please run those test and let me know what you got.
Thanks!

Here the problem

with WPML! with product translated in 4 languages, works with ENG,FRA and DEU, but not in ITA that is the default language!

What can i do?

@frankhmila, so its working for all those 3 files except for the default language? This is not something we are hearing a lot from others, so something unique might be in your case. Did you tried to disable all extra plugins except for ours and wpml and then see if this start to work?

Works in default language only if i disable WPML

all plugins disabled, default theme and only wpml enabled, not work default ITA language

@frankhmila, Thanks for the feedback. We’ll add this to our GitHub repo for the next update and will see if we need to make any adjustments then will do that.

Ok, but i need it now, not in the next version.

Why all be good with secondary languages and not work with primary?

Can you access the site and investigating?

@frankhmila, It’s tough to say what could be going on there. We’ll have to install the plugins together, setup some translations, and run some tests to see if we can reproduce the problem. At that point we can make adjustments to fix it.

Unfortunately, this plugin is not one of our more popular plugins, and while we love it and will continue working on it in the future, it’s tough to make it a priority over some other things right now. As mentioned, we’ve added it to GitHub and we’ll certainly look into this as quick as we can.

If you need more immediate assistance with this you could submit an order for premium support. It’s tough to say how many hours it will take to fix it, though, without doing the initial testing/troubleshooting. I would guess it could end up being a 3 – 5 hour deal.

If you want to do that we can get somebody on it right away. Otherwise, we’ll get back on this project ASAP!