Posts Tagged blogs

Haloscan Closing Its Doors

Ouch.

Haloscan, that blog commenting software that has been around for years, is closing the service. This is from their website.

Haloscan, the legacy comment system that JS-Kit acquired last year, is physically starting to fail (the software and hardware). In order to minimize the disruption for users and avoid a hard stop, we have worked hard to provide two ways to transition off the system.

This transition will happen in batches of users over the course of a couple of months. The first batch of users will start getting a notice of the upgrade right away on their Haloscan admin dashboard.

Once presented with the upgrade message, Haloscan users will have 2 weeks to make a decision. You will have the following two options.

1. Upgrade to Echo for a 30 day free Trial and then $12/year – all your comment data will be transitioned over automatically. Read below for important information about Echo.
2. Export your Haloscan comment data and turn off their service – Haloscan comment importers are on the way from various vendors.

If you do not choose a specific path within the 2 weeks notice, you will be upgraded to the Echo trial automatically.

Haloscan was very popular with Blogger, since Blogger’s commenting functions are woefully inadequate (even after a few small tweaks by Google). I tried Haloscan a few years ago, and wasn’t too impressed. Of course, the Blogger commenting functions are terrible. But rather than continue to work with Blogger, I just went to Wordpress and my own self-hosted blogs. It’s been a great experience, with Wordpress.

Regarding Haloscan, some bloggers are afraid they may lose all their comments across hundreds of posts. I *think* Haloscan is offering a free comment migration back to your original blog host, through various third-party vendors. Not sure, though, because it seems some things are still up in the air. Read the FAQs here.

Haloscan is closing February 20.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Tags: , , ,

Good News For Scheduled Post Wordpress Users

There was some problem with the new Wordpress 2.9 release that occurred a few weeks ago: complaints were rolling in that scheduled posts were not publishing. I didn’t experience the problem (I hadn’t any scheduled posts), so I don’t know if the issue affected any of my blogs. But the Wordpress dudes have solved the problem with the release of 2.9.1.

After over a million downloads of WordPress 2.9 and lots of feedback from all of you, we’re releasing WordPress 2.9.1. This release addresses a handful of minor issues as well as a rather annoying problem where scheduled posts and pingbacks are not processed correctly due to incompatibilities with some hosts. If any of these issues affect you, give 2.9.1 a try. Download 2.9.1 or upgrade automatically from the Tools->Upgrade menu in your blog’s admin area.

I know quite a handful of Wordpress users who will be happy to see this! Since it’s not a security release, I don’t thunk it’s a critical update. However, I usually update when I can. just so I don’t have a huge update to do the next time another major release is issued.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Tags: ,

How To Keep Your WordPress Blog Secure

In case you haven’t heard, there’s a virulent worm spreading and hacking Wordpress blogs that have not been updated to the latest version, 2.8.4. Wordpress founder Matt Mullenweg advises everyone to update their Wordpress blogs:

Right now there is a worm making its way around old, unpatched versions of WordPress. This particular worm, like many before it, is clever: it registers a user, uses a security bug (fixed earlier in the year) to allow evaluated code to be executed through the permalink structure, makes itself an admin, then uses JavaScript to hide itself when you look at users page, attempts to clean up after itself, then goes quiet so you never notice while it inserts hidden spam and malware into your old posts.

The tactics are new, but the strategy is not. Where this particular worm messes up is in the “clean up” phase: it doesn’t hide itself well and the blogger notices that all his links are broken, which causes him to dig deeper and notice the extent of the damage. Where worms of old would do childish things like defacing your site, the new ones are silent and invisible, so you only notice them when they screw up (as this one did) or your site gets removed from Google for having spam and malware on it.

I’m talking about this not to scare you, but to highlight that this is something that has happened before, and that will more than likely happen again.

Hacking blogs and worms are not new to bloggers, whether you have Blogger or Wordpress, but I certainly didn’t like to read Mullenweg’s “this is something that has happened before, and that will more than likely happen again.” :yikes:

The only thing Mullenweg has to say about future hacking is:

There is only one real solution. The only thing that I can promise will keep your blog secure today and in the future is upgrading.

I admit, I sometimes wonder if hack attacks are built by certain people who use such attacks to get everyone to upgrade. This particular worm is relatively harmless, and easily detectable. I’ve heard of horrible hacker attacks, where entire blogs are wiped out or are used as vehicles to spew p*rn and other filth. This worm seems quite tame, and leaves behind broken links, which is easily detectable. Did someone create this worm simply to scare Wordpress users into forcing them to update their blogs? I’m not saying I believe this is so, just that there is that possibility. Maybe there’s more to this worm than is being publicized… But if that’s all the worm does, what else could be the motive?

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Tags: , , ,

Wordpress 2.8.3

Well, they’ve updated it again! What is this, the third/fourth time in two/three months? It looks like this latest update addresses an unchecked security bug. An astute WordPress user alerted the WordPress geeks to the security leak, which was promptly fixed. It is advised that all WordPress users update immediately.

Unfortunately, I missed some places when fixing the privilege escalation issues for 2.8.1. Luckily, the entire WordPress community has our backs. Several folks in the community dug deeper and discovered areas that were overlooked. With their help, the remaining issues are fixed in 2.8.3. Since this is a security release, upgrading is highly recommended.

Thank God WordPress is easier to update. If I was still manually updating 7, 8 blogs everytime WordPress issued an update… well, let’s just say that Typepad would look a lot better! But I do love WordPress, I admit.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Tags: ,

Wordpress Plugin: Revision Control

Wordpress 2.7 is great– so many new functionalities! BUT please– why oh why did they not revise the “revision” capability?! Wordpress’ existing Revision feature is like an auto-save feature– it will automatically save your posts as you write them, so that should your computer or software crash, you have a current copy of what you’re writing. It’s a very nice feature, except for these reasons:

  • It saves every minute or so, making a new copy (not over-writing the old copy).
  • It creates a huge post database which makes your blog work harder to load your posts.
  • It has no delete capability, so these revisions sit in your database, unused.

Yeah yeah, there are ways to tinker with your wp-config.php file and disable the revision feature. But the ability to delete and/or disable and/or control the revision feature SHOULD BE built-in. It’s ridiculous not to have it!

So, anyway, I’ve found a very good plugin for revision control, called, not surprisingly, Revision Control. I’ve tried it an all my blogs, and it works perfectly. I have mine set to auto-save only TWO posts (you can choose to save more). It also gives you the ability to disable revisions completely, and to delete existing revisions. Kind of like virtual wrinkle creams for all the excess baggage you want to smooth out of your databases! (How’s that for fitting it in, huh?) :-p

My only complaint with Revision Control would be that I wish it had a checklist where I could tick off radio buttons and delete the revisions all at once. As it is now, I have to click “Delete” for each revision that exists, which is tedious, because a lot of my old posts have a dozen or more revisions sitting in my database! But that’s a small complaint.

Check out the plugin, it works well for all my 2.7 blogs (and I hear it is compatible for 2.6 WP blogs as well).

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Tags: , , , ,