Cheyenne Throckmorton
Forum Replies Created
-
Forum: Plugins
In reply to: [BigCommerce For WordPress] Cookie Naming Issue for PantheonAfter BC4WP version 3.8 you will also need to look into the JS files where the cookie is named in a way that interferes with Pantheon default varnish cache solution.
Do a find and replace within /assets/js/dist/script.min.js for “bigcommerce_cart_id” and “bigcommerce_cart_item_count” and then replace them with “wp-bigcommerce_cart_id” and “bigcommerce_cart_item_count” respectively. This should fix the carts ability to update quantities and have the remove item buttons operate normally. I presume this probably fixes some other things as well.
There is probably a better way to do this and as we find them I’ll try and remember to update this thread.
You might also find this thread helpful where there are few more details. https://support.bigcommerce.com/s/question/0D54O00006Mp4SPSAZ/remove-button-from-cart-is-not-working
I haven’t heavily tested, but after upgrading to 2.2.6 I have not seen any errors where I was seeing them. Nice job!
I’m seeing the same thing. Logs seem to point to a memory error. Happened right after moving from 2.2.4 up to 2.2.5.
Forum: Plugins
In reply to: [BigCommerce For WordPress] Cookie Naming Issue for PantheonI ran into this same issue @adamwlang
For now, I’ve manually edited the cookie name in their plugin to be wp-bigcommerce_cart_id so this plugin will work on Pantheon.
In talking with BC support, I’ve suggested they change the cookie name from a constant to a variable with getters and setters with a hook so if need be we could rename from the default. That way we wouldn’t have to edit the plugin itself… which is not my favorite, but necessary for now as I see it.
There will be other issues to resolve like we will lose the advantage of Pantheon varnish cache as soon as someone adds a product to cart. That’s probably another issue to tackle on a different day… but maybe something with setting the cookie at path of /cart and then making sure checkout is at /cart/checkout or something. I’m not sure that will solve everything like the cart pebble update but getting these systems all working together should provide a nice and snappy speedy site.