Tag: upgrade

Posted on
by

WordPress has been making a big deal out of their new default theme, Twenty-Ten, released with WordPress 3.0. Meanwhile, I’ve been watching this site get more and more cluttered, and I keep having to tweak the existing theme to be able to deal with new WordPress features like nested comments, custom menus, etc.

Last week I had to replace the theme’s comment form (fortunately with something simpler) because it didn’t interact quite right with WordPress 3.0.

What the heck. I haven’t changed the look since 2007, so I might as well give it a shot.

I’ve switched over to Twenty-Ten, using one of my own photos for the banner. It’s a view from Modjeska Grade Road, taken last January.

Modjeska Grade View

I’m not quite happy with it yet, but I’m not sure what I want to do next.

My main goals for the new layout are:

  • Move the last of the customizations out of the theme and into plugins (so that I can easily switch to another theme if I want to).
  • Keep the new page uncluttered and relatively fast-loading (which is why I haven’t added everything back to the sidebar).

I have had to make a couple of adjustments to the theme itself. Twenty-Ten insists on showing excerpts instead of complete posts for archives, categories and searches, so I had to go in and modify that. I also added a couple of bits to the stylesheet: alternating comment backgrounds, tweaks to the old Twitter digests, etc. Still, I’m making a point of keeping those changes minimal and grouped together.

I’m also trying out WP-Minify, which should make scripts and styles load a lot faster, or at least the ones hosted locally. Unfortunately there are still a lot of remote scripts for things like Google Analytics, the Share This buttons, and the Link Within thumbnails. Some of them might work. I’ll have to experiment.

So, things are in a bit of flux. Please let me know if you find something that doesn’t work, or miss something that used to be here, by doing one of the following:

  • Leave a comment on this post.
  • Use the contact form.
  • Email me at kelson – at – pobox – dot – com.

Thanks!

Posted on
by

OK, I think the new server is tested enough for now. Time for lunch. And, I think, a walk.

…

Odd: I just watched two people tossing things over the edge of the roof of an office building in the distance for several minutes.

…

I’ve just turned off our oldest internet-facing server. I’m not 100% sure, but I think it went back to 2001 – almost as old as IE6!

Posted on
by

Fedora LogoA few days ago, my Linux desktop at work popped up a message saying that Fedora 11 was available, and asking whether I wanted to upgrade automatically. Well, I didn’t have time to deal with it then, and in the past when I’ve upgraded Fedora (either from a CD or from a downloaded image), it’s been a big production, what with running the installer, rebooting, installing updates, updating third-party repositories, and finally rebooting again after all the updates are installed.

So I put it off for a few days.

Today I decided to try it.

The automatic upgrade program is called preupgrade, presumably because it downloads everything you need in order to prepare for the upgrade. It downloads everything while your system is up and running, then sets it up so that when you reboot, it will launch the installer. It installs everything, makes the changes, then reboots into the newly upgraded system.

And then it’s done.

It’s network aware, and works through yum, so it will actually take into account both third-party repositories and anything that’s been updated since the new release. It actually went out to livna.org RPM Fusion and picked up the appropriate NVIDIA display drivers.

Download while you work. Reboot. Wait. Done.

The only snafu I ran into was that it removed my copy of the Flash plugin, but I think I was using the experimental 64-bit one anyway, so it’s not terribly surprising.

I get the impression that Ubuntu has had a similarly smooth upgrade process for a while. And after my experiences moving from Fedora 9 to Fedora 10, I was seriously considering jumping ship. (Hazards of living on the bleeding edge.) But it looks like I won’t have to.

Now I just have to find time to play around and see what’s new!

Update: I’ve run into one snafu: xkb error popups every time I wake the computer from suspend. Resetting the keyboard worked.

Posted on
by

I have now updated this blog (and Speed Force) to WordPress 2.7 Final — using the built-in updater. It takes a while, but it’s entirely automated once I tell it “Install” and enter my FTP info.

The built-in plugin installer is very convenient as well.

The Flash 10 upload bug is fixed!

As with Speed Force, I’ve dropped the plugin I was using for avatars in favor of the built-in feature. It still generates Wavatars for those of you who leave your email address but don’t have Gravatars, but it seems to generate them differently, so you get a new and different monster.

All my plugins work as far as I can tell, but there are a couple of glitches:

WP-Super-Cache doesn’t seem to be deleting expired pages on schedule. And the spot for the convenient clear-cache-now buttons for that and WP Widget Cache doesn’t exist anymore, so if I do need to clear them out I need to go to the plugin’s settings page — which is what I had to do until a month ago anyway, so no big deal.

Also, Twitter Tools doesn’t seem to be able to pre-check the “Notify Twitter about this post” checkbox. But the important stuff works.

I’m still getting used to the new admin layout, but the only thing that really bugs me is there doesn’t seem to be a quick way to get to scheduled posts from the dashboard.

Other than that, so far so good. As always, let me know if anything seems broken.

Posted on
by

Last month I finally got around to a major rebuild of my computer, something I’d been meaning to do since May when I traced some display problems to the motherboard*. I finally bit the bullet when I started seeing signs of disk errors, and dragged the machine into the present day. (64-bit, dual-core, 2 GB RAM, SATA drive, faster everything.)

Then I discovered that some of the display problems actually were the fault of the monitor.

So I went out and bought a new monitor while Fedora was installing, and I took the opportunity to go widescreen.

My criteria were simple: The resolution and physical size both had to be as big or bigger than the old one (17″, 1280×1024), and it had to be under $300. That meant at minimum a 22″ display at 1680×1050, and I found a Hannspree 229HBP for about $190.

There was a Dell right next to it, same size & resolution and comparable specs, and the Best Buy employee had been talking both of them up. The Dell was on sale for $290. I asked what the difference was. He thought about it for a few seconds. “Well, this one [the Hannspree] does run a little bit hotter. But mostly it’s just the name.” Thank you, Best Buy employee whose name I’ve forgotten, for helping me save $100.

The biggest difference, aside from actually having room to show both the toolbox and document windows on GIMP, is that I don’t maximize windows anymore. Not that I maximized apps that often before, not counting the stuck-in-low-res period. I’ll occasionally run a video or slideshow fullscreen, but the only program I regularly maximize is my email client, and that’s because I can put it in three-column mode (Folder tree on the left, mailbox listing in the middle, message content on the right).

Something to watch out for: At first I left the monitor off-center, because there wasn’t enough room on my desk for it. I figured as long as I worked mostly on the right part of the screen I’d be fine. But I ended up having neck problems shortly afterward, and Katie suggested I check the placement of the monitor. I shifted things around so I could center it, then set it on top of an Amazon box to raise it a couple of inches, and the sore neck cleared up.

I’ve only run into two problems (not counting the placement): There’s one dead pixel, but it’s off in a corner so that it’s not really an issue. I almost didn’t notice it at first when I was still setting things up, because the default GNOME layout has a Mac-style ever-present menu bar, and it falls right on the edge. Usually it ends up either on the edge of a window border or lost in the wallpaper noise.

The other problem: the built-in speakers pretty much suck, but I had external speakers already, so again: no big deal.

* It stopped displaying any resolution past 1024×768. I could tell it wasn’t the monitor because it was perfectly happy to show another computer at 1280×1024. And not the drivers or OS because I had the same problem booting from a LiveCD. And not the video card because plugging in another one didn’t solve it. This was particularly frustrating since it was an LCD monitor, so running at less than native resolution made everything blurry. Still, I put off replacing the mobo for months since it’s such a pain to do.