thedrumdoctor

Thank you very much for your reply. This has confirmed what I was thinking.

I will not be using iframes either!

Many thanks.??

Glad to be of service!

Just to clarify, I have never used the ‘minimise CSS’ option in Breeze and its setting (on or off) makes no difference to the issue. It just makes the site look ugly if it’s enabled!

I’m not sure why, but the behaviour has now stopped!!!! However, there has been a WordPress update and a theme update since I started to notice the behaviour so maybe we’ll never know.

Anyway, regard this issue as solved.

Thanks for the video, but it looks like I am using a different Composite Products to the one you are testing:

Woo Composite Products – https://woo.com/products/composite-products/

I think your demo is using WPC Composite Products for WooCommerce.

By the way, minimising CSS in Breeze ruins the layout on our site! Not only that, disabling Breeze seems to make the site more responsive! However, this could be due to my inexperience with configuring Breeze.

Here’s the settings backup JSON:

{“breeze_basic_settings”:{“breeze-active”:”1″,”breeze-cross-origin”:”1″,”breeze-disable-admin”:{“administrator”:1,”editor”:0,”author”:0,”contributor”:0,”subscriber”:0,”customer”:0,”shop_manager”:1},”breeze-gzip-compression”:”1″,”breeze-browser-cache”:”1″,”breeze-lazy-load”:”1″,”breeze-lazy-load-native”:”1″,”breeze-lazy-load-iframes”:”1″,”breeze-desktop-cache”:”1″,”breeze-mobile-cache”:”1″,”breeze-display-clean”:”1″,”breeze-ttl”:60},”breeze_advanced_settings”:{“breeze-exclude-urls”:[],”cached-query-strings”:[],”breeze-wp-emoji”:”0″,”breeze-store-googlefonts-locally”:”1″,”breeze-store-googleanalytics-locally”:”1″,”breeze-store-facebookpixel-locally”:”1″,”breeze-store-gravatars-locally”:”1″,”breeze-enable-api”:”1″,”breeze-secure-api”:”0″,”breeze-api-token”:”mPTbCpUR7Oit”},”breeze_heartbeat_settings”:{“breeze-control-heartbeat”:”1″,”breeze-heartbeat-front”:”disable”,”breeze-heartbeat-postedit”:”300″,”breeze-heartbeat-backend”:”disable”},”breeze_cdn_integration”:{“cdn-active”:”0″,”cdn-relative-path”:”1″,”cdn-url”:””,”cdn-content”:[“wp-includes”,”wp-content”],”cdn-exclude-content”:{“0″:”.xml”,”1″:”.csv”,”2″:”.tsv”,”3″:”.txt”,”4″:”.xls”,”10″:”.php”}},”breeze_varnish_cache”:{“auto-purge-varnish”:”1″,”breeze-varnish-server-ip”:”127.0.0.1″},”breeze_first_install”:”no”,”breeze_preload_settings”:{“breeze-preload-fonts”:[],”breeze-preload-links”:”1″,”breeze-prefetch-urls”:[]},”breeze_file_settings”:{“breeze-exclude-urls”:[],”cached-query-strings”:[],”breeze-wp-emoji”:”0″,”breeze-store-googlefonts-locally”:”1″,”breeze-store-googleanalytics-locally”:”1″,”breeze-store-facebookpixel-locally”:”1″,”breeze-store-gravatars-locally”:”1″,”breeze-enable-api”:”1″,”breeze-secure-api”:”0″,”breeze-api-token”:”mPTbCpUR7Oit”},”breeze_ecommerce_detect”:false,”breeze_advanced_settings_120″:”yes”}

Thanks again for creating it!

The only thing it doesn’t do (and I feel really bad for saying this) is putting the converted images in a div with the standard wp-block-image class. When I open a post and click on an image in the newly converted layout, it seems to trigger the addition of the missing div. Without doing this, the images convert wrapped in a pair of <figure/> tags.

Having said that, I could always use an adjacent sibling combinator to try and pass on the right styling to the <figure/> tags not wrapped in a wp-block-image parent div. Images normally come after paragraph tags to I can see p + figure {} being a target for styling.

(@bisratlearn) Many thanks for doing this so quickly.

Normal service has been resumed! >:-)

• This reply was modified 1 year, 1 month ago by thedrumdoctor.

@stestory Yes indeed, why do a job once when you can do it twice!!!!

I think Woocommerce devs need to do a bit of research into how products use attributes and populate them with terms. ‘One-size-fits-all’ does not apply in retail. To learn this is a supposed ‘improvement’ now manifesting itself as a bug surely must send a message to rethink?

Now I have to consider wasting more time prepping for a rollback.

@nigeljamesstevenson please make it go away! I have circa 200 attribute terms in one of my attributes named ‘Model’ – because there are so many model names of products across manufacturers.

Now imagine having to delete 199 attribute terms just to get to the term you want. This is not a time-saving feature! I can’t see why it was ever considered a useful change.

Edited my review!

Disabling the integration for YouTube worked! Thanks for that pointer.

Quick response!

I actually deleted the plugin but I’ll get it again and try disabling YouTube integration. We try to collect as little data as possible from our visitors and we don’t use their personal information for anything other than processing orders. We don’t use mailing lists either so we’re looking to make the site ‘tick the boxes’ for GDPR at minimum level. I’ll try again and report back. Thanks.

I’ve installed Jetpack in the past on various sites and it didn’t give me anything I really needed. Unfortunately, the Woocommerce app would have to be independent of Jetpack for me to consider using it.

I’m going to look at what @israelb1 suggested as Jetpack is not installed on our site and is not going to be installed again.