And the CSS… Well… At least was easy to de-uglyfy. =)

TL;DR: Preloading takes forever, does not get finished all the time, must be run on every little change for the entire cache and makes the caching solution almost not usable. Is this only me or normal behavior?

First, I tried many caching plugins and experimented with all kinds of server and application level caching.

I am impressed in what Swift Performance offers – even in the Lite version.

However, I also see myself putting in many hours, where I need just a couple of seconds with other plugins (i.e. click 6 or 7 check boxes and hit save).

From my experience so far there is not one plugin that works best with every site + hosting. Hence, I try to get myself familiar with a couple of caching plugins.

My biggest concern with Swift is that preloading takes so long. You make a tiny change, and the entire cache must be preloaded, which can take 30 minutes or longer (not talking about large websites with hundreds of posts but rather small websites).

It’s also not guaranteed that preloading will start or complete.

Maybe that works for a site that does not get touched any more later on. But sites that are a live and get regular changes can’t afford that.

I tried this on several websites and two different hosting (one traditional and good shared hosting, one cloud hosting equivalent to a VPS).

No difference.

Am I doing something wrong, or is this the intended behavior?

Thanks a lot
Markus

From the timing – oh, look, a national holiday! – to the clumsiness, to the breaking of sites, to the absolute terrible UI…. what a mess.

This could be the straw that breaks the camel’s back for anyone concerned enough about WP’s direction to consider other platforms.

I’m also a dev. I’ve been one for 12 years. I’ve invested countless hours learning and re-learning HTML, PHP, SQL, CSS, JS and Apache settings. And after a lot of pressure to mass produce sites with preset functionality really quickly with people who don’t know or hate to use code, WordPress itself. And writing plugins for it. And making themes for it. And evading its quirks.

I gave Gutenberg a try for an hour on a fresh single-site install about 2 weeks ago. Let’s tally the results:

– Can’t switch back to regular editor, no matter how many times I press that button.
– Image block alignment to center just didn’t work. Where’s the code editor?
– Where did all the settings go? Like custom meta fields, post type, template selector etc.
– Didn’t dare to see what’s inside, and what it puts out and into the db yet. Or how it behaves on a multisite. Or test it with all the other plugins. I dread the day I would have to crawl around the database on some serialized data hunt.
– In the end, with it wanting to be mandatory, I saw it more as a burden, than as a relief.

Unfortunately, there exists an inverse relationship between “fancy, quick, one-click drag-and-drop solutions” and stability, reliability, and maintainability. (Praise be the exceptions.) I see a serious problem with making a decision to ship it in version 5.0, while at 4.9.8 it still has bugs no editor should have, not to mention a reliable one. Therefore I beg you, delay it at least until all wrinkles have been smoothed out, make it a plugin until then, and give it more time in live environments.

You know, I’m the one my collegues and clients turn to when stuff breaks or doesn’t work, or should be customized, unless it’s the server itself. I can’t count the times a theme (or library or framework etc) has promised to be responsive, or easy-to-use, when it wasn’t. Or the times it just broke a site. Or left trash around. Or had a disagreement with other installed stuff. I’m quite fed up with over-hyped, flashy stuff that just fails to do what it’s for.

IT IS HIGHLY PROBABLE, that with this update a huge majority of existing sites will crash and burn. Will have to REBUILD them from SCRATCH. That is what the future holds for us who do this kind of work if this is incorporated into the core, and it’s not a bright one.

TL;DR:
– At 4.9.8 it still has bugs no editor should have, not to mention a reliable one. Therefore I beg you, delay it at least until all wrinkles have been smoothed out, make it a plugin until then, and give it more time in live environments. WE WORK WITH THIS TOOL!
– Whoever wants a -good- website, has to either have knowledge about code, or have someone do it for them. There is no easy way around.

However, the scan (which went through the first few hundred Mbs very quickly is really labouring at the 1.9x Gb mark (5.64 in total) and is taking hours…

View screenshot at : https://www.dropbox.com/sh/nw6bh7nszyka544/AAC-8yWyM0pJl2z0_flQlQhaa?dl=0

Please help, its a nice interface etc and seems well liked but something is not right…
I’m with Bluehost if that matters.

Thanks in advance.

https://www.ads-software.com/plugins/wordfence/