Frank.Prendergast

Thank you, I have no idea how it happened but my wp-config did indeed include:

define( ‘SUBDOMAIN_INSTALL’, false );

It’s possible it was accidentally changed recently when some domain mapping troubleshooting was being done. I hope that’s what happened because otherwise it’s a mystery as to how the sites were being set up as subdomains until now.

Many thanks,
Frank

Thanks James, I took a look at the Cookie Consent banner in Jetpack but I couldn’t see a way to add other code to set cookies if the user accepted them.

For example, how would I manage Google Analytics code or Facebook Pixel code in such a way that they were only set if the user accepted cookies?

This is why I ended up using Cookie Notice, because it has an easy way to add all the codes provided by third parties in such a way that they are only added when user hits the accept button.

Hey Volkmar – so I think it might not be Jetpack after all, the timing must have been co-incidental.

What I *have* discovered though is that my sites use SSL. If I inspect the element and open the image in a new window and change the image url to https to http I see the cropped image.

I have also discovered that if I simply wait the cropped images eventually turn up on the front end.

I don’t know why this would be happening, but I thought I would share it with you in case it was useful information for you.

Sorry – it’s this plugin: Cookie Notice.

This was happening on two sites for me yesterday and I just tested with a third on a test site to be sure – it works consistently like a toggle. Activate (not even set up) Jetpack and the code above changes. De-activate and the code returns to what I pasted in.

Marking as resolved.

I do apologise – this may not be Jetpack related after all. I tested two sites yesterday and both had issues with thumbnails that seemed to resolve when disabling Jetpack.

I knew Speed Up Image Load Times *wasn’t* turned on so I did some more digging and the issue seems to be related to SSL cert and the timing must have been coincidental.

I may have tracked this down to a Jetpack conflict? Jetpack was installed and activated but NOT set up. Disabling the plugin seems to have solved the issue.

This is actually the second plugin I have found Jetpack to interfere with even when not set to use ANY modules.

Jetpack wasn’t set up at all on the subsite. It was just present.

The same as if you installed the plugin but never logged into WordPress.com or set up ANY of the modules.

That’s why I’m a bit confused.

I’m testing it on another subsite now and I am finding the same thing. Thumbnail crops won’t show unless I disable Jetpack which is present but NOT set up to use ANY modules.

Very odd.

Jetpack was network enabled but not set up for the subsite in question. Is it normal for jetpack to interfere with the plugin even though there were no image management modules in operation?

Thank for your swift reply – I can confirm it is now working fine with Multisite. It turned out that Jetpack was the issue.

I have just realised this is a Jetpack issue, Jetpack is network enabled – because I had NOT configured Jetpack or turned on any modules for this site I didn’t think it would be causing an issue. But it seems as though it is.

I’m also having this issue – did you by any chance figure out what was causing it?

Apologies for the delay responding, thank you so much – I should be able to sort out the theme’s title output with this info.

I don’t know why I’m not getting notifications – I’m glad this was helpful. Thanks for the tip re the additions tab.

I love your plugin by the way.

Apologies – I didn’t get the email notification about your reply. Divi is up to date, and I have tried the Title Fix. I tried the plugin first and just now tried via the Extensions Manager. No joy.

But I think I just figured it out – under homepage settings previously I had Custom Home Page Title set but I didn’t see the need for Custom Home Page Title Tagline. Once I split the title into two parts and put the first part in the title and the second part in the tagline it worked.

It was not intuitive to me that I *had* to have both parts filled in for the title tag to be set.

Is this expected behaviour?

Thanks for your help.