T4ng
Forum Replies Created
-
Forum: Plugins
In reply to: [Post Types Order] Reset button@tdgu, changing the color is great. But I still feel it is very misplaced where it is now 🙂
Thanks!
Forum: Plugins
In reply to: [W3 Total Cache] Missing Elementor CSS pages when using page cacheHi there,
Interesting. Not sure it align with my case though.
In the meantime, we found that W3 Total Cache database cachen, and Asset Cleanup (even with CSS/JS caching disabled), were somewhat messing up with Elementor’s CSS.
By the way, I also read that with recent PHP versions, the usefulness of database caching is no longer so obvious.
Long story short: it’s bit empiric but disabling both of them solved the issue. We don’t notice any Elementor CSS missing since both of these changes were applied.
Forum: Plugins
In reply to: [W3 Total Cache] Missing Elementor CSS pages when using page cacheHi @jamieburchell,
Yes the patch is applied, for sure.
Couple of days after, here is what I can notice :
- The bug actually also happens on the test website. Less, but still happens. I suspect this is because this environment is faster/has more resources for each request. Which is possible since this website get no real trafic, besides cache priming and… me.
- I tweaked the setup a bit:
– I can’t purge a page individually when Always cache Pro extension is enable: I’ll get a “Failed to handl page url” message.
– Clearing redis from the cli solves it… only for the pages that have already been callded, the other one, not yet cached, will render broken.
> So got rid of this extension. - I enabled the Late Initialization setting. Can’t harm much, IMO, considering the bug we face.
- From my testings now, with this setup, iwhat seems consistant is that, as long as I call pages individually, wait for these to render, I’ll be fine. As soon as I call too much pages too quickly, I’ll start getting Elementor pages missing their CSS.
May I know which Elementor CSS rendering method you use? I also believe you’re on W3TC 3.8.12?
Thanks
Forum: Plugins
In reply to: [W3 Total Cache] Missing Elementor CSS pages when using page cacheHi @jamieburchell,
We gave it a try yesterday, and it seems to work. I noticed zero Elementor broken pages while all of them were without this patch 🙂
This was tested with W3TC 2.8.10
Therefore, we pushed this live, and… get broken pages again :((
Forum: Plugins
In reply to: [W3 Total Cache] Missing Elementor CSS pages when using page cacheHi @jamieburchell,
Ready to test your fix!
So to my understanding, it basically consists in patching Elementor with the aforementioned modification, isn’t it? No modification required on W3TC?
Thanks!
Forum: Plugins
In reply to: [W3 Total Cache] Missing Elementor CSS pages when using page cacheHi @jamieburchell,
Great you came up with a working patch 🙂
Unfortunately, I won’t be able to test it by the end of the month.
I’ll keep you posted
Forum: Plugins
In reply to: [W3 Total Cache] Missing Elementor CSS pages when using page cacheI’m not even going to bother trying to open this as an issue with Elementor since it’ll get immediately closed or ignored.
Thanks for taking time digging this issue. Let’s hope Elementor takes a look at it as well.
Forum: Plugins
In reply to: [W3 Total Cache] Missing Elementor CSS pages when using page cacheIt was introduced in W3TC 2.8.11
Enhancement: Flush Elementor cache when all caches are flushed
Thanks!
Off topic but I think producing websites in MS Word would be better than using Elementor 😀
Yeah… Projects evolve, plugins as well. Elementor was promising at first but seem to have lost themselves in adding useless functionnalities, rather than fixing what’s essential. At least for what I need now.
V4 seem to address some of these issues, but it’s just way too late.
Now we just value structure and reliability over shine.Forum: Plugins
In reply to: [W3 Total Cache] Missing Elementor CSS pages when using page cache@jamieburchell you say W3TC now calls Elementor’s regenerate CSS function when purging all caches. That’s pretty bad.
Do you know since which version?By the way, we’re also moving away from Elementor, but I need a solution to keep the website fine untill we switch for real. We’re moving to Gutenberg/custom blocks. Bricks seems great, but we didn’t want to rely on an external page builder. We’ll see how it goes.
Forum: Plugins
In reply to: [W3 Total Cache] wp_options w3tc_pagespeed_data_ still autoloadedAs explained, I didn’t want to keep that PageSpeed functionnality on, so disabled it. So there shouldn’t be any further request to PageSpeed.
Therefore, the question was not “Why PageSpeed requests won’t go through?”, but rather “Why do I stil get a W3TC>PageSpeed error, thus PageSpeed requests at all?”
Anyway, I just re-enabled / disabled the PageSpeed authorization. Which was followed with that message:
… and I don’t see any error message anymore.
I don’t know what happened during my last request, but this seems solved now.
Forum: Plugins
In reply to: [W3 Total Cache] wp_options w3tc_pagespeed_data_ still autoloadedMmh, surprizing, I can see it from the editor and the page while not connected.
Anyway… Here is the link to the screenshot: https://imgur.com/ts15ItT
Forum: Plugins
In reply to: [W3 Total Cache] wp_options w3tc_pagespeed_data_ still autoloadedOK.
Now, I don’t want to keep that PageSpeed function on, so removed the access. So now, I get 401 errors from the general thumb.
Forum: Plugins
In reply to: [W3 Total Cache] wp_options w3tc_pagespeed_data_ still autoloadedHi,
As suggested, I removed theses wp_options w3tc_pagespeed_data entries from the wp_options table.
Then enabled PageSpeed again, succesfully achieved a PageSpeed Test, with results.
After which, I can’t find any wp_options w3tc_pagespeed_data (LIKE %…%) entries in the table anymore.
Is it the expected behavior? My understanding is that these should still be there, just not autoloaded.
Thanks
Sure, thanks!
Hi,
I received another order in the meantime, which went fine.
Today, there’s no webhook error message anymore:
Still, I reconfigured the webhook.
It’s still not clear what happened, but I hope this problem is behind me now.