goti

Hello @arcangelini !

Thank you for your reply. I wrote to the plugin author, Amazon Web Services.

Their reply was that we should disable Ajax “Add to cart” feature following the below steps:
“Woocommerce -> Settings -> Display -> Shop & product pages -> Add to cart behavior -> (uncheck) Enable Ajax add to cart buttons.”

However I am feeling like I should not disable Ajax, because we use the get_refreshed_fragments function to update cart contents widget and I am not sure what else is affected.

>>> I would be grateful to have your views, are there some specific headers or HTTP methods that should by-pass CDN caching for TO CART button and ATTRIBUTE FILTERS to continue working?

Thank you!!!

Below is their full reply for your reference.

Firstly, I apologize for the inconvenience you have experienced because of this issue. As I understand, you are using “Woocommerce” plugin for WordPress and “Add to cart” and “Attribute filters” stopped working. Please correct me, If I’ve misunderstood your query.

=========================================

After researching about this plugin and the issue that you have encountered, I was able to see that there has been multiple posts/blogs about this issue – “Woocommerce – Add to Cart not working” and I would like to quote those posts here for us to rule out the probable cause which has contributed to this issue. They are:

(1). Cloudfront caching
(2). Disable the Ajax Add to Cart feature

One speaks from AWS perspective and another from the plugin perspective. I have tried my best to address both here. Please do not hesitate to bring to my knowledge if there were any gaps in my understanding of the query.

—————————

(1). Cloudfront caching:

After consulting our internal team, we could see that the ‘caching’ is enabled in all the distributions with the TTL values as follows:

– Minimum TTL 0s
– Maximum TTL 365d
– Default TTL 1d

With that said, origin provided cache-control header may override behavior at times. But, It really depends on the object in question and the response received from origin.

So, to proceed further with our investigation – I request you to provide us the response headers which might be the following format – “X-Amz-Cf-Id”.

For reference:
==============

-> What information should I give AWS Support for diagnosing CloudFront web distribution latency issues?
https://aws.amazon.com/premiumsupport/knowledge-center/cloudfront-latency-diagnosis-data/

-> AWS for WordPress plugin Site Acceleration with Cloudfront
https://www.ads-software.com/support/topic/aws-for-wordpress-plugin-site-acceleration-with-cloudfront/

As soon as I have this information, I’ll work with our service team to assist you further on this case.

—————————

(2). Disable the Ajax ‘Add to cart’ option:

As per my research, the add-to-cart feature uses a function called an Ajax call to process the cart without having to load the page again. This is the same thing for product filters.

Here’s the reasons having this option disabled.

-> Why disabling WooCommerce Ajax Cart Fragments?
https://www.businessbloomer.com/woocommerce-why-how-to-disable-ajax-cart-fragments/#1-why-disabling-woocommerce-ajax-cart-fragments-
(As per the above reference, the conclusion is:

– if your theme does NOT have a dynamic header Cart widget, you can disable “/?wc-ajax=get_refreshed_fragments”
– if your theme has a dynamic header Cart widget, but you don’t care about showing the Cart widget content on the go, you can disable “/?wc-ajax=get_refreshed_fragments” everywhere
– if you want to keep the Cart widget functionality active, you should disable “/?wc-ajax=get_refreshed_fragments” ONLY on those pages where there is no Ajax Add to Cart functionality (WooCommerce Product Archives) or Cart update functionality (Cart page).)

-> WooCommerce Ajax add to cart not working
https://www.ads-software.com/support/topic/woocommerce-ajax-add-to-cart-not-working/
( where the theme author of “OceanWP” recommended to disable the add to cart ajax feature.)

If you wish to disable Ajax “Add to cart” feature then you could follow the below steps:
“Woocommerce -> Settings -> Display -> Shop & product pages -> Add to cart behavior -> (uncheck) Enable Ajax add to cart buttons.”

You could try this suggestion and let me know if it changes anything for you.

With that said, I would like to emphasize that WordPress/Woocommerce is a third party application, and it falls outside the AWS scope of support [1] as does performing system administration tasks. We don’t have much expertise about the internal configuration of you instance [2][3]/wordpress configuration. So, if you wish to get assistance related to “Woocommerce” plugin then you can contact WordPress support directly as they have better understanding about the plugin features (https://www.ads-software.com/support/ ). I hope you understand our limitations here.

=========================================

Nevertheless, I will do my best to ensure that we have a clarity from AWS(Cloudfront) and if it’s in place then you can consult wordpress support for further assistance.

I trust that this information will help you.

Awaiting your kind response – headers.

As always, I’m here for you. Please feel free to let me know If you have any concerns or questions so that I can address them at the earliest.

Thank you @nko!

That would be amazing if it is possible

I think I’ve discovered a work-around for Vimeo background for mobile devices.

I have set:
– Enable on Mobile Devices = Ticked
– Parallax Type = Scroll
– Parallax Speed = 1 (because my background was not meant to have parallax)
– Parallax Enable on Mobile Devices = Ticked

Notice, if I set Parallax to None, the video stops playing on mobile devices altogether. @nko may have further insights.

@nko hello,

This has been a good plugin.

However, now I still find no videos play from Vimeo on mobile devices. I disabled all plugins except AWB (v1.4.10) and Visual Composer. Still not playing on mobile devices. I have enabled the “Enable on Mobile Devices” tickbox.

I made a trial with Vimeo’s iframe code and that works fine, so suspect some fault with the plugin…

@royho Hello!

I’m so happy you implemented 3D secure in v4.0.

I just found this thread very useful and will add filter as above.

I’d like to suggest we’d bring these 3D secure levels recommended, optional, off to the settings interface.

Thank you

I think I found the cause. If the plugin Enhanced E-commerce for Woocommerce store (by Tatvic) is enabled, it required the new Accept Privacy Policy of Plugin option to be checked on the plugin’s Settings page.

Else it WILL disable the payment fields on the payments page!!

None of this was not caused your plugin. Have a nice day

Thank you @kibus90. You saved me lots of time researching!

Not nice this bug..

We would also desperately need 3D secure that is also planned in 4.0. Would be great if community (us) could help in making this available sooner.

Hi @fernashes
Yes I’ve seen that dev version on github too.

Do you still need help with testing, or is it just being held up as you fix known issues?

3D is vital for our store, otherwise can’t use stripe. Too risky otherwise.

Hannah hi

Do you have any updates on 3D secure suppport? Very essential in the international marketplace.

Thank you

@fernashes

Hi Praveen, @spraveenitpro

May I ask do you have any plans for releasing 3D Secure support for this Stripe Woocommerce app?

It’s been 2 months 3 weeks since your last post so I thought I’d ask if you’re still planning on this.

Have a nice day

@hchouhan hello

Thank you for coming back. Indeed it seems it is the theme that is causing the issues with iPhone.

Hi @scottsweb

I would be grateful of your views on the following:

1) CHINA. Speedtest from China shows that our page load time is increased from ~10s to about ~50s as browser is unsuccessfully trying to fetch images from Instagram’s servers. Can you think of a simple way to turn off widget/fetch when user is in China?

Guess there is no way of us hosting the img files on our server either?

2) Mobile images. I have set image-size to Small in Widget. I am getting 300x300px images. Is there any way of using getting even smaller, so when viewed from iphone I wouldn’t have to scale them down that much? For example, Currently they’re rendered 106.666 wide 3-abreast on iphone.

Many thanks in anticipation

I went with the 2nd option offered here and it worked.

Perfect! Thank you @antoscarface

I went with the 2nd option above and this works!!