-
AuthorPosts
-
January 24, 2016 at 12:45 am #761165
Hi DonWattz,
Settings are okay, the code works now. What missing is the action that will trigger the ajax call. Have you done some customization before this?
Please provide your FTP login as well.
Thanks!
January 27, 2016 at 6:58 am #766733This reply has been marked as private.January 27, 2016 at 2:29 pm #767490Hi there,
Thanks, it happened on my other installation which is recently updated. What I did is switch stacks in customizer and save it. Then switch it back to preferred stack. That clears my cache and ajax confirmation/message works again.
Could you try that too and let us know?
It works on my fresh installation too, so it could be related to old installation that recently updated.
Thanks.
January 27, 2016 at 2:32 pm #767499Still no luck with the pop up with out refreshing the page. I did what you told me to do. :/
January 27, 2016 at 9:46 pm #768058Hello There,
Could you please try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.
Please let us know how it goes.
January 28, 2016 at 11:22 am #769101I deactivated all plugins except cornerstone and woo commerce and no luck. Didn’t you say i am missing a trigger?
January 28, 2016 at 8:29 pm #769773Hello There,
Sorry for the inconvenience. This issue was reported as a bug in the latest release X because there was a conflict with the X and the latest WooCommerce release. Our developers is already looking into this. Once they’ll have it fixed, it will be updated and will be rolled out in out next update release.
Please bear with us. Thank you for your understanding.
April 1, 2016 at 11:47 pm #863452I’m just subscribing to this thread and adding a ‘me too!’ to what @justmasc said. I’d rather build product pages and/or use the new grid plugins to create ‘stores’ and it would be *SO* excellent if that fancy add to cart overlay could display on those kind of pages too (or, really anywhere there is a Woo product embedded, not just on archive pages).
Is this something Themeco could do, or would this need to happen with the WooCommerce folks? (IMO, it seems quite odd that the above isn’t the default behaviour. Why would we want the add to cart behavior to vary between archive pages, shortcode embeds, or other plugins that display Woo products?
April 2, 2016 at 6:40 pm #864130Hi there,
This was a bug, should be fixed now in the latest version. This thread is old if you have an issue with add cart ajax, then please start a new thread while linking back here.
Thanks!
April 14, 2016 at 3:29 pm #883020Hi Rad,
I think we might be talking about two different things (I hope not, but I think so). I’m talking about the green/gray overlay that fades in/out in the center of the browser window when you add to cart on the ‘official’ WooCommerce shop page (and looks like the colours can be adjusted in the Customizer for X) or possibly other ‘archive’ pages that use that template. (The products do add to cart, I just don’t get that cool display effect that lets the user know it was added.)
I’m talking about if it’s possible to add that to any page that might display a one-off WooCommerce product (say, via shortcode), or a page of WooCommerce products built with The Grid or Essential Grid (I haven’t tried either of these yet, but assume they will behave like shortcode embedded product).
If the latter is possible, I’ll *absolutely* start another thread on it! 🙂 And, if not possible, PLEASE, PLEASE add it to the feature request list, as with all these powerful ways to build WooCommerce product displays (that don’t use the default Woo shop page template), it’s a shame WooCommerce makes it so hard to get all the same functionalities. (I just got through a bunch of code mods to change the default ‘shop’ URL… which IMO is a bit silly that’s not built in by default too!).
Thanks,
-SteveApril 15, 2016 at 2:11 am #883806Hi Steve,
Ah, thanks for the clarification. But not sure if possible, but the code is bind to specific element and page. The customization may require javascript editing which is part of the core and PHP coding to selectively add the required structure. We don’t recommend editing any part of the core files. Though, I agree that this feature very useful and been added as a feature request.
Thanks for understanding.
April 27, 2016 at 7:05 pm #903235Maybe Themeco (and as many of us as possible) could put in a feature request to the Woo (Automattic) folks? I can’t imagine that such a feature wouldn’t be widely used! So many people embed products in pages or built alternate ‘shop’ pages.
If you folks have a better description of this problem to help us explain it in a clear way to the Woo folks, that would be a really nice addition to this ticket!
(rant – Actually, as I’ve started building more ecommerce sites, there are a whole bunch of rather obvious things WooCommerce needs to add to the core code that nearly every ecommerce site seems to be doing via code modification, or if we get lucky, plugins. ex: why should we have to jump through so many hoops to redirect the default shop page? – end rant.) 🙂
April 28, 2016 at 7:26 am #903982Hi there,
I’m not sure if we can do that, Themeco as whole will only count as one entity if we do the feature request.
https://support.woothemes.com/hc/en-us/articles/202536848-How-to-Submit-a-Feature-Request-
But, maybe if multiple people will request the same feature, then there could be a chance. Tough, I’m not really sure.
More useful features the better. Or maybe Woo prefer to have a basic platform and just let users add their own extensions/add-ons. It will still fall under custom developers.
Thanks!
April 28, 2016 at 5:08 pm #904825Thanks Rad, well, hopefully some folks will run across this thread and try to request this to the Woo folks (as will I). It wouldn’t hurt for Themeco to do so, too, even if it only counts for one. 🙂
I certainly understand the WordPress (and now Woo) mentality of core, and then adding via plugins and custom development. But, I’m finding myself doing the same kinds of customization to every WooCommerce site, and when I go looking for such solutions, there are site after site and forum after forum of others struggling/implementing the same exact stuff as well. Some of it sure seems like it should fall into core.
(Like I said above, you shouldn’t have to hack code to change the store URL, or add ‘back to store buttons’ on cart/checkout pages, etc. I’ve done zero sites where I haven’t had to change that stuff yet. 🙂 Anyway, probably preaching to the choir, but the more people we can get to ask, maybe they’ll do something.)
April 28, 2016 at 6:11 pm #904897I have added a WooCommerce improvement submission around what we were discussing above. They seem to work on a ‘points’ basis (with voting) so if anyone reading this agrees, maybe it would be best to vote for this one submission collectively.
Thanks much! -Steve
-
AuthorPosts