Patrick Rauland

Just a note that there are other places in the code (like authentication endpoint) that have the same problem.

To close the loop on this.

This issue is related to a WooCommerce issue: https://github.com/woocommerce/woocommerce/issues/24244

Essentially, a bot can check infinite URLs with this structure: /shop/product-category/ANYTHING/product-slug/

WooCommerce returns a 200 response instead of a redirect so caching plugins cache far too many pages.

I’ll still hold that it isn’t a list. But let’s keep the HTML the same. ??

Can you add aria role to the UL element? Aria roles tell accessibility software how to treat an element.

If you can set the role of the UL to presentation that should fix this issue.

Docs: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/presentation_role

Wild!

I turned on WP Debug and didn’t see any errors.

But I did notice that the priority changed since the last time I logged in ??

Screencast: https://d.pr/v/AvbnQx

So maybe it does have something to do with caching? ??

I can setup a test site for a developer (with similar caching plugins installed) if you want. Contact me here if you want that: https://www.speakinginbytes.com/contact/

Hey Carl!

I’m having the same issue. I have a demo site with only WooCommerce, this plugin, and Storefront installed.

I update the priority and when the page refreshes the priority is still set to 0. ??

Here’s a 40-second screencast showing the issue and my status page: https://d.pr/v/3PD0Ne

Fantastic!

Thanks for digging into it! It was indeed a caching issue of some sort.

I couldn’t figure out how to clear the cache but now it’s at least cached correctly. ???♂?

Thanks!

I’m also having difficulty with the new GA4 property:

• It won’t show up in the list of properties after authentication
• I can’t manually add the measurement ID

Hoping the development team is working on this.

Thank you!

*Resolved*

I just realized I missed a key point in the email:

This change will be rolled out on June 3. If you have any questions, please reply to this email and I’d be happy to follow up.

Since this broke last week it doesn’t have anything to do with the above email.

I haven’t received any other emails from Stripe recently. ??

Yep,

I recently rolled my Stripe API Key. ??

I received an email from Stripe a couple days before I noticed my site broke.

Today, when your integration makes an API request to create a Charge, its identifier (ch_12345678) has a length of 17 characters. This is specific to your Stripe account as other accounts already use a length of 27 characters instead. The same applies to other objects in the API such as Subscriptions or Payouts.

[If] you’re using a third-party platform or plugin with a recent version it should already support longer ids as this has been enabled on newer accounts for multiple years. The most common ones would be Spreedly, WooCommerce, WHMCS or WP Gravity Forms for example. If you’re not sure, we recommend that you contact their support team directly to confirm that this change wouldn’t impact you as they built your integration and would be better equipped to confirm.

They didn’t mention keys in the email so I didn’t bother updating them. And I know Woo has always been good about updating Stripe and I had the latest version myself. ???♂?

I believe you could run a separate function right before you block the ads right?

Ex. add_filter( 'jetpack_just_in_time_msgs', 'log_jetpack_just_in_time_msgs', 19 );

Then fill out log_jetpack_just_in_time_msgs to update an option in the DB.

I didn’t have any issues with thumbnails disappearing but I did have an issue with the “display product sorting” option with Storefront.

I logged the issue and the developer is pretty great. I bet it will be resolved soon.

Hey guys,

I just stumbled across the same problem. I logged it (https://github.com/woocommerce/storefront-sticky-add-to-cart/issues/10) and sent in a patch. Hopefully the devs accept it and make it more usable on mobile. ??

We are working on version 1.0.5. It should take care of this issue and a few other payment related features.

We’re wrapping up some work on our Amazon extensions and then we’ll focus on finishing this up. I hope to have an update for you next week. ??