ronr1999

Looks like I’ve solved this issue and there appears to be a bug. We’re using WP-Optimize caching and turning on CSS Minification breaks Depicter’s font-family setting.

I’m running version 2.9.15 and am getting the translate bar on multiple sites… and yes, cache is cleared. Anything but English the bar appears. Looks like it’s a simple css:
.skiptranslate { display:none; }

Please confirm.

Seriously! Spam much! Not even close to answering the question.

Do you have a source for that statement? I have to disagree. Sections and Containers can easily work together as they are separate code structures. Elementor gives us the option of converting one section at a time. You do not need to convert a whole site. Keep in mind that once your convert and remove a Section, you cannot revert back from Container to Section.

And, the only plugin that’s causing any issues is this one…

Ok, I understand. Then I would highly recommend providing an announcement in the Dashboard that by simply turning on Flex Containers that Breaking Bad will be turned off and existing Sections will be compromised. I thought that we could simply convert a single page or a few pages to containers and the other pages with sections would be fine. Nope!

You wrote: “If you still want to work with Sections and Columns (and Breaking Bad) simply disable the Flex Containers feature.”

The problem here is that we are using both, Sections and Containers. On existing sites, it makes no sense to convert every Section to a Container. When you turn off Breaking Bad when Containers are turn on it totally destroys all the sections. Can you please rethink this and turn it back on for Sections?

• This reply was modified 1 year, 10 months ago by ronr1999.

I so agree. This has been a disaster. I used Breaking Bad extensively and now that’s no longer available after Elementor 3.5.9. This breaks everything on every site I manage.

Maybe there’s a way to turn it back on for sections and have it ignore containers?

• This reply was modified 1 year, 10 months ago by ronr1999.

NO… I would have known if I created it as a custom field. It certainly appears that it’s coming from your plugin. It’s right right there at the top of the custom fields with <p> tags like the others. Also, I deactivated the plugin it goes away. Somehow it’s coming from your plugin.

Interesting… I’ll try that. Thanks for the tip!

I’m have the same (or is it similar?) problem. I have a CSV file encoded with UTF-8 (from excel) and have a meta: meta:brand with a field: S&B. Upon importing it’s converted to: S &amp ; B. This happens with all Product custom meta fields.

Might there be a Woocommerce filter to fix this. I’ve looked…

• This reply was modified 1 year, 12 months ago by ronr1999.
• This reply was modified 1 year, 12 months ago by ronr1999.

Thank you. We appreciated the quick response and actions!

We turn off srcset. OUR TEST PAGE

We do not want the browser to use images that could be twice or three times in file size. And with your plugin providing optimal compression and sharpness… we’re happy. I hate to ask to change your plugin’s code for 768. We did find a way to disable it with:

// REMOVE MEDIUM_LARGE FILE SIZE
add_filter( 'intermediate_image_sizes', function( $sizes ) {
    return array_filter( $sizes, function( $val ) {
        return 'medium_large' !== $val; // Filter out 'medium_large'
    });
});

Thanks for the quick reply. This really relates to our extensive use of Elementor and its new Container layout. And, the information found in this YouTube and this Grid Layout.

I want to size my images to fit that flex 1120px grid with 20px gutter. Those images sizes then become: 265px, 360px, 550px, 1120px. Having 768px does not fit that layout and just adds another file to the server. ( still haven’t found a way to remove the medium_large size ).

I’m thrilled to have found your plugin. Except for the 768 issue, it’s perfect!

Obviously that should read:

Suggestion – Snippets in the Cloud

Thanks, that was the problem.