There’s a reason for my ‘Friday’ post showing up Sunday morning; and this week’s ‘Sunday’ post, whatever it’ll be about, getting delayed until next Sunday.
It’s been ‘one of those weeks.’
Starting Monday afternoon, I’ve experienced a series of minor technical glitches and a major one, simple tasks that turned complex, swift errands that took hours – – – you get the idea. Then on Friday I discovered that I couldn’t update this blog.
On the ‘up’ side, I was getting the same “Fatal error: Call to undefined function wp_raise_memory_limit…” message each time I tried logging in, right after WordPress crashed.
That gave me and my son something to talk about when he got home from work.
We agreed that something had gone wrong when I updated WordPress — before adding Friday’s ‘science’ post, not one of my better decisions — and that fixing the problem would take much less time and effort if I let him sit at my desk and work: undistributed.
That discussion started late Friday, continued in sporadic bursts through Saturday evening, and ended with my son playing a choral “ALLELUIA!” on his phone: by way of announcing that the errant software was (probably) working again.
I can’t complain. I could, actually, but it wouldn’t be reasonable or helpful.
More good news: my wife and #3 daughter got back from St. Cloud, an hour down the Interstate; and the family van is (probably) safe for in-town driving. The brakes, probably, had started smoking after they got lost. After dark. In the larger town.
I spent part of Saturday catching up on tasks that hadn’t gotten done since Monday, and expect to be doing more of the same through part of tomorrow: at least. Then I hope that I’ll be back to my usual Weekly Schedule, getting next Friday’s post ready.
That’s the plan. What actually happens: we’ll see.