T4ng

I’m afraid that there is no way to stop showing Ai notification from elemetnor except to deactivate AI feature from?Elementor> Settings> Features

So should I consider it doesn’t work?

Any reason why there’s no Elementor AI sectin in the user settings?

Thank you.

Hi,

Thanks for your answer. Unfortunately, no, it doesn’t help much.

I already turned off the AI Feature. Nonetheless, there are still AI features everywhere.

View post on imgur.com

View post on imgur.com

View post on imgur.com

Finally, in my admin user settings page, I can’t find any Elementor AI section, while I’m an admin with all permissions granted:

View post on imgur.com

Finally, what’s the difference between diabling the feature, and unticking this checkbox from the user profile.

Thank you.

Hi?@vmarko,

Any updates on this issue ?

Thank you

Hi @vmarko,

Same here, I am afraid.

As a cross check, I’m using the inline Elementor CSS, and in my case, after clearing ALL W3TC caches, the Elementor inline CSS section of the broken pages is empty. Here it’s not even calling upon an external CSS file, the CSS should be delivered inside the page

I can see that:

• from a browser who’s cache has been emptied after the W3TC cache clearing
• after refreshing with Ctrl + Shift + R
• from with other cache-cleaned web browsers
• Same for my colleagues from other computers or phones, cache cleared as well

When flushing Elementor’s CSS cache

>> No, I barely do that. When I do, it’s an attempt to solve the broken CSS issue, but it never works in my case.

When the CSS print method is enabled no matter which one is selected: External file or Internal embedding

>> Yes

After that if the W3 Total Cache Page Cache is purged, the page appears broken

>> Some pages in my case, only pages built with Elementor.

This mostly happens when I restart the server. Caches were CLI-cleared, before and after.

Then I try to clear these pages individually. It generally works but sometimes, for some reasons it won’t.

(That one’s another issue, I guess, not the topic here, let’s forget this here).

Then that’s why I sometime end up flushing all the caches. But then I often run again in many more broken pages.

I confirm.

No page cache > no issue. The Elementor CSS is always delivered.

Page cache enabled > The Elementor CSS is often missing/not embeded when CSS is delivered as inline.

I compared the html of a specific page:

1. the broken one
2. the same page after successful cache clearing

The only, single difference in the CSS is the css section missing… or being there.

Almost the same when Elementor CSS is set to external file, besides it’s the file itself being findable or not.

This occurs whatever the W3TC minified setting.

Regenerating the Elementor CSS doesn’t solve thie issue.

Only getting the cached page cleared will.

This mostly happens after a new deployment (almost systematic in our case). Also sometimes in between, while this is much less frequent. I couldn’t find after which specific events.

We use the Redis page cache method.

• This reply was modified 6 months, 1 week ago by T4ng.

Hi,

I face the same issue.

In my case, this occurs with or without W3TC CSS minication, internal or external Elementor CSS embedding, and combination of those.

Any genuine interest in getting this issue solved, really?

Just so you know, I’ve very much improved the understanding of this issue, and described it thoroughly to Elementor.

https://github.com/elementor/elementor/issues/27320

It’s obviously not W3TC’s behavior that’s in cause, but most cache plugins seem to be impacted by this issue. Since you’ve got a much better understanding what’s going under the hood, thanks for taking a look at it, and ideally, team up with Elementor to find a solution.

Thank you

• This reply was modified 10 months, 2 weeks ago by T4ng.

Hi,

Did you get to discuss this internally?

We’ve just published our monthly update. As usual, after clearing cache, some of our main pages (always the same, mentionned above) were broken. Clearing all the cache resolve the issue, for these page (sometimes, or only partially with some elements still broken…), then that’s other pages that do not display properly.

It’s a nightmare to deal with this, for each deployment

• This reply was modified 11 months ago by T4ng.

Hi,

Thanks for your reply, and for trying to investigate this a bit further.

If I can add details, we face this error almost systematically right after proceeding to a deployment, even though it purges all W3TC caches from the CLI, and the opcache. In such cace, most, if not all the pages including a nested Elementor template miss the related CSS.

Last precision, we face this issue on 2 different environments, staging and live, which both exploit the same deployment process, for the same WordPress code. It’s very painful to solve, since at that time, purging the whole website manually won’t help, and we have to spot all the broken pages to purge them manually.

Later on though -out from a deployment- I can purge all the caches, and the issue won’t occur.

The error only seems to occurs right after the deployments.

Hi,

I’ve been working on these pages today. Surprizingly, today I was able to clear the page cache for there homepages, multiple times. It worked consistantly.

I was surprized, because I’m quite sure of the clearing I processed yesterday, right after adding the setting you asked for.

• I cleared all W3TC caches, from the W3TC admin > Top Right Save Settings button > bottom arrow > Clear caches button
• My browser cache (another browser, on which I’m not connect as admin, of course)
• and CloudFront as well…

But today, it just worked, like a charm.

I must admit though, that I had a doubt about the actual clearing from the first step I mention (Top Right Save settings > bottom arrow > Clear caches butoon, where I did get a proper page reload…

Anyway… I’ll stick with these settings and hope it keeps working in the long run. I’ll keep you posted if something comes up.

Thanks a lot for your help here.

OK, thanks. This seems different from what I’m fighting against.

The issue I’m facing has been described here.

• This reply was modified 11 months, 2 weeks ago by T4ng.

Hi,

No I didn’t, for 2 reasons:

• The tip of the option doesn’t seem to relate to the issue I’m facing :
  “Specify full home?URLs of your mirrors so that plugin will flush it’s cache when content is changed.”
  For example:
  https://my-site.com
  https://www.my-site.com
  https://my-site.com
• You said “If the same content is accessed from different domains”, and I’m not falling into that case – All my pages are accessed from the same domain.

But since you insist for me to test, I just added the WPML homepage alternatives (one per line, full URLs), like this:

https://mysite/fr/
https://mysite/de/
https://mysite/es/
[…]

I did not tick the “Cache alias hostnames:” tickbox.

Then I purged all caches, and tried reloading.

Unfortunately, it did not help: I still cannot purge these pages individually.