I recently added live chat to my site in hopes of helping my readers and picking up more business. Adding live chat is easy when you use a service. I’m using Olark. They offer different plans, depending on your budget; I’m using their free version.

When implementing the code, I had a few different, easy to implement, options:

  1. Copy and paste the code, as is, without change (most slackers do it this way).
  2. Put the code in a theme function with a descriptive function name using the wp_footer hook.
  3. Put the code in a plugin, existing or new, using the wp_footer hook.

I’m sure the quickest and easiest way would have been to use option #1. It’s easy to implement and it takes 2 seconds. Right? Well, here’s my problem with that approach. You have ugly, loose code in your theme. That right there should scare you away from that approach; however, your average developer will do it this way. It’s sad, really. What you need to understand is that being a good developer does not necessarily imply that you’re the fastest. Remember the story about the tortoise and the hare? This approach is horrible. Having un-organized code just laying around is bad. What happens when you need to make changes? What happens when you forget what the hell that code is? Forgive my cursing, sometimes I forget where I am.

The second approach is better; however, what happens down the line when you need to change the theme and you want to keep live chat on your site? You’d have to move the code over to the new theme.


CONTINUE READING


Internet Explorer 8 was released March 19, 2009 and what an exciting browser it was supposed to be. It was going to be faster, allow you to browse privately, it was going to be be XHTML compliant, and it was going to be more secure. All those fun things, right? Sadly, IE8 was faster, had a private mode, it was XHMTL compliant, and more secure than the older IE browsers.

The Problem

You must be wondering what the problem is right? Well, there wasn’t really a problem with the browser. There was a problem with your code, wasn’t there? You coded around IE6 & IE7 bugs. You made your site look lovely in those 2 browsers, and now that IE8 is out, your site looks broken again, doesn’t it?

What are you supposed to do about it?

The Solution(s)


CONTINUE READING


10 Ways To Make Your XHTML Site Accessible Using Web Standards

In 2009, Smashing Magazine wrote up a great article about the 10 ways to improve the accessibility of your XHTML website by making it standards-compliant. A few of the things they touched up on were specifying the correct DOCTYPE, one thing we seems to ignore because most of the time our IDEs generate this for us; defining the namespace and the default language; supplying proper meta tags. They go ahead and list 10 of them.

Again, a great article. I like to brush up on the article every few months so I can save time in the long run.


CONTINUE READING


When I researched how to get pop ups to not be blocked using flash, in that research, I found out how to check and see if a popup was blocked or not. It’s such a simple solution I don’t know why I haven’t consciously noticed it before. I’ve created many popups in the past, just never thought about how I would check if a popup was blocked.

The Solution

Using JavaScript, put something like this in your code:

1
2
3
4
5
6
7
8
// this is sample code so replace
// wurl = the url you want opened
// wname = name given to the window so you can reference it again programmically
// wfeatures = optionally you can give it scroll bars, make it resizeable, etc.
var win = window.open(wurl, wname, wfeatures);
if(win == null || typeof(win) == "undefined" || win.location.href == 'about:blank') {
   alert("Please enabled popups for this site to continue.");  
}

That’s it! That’s all you need to do to test if someone has blocked your popup. Now you need to decide if it’s worth the hassle of working with popups and how to handle when a popup is blocked.

The three simple ways around using popups are:
CONTINUE READING


I’m always looking for economical ways of getting pretty visuals for my sites. Techradar put together a great list of sites that will help you into some nice visuals for you web sites.

Visit Source

20 Useful Desktop Blog Editors

Even though I prefer a web interface when blogging, I feel I should let you all know about a great article introducing 20 or so blogging tools. It’s really well written so I don’t feel the need to summarize. Check it out and enjoy!

Visit Source

In a perfect world this article would be King. But… you know…

Visit Source


TomatoCMS

Ladies and Gentleman, the moment you have all been waiting for – a new CMS to come into your life and confuse the shit out of you – TomatoCMS. Just when you thought there were enough CMS’ out there to choose from, a new one pops out and says “Hello World.”

All kidding aside, I’m actually quite intrigued by TomatoCMS. Now, I haven’t tested it out yet, but this CMS does sound promising. I know there are better ones out there that you might know about (Drupal), but you should still give this one a try. And here’s why.


CONTINUE READING