- This topic has 4 replies, 2 voices, and was last updated 12 years, 8 months ago by .
Viewing 5 posts - 1 through 5 (of 5 total)
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › Items won't add to cart
Tagged: shopping cart problem
I installed WP eStore fine, everything worked fine, shopping cart showed, tested good to PayPal. Added additional products, now clicking “add to cart” does not add items to the cart, even on same original test products. Cart stays empty.
Page that store is on is:
I have done nothing since installing and populating store. No plugin changes, theme changes, updates, etc. Just installed eStore, tested successfully, added products, now not working.
Could this be a license issue? I purchased the eStore about a year ago and am moving it to a new site. Is there a number of products limitation because I haven’t somehow connected it with my license?
Hi,
Since your eStore version is fairly outdated please load the latest version by following the instructions here, and if there’s still a problem we’ll take it from there:
https://support.tipsandtricks-hq.com/forums/topic/re-install-or-load-a-fresh-build-of-the-plugins
Updated to Version v6.5.1. Still same problem. email if you need to log into my WP I’ll make a user for you.
Hi,
You say that you’ve moved eStore to a new site – is this a completely different WordPress installation or have you migrated an existing site to another host provider?
If it’s a completely different WP install, have you ensured that you’ve configured it correctly?
ie, have you added a cart somewhere on the page such as the sidebar widgets or on the page using a shortcode (I can’t see a shopping cart shortcode on your site)?
[wp_eStore_cart_when_not_empty]
FIXED: I decided to add a new page and paste the existing code there and the page cart now works. (Yes the short codes were there). Must have been a bug on that specific page!
Thanks for your attention!