Home › Forums › Mikmag WordPress theme › Shopping Cart updating issue
- This topic has 1 reply, 2 voices, and was last updated 11 years, 3 months ago by Anonymous.
-
AuthorPosts
-
-
at #12861AaronMember
At first I thought this was strictly a woocommerce issue, but after looking into it more it’s more likely that the theme is overriding one of the woocommerce files that might possibly address the issue. Basically, at my site vrtssystem.com if you add something to the basket and checkout, it works great, no problems. However, if you click the ‘remove’ X on the left side with something in the cart, depending on the browser it may or may not work. Latest version of firefox, doesn’t work. Earlier version does though. It’s like the page doesn’t reload properly sometimes. Clicking ‘refresh’ always solves the issue though. Is there any way I could insert some code to force refresh the cart page on remove actions? Thanks!
-
at #12867AnonymousInactive
Hi Aaron,
I’ve taken a look at it and I see how your cart is somehow being cached or not properly reloaded ( I am testing on chrome, currently). I then went to our demo page http://www.theme-dutch.com/presents/mikmag/ to see what would happen there but I did not get that same issue on our website.
Have you tried disabling your plugins for a bit (except woocommerce, obviously) see if it still happens then? Perhaps you have some caching plugin that might be causing this?
Also just to make sure there really is this difference between both our websites, does our demo site’s cart work properly for you on latest firefox?
Kevin
-
at #12872AaronMember
I don’t have any caching plugins, my plugins are basically just woocommerce and the woocommerce ups shipping plugin. However, I am probably running a newer version of woocommerce than you are using, perhaps that’s the issue. I’m currently using 2.0.14, what is the demo site using currently? Thanks
-
at #12875AnonymousInactive
On our demo we currently run wp 3.6.1 and woocommerce 2.0.13
So that could indeed be the difference that causes the issue.
Do you think you could try it on 2.0.13 to see what happens?
With kind regards,
Kevin
-
-
AuthorPosts
- You must be logged in to reply to this topic.