Get Back

When this little blog launched back in December 2004, It was a Blogger blog. You know, the URL contained blogspot: http://basils.blogspot.com/. I decided to get my own domain name: basilsblog.net was what I chose to use. At the time, there was no capability of having my own domain name on a Blogger blog. And, I wanted some additional functionality I couldn't get from Blogger ... at the time. So, I moved to TypePad, which is based on MovableType. And, it allowed me to have my own domain name. But, TypePad and Network Solutions, who I've used for years, don't play well together. That is, http://www.basilsblog.net/ works with TypePad, but http://basilsblog.net/ does not. Since Network Solutions has been around longer than TypePad (or SixApart, who owns TypePad), I figure that the problem lay with TypePad, since other hosts don't have that issue. So, I decided to go elsewhere. That's when I settled on WordPress. I hosted the blog myself for a bit, then decided I didn't want to be bothered with all the issues that arise with self-hosting. I proved I could, and decided I didn't like it. So, I moved to a hosting service. A couple, actually. No matter what I decide to do, there are issues. Using WordPress.com for hosting (it's free) has some drawbacks. The main ones are:

• JavaScript isn't allowed.
• Advertising isn't allowed.
• Limited (though professional look) templates.

Those are really the only issues with WordPress.com for hosting ... but those make that solution unacceptable to me. Others might have no problem with those issues, but I do. Paying for hosting with, say, Network Solutions has some issues, and they relate to the cost:

• The cost. True, shared hosting is only about $10/month, which isn't bad. But, that's $120/year. That's acceptable, though.
• Shared hosting encounters slowdowns from time to time. That's because other Websites are on the same server, hence the "shared hosting" name. Slowdowns happen enough that it's not acceptable to me.
• Private hosting, which would eliminate the slowdowns associated with shared hosting, costs a lot more. Around 5 times as much. That's too much, considering I make very little money on this blog.

So, even though I really like WordPress, there are some things about it I don't like:

• Security updates. It's almost as bad as Microsoft Windows. Every time you turn around, there's another security issue with WordPress, and a security update is needed. And, upgrading WordPress isn't the easiest thing in the world to do. Installing fresh is a breeze, but upgrading is a bear.

Another option is: Blogger. Yes, the very hosting platform I used to begin with. But, Blogger in 2004 isn't the same as Blogger in 2009. Blogger now allows your own domain name. That is, with a Blogger blog, I can use my own domain name now. And, for free! But, Blogger doesn't have all the bells and whistles of, say MovableType, TypePad or WordPress. But, it does have a lot of really good features. And, its servers can handle a load.

What's all this mean? There is no good solution. And, for some time, I've kicked around those different options, and it still has the same answer: there is no good solution. Then, it hit me. If, when this little blog first started, Blogger had the functionality it had today, would I have ever moved it? I'm thinking no. Blogger has some really good functionality, and I can have my own domain name for free. And that was the reason I moved in the first place. So, I'm moving it back to Blogger. There will be some issues with links breaking, but I'm slowly working those issues out. Spam filters aren't as sophisticated with Blogger as with WordPress, but they do offer registration for comments. Yeah, that's a little more troublesome overall for users wanting to leave a comment, but it sure keeps trolls away. TrackBacks and Pingbacks don't work with Blogger, but since it's owned by Google, it automatically uses Google technology to list links to the blog (called Backlinks). Not as immediate at TrackBacks or Pingbacks, but more certain; there's no TrackBack Spam. Again, not perfect. But, if Blogger had been this way all along, I'd never have left. Now, I'm back.

Problems with Safari browser and WordPress ... resolved!

A year ago today, I wrote about how WordPress (version 2.2.3 at the time) and the Safari browser (version 3.0.3) didn't play nice together.

Well, they do now.

I'm not sure when it happened. But somewhere along the way, either Safari or WordPress ... or both ... changed something.

I'm running WordPress 2.6.2 now, and Safari 3.1.2 (5525.20.1). And, unlike last September 25th, I'm able to write a post on WordPress, using Safari, and everything's just fine.

Whether I use the HTML mode (which I do use most often) or the Visual mode (which is sometimes really handy), everything is now fine.

I wonder if WordPress knows. You see, the topic is one of the items listed as "Under Consideration" for a WordPress enhancement.

And it works with both Mac and Windows (Safari 3.1.2 / 525.21). I wrote this on my Mac, part using OS X 10.5.5 and part using Windows XP SP3.

So, whatever problems there were ... are resolved.

At least for me. At least for now.

Problems with Safari browser and WordPress

See update.

¶ If this post is hard to read, it's because I'm using the Safari browser to write this on a WordPress blog. ¶ You see, I got a MacBook computer recently. And I've been trying out all the functions of a Mac as I make the change from 20+ years of PC computing. ¶ Now, to be sure, I do like the MacBook. I like it a lot. Oh, sure, there are some differences. But the main thing is, the MacBook is easy to use. Really easy to use. ¶ But it's not perfect. ¶ You see, Apple has their own browser: Safari. ¶ It's a fine browser, to be sure. It's pretty fast. Everything on the Mac is fast. Except for my Microsoft Office 2004 suite. ¶ So, Safari is fast. But it has a bug with WordPress. ¶ Now, if you don't use WordPress, you might be just fine. But WordPress and Safari don't play nice together. ¶ It seems that if you use the Visual Editor for writing ... and I do ... the paragraph formatting screws up. ¶ How bad? Well, you see those little paragraph marks all through this post? That's where I put paragraphs when I wrote this. ¶ And, you see how this has all run together as one big paragraph? That's because of the bug in Safari. ¶ Now, there are reports that the new version of Safari has solved this issue. ¶ But it hasn't. ¶ You see, I'm using Safari 3.0.3 (522.12.1) ... and WordPress 2.2.3. ¶ Yes, that's a beta version. But it's the version that they say has the issue fixed. And it doesn't. ¶ So, excuse how this post looks. But it looks this way because Safari 3 hasn't fixed the bug. ¶ Which means I'll continue using Firefox. Which I like. And won't be using Safari. Which I thought I'd like ... and would if Apple would get off their butts and get it fixed.

UPDATE: Some time in the past year, things got better. They play nice now. Read about it here.