WebePc Gianluca Molina

Hi

Thanks for the update, I would like to point out that with the latest update there was a CSS problem, the title and background took on a different color
Look: giurisprudenzapenale.com

Ok but if I disable for that type of “post” Elementor and return the standard editor (Gutenberg) I would expect that if I go to edit the page with the standard editor then I would see the content changed not that it would “force” remain the Elementor content that should be disabled I am talking about websites where Elementor is used only for content so no header, footer, etc.

I explain in detail
During the development of a new site a client started writing articles, simple text.
Instead of using the WordPress editor he clicked, out of habit, on “edit with Elementor.”

Considering that the articles will only be featured image + simple text I disabled Elementor for that type of post (articles)

On the backend, opening the articles that had been made with Elementor now appeared properly editable with Gutenberg.
But in the frontend the content was not updated, it continued to retain the initial version created with Elementor.

I had to re-enable Elementor for that type of post, go into the articles and click on the appropriate “return to standard editor” button

But what could it be? I mean I’m sorry to leave Cloudflare disabled

I did further testing and also asked the hosting service.

I found that the problem seems to be “regional” i.e., I and the hosting service are in Italy.
A colleague who is in Spain ditto

I tried pausing Cloudflare and indeed the problem disappears!

This is the strangest thing!

I tried Firefox today by first deleting EVERYTHING (cache, images, history, etc).Initially aesthetically it seems to load correctly but without images….

After a while it’s like it discards, looks bad and doesn’t load images.

It is definitely something about caching because if I turn it off it works correctly.

Elementor’s element caching feature is disabled

Unbelievable!

Even from mobile I can’t see the correct background.I have tried different browsers and excluded the CSS from Litespeed Not only me but also other people do not display the page correctly

For the “woo porduct grid” it is the “Masonry” setting that causes the problem

Look ?? :
https://youtu.be/QlSLR5z1AZI

For woo porduct grid look:
https://gruppoimballaggifrancesca.it/pluriball/
It seems that the generated css does not have the correct height:

<ul class="products" data-layout-mode="masonry" style="position: relative; height: 223.646px;"> 

The same problem appears on one of my client’s sites with the “Woo Product Grid”

Hi
The problem continues although to a much lesser extent, as soon as all the cache has been deleted the results are excellent:
https://pagespeed.web.dev/analysis/https-www-disintop-it/aczxxvoqya?hl=it&form_factor=mobile

Now it no longer errors since after a while the results get worse:
https://pagespeed.web.dev/analysis/https-www-disintop-it/zlh52fk93v?hl=it&form_factor=mobile

On the recommendation of the plugin developer, I tried changing the plugin settings:
https://pagespeed.web.dev/analysis/https-www-disintop-it/3a32n5t3c3?hl=it&form_factor=mobile

So far so good I hope that in a few hours it will not fail again

Ok:

https://pagespeed.web.dev/analysis/https-www-disintop-it/a0skxkvapg?hl=it&form_factor=mobile

Performance drops but seems to remain stable.

So how can you isolate just the problematic CSS?

• This reply was modified 3 months, 2 weeks ago by WebePc Gianluca Molina.

That’s the problem! Great start now, after about 20 minutes, it went into lockout

15:48
https://pagespeed.web.dev/analysis/https-www-disintop-it/6d7o34sax7?hl=it&form_factor=mobile

15:55
https://pagespeed.web.dev/analysis/https-www-disintop-it/zezfaqyab3?hl=it&form_factor=mobile

16:04
https://pagespeed.web.dev/analysis/https-www-disintop-it/mhn8saild0?hl=it&form_factor=mobile

For a moment I’ll talk about the setting; “Server IP:” in quick.cloud settings

I had to update it manually, the old IP from the previous hosting remained