thedrumdoctor

Thanks for the response and as I feared, the answer lies in yet another plug-in to add to a WordPress installation. Oh well….

Thanks for the reply, I thought it might be a long shot!

It’s not mission-critical for us but would be ‘nice to have’ for when the boss forgets to add shipping to a listing he’s made in a hurry!

Maybe I’ll try and find the last known working 1.12 version and install that whilst waiting for a fix.

Thanks for that info, can I change the image settings in a child theme functions.php and over-ride the parent theme?

Object Cache Pro which not connected was the problem. Once this had been disabled the plugin connected.

Thanks for that information!

The Woocommerce Blocks idea seems like the way forward in this case – though I’d never heard of the plugin before you mentioned it.

I didn’t know there was Storefront ideas page either. I’ll check that out now and see what other people are asking. In the meantime, I shall proceed on the dev site with the blocks plugin as it looks like it’ll do the job.

Also, I meant to type ‘Widget’ in the topic title instead of ‘Plugin’!

Thanks for getting back to me.

I’m actually not using a plugin to display products on the home page (and yes, I have set the site’s homepage to ‘Home’). I’m using the theme’s option to place widget area below the header to which, I’ve added 2 Woocommerce widgets. The first holds the latest posts and the second holds a display of the newest products.

The widget container for the latest posts renders in HTML as:
<div id=”block-3″ class=”widget widget_block widget_recent_entries”>

The widget container for the newest products renders in HTML as:
<div id=”block-6″ class=”widget widget_block”><div data-block-name=”woocommerce/product-new” data-columns=”4″ class=”wc-block-grid wp-block-product-new wc-block-product-new has-4-columns has-multiple-rows”>

Now this renders as I want it on the home page which has a body CSS class of “home page-template”.

When I click on a single product on the home page the body CSS class changes to “product-template-default”, but the widgets below the header still render on this page.

I only want these widgets to display on the home page – not any other product pages. Obviously, I can add a ‘display: none’ rule on the widgets for every class of page I don’t want them to appear, but surely there is something I can do in my child theme to do this?

When a site visitor clicks on one of the newest products on the home page, a good theme design should allow the visitor to immediately click through to the product page without any other clutter on the product page. If the widgets below the header are always set to render on every page without any way of setting them to specific pages, then the UI becomes very user-unfriendly, especially on mobile screens where screen-space is premium.

Using CSS to hide widgets is not ideal in 2021! The theme should give more control over the pages they render on.

I’d consider this plug-in as ‘dead’ now. It stops sites working and hasn’t been updated for lots of new releases of WordPress. Deactivate!

Thanks to Manuel for looking into this issue, especially as I’m a user of the free version of the plug-in. At the moment, we don’t need the extra functionality of the plug-in but if I ever do need to do more with social media feeds, I would happily invest in their product.

The issue appeared to be a CDN problem with Jetpack which was resolved by making sure images on the site were served locally. CDN is all very well and good for enhancing site response, but it can fall over with image caching!

Many thanks for your support on the free version, I have sent the request on your contact form.

Yes, confirmed working in Firefox, many thanks.

Yes, issue still not resolved as in the other thread in this support forum. I am using Firefox, plugin version is 1.0.54.2 and the functionality is affected.

Still not working on version 1.0.54.2 in Firefox. Same issues as @jarwu and @virosept.

Yes, same here. I haven’t tried the back-end in Chrome or Edge though as I use Firefox.

*UPDATE*

It works for me in Google Chrome so there must be something which has changed the way Firefox renders it.

• This reply was modified 3 years, 11 months ago by thedrumdoctor. Reason: An update