docmartinhk

Thanks Shameen; and apologies to Pepe, I’ve edited above [so many fake accounts trying friend requests on Facebook, I wonder at times!]

Yes, seems like a bug; for the time being, I’ve added a note to my checkout page about postcode / zip not being optional. In many places, it’s just normal to add this code, so the bug might pass unnoticed.

I’ll add a bug report, tomorrow probably; late now in HK.

Thanks! Hope you too have a great day.

By Hey Presto, I meant just do this, and problem solved, just like that.

No, what’s needed is something in the postcode / zip code box.

I have a screenshot on my computer, can’t see how to upload it.

• This reply was modified 11 months, 3 weeks ago by docmartinhk.

I alerted the customer, and Hey Presto! – her order worked just fine when filled in the postcode/ zip code info.

Just commenting to say I too find it odd the dark captions are very hard to read against dark background, and would seem better if default captions are readily visible if not too “overwhelming” against photo.
– and don’t really want to style one by one.

While also: thanks for this block; I do appreciate the way it arranges photos!

Update: in case any use to anyone.

Just done a migration to https – as wanting to try and sell photos thro site.

I tried disabling Cloudflare thro W3 Total Cache settings; the one click upgrade via Site Health again didn’t work.

Instead, to Cloudflare: could stop caching here; I also disabled Cloudflare.

Then, the change to https via Site Health worked.
Had another issue, with login not enabling me to administer site.
Tried a few things; searched online, and found I had to add these lines of code to around top of wp-config:

/** SSL */  
define('FORCE_SSL_ADMIN', true);  
// in some setups HTTP_X_FORWARDED_PROTO might contain  
// a comma-separated list e.g. http,https  
// so check for https existence  
if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false)  
    $_SERVER['HTTPS']='on';

Thanks Adam; I figured many EWWW users will also have cloudflare, so wondered if it’s the way it’s enabled via W3 Total Cache: don’t know how this would differ though.

Yes, the free version; and since I have optimised the site images [Cloudflare off via W3TC, cache deleted, optimised, Cloudflare back on], I’m happy now. Checked that cached page accessed with Chrome is indeed serving WebP images.

– was mainly letting you know, and posting in case anyone else has same issue and finds the posts.

Thanks
I’ve seen that google now prefers sites with HTTPS, for instance. [Yes, likely v small benefit in SERPS, but seemed worth a go]

WordPress site health advises the change; seen articles re WordPress on it being better to use https even if not gathering data.
Indeed, from WordPress:

“It is recommended for all production WordPress sites to use HTTPS.”

So feeling almost a bit primitive in being with http!

I did try those encryption modes on Cloudflare; one stopped site working at all!

– And in development mode w Cloudflare, no difference; suggesting the one-click migration hadn’t worked properly with the site.

So I may try the migration with Cloudflare in development mode, using certificate on the website [from host]; and then indeed see which of the Cloudflare encryption modes works.

• This reply was modified 2 years, 9 months ago by docmartinhk.

Thanks!

I had seen articles like this; figured not plugin as WordPress core caused this; and htaccess not changed. clearing cache, changing browser not helping.

Just changed siteurl and home back to http from https, and now can access admin pages.

But this didn’t give insight into why this happened; I don’t know what WordPress should do when hit the “Update your site to use HTTPS” button – it’s surely more than simply changing home and siteurl… …

Just found I could get it working switching from https [via cloudflare] back to http

New to WordPress; noticed this issue, found it weird.

Just tried Gallery block among Coblocks, in case any different; but same problem.

Glad to have found this thread: Kenny’s workaround just worked for me too.