Hi @apachevape,
Are you able to have a look in the browser console for javascript errors? It’s like to be a conflict with some other plugin.
Here’s a guide how to do that:
https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors
Once we know what the error is we might be able to narrow it down to a particular plugin.
The other way you can do it is disable all plugins then re-enable them one by one to see which one causes the conflict.
Hope this helps!
Cheers,
Josh
OK, I’ve tracked it down to the WPBakery Visual Composer plugin – disabled it and I can edit the Wholesale prices – not ideal having to do these edits at strange hours of the night though – is there anything I can do to fix this?
Hi @apachevape, are you on the latest version of both our plugin and also theirs?
Any chance you could post the error?
You might also like to check the error_log file which should be in the base directory of your install (you can get it via FTP).
Keen to see if we can trouble shoot this for you.
Cheers,
Josh
We have managed to fix the javascript conflict and can now add wholesale prices in the backend – these show perfectly in the backend – I have assigned a user as a Wholesale Customer, logged into the site frontend and viewed a product which I know a wholesale price was applied too – and nothing still shows the retail price.
Hi @apachevape,
It might be worth checking caching, do you have server side caching? Or running an aggressive caching plugin perhaps? Does it apply to logged in users too?
Typically all you need to do is create a new user, assign the wholesale customer role, then make sure your product has a regular price and a wholesale price defined.
Couple of things you could try after checking the above:
1. Login using a fresh Incognito/Private Browsing window and test again.
2. Goto WooCommerce->System Status, Tools tab, hit clear sessions to clear all the cart sessions. Normally this isn’t required but it might help.
3. Turn off your caching temporarily to see if the problem goes away.
Hope this helps narrow it down!
Cheers,
Josh
PS. Do you have any details about the JS conflict? Would love to know what it was exactly.
(EDITED) Accidentally posted same answer twice…
-
This reply was modified 9 years, 4 months ago by
Josh Kohlbach. Reason: Deleting double entry
