Why?

I really liked the time tracking/time management that MyIntervals offered, but there are several areas where I feel it didn’t meet my needs as well as Basecamp did.

While MyIntervals might be a terrific solution for some web developers, it has some features I didn’t need that only added to the complexity, and it was a lot weaker in terms of communication between me and my clients, an area that Basecamp is particularly strong in.

I’m going to really miss some of the time management functionality that MyIntervals provided, but there are a few add-ons to Basecamp that I believe will help close the gap in that area between the two solutions. In particular, Project Recon is one that I will definitely be trying out. I might also try some of the other solutions listed here in the near future, as they have several interesting ones listed there.

I first used Sphinx well over a year ago, when I had a project that required full-text searching of a massive, 25 Million + database, something that was probably a little too big for the default MySQL full-text engine to handle. Additionally, I wanted to use the InnoDB MySQL engine, as opposed to the ISAM (which is the one that had full-text capabilities).

After doing some research, I ended up going with a MySQL/Sphinx joint solution, where I stored the data in MySQL, and used Sphinx to actually do the searching.

Since then, this already impressive project has come a long way, and if you haven’t already checked it out, it is well worth a look. It seems to be gaining quite a bit of traction. From the latest email:

Also in the news, we’re among the finalists in SourceForge Community Choice Awards 2008! Sphinx is in the shortlists for “Best Project”, “Best Project for the Enterprise”, and, somewhat unexpectedly for me, “Most Likely to Be the Next $1B Acquisition”. Many thanks to all who voted for Sphinx during the nominations! Now is the time to vote again in the 2nd round. There are several quite popular competitors (such as OpenOffice), so please spread the word as much as you can.

Here’s the link again…

I have, in the past, used Basecamp to manage my projects (in conjunction with Blinksale). Recently, however, I have been wanting something a little different, so after eying it for a few weeks, I finally set up a trial account with MyIntervals this morning (both software packages offer a free trial).

Pros? Cons?

Well, they each have their strengths, I suppose.

Basecamp is stronger on the communication side of things (with “Writeboards”, Messages, and even chat software integrated). They also pride themselves on the simplicity of their software, and in my experience, clients rarely have any trouble learning how it works. It doesn’t have any invoicing functionality, but I have made up for that deficiency by integrating it with Blinksale.

MyIntervals, on the other hand, is stronger on time management. It has detailed time tracking and reporting interfaces, as well as invoicing functionality, and has a good many more features then Basecamp has.

It’s just been one day, but so far, I am really liking MyIntervals, and their emphasis on time management/tracking, so I will most likely be staying with them.

One thing that always surprises me when working on code written by others is how frequently the code is subject to what is called MySQL Injection Attacks.

Although some servers handle it automatically (which is highly undesirable, for several reasons), anytime you use any user-submitted data in a MySQL query, you MUST “escape” the data to ensure that it is safe from an “Injection Attack”.

For those of you who are programmers and are unfamiliar with what I mean, you can read up on the subject more at the PHP Manual, but regardless of which database abstraction library you use (or if you directly use PHP’s MySQL class/funtions), always ensure that you have the database secured by escaping everything.

I won’t post examples here, as the link above has several excellent examples of ways to prevent it, and all decent database abstraction libraries should have their method of escaping the data implemented and documented. Just ensure that you use the methods provided!

The nature of the work is that it often exposes us to many distractions, ranging from email (always log out of email when you’re working!) to chat (same here…) to an interesting link you happen to stumble upon.

Although I have read many productivity and time management books through the years, many of which were helpful, there are a few things that are unique to fulltime web professionals, a group that none of the books I read specifically targeted.

However, late yesterday afternoon, I got an email with a link to a half-hour video put out by Eben at Guru MasterMind titled Becoming a Productive Modern Guru, which had some very helpful advice.

If you have read or studied the subject in the past, you will likely hear some familiar techniques, but if you take the time to watch it, you will hopefully pick up some new “tools” to improve your productivity.

To those ends, I came across the family of MVC (model-view-control, a class design pattern) frameworks for PHP early in my “productivity quest”, and have never looked back.

Although there are several other frameworks, such as the Zend Framework, and CakePHP, my current favorite framework would have to be the CodeIgniter framework.

This framework, like the others mentioned above, uses the MVC design pattern, similar to the popular Rubies on Rails (ROR programmers shouldn’t have much trouble jumping over to a MVC PHP framework, as the syntax is in many ways, very similar).

I now start most new projects with a copy of CodeIgniter using the Smarty library for templating (I prefer that to the default CodeIgniter templating system), and have noticed an increase in development speed of new projects since using it.

It is possible to simply plug in different libraries (in addition to the libraries that come with CodeIgniter), and I have done that with graphing libraries, image libraries, and a host of other third-party solutions in my applications, to significantly speed up the development of new sites.

For those of you who are currently using another framework or are not even using a framework, CodeIgniter is definitely worth a look, to see if it fits with your programming style. It’s not the only solution out there, but it has done well for my projects.

Header redirects are redirects that are handled instantaneously and transparently by the browser, and come in two common forms: 301 redirects and 302 redirects.

The difference between the two is that a 301 redirect is used to tell users that a particular page has permanently moved, and a 302 redirect is used to tell users that a page has only been moved temporarily.

To implement a redirect, the following code must be placed in your PHP script before it prints out any output. Because the redirect is sent in the HTTP header, if the PHP script outputs anything before the redirect header is set, PHP will automatically send headers along with the data that is printed out, and it is impossible to add other headers after data is printed.

301 Redirect:

header("HTTP/1.1 301 Moved Permanently");
header("Location: http://www.prophpdevelopmentblog.com/");

302 Redirect:

header("HTTP/1.1 302 Moved Temporarily");
header("Location: http://www.prophpdevelopmentblog.com/");

One important thing to keep in mind when considering putting up a redirect, is that search engines will generally follow and pass link popularity on through 301 redirects, but not 302 redirects, so if the redirect is more or less permanent and you would like the search engine indexing/ranking to reflect that, then a 301 is the way to go.

“How do we compress the (HTML) page output?”

First of all, why would anyone want to compress their webpages? There are really two reasons why it is useful:

1. The page loads faster, especially for users with slower internet connections
2. The site uses less bandwidth, which means that the site, especially if it gets lots of traffic, is cheaper to run

The downside to compressing page output is that it uses more CPU processing power, but the benefits usually outweigh the extra processing that needs to take place server-side.

Techniques for Compressing Page Output

There are several ways to compress page output, which we will discuss below:

First of all, it is possible to activate it for all content (both PHP and non-PHP) served by your Apache web server by changing the configuration of Apache. However, for this post, we will focus on doing it with PHP, as that is the subject of this blog.

If you have access to your php.ini configuration file, the preferred method of compressing all PHP output is to do it by modifying the following configuration settings in that file to have these values:

zlib.output_compression = On
zlib.output_compression_level = 5

In the above code, “zlib.output_compression_level” should be set to a value between 1 and 9, with the higher values giving more compression, but using more server (CPU) resources.

Alternatively, if you don’t have access to the php.ini file on your server, you can put the compression code directly in your PHP scripts. To do that, put the following line at the top of all of your PHP pages that you want compressed:

Either way you use, once you think you have everything in place, you can use one of many compression testing websites in order to verify that your site is indeed sending compressed output to browsers.

Is it worth it to set up page compression? In most cases, yes.

For example, on one site I was recently working on, we were serving up about 2 Million pages/month without compression. We had complaints of the site loading slowly for some users (the pages were large), as well as the bandwidth getting expensive, so I took steps to set up page compression using the (first) php.ini method.

After getting it configured, I saw a noticeable decrease in page loading time, even for me with my fast internet connection, and the bandwidth bill dropped to only around 30% of what it was before. At the same time, the load on the dual Xeon processor didn’t move up noticeably, so in this case, I considered it to be a success.