nemi5150

Thanks for your reply, I do appreciate it.

I tried it again today and the dismiss link now worked. Yesterday clicking the dismiss link or the “I have already reviewed” link just didn’t do anything. Like you said, it was probably a javascript error, but I did not crack open the console to see what it was.

The dismiss button (red X) would close the notification, but it come back upon refresh.

Here is the post that has the screenshot that looks exactly like mine

https://www.ads-software.com/support/topic/stripe-checkout-fields/

I want to reiterate that this ONLY happens on older ios devices, as far as I can tell. I had a customer with an iphone 6 send me a screenshot, I have a customer with an older ipad that says that they are having this issue, and I was able to duplicate on an iphone 5. My pixel 7 and a 2021 ipad pro work as expected, as does Chrome on Windows in both desktop mode and mobile mode using the Dev tools.

• This reply was modified 1 year, 6 months ago by nemi5150.

I cannot share a screenshot because I have no place to host it. However, it looks exactly like it does on a couple of other recent posts here on the support forum.

As for a possible clue, downgrading the stripe plugin to 7.2.0 seems to resolve the problem for me. Something you introduced in 7.3.0 is causing this for multiple users.

There are no fatal logs at woo->status->logs. Below is the system report you requested:

https://gist.github.com/Nemi5150/5998364e302c900abe45b932075ac4fc

• This reply was modified 1 year, 6 months ago by nemi5150.
• This reply was modified 1 year, 6 months ago by nemi5150.

Also for what it is worth, the wp_cache_get/set calls are not using a null/empty string/false key, as per the bug you found.

My understanding is that the wp_cache_get/set calls were supposed to be scoped to the current running php script only and that it is not saved across calls/users. But it seems like your plugin IS saving it across php calls/users. Am I interpreting this correctly?

For what it is worth, I commented out the wp_cache_get/set calls and the odd behavior goes away. Unfortunately, removing all of them from our code is a non-starter, plus I am sure woocommerce uses many of these calls throughout it’s code.

• This reply was modified 2 years, 3 months ago by nemi5150.

@killer777 I have no idea if this is fixed in today’s update, but like alfredo49 says, it is not listed in the changelog so I am not going to try it. If you try it, let us know by posting here.

For those where this is a critical problem you can downgrade to version 1.9.9 and it will start working again. Here is a link describing how to do that, or just google how to downgrade a wordpress plugin version.
https://increasily.com/how-to-downgrade-a-wordpress-plugin/

I posted about this a while ago and the developer is not responding. For those where this is a critical problem you can downgrade to version 1.9.9 and it will start working again. Here is a link describing how to do that, or just google how to downgrade a wordpress plugin version.
https://increasily.com/how-to-downgrade-a-wordpress-plugin/

For those that are frustrated with this, know that there is a way to help with this. Hit the escape key (ESC) instead of mouse clicking the Close button or the X in the corner when viewing an email. The page still moves but the last “view” button you clicked will still be in focus and highlighted, at least in Windows. It at least helps you find your place again when reviewing many emails.