LovingBro (woo-hc)

Hi @mmk175,

Thank you for sharing the screenshot, this helps clarify what you are seeing on the Updates page.

Based on the screenshot, this does appear more likely to be related to stale cached update metadata, transients, or possibly an incomplete update state from a previous WordPress update/recovery process. The fact that WordPress reports version 7.0 correctly, while still offering a reinstall of 6.3.8-en_US, is definitely unusual.

For now, could you please try the following steps carefully:

1. On the Updates page, click the “Check again” link beside the Current version: 7.0 section.
2. Then try clicking the “Update Translations” button to see if the persistent translation notice clears successfully.
3. After that, go to: WooCommerce → Status → Tools

Please run:
– Clear expired transients
– Clear template cache

4. Clear all caches completely, including:
   – Browser cache
   – SiteGround/server cache
   – Any caching plugin cache/CDN cache if enabled

Once those steps are completed, revisit Dashboard → Updates and check whether:
– The “Re-install version 6.3.8-en_US” button disappears
– The “Update Translations” notice clears

If the notices are still showing afterward, please let us know and we can continue investigating further.

Hi @christie212,

Thanks for reaching out about this. It can definitely be confusing when the checkout asks for a reCAPTCHA verification but the actual reCAPTCHA field is not visible on the site.

Since you are using a third party reCAPTCHA plugin, this is usually caused by either an incorrect reCAPTCHA configuration, a JavaScript conflict, caching, or the plugin not properly loading the reCAPTCHA script on the checkout page.

To help narrow this down, could you please try the following:

1. Double check that your Google reCAPTCHA site key and secret key are correctly added in the plugin settings.
2. Clear all caches on the site, including any caching plugin, server cache, or CDN cache if you are using one.
3. Temporarily switch to a default theme like Twenty Twenty Six and deactivate all plugins except WooCommerce and the reCAPTCHA plugin, then test again to see if the checkbox appears.
4. Open your browser console while on the checkout page and check for any JavaScript errors. If you see any errors, please share a screenshot using https://snipboard.io
5. Please also share your WooCommerce System Status Report so we can better understand your site setup. You can get it via WooCommerce > Status > Get system report > Copy for support, then paste it to https://pastebin.com or https://quickforget.com and share the link here.

Looking forward to your update.

Hi @fullcolor,

It sounds like you already have a clear idea of the layout you want, and yes, this is definitely possible with Storefront and WooCommerce.

For the structure itself, the easiest approach would likely be using the built in WordPress Columns block, where each “block” contains: Name, Photo, & Text
You can then place 3 of these in a row and continue adding more rows underneath.

For the two features you mentioned:

1. Automatic chronological order
   The default Columns block does not automatically reorder items by newest first. For that functionality, a gallery or grid plugin would work better. A plugin like WP Grid Builder or Content Views could help display entries automatically with the newest items first.
2. Keeping everything aligned evenly
   This is usually solved by using equal height columns/cards. Many grid plugins already handle this nicely, especially when product names or text lengths differ.

Another good option could be creating these as regular WordPress posts or portfolio items instead of manually building each block. Then the gallery/grid plugin can automatically organize them in a clean 3 column layout with sorting and alignment.

You can also explore the default WordPress Gallery block documentation here:
WordPress Gallery Block Guide

I hope this points you in the right direction.

Hi @danidub,

Thanks for providing such a detailed breakdown of what you’ve tested so far, that really helps narrow this down.

From what you’ve shared, the behavior does appear to come from Stripe’s platform level configuration for Link rather than WooCommerce itself. The log message: “display_preference is not overridable” typically means that the Link payment method has been enabled directly within the Stripe account or through a Payment Method Configuration that WooCommerce cannot override locally.

Since WooCommerce Stripe syncs supported payment methods from Stripe, the plugin may continue re-enabling Link after saving if Stripe reports it as enforced or non overridable.

To help confirm this further, can you please share the following:

1. A copy of your WooCommerce System Status Report You can get it via: WooCommerce → Status → Get system report → Copy for support. Please share it through: https://pastebin.com or https://quickforget.com
2. A screenshot of what you currently see under: Stripe Dashboard → Settings → Payment methods → Link. You can upload screenshots via: https://snipboard.io

3. Your WooCommerce Stripe logs, especially entries around the “display_preference is not overridable” message. You can find them under: WooCommerce → Status → Logs. Please share the logs using Pastebin or QuickForget as well.

Once we have those details, we’ll be in a much better position to determine whether this is coming from Stripe account level restrictions, a connected platform configuration, or something specific to the migrated environment.

Hi @shirleyrma,

Thanks for reaching out. To make sure we are guiding you in the right direction, could you clarify a bit more about what you mean by “delete WooCommerce on Stripe”?

Are you trying to:

1. Disconnect the WooCommerce Stripe plugin from your Stripe account,
2. Remove WooCommerce as a platform connection inside Stripe,
3. Or simply enable Klarna as an additional payment method in Stripe?

Also, can you let us know if you are currently using the official WooCommerce Stripe Gateway plugin on your site?

If possible, please share a screenshot of what you are seeing in your Stripe payment methods page, especially where Klarna is unavailable. You can upload the screenshot via https://snipboard.io and share the link here.

That will help us better understand what is blocking the Klarna activation.

Hi @davidecho,

Thank you for sharing the System Status Report. :contentReference[oaicite:0]{index=0}

From what you described, this still points more toward the Apple Pay shipping address validation itself rather than the WooCommerce checkout address.

With Apple Pay, the shipping address a customer enters on the WooCommerce checkout page is not carried over into the Apple Pay popup. Apple Pay instead uses the shipping address already saved inside the Apple Pay account/wallet on the iOS device.

If Apple Pay is showing “Update Shipping Address”, it usually means the shipping address saved in Apple Pay is either incomplete, invalid, or Apple Pay is unable to validate it correctly against the available shipping methods returned by the store.

Since we cannot fully test the Apple Pay checkout flow while Apple Pay is disabled on the site, could you please temporarily enable Apple Pay again so we can test the checkout flow from our side? Alternatively, you can also reproduce and test this safely on a staging site first.

Looking through the SSR, I also noticed a few things worth updating first before further testing:

1. Your WordPress version is still on 6.9.4, while WordPress 7.0 is available.
2. Your WooCommerce Stripe Gateway plugin is currently on 10.6.1, while version 10.7.0 is available.
3. Your theme contains multiple outdated WooCommerce template overrides, especially several checkout related templates. These outdated overrides can sometimes interfere with newer checkout or payment gateway functionality, including Apple Pay behavior.

Please first:

• Update WordPress to 7.0
• Update WooCommerce Stripe Gateway to 10.7.0
• Clear all caches after updating
• Retest Apple Pay again afterward

If the issue still continues after the updates, please let us know and keep Apple Pay enabled so we can test further from our side.

Hi @gwenwruck,

Thank you for your patience and for working through the troubleshooting with us.

No issues at all. Please feel free to check back once the upcoming plugin update containing the fix from PR #1175 is released, and let us know if you notice any remaining issues or changes in the Event Quality reporting after updating.

We’ll be happy to take another look if needed.