Just out of curiosity... can you please do the theme switching test explained here and let me know if that makes any difference?
http://www.tipsandtricks-hq.com/forum/topic/test-to-identy-a-conflicting-theme-or-plugin
Just out of curiosity... can you please do the theme switching test explained here and let me know if that makes any difference?
http://www.tipsandtricks-hq.com/forum/topic/test-to-identy-a-conflicting-theme-or-plugin
Hello again!
The theme is definitely the culprit here for this project. Went through the motions of cleaning it up a bit but unfortunately didn't have any luck. :/
In lieu of your previous comment though, I went ahead and enabled the redirect upon adding to cart option (which had worked), and set the URL set to "#". Kind of an unorthodox fix, but it should do the trick. The only issue that remained was receiving the 404 error upon removing an individual product. I noticed that the "Clear All" button seemed to behave appropriately with this runaway theme even though the individual remove did not.
I just added display prop to the following in the eStore CSS:
.eStore_remove_item_button{
width:20px;
height:20px;
display:none;
}
This should work out for the time being until I can figure out a way to have the individual remove button achieve the same effect.
Thanks again for an amazing product!
Cheers,
Hi,
Just a quick message to say "Thank You" to raistlin for this thread!
I was experiencing exactly the same problem on a client's site. Trying to use the WP eStore plugin and a theme that had a default cart built in was definitely causing a 404 error when trying to update the shopping cart. (The theme was Kid's Toys from Theme Forest, if you're wondering!)
Disabling the theme's default cart (i.e. removing the files and all functions references) does fix the problem.
As raistlin notes:
$products variable is used in the theme for its own purpose and I replaced them with $wp_shopping_cart_products and my problem resolved.
Question: Would it be possible to change the $product variable in the plugin to be unique (and so resolve any future conflicts)?
Cheers,
Zain
We don't have a global $product variable. I am not sure what that theme is trying to do but a product should not be accessed via this $product variable.
Good answer. ;) I'm not sure either, although something was really messing up the eStore plugin. I managed to fix it(i.e. hack the living daylights out of the theme)... I'm just glad for raistlin's observations! Phew. :D
You must log in to post.