Digital experiences for all disciplines
New Landing › How can we help? › Atelier › add to card short code problems
New Landing › How can we help? › Atelier › add to card short code problems
- This topic has 9 replies, 3 voices, and was last updated 8 years by Mohammad – SUPPORT.
-
Posted in: Atelier
-
August 31, 2015 at 12:23 pm #208837
the woocommerce add to cart short code has a lot of problems.
again it is not clear who is to blame, woocommerce or swift, as it not possible to tell whose code is whose when looking at source.problem is this: user clicks on add to cart item and eventually the icons turn into 2 message: adding… (with a check mark), and view cart.
click on view cart does nothing.
clicking on adding… takes you to a product page.
this is just plain incorrect.
fix?
you can see this here: https://needlepoint.land/index.php/clearance-2/
i have added the following short code below the slide content image in the slider
[add_to_cart id=”some woocommerce numeric product code”]the id is test
the pwd is urmyrombiosSeptember 2, 2015 at 8:47 am #209505Hi,
I cannot login with those details provided.
Have you set your cart page within the WooCommerce settings? WooCommerce => Checkout => Checkout Pages?
Thanks,
David.September 2, 2015 at 8:59 pm #209923This reply has been marked as private.September 3, 2015 at 5:33 pm #210208Hi,
“the shopping cart turns into (checkmark + icon + View Cart) this d(checkmark + adding) does not go away”
– It goes way for me, it returns to Add to cart.“and is taken to Products page (this is INCORRECT)”
– For me I get ‘You cannot add that amount to the cart — we have 1 in stock and you already have 1 in your cart.’Can you test this with the default Twenty15 theme activate also or on your development site?
Thanks,
David.September 4, 2015 at 11:40 am #210404Hi David,
This client is unwilling to test on another theme at this time, as she has not paid Siteground for a dedicated test/staging area — ie, live and test are the same — and is concerned that switching to another theme might ruin her current interface in some way that would cost her to rebuild.
By the same token, she is reluctant to update to the latest Atelier 1.72 for fear that something will break — the client is about to start uploading many more products on her catalog (since she has increased confidence in Atelier), which would take her past the point of no return in terms of the GO/NO GO decision as to switching to another theme if necessary.
Thank you for looking into this, though.
I will view this on a mobile device, and see if the same results persists in that env. Hopefully, not.Cheers,
AliSeptember 4, 2015 at 11:46 am #210409Hi Ali,
As long as all changes are within a child theme nothing should break for a minor .01 update.
Also, uploading products (anything WooCommerce) is separate from the theme, meaning if the theme was to be removed or break uploaded products and data are not changed and will remain as they are part of the WooCommerce plugin.
Thanks,
David.September 4, 2015 at 11:55 am #210419Hi David,
Okay, looks like this is the right time to set up a child theme!
Cheers,
Ali
September 4, 2015 at 12:04 pm #210422Hi Ali,
We supply one with the main download zip on TF.
A good instructional read also: https://codex.wordpress.org/Child_Themes.
Thanks.
September 15, 2015 at 12:44 am #212982topic closed.
September 15, 2015 at 6:37 am #212994Hi,
Its ok. Thanks for confirmation.
Mohammad -
Posted in: Atelier
You must be logged in and have valid license to reply to this topic.