I Survived the Update to 3.0

Well, I took the plunge. To WordPress 3.0.

For you WordPress newbies out there, I remember the olden days, back… Ohhhh… TWO years ago before WP incorporated the automatic upgrade feature. Back then, we used to have to update our blogs manually. As in SAVE everything first. As in upload (via FTP) all the new files. As in “hold your breath and pray it doesn’t explode” updates. Nothing bad every happened to me, thankfully, (didn’t stop me from making billions of backups, though), but I heard horror stories about folks whose entire blogs self-destructed.

Anyway, it’s easier now. But the old terror still clings as I hit the “upgrade now!” button.

All’s well that ends well. I updated 12 blogs, and all are OK.

Whew.

Oh, and how is WP 3.0?

It’s OK. I don’t see much difference. They added some features that I don’t need, so its not much different besides the light blue color and the fact that my username doesn’t automatically save so I can log in (so I have to type it in each time)> What is up with that, anyway?

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]
Posted in blogs, desktop publishing, Wordpress. Tags: , , . Comments Off »

WordPress 3.0 Coming Soon

I don’t know about you, but I’ve had WordPress-Update-Disease. I’m tired of updating WordPress all the time! :-p

Each new version is an improvement, so that’s a plus…. but I don’t want my WP to be a Swiss Army knife of blogging platforms. Unless there’s a necessary security update, I’m really happy with what I have and don’t want any new, complicated features.

In case you haven’t heard, WordPress 3.0 is slated for an April release.

Highlights

* The merge with MU (but not the extra domain stuff, which will remain plugin territory for this version)
* Better support for custom post types
* Better support for hierarchical (category-style) taxonomies
* New default theme “Twenty Ten”
* Better menu management

New Features

* Multisite capabilities (#11644)

User Features

* Custom Navigation (#11817)
* Custom Backgrounds (#12186)
* Upgrade plugins in bulk from the plugins page (#11542)
* Active plugins can no longer be edited; you must first deactivate
* Choose username for the first account, rather than using ‘admin’

Development, Themes, Plugins

* Admin support for custom post types (#9674)
* New template files for custom post types (#12105)
* Admin support for hierarchical taxonomies (#10122)
* Author specific templates (#12064)
* get_generic_template function to include generic files (other than header, sidebar, footer) (#13146)
* Standardized comment form with comment_form() (#10910)
* jQuery updated to 1.4.2 (#12305)
* get_taxonomies() function to get a list of all registered taxonomies (#12516)
* Settings API now supports automatic error display for validation problems with add_settings_error() (#11474)
* the_shortlink() template tag (#10640)

Advanced Features

* Customizable death (wp_die is now pluggable) (#11892)

“Customizable death,” LOL?! Now I KNOW that WordPress is getting too big for its britches.

It’s unfortunate that WordPress couples security updates with software updates. They should be separate. I would like to update ONLY security releases. Why must we be forced to clutter our databases with more and more updates, throw our themes and plugins out of whack, and more, for a fancy new machine? I dislike it.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]
Posted in blogs, Wordpress. Comments Off »

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]
Posted in Wordpress. Tags: , . Comments Off »

Another Great WordPress Theme Site

Believe it or not (!!), I’ve started up some new blogs! :D So I spent quite a few hours looking over my options. I checked out Drupal, Joomla, and b2evolution platforms for possible choices… but Drupal was difficult to manage and had very limited choices. Joomla looked too complex, and b2evolution was too plain. So I reverted back to WordPress. When it comes to blogging, I really need a variety of nice themes. I’m willing to slog through technicalities and database manipulating, but when it comes to nice themes, I draw the line. By FAR, WordPress has the best themes around. And there are plenty of exceptional-quality themes, too. Here’s one: Template Lite WordPress Templates. (This is not a sponsored post!). I have used some of their themes, and I think they are beautiful. They are very artful, and free! I’m going to use one o their new ones, Sunset Farm, on my new blog very soon. I’ll be sure to let you know about the grand opening. ;) Check out Template Lite for free WP themes. I’m very impressed with what’s there.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]
Posted in blogs, Wordpress. Tags: , . 2 Comments »

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]
Posted in crime, security news, Wordpress. Tags: , , , . Comments Off »

WordPress.com vs. WordPress.org

A fellow blogger recently asked, “What’s the difference between hosting yourself and just doing it with wordpress.com?” I get this question a lot, and I realize I have never written a post about it. So I thought I’d explain.

WordPress.com is the website where you can start up a free blog and get it hosted for free on the WordPress servers. It’s something like Blogger, another free blogging company. And, just as with Blogger where your blog’s domain has a “.blogspot.com” after it, all the free WordPress.com blogs have the “.wordpress.com” after it. For example, I have a WordPress blog called www.newyorktraveler.wordpress.com. It’s free for me– it was free to create, free to set up, and it’s free for me to maintain.

WordPress.com blogs have stricter regulations than Blogger blogs. WordPress does not allow sponsored posts; you cannot access the database files to your blog, which means you cannot customize it wholly and you may only choose from a select (albeit large) group of blog themes; you cannot place widgets or ads in your sidebar (such as Entrecard, Adgitize, etc). And last I heard, unless it changed somewhere along the way, WordPress inserts ads into your blog periodically.

WordPress.org is the website that showcases the blogging software (the “platform” they call it) that you may use for free on your own hosted blog. The WordPress.org software is installed onto your web host’s server– you install it. It’s not difficult to install, but it’s a technical process even though web hosts have made it as easy as possible. I recently installed two new ones for my daughters, so this is all fresh in my mind.

WordPress.org software hosted on your own web hosted server will NOT assign a domain name for you. You must register one yourself, at eNom, Godaddy, or even through Google (which has the least expensive option, at $10). Your domain name is a “house address” of sorts. You want to build a dwelling located at that house address, but you need two things– a house and a rented lot. The “house” is the WordPress.org software and the “rented lot” is the web host you choose.

I’ll discuss more about getting a self-hosted WordPress.org blog in the near future. I hope this helps clear up a little about the difference between WordPress.com and WordPress.org blogs.

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