Earlier this week, I was working on some of my typical spring photographs – buds and blooms from throughout my garden – when I took a short break, went outside, and immediately felt like I was being watched. Well, I was being watched, by the nemesis whose reappearance every spring has me overplanting my pond, surrounding it with pots and wire trellises, and taking frequent headcounts of my poor carp that just want to be left to swim and eat in peace. It’s a blue heron, either the same one or certainly a relative of those that have been visiting my neighborhood – so I’ve been told – for at least a decade. “Blue heron” is surely a fine name for a big bird, but I prefer “Pond Monster” – a better reflection of our relationship.
It flew off my roof before I could get my camera out; in these shots, it’s perched on the front peak of my neighbors house.
Click the picture for a wider version; something about those eyes…. you know you’re being evaluated as potential snack when those things turn toward you.
This isn’t a great shot, but it’s the only one I’ve ever gotten of the bird in flight. That wingspan has to be six to eight feet, maybe more. Can you say pterodactyl? Those dangling “fingers” are a nice touch, eh?
Through a series of mis-steps this evening, I managed to quite effectively destroy my fledgling photoblog, afewgoodlenses. It wasn’t as hard as you might think, and I did it while trying to solve a "problem" that really didn’t need solving, after reading this article:
Giving WordPress its Own Directory While Leaving Your Blog in the Root Directory
There’s certainly nothing wrong with this article, or with the instructions. The change is appropriate to a situation where you’ve installed WordPress in a subfolder (such as "blog") but don’t want users to have to key in a URL that includes "blog" to get to your site. And following the instructions worked, but I didn’t like the fact that after I got it working, keying in the following URL…
… exposed the directory structure for my site. So, I attempted to reverse the procedure, got it wonky somehow, and afewgoodlenses became inaccessible. I tried for an hour or so to twitch things around and get it functioning again, but finally gave up. Someone with more WordPress experience than I have would probably have been able to figure it out, but I couldn’t and decided to just reinstall WordPress and start over.
It occurred to me after I cleared my WordPress database that I probably could have backed it up and restored the contents to the freshly installed tables, but having not done that before probably would have gotten me in even deeper.
I had previously been using an HTML redirect to send users from www.afewgoodlenses.com to www.afewgoodlenses.com/blog … and have reverted to that approach now that the site is back up and running.
On the bright side, the theme modifications I made so far remained intact and the photos I had posted were still on my host, so it’s just a matter of setting up categories again and re-posting them — which I’ll do over the next couple of evenings. In the meantime, if you linked to any of the posts on afewgoodlenses, the link is now broken and will likely have a different URL when I repost the articles. My apologies for the inconvenience, but you may want to remove those links.
The experience does raise a couple of questions in my mind about backing up a WordPress installation, something I’ve never even looked into. Please post suggestions in the comment section if you have any experience with that; I’d be especially interested in hearing from any one who has actually restored a WordPress backup successfully.
Thanks for reading!
Here’s a little (!!) something you don’t expect to see perched on your roof when you get home from work:
Why is there never a cat around when you need one?