I was going to start yesterday’s aborted post by making fun of these horrifying things. After that I had a whole gross story about getting sick at work and hell if I remember what was coming after that.
So, yeah, I got sick at work, and then made it through the rest of the day and I’m fine now. Meanwhile, I haven’t technically fixed the deeply weird issue the new laptop is having– I think something about the OS isn’t playing fair with Gutenberg at WordPress, because nothing else makes sense– but I’ve found a sufficient workaround for now. I’m going to spend some more time tomorrow or Sunday fiddling with it; until then, all good.
Anyway, I’ll do a review of the laptop once I’ve had it for a week or so and put it through its paces. I’m pretty sure this particular issue (did I ever say what it was? Click on “new post” in WordPress, get a white screen. In every browser. No matter what. Every other device I have is fine.) is not the laptop’s fault. We’ll see if anything else stupid crops up.
Tomorrow we’re going to get some more shit done in the bedroom. The goal is to get work done in the house without inhaling enough drywall dust to give me cancer. Not the highest of bars. We’ll see if we can pull it off.
Discover more from Welcome to infinitefreetime dot com
Subscribe to get the latest posts sent to your email.
It might be something as daft as an adblocker disabling pop-ups. Sometimes it interferes with a website opening a new page.
Or you could try clearing your cookies from your web history. Something may have gone wonky there.
These two are always the first things I try, and 99% of the time it works.
It’s fresh installs of the browsers on a brand-new laptop, so there aren’t even any adblockers to disable. Plus it’s happening across three different browsers, so it’s got to be something about the computer itself that’s not playing nice with whatever’s going on at WP’s end. The only significant thing that is different is the system software version.
Reminds me a bit of what happened with my company’s product about 8-9 years ago. We upgraded the React framework, and with the new React release they changed how it handled various minor Javascript errors: previously it had tried to continue working where possible, but now instead they went ahead and unmounted the entire UI. Resulting in a blank white screen. We had to put in null-guards in all sorts of places. (We also were able to add something called an “error frame” that would allow us to display a message saying “an error has occurred” instead of just blank white.)