Posted by & filed under Developer Blog.


Coda by Panic

I’ve recently abandoned Dreamweaver as my primary web development platform. I know what you are thinking, “what took you so long?” Well, the truth of the matter is, I think Dreamweaver gets a bad wrap, just because of the WYSYWIG stigma. Frankly, I rarely if ever, was using the Design view in Dreamweaver and I mostly used it as a text based editor. I really love the shortcuts they’ve built in and found myself developing rather quickly because of them. So much so, that it has taken me quite some time, and quite a bit of trial and error, to actually end up leaving it behind.

There are several features that Dreamweaver has that I was always very particular about when looking for a new tool. Some of the requirements I have are:

  • Built in SFTP (many editors only have FTP, if anything at all)
  • Rich HTML, CSS, and Javascript support with good shortcuts and autocompletion. (Many, like Eclipse, are really good for back-end dev, but downright suck at front-end. I’m a front-end developer.)
  • Synchronization feature, or at least some way of tracking which local files are different than those on the server (surprisingly few editors have this as a feature).
  • Quick access to projects (The ability to save “Sites” and jump between them without ever using the “Open” dialog).
  • Subversion integration was a plus, but not a requirement.

Frankly, Eclipse is a huge, bloated piece of nightmare for installing and running. Slap Aptana on top of that and you’ve got yourself a mess. Granted, Dreamweaver is also bloated, but not nearly as bad. As mentioned above, I also feel that Eclipse is really great for back-end programmers, but falls short for front-end. Same feeling about Textmate. Only Textmate is missing even more of the features listed above. After giving these, and others a shot, I would always find myself switching right back to Dreamweaver just to get the job done in an efficient matter. There are other programs I gave a shot, but it just seemed like they were all doing some things really well, but others really bad.

Enter Coda.

I learned about Coda from another web developer/designer that I follow on Twitter, @cliftonite. Obviously, I was skeptical at first. But I decided to fire up the 14 day trial. If I was going to ask my employer to purchase a license for me, I was going to have to make a good case, so it had to be really convincing. So I started keeping a list of things I liked about it, and things I missed from Dreamweaver.

Within a week I was sold. Here’s the list I came up with:

Coda’s strengths over Dreamweaver

  • Remembers which files were open from site to site, even after closing the app
  • Remembers and displays which files have been edited and need to be published
  • Can publish each file with a single click
  • DW sync takes *forever* – the 2 points above are the better solution
  • Subversion integration
  • Terminal integration (very cool)
  • Much more robust CSS editor
  • Much faster startup time (not bloated)
  • Image Previews (!)
  • Show change marks
  • split file editing (edit more than one file at a time, or reference the one while working on the other.)
  • Awesome visual representation of my Sites.

Dreamweaver’s strengths over Coda

  • WSYWIG / Split screen editor
  • common task dialogues
  • Find/replace is cleaner
  • Better and more helpful predictive code hints

At first, I’ll admit, I was still running over to Dreamweaver to accomplish certain things that, at the time, I didn’t realize Coda could do—or more importantly, I didn’t realize there was a better way to do it. For example, I’ve since learned to love Coda’s Find/Replace, it’s just a whole different paradigm.

I’m sure there are other things to add to this list, but it’s the list I sent my employer. I think it’s pretty obvious I felt that Coda had many more strengths. I’ve been using Coda pretty heavily now for several months and haven’t opened Dreamweaver for a very long time.

In a nutshell, I LOVE CODA! It’s the editor I’ve been holding out for. If you are a Mac user, head over and give it a whirl.

Posted by & filed under Developer Blog.

If you are using the instructions found on Bluehost’s Knowledgebase about How to host the Primary Domain from a subfolder for a wordpress site, you may notice that when you add wp-admin to the end of your URL it seems that can’t log in. The issue is that there are so much redirect magic going on, that the correct handling of redirecting /wp-admin without a slash to /wp-admin/ with a slash doesn’t happen correctly. You can fix this by either always typing the trailing slash, bookmarking it with the slash and not typing at all, or using the following addition to the bluehost .htaccess file they provide. Add it just below the line containing “RewriteEngine on”:

# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} ^.*/wp-admin$
RewriteRule ^(.+)$ /wp-admin/ [R=301,L]

Posted by & filed under Developer Blog.

There are several forum posts, articles, and help from bluehost attempting to explain how to get the default address on Bluehost to send to something besides user@*** when using CForms II plugin for WordPress. However, I had no success with following them. They all seem pretty out of date and are lacking in specific instructions. So, I’m not trying to beat a dead horse here, I’m just trying to sum up exactly what I did that gave me success (after 3 days of trying). My method focuses on using the php.ini approach. Further, I’m using an approach that allows a different email address to be specified for various multiple domains on the same Bluehost account.

    1. Using cPanel, go to PHP Configuration under the “software/services” section. There you will see 3 options: PHP5, PHP5 (Single php.ini), and PHP5 (FastCGI). If you are going to be using multiple domains in a single Bluehost account, make sure the first option is selected. If you are only using one domain on Bluehost or you want to use one setting to handle all of your domains, select the second option.
    2. In the same PHP Configuration panel, under the install default php.ini section, select to include IonCube & SourceGuardian
    3. Click on install php.ini master file. If the file already exists, it will give you an error. That’s fine, we can use the newly generated file or an existing file.
    4. Using either the file manager, your ftp program, or SSH, navigate to the root of public_html and make a copy of php.ini.default named php.ini
    5. If you selected the first option in #1 above, copy that php.ini file into the root of your cforms plugin directory. If you selected the second option, leave that file where it is.
    6. Edit the newly created php.ini file by doing a text search for sendmail_path and replacing the entire line with something similar to the following:
sendmail_path = /usr/sbin/sendmail -t -i -f '"User Frienldy Name" <>'

(note: you are allowed to use a Friendly Name, which isn’t something I could find in any other documentation. I was just experimenting and found out it worked for me.)

    1. Create a file named info.php and place it at the same directory as your php.ini file. In the info.php file, simply include the following php:
&lt;?php phpinfo(); ?&gt;
  1. View that page by visiting the correct path in your browser, whether it be or if it be
  2. Verify that the “Loaded Configuration File” option is showing the directory you placed your php.ini file in. If it shows /etc as part of your location, something is not right. Repeat steps 1-8 until that shows up.
  3. Also using cPanel, go into the Email Accounts settings under the “Mail” section. Add as a valid Bluehost email address.
    (note: this does NOT have to be, it can be anything as long as this matches what you placed in your php.ini file and you use the domain associated with Bluehost. Without this account, none of the settings above will work.)
  4. Test your CForm to make sure it gets emailed correctly.

That’s about it. I hope this helps you. If so, leave a comment below.

Posted by & filed under Developer Blog.

I found some instructions from J. Taylor on how to install SVN on Bluehost, but they were a bit out-dated. For one, Subversion is now an Apache project and isn’t found on anymore. You can find the project on Other than that, the instructions are great!

mkdir src
cd src
tar -xvjpf  subversion-1.6.15.tar.bz2
tar -xvjpf  subversion-deps-1.6.15.tar.bz2
cd subversion-1.6.15
./configure --prefix=$HOME --without-berkeley-db --with-ssl LDFLAGS="-L/lib64"
make install

Note: I did get one error during the make install process, but it didn’t seem to matter. SVN works great for me.

Posted by & filed under Developer Blog.

I want to set the record straight once and for all. The term “Cloud” refers to the internet. Cloud computing is using the internet to create, store and access information rather than desktop computing where you create, store and access information on your own machine. Here’s the proof.

The Cloud = The Internet

It is not some magical product that Microsoft has invented. Microsoft is using the term to make you think they are smart and innovative. They are using the term to make you think they have some new software that will do whatever you want it to do. When in fact, it is frankly false advertising. Microsoft hasn’t had an original idea, since…well, ever.

For example, that commercial where the lady fixes photos of her family and then posts it on Facebook:

The only “to the cloud” actually happening there is when she actually posts the photo to Facebook, a service that allows you to put your photos “in the cloud.” Microsoft is not offering any actual cloud based service in this commercial. It’s freaking ridiculous! Don’t believe me? Try to find a single reference to photo editing, photo sharing, or photo uploading on Microsofts own Cloud Page. If you find it, let me know in the comments below.

And the next time I suggest you use the cloud, please, for the sake of the children and for the love of all that is good in the world, do not respond by asking, “isn’t that some new Microsoft thing?”

No, it’s that old internet thing. But I’m not bitter or anything.