Long awaited WordPress 2.5 is here

It’s here. It’s here. WordPress 2.5 is here. For those who haven’t been keeping up with the development, this newest version features a cleaner interface, widgets for the dashboard, tag management, search pages in addition to posts, easier plugin upgrades and tons more.

I upgraded my site tonight and so far nothing has broken. The development folks say there were very few changes to the database, so most plugins that were compatible with 2.3 should remain compatible with 2.5.

My first impressions are:

  • I love the new, cleaner dashboard
  • The one-click plugin upgrades ROCK
  • Built-in galleries look like a great addition, but I haven’t played with it yet

I can’t see anything that jumps out and screams “woah – why did they do that?”. Everything I’ve poked at so far makes perfect sense and it’s obvious the amount of time and thought that went into this release.

Thanks to the WP team and everyone involved with contributing, testing documentation and development.

Guest blogging at Loose Ends

Writing isn’t my thing. I can sit down and type up a quick blog on an off the wall topic, but to actually write an article can be a struggle. When I find a topic I enjoy, the writing comes a bit easier. Such was the case with a guest blog I did for my friend Katie Baird at Loose Ends.

During a recent teleclass we were discussing websites. I mentioned the importance of having a high content ratio (code to text ratio). This was a new term to most of the attendees. So, when Katie asked if I’d be willing to write an article for her blog on the topic, I said sure.

It took me a bit longer than I first expected because I reread and tweaked it for a few days before declaring it ready for publication. I wanted to be sure the article provided good information while not becoming boring. Sometimes I have a tendency to speak a bit too techy and I tried to avoid doing that with this blog.

Katie has posted the article on her site. You can read “How Code to Text Ratio Affects Your Site’s Performance” at the Loose Ends blog.

Protecting Your Website

How safe is your website? Did you know some of your hidden files may be visible to the public? Could someone intent on wreaking havoc hijack your site and pose as a banking institution?

These are questions not often considered by a website owner, but should be. Here are two quick and easy ways you can use to help increase the security on your site, making it less appealing to hackers.

CONSIDERATION # 1 – file list showing in open directory

By default, web servers are set to show a file named “index” when a user browses a directory or folder. If there is no file named “index”, most web servers will show the contents of the directory. This directive may open your website up to unwanted viewing.

Consider this – do you store your image files in a folder called graphics or images? You aren’t alone. It is common practice for web designers to keep all of the graphics files in a sub-directory for ease. However, if the web server for that account does not have restrictions on what to display, all files in that directory may be exposed by simply pointing a browser to the URL of that folder.

Now, for an images folder that may not be critical. Let’s imagine we are working in a directory that contains member applications or PDF forms or something with more importance. Suddenly you can see where there may be significant risk to not securing directories.

Here are two methods you may use to close down your directories and prevent the files from being displayed in folders where no index file exists.

Method #1 – Add a line to your htaccess file (Unix/Linux)

If you have access to and are familiar with the .htaccess file, this is the best option. Add the following line to your .htaccess file to prevent a directory from showing its contents when no index file exists.

Options -Indexes

When a user attempts to view a directory, they will instead see a blank page or a 404 error, depending on your server settings.

Method #2 – Upload a blank index file

If you are unsure about modifying the .htaccess file and/or you do not have access to it, this is the second best option. It is a bit more tedious, but a safer option than meddling around with the file that controls your web server behavior and could potentially break your website. Simply create an HTML file and name it index (.htm or .html). You may leave the content blank or enter something such as “This page intentionally left blank” or another creative message. Upload this file to any folders that do not have an index page. When a user attempts to view the directory, they will instead see this blank page.

CONSIDERATION # 2 – incorrect permissions on file folders

In some instances, you will need to modify the permissions on a directory to allow the server to write to a file or execute a script. Changing file/folder permissions should only be done by someone who understands the settings and possible consequence of making such changes.

Changing a folder to 777 access permits anyone to read, write and execute that folder. This is a huge security risk. Potential hackers are constantly combing the Internet for folders to exploit. A folder with incorrect permissions may allow hackers the ability to upload fraudulent scripts (most often fake banking pages to collect sensitive data from unaware uses).

If you are installing a script that directs you to make changes to your folder permissions, be sure the script is from a dependable source. If you are unsure, get a second opinion or just don’t do it!

Testimonials plugin listed in WP directories

The WP-Testimonials plugin is now listed in the Plugins directory of WordPress Extend. The feedback has been positive so far and I am pleased so many users are giving it a download.

A few people have said the table wasn’t created automatically when the plugin was activated. This is something I did not have happen during development testing, so I am not sure what is causing the problem. The people who encountered this were knowledgeable enough to create the mySQL table manually, but it’s certainly something I want to resolve. I will be looking into it and if I find the issue, I will release an update.

Testimonials plugin released for WordPress

Several people have contacted me looking for a testimonials plugin for WordPress. Most times, they found my site because of a similar testimonials plugin I developed for Geeklog awhile back. I searched around for a bit and could not locate a plugin like this for WordPress. So, I decided to create one.

The plugin is online and available for download from the WP-Testimonials page. I have also submitted it to the WordPress plugins directory and am waiting to hear back.