Big thanks to Danny Mustafic for recording the presentation (which should be available here in a few days) and to Chris Spruck and Kevin Roberts for putting the event together.

Form validation demo

Pagination demo

Bookmark It

Hide Sites

Lasmus Rerdorf was quoted saying “What do you expect? With the upcoming release of Facebook’s R&B PHP there’s no way we can compete; PHP cannot continue to exist in its current form.”

Unsurprisingly, the community received the news with anger. In an unprecedented show of solidarity and unity, Ruby and Python developers joined forces with PHP enthusiats and flooded the streets of major cities worldwide under the slogan “We are all PHP.” Still, not everyone is in agreement. One very well known community leader that asked to remain anonymous said “It’s time to turn this over to a handful of engineers that can do the right thing, the community has ran its course.”

It seems that the only way of avoiding the fees is renaming any publicly accessible .php files as .rff (royalty free file), yet it hasn’t been fully tested against Løøf Lirpa’s fee-collection script. Alternatively developers can opt to downgrade to PHP 3 or earlier as it will remain open source for the foreseeable future.

Bookmark It

Hide Sites

We’ll do a quick walk-through to get started with error logging.

Prepare php.ini

There are a few options that need to be set in php.ini to make proper logging possible. If you don’t have access to php.ini you can attempt to set the options at runtime (your mileage may vary.) An alternative to using php.ini is setting directives in an .htaccess file, but I won’t be discussing it in this post.

error_reporting  =  E_ALL
display_errors = Off
log_errors = On
error_log = /file/writeable/by/web/server/

Let’s look at this options a bit closer to understand what they do. error_reporting can take a number or different settings that grant an entire discussion all their own. I like using E_ALL which can be a little chatty at times, but can help to write better code. With PHP 5 E_STRICT has also been included, and has to be declared explicitly (not included in E_ALL.) This setting doesn’t provide additional logging, but gives recommendations to write even cleaner code.

display_errors is usually turned on during development, and turned off when going into production. If you are using logging, you’ll soon realize that it’s not necessary to turn this on at all.

log_errors is almost self explanatory, but could cause a newcomer to wonder why log files aren’t being written. This is the first place you should look if you aren’t getting logging information.

error_log has to be set to the path of a file writable by the web server; this is the second place you should look if your logs aren’t working. File ownership and permissions aren’t as daunting as they seem and you’ll be doing yourself a huge favor by learning how to apply them properly. If log_errors isn’t turned on, then this setting will have no effect whatsoever.

Set Up Your Box

This is where the rubber meets the road. Once you have all your settings in place and you’ve verified that errors are written to the log, it’s time to start using it. Open a terminal (command line as some folks call it) and give it the following command:

tail -f /log/file

The tail command retrieves the last 10 lines of a given file, the -f switch tells it to do it in real time. That is to say, that the display will be updated each time there’s a new entry in the log as opposed to having to run the command each time you want to see what’s going on. Leave this terminal running at all times and make it the first thing you glance at when something isn’t working right.

Talk To The Log, It Listens

So far you are able to view errors generated by PHP which is incedibly useful, but how about sending your own messages to the log? Enter error_log. This function allows you (in its simplest form) to send a custom message to the log. Let’s see an example, enter the following bit of code in a file and access it with your browser.

<?php
if ( 1 > 0 )
{
    error_log('it would be weird to NOT get this message');
}
?>

Now the log in the terminal (that’s ALWAYS open) will display something like

[22-Mar-2010 06:54:05] it would be weird to NOT get this message

This function also provides several other options such as being able to send the message via e-mail, or to a TCP port. So you can imagine the possibilities for customizing responses to different situations are endless. Here’s a list of useful resources that will help you in your logging quests.

• error_log – Manual
• Errors and Logging Configuration Options – Manual
• php.ini Guide: Error Handling and Logging – Added Bytes
• tail () – Unix man pages (if you have *nix system available just type ‘man tail’ )

This post only covers the very basics of logging PHP, but it’s intended as a starting point. I’m very interested in learning how you use logging or what debugging techniques you’ve developed. Don’t be shy and leave a comment.

Bookmark It

Hide Sites

So what’s the solution? We will use a ‘hash’ to store password validation. Without getting scientific a hash is the result of a transformation applied to the password string. This transformation is very likely one of the better known cryptographic methods such as MD5 or SHA1.

Let’s see it in practical terms. The user provides a password of  ”abc123″ , once hashed with SHA1 it looks like 6367c48dd193d56ea7b0baad25b19455e529f5ee. A hexadecimal number 40 characters in length. The process of hashing is one way only, so it’s not possible (for regular folks) to guess the password by looking at the hash. Next time the user logs in, the system will hash the password entered and compare it to the stored hash to validate the credentials.

So far so good, except that “abc123″ is a fairly easily guessable password, and it would probably be included in a dictionary based attack using rainbow tables. A rainbow table is a lookup table containing hashes based on a dictionary of possible passwords; “password”, “Password”, “root”, etc. would be the kind of passwords that you might find in said tables, and of course “abc123″ would make the list as well. So, in this case even though it’s harder to do, it’s still possible to reveal the actual password from the hash. As usual, using had-to-guess passwords mitigates this risk.

The solution to this issue is to use a ‘salt’ which is a random value attached to the password. By appending the salt, the rainbow table becomes useless, as the number of possible combinations makes it nearly impossible to guess using this method.

Photo by PhyrePh0X

Let’s tie all the pieces. The user signs up and picks a password, we take the password salt it with a random value, hash it, then store the hash and the salt. In PHP it might look somewhat like this:

$password = 'password';

$salt = sha1(rand()); //According to PHP.net some systems such as Windows will use a max number of 32768 unless explicitly specified

$hash = sha1($salt.$password); //Hash the concatenated string of the password and the hashed random salt

//Store values

See the output of this example

Going back to the original example, you wouldn’t be a able to e-mail the exact password back to the forgetful user at this point, instead, send him a link to a password reset page where they can enter a new one, and you can store it in the form of a new hash.

As usual this is only a little something to get you started and not an in-depth production ready sample. Use common sense when dealing with security and user experience issues. It’s possible that you work in an industry that has certain requirements regarding storing passwords and such, make sure you always check what’s appropriate for the particular project you are working on.

Do you use any of these methods in your projects? What else do you do to ensure security and a good user experience?

Bookmark It

Hide Sites

I heard many arguments why some PHP folks don’t like WordPress and I’ve heard counter-arguments to those reasons; but I never quite got the essence of why WordPress doesn’t get the respect it deserves from a large part of the PHP community.

Let’s go down the checklist to clarify things a bit

Hater: WordPress security sucks!

Lover: The community does an awesome job at plugging holes quickly.

Hater: It’s PHP 4!

Lover: Yes, I concede on that one, but the more WP users and developers continue pushing for a full PHP 5 core the sooner we’ll get it (maybe. some day.)

Hater: It’s just for blogs!

Lover: That’s just dumb. How long has it been since you visited the intarwebs?

Hater: It’s a little toy for people that don’t know how to code.

Lover: It can be, but it can also help you create very powerful stuff. The tools are there for you to use, and they won’t get in the way if you don’t.

So you get the picture. There are valid arguments, but the truth is some PHP developers hate WordPress because it isn’t coded like the applications they are used to working on. As easy as it is to get started coding for WordPress, for someone that is used to building sites from scratch, or even using a framework, being subjected to ‘actions’, ‘filters’, ‘The Loop‘ and other WordPress idiosyncrasies causes some discomfort.

If you are the PHP developer I describe here, don’t get offended. Give WordPress a try. Don’t just install it, but actually get your hands dirty with a theme or plugin. It’s weird at first, but once you get past the initial annoyance you’ll find an extremely powerful platform that just might be the wrench you’re missing in your toolbox.

A great place to answer your questions is the Codex, but there are a million and one resources out there. If you are in the mood for reading a book I recommend the WordPress Bible by Aaron Brazell, truly an awesome resource (which you might just end up buying.)

Bookmark It

Hide Sites

First of all you’ll want to set up your Ping.fm service right to update the feeds of your choice, as well as create the necessary permissions to post to each service. Log in to your account and select Add More Networks; now make your selection.

Now that your account is set up you need to gather your api key and a user key. I found this point to be the most confusing of the entire set up. Apparently the user app key is no longer necessary, but I couldn’t find an explanation of what the new method is.

If you take a look in the footer there’s a ‘developers’ section that has all the information necessary to get the keys and such.

Now you can go ahead and send your updates from your web app.

<?php

 $api_key = ''; //Don't forget your keys
 $user_app_key = '';
 //$api_call = 'http://api.ping.fm/v1/system.services'; //Good test
 $api_call = 'http://api.ping.fm/v1/user.post';

 //I assume you are pulling this content from a database, a feed, or some other automated method. But it's not important for this example.
 $title = "Something really witty";
 $content = "Your awesome post";

 //Set up the connection and pass the options required by the API.
 $curl_conn = curl_init();
 curl_setopt($curl_conn, CURLOPT_URL, $api_call); //URL to connect to
 curl_setopt($curl_conn, CURLOPT_POST, 1); //Use POST
 curl_setopt($curl_conn, CURLOPT_HEADER,1); //Get the header. This is key to getting the response code!
 curl_setopt($curl_conn, CURLOPT_RETURNTRANSFER, 1); //Return the result as string.

 //Check out all the options in the Ping.fm documentation
 $options = array('api_key' => $api_key, 'user_app_key' => $user_app_key, 'post_method' => 'blog', 'title' => $title, 'body' => $content);
 curl_setopt($curl_conn, CURLOPT_POSTFIELDS, $options);
 $output = curl_exec($curl_conn);

 echo $output; //See what you get

 ?>

Here’s an example of posting to a Facebook page.

Bookmark It

Hide Sites

We will be using PHP and cURL to access the API. If you aren’t too familiar, please read this post.

Each heading is exactly what you will find in the Twitter API documentation, along with my own explanation and some examples.

200 OK: Success!

Let’s say I want to get a list of my followers, I can use the code example below, and if I get a 200 OK return code I know that my request has been successful.

//Create the connection handle

$curl_conn = curl_init();

//Set up the URL to query Twitter
$user_followers = "https://twitter.com/statuses/followers/nicdev.xml";

//Set cURL options

curl_setopt($curl_conn, CURLOPT_URL, $user_followers); //URL to connect to
curl_setopt($curl_conn, CURLOPT_GET, 1); //Use GET method
curl_setopt($curl_conn, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); //Use basic authentication
curl_setopt($curl_conn, CURLOPT_USERPWD, 'username:password'); //Set u/p
curl_setopt($curl_conn,CURLOPT_HEADER,1); //Get the header. This is key to getting the response code!<strong></strong>

curl_setopt($curl_conn, CURLOPT_RETURNTRANSFER, 1); //Return the result as string.

// Result from querying URL. Will parse as xml
$output = curl_exec($curl_conn);

// close cURL resource. It's like shutting down the water when you're brushing your teeth.
curl_close($curl_conn);

echo $output;

If you are following along you will now have a pretty messy screen full of information about your followers. The part of the response we are interested in, it’s in the first line.

HTTP/1.1 200 OK Date: Tue, 10 Nov 2009
13:51:56 GMT Server: hi X-RateLimit-Limit:
20000 X-Transaction: 1257861116-80037-4182
Status: 200 OK

The 200 OK code let’s us know it’s all good, and our request has been successfully processed.

304 Not Modified: There was no new data to return.

This one is a bit trickier. In short, a 304 code means that there is no new data to a request. I attempted to send the request repeatedly through a “for loop” but I got a 200 OK every time. I tried to search for bug reports so I could try to reproduce it, but no dice. Maybe they don’t really provide 304′s? If you know a way of getting it to reply 304, please comment.

400 Bad Request: The request was invalid.  An accompanying error message will explain why. This is the status code will be returned during rate limiting.

Well, Twitter imposes all sorts of limits on the amount of API calls you can make, and this is a good thing. The limits imposed are workable, and can be increased if you are a developer and ask nicely. The default limit is 150/hour on any given account, so it was easy to reproduce.

Change the script as follows, and refresh the page.

//Replace the line  $output = curl_exec($curl_conn); with the following block of code.

for($i = 0; $i < 160; $i++)
{
    $output = curl_exec($curl_conn);
    $output = substr($output, 0, 200);
    echo $output."<br />";
}

You will probably get a lot of 200 codes followed by 400′s.

HTTP/1.1 400 Bad Request Date: Tue, 10 Nov
2009 14:43:40 GMT Server: hi
X-RateLimit-Limit: 150 Status: 400 Bad
Request X-RateLimit-Remaining: 0
X-Runtime: 0.01104 Content-Type:
application/xml;

401 Not Authorized: Authentication credentials were missing or incorrect.

Does as it says, and there’s a great way of testing it out, the verify_credentials method. Simply pass it a bad username and password and you’ll have a 401 error to call your own.

//Change this part in the original script.

//Set up the URL to query Twitter

$user_followers = "http://twitter.com/account/verify_credentials.xml";

//Don't forget to change the credentials to something invalid

Here’s the result

HTTP/1.1 401 Unauthorized Date: Tue, 10 Nov
2009 15:16:24 GMT Server: hi Status: 401
Unauthorized

403 Forbidden: The request is understood, but it has been refused.  An accompanying error message will explain why. This code is used when requests are being denied due to update limits.

You simply tweet too much! Again, you hit a rate limit that is pretty forgiving for most people. The following piece of code will actually post just one tweet to your account, which will most likely get a 200 OK code; I’m posting in in case you were looking for a short script to post updates to Twitter. The second one will actually try to post more messages than it’s allowed in order to purposely get a 403 code.

Please note that because Twitter checks you aren’t sending the exact same message repeatedly, I’m changing the text in every post.

One tweet:

//Create the connection handle

$curl_conn = curl_init();

//Set up the URL to query Twitter

$api_call = "http://twitter.com/statuses/update.xml";
$options = "status=This is a test status made with PHP"; //The actual message is a required parameter

//Set cURL options

curl_setopt($curl_conn, CURLOPT_URL, $api_call); //URL to connect to
curl_setopt($curl_conn, CURLOPT_POST, 1); //Use POST
curl_setopt($curl_conn, CURLOPT_POSTFIELDS, $options);
curl_setopt($curl_conn, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); //Use basic authentication
curl_setopt($curl_conn, CURLOPT_USERPWD, 'username:password..'); //Set u/p
curl_setopt($curl_conn, CURLOPT_HEADER,1); //Get the header. This is key to getting the response code!

curl_setopt($curl_conn, CURLOPT_RETURNTRANSFER, 1); //Return the result as string.

// Result from querying URL. Will parse as xml

$output = curl_exec($curl_conn);

echo $output;

// close cURL resource. It's like shutting down the water when you're brushing your teeth.
curl_close($curl_conn);

Many, many tweets.

//Create the connection handle

$curl_conn = curl_init();

//Set up the URL to query Twitter

$api_call = "http://twitter.com/statuses/update.xml";

//Set cURL options

curl_setopt($curl_conn, CURLOPT_URL, $api_call); //URL to connect to
curl_setopt($curl_conn, CURLOPT_POST, 1); //Use POST
curl_setopt($curl_conn, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); //Use basic authentication
curl_setopt($curl_conn, CURLOPT_USERPWD, 'username:password'); //Set u/p
curl_setopt($curl_conn, CURLOPT_HEADER,1); //Get the header. This is key to getting the response code!

curl_setopt($curl_conn, CURLOPT_RETURNTRANSFER, 1); //Return the result as string.

for($i=0;$i < 160;$i++)
{
    $options = "status=This is a test status made with PHP to reach a 403".md5($i); //Change the message on each iteration
    curl_setopt($curl_conn, CURLOPT_POSTFIELDS, $options);
    $output = curl_exec($curl_conn);
    $output = substr($output,0,200);
    echo $output;
}

// close cURL resource. It's like shutting down the water when you're brushing your teeth.
curl_close($curl_conn);

HTTP/1.1 403 Forbidden Date: Tue, 10 Nov
 2009 18:54:52 GMT Server: hi
X-Transaction: 1257879292-55915-20315
Status: 403 Forbidden
Last-Modified: Tue, 10..

In case you haven’t noticed this is spamming, and it uses a lot of resources unnecessarily, so don’t do it, please.

404 Not Found: The URI requested is invalid or the resource requested, such as a user, does not exist.

This one is very simple. You’re looking for something that’s just not there. To try it out, go to the original script and change the request to a user you know doesn’t exist. For example @nicdev1232342

$user_followers = "https://twitter.com/statuses/followers/nicdev1232342.xml";

HTTP/1.1 404 Not Found Date: Tue, 10 Nov
 2009 19:16:49 GMT Server: hi
X-RateLimit-Limit: 150 X-Transaction:
 1257880609-95984-9773 Status:
404 Not Found

406 Not Acceptable: Returned by the Search API when an invalid format is specified in the request.

Either the dpcumentation is wrong, or I’m too slow to understand. I tried making a request for followers using an non-existing format of .noformat, and all I got was a lousy 403. Again, if someone knows how to get this one to fire, please let me know and I’ll update the post.

$user_followers = "https://twitter.com/statuses/followers/nicdev.noformat";

I wanted a 406!

HTTP/1.1 403 Forbidden Date: Tue, 10
 Nov 2009 19:23:03 GMT Server: hi
 X-Transaction: 1257880983-50850-
1216 Status: 403 Forbidden

500 Internal Server Error: Something is broken.  Please post to the group so the Twitter team can investigate.

This one you can’t reproduce at will, but if you play with the Twitter API long enough you’re bound to run into it.

502 Bad Gateway: Twitter is down or being upgraded.

503 Service Unavailable: The Twitter servers are up, but overloaded with requests. Try again later. The search and trend methods use this to indicate when you are being rate limited.

The following script will run a search for the term “argentina” against the Twitter search API. Search limits are independent of other limits, and will return a 503 as opposed to a 403 when reaching the rate limit.

$curl_conn = curl_init();

//Set up the URL to query Twitter

$api_call = "http://search.twitter.com/search.json?&q=argentina";

//Set cURL options

curl_setopt($curl_conn, CURLOPT_URL, $api_call); //URL to connect to
curl_setopt($curl_conn, CURLOPT_GET, 1); //Use GET
curl_setopt($curl_conn, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); //Use basic authentication
curl_setopt($curl_conn, CURLOPT_USERPWD, 'username:password'); //Set u/p
curl_setopt($curl_conn, CURLOPT_HEADER,1); //Get the header. This is key to getting the response code!

curl_setopt($curl_conn, CURLOPT_RETURNTRANSFER, 1); //Return the result as string.

for($i=0;$i < 160;$i++)
{
    $output = curl_exec($curl_conn);
    $output = substr($output,0,200);
    echo $output."<br />";
}

// close cURL resource. It's like shutting down the water when you're brushing your teeth.
curl_close($curl_conn);

This one was a true surprise. While running the script that loops around 160 times I received many 200′s, followed by a 502 Bad Gateway, followed by a 503 Service Unavailable (what I was expecting), and then again by a bunch of 200′s. It seems to me that the rate limit on search is very forgiving.

HTTP/1.1 200 OK Date: Tue, 10 Nov 2009 19:49:38
HTTP/1.1 502 Bad Gateway Date: Tue, 10 Nov 2009 19:49:42

HTTP/1.0 503 Service Unavailable

HTTP/1.1 200 OK Date: Tue, 10 Nov 2009 19:50:01

I hope you enjoyed the post and that it’ll help you when writing applications for Twitter, or any other app that relies on response codes. To finish here are some great resources.

• Twitter API Documentation – Good docs and a great community built around it.
• Scripting Twitter With cURL – Tech@Sakana

Bookmark It

Hide Sites

If you also hate CAPTCHA but still want to avoid SPAM, here’s a trick that I learned from my buddy Reece. It’s extremely simple to implement, and works like a charm. All you have to do is create an input field that is invivisible to the user. When the form is submitted you can check for the value of that field, if it’s not empty, it’s more than likely a spambot.

Here’s a code sample to clarify.

The Form

<form action="process_form.php" method="post">
<ul>
	<li>Name:
<input name="name" type="text"> </li >
	<li>Last name:
<input name="last_name" type="text"> </li>
<ul>
<div style="visibility: hidden;"> <input name="bot_catcher" type="text" /> <div<
<input type="submit" value="Submit" /> <form>

The PHP

//I'm only showing how to look for the invisible field, not how to process the entire form

if($_POST['bot_catcher'] != '')

{

echo "No bots allowed"; //This is for illustration purposes,you're better off not giving any response

exit(); //Stop processing

}

Loved it, hated it? Please leave a comment to let me know.

Bookmark It

Hide Sites

I figured it couldn’t be that hard, but for some reason I was struggling to get AJAX to work like I wanted, and in talking to other developers I found out I wasn’t alone. For all of you that can relate to my story, here’s quick tutorial.

The Setup

We need a simple HTML page with a block element, with an id of  “element”. This page will also have the Jquery/Javascript needed to make the magic happen ( Usually you’d like to have most of your scripts in a separate file.) Later on we’ll add more to it, but this is all we need to get started.

<!-- import jQuery wherever it is, in this case it's the same dir -->

<script src="jquery.js" type="text/javascript"> >/script> <!-- This is the secret sauce --<
<script type="text/javascript">
    $(document).ready(function ()
    {
        $('#element').load('output.php');
    });
</script>
    >div id="element" >/div>

Let’s take a minute to explain the code above. First we need to import jQuery. Then we run our little script which says when the DOM is ready grab the output from output.php and attach it to #element (that is the div with id ‘element’.) The best part of the load function is that it expects a piece of HTML to attach to the given selector. It’s simple, rudimentary, and exactly what backend developers need.

Of course, we also need a very simple PHP script to give us the output we want to bring in via AJAX; I’ll name the file output.php. Again, we’ll add some complexity in latter examples.

<?php
echo "Hello AJAX";
?>

At first sight this example seems as if the “Hello Ajax!” message is just part of the page we’re viewing, so we’re going to modify the scripts a bit to show that is actually making a call to the script. Alternatively you can use the Firebug console to view the request and script information (highly recommended.)

Wait for me!

This time around, instead of making the request as soon as the DOM is ready, we’re going to do it at the push of a button.

<script src="jquery.js" type="text/javascript"></script> <!-- import jQuery wherever it is --> <!-- This is the secret sauce -->
<script type="text/javascript">
    $(document).ready(function ()
    {
        $("#btn").click(function ()
        {
            $("#element").load('output.php');
        });
    })
</script>
<div id="element"></div>
<input id="btn" type="submit" />

This time around we told the function to wait for the button with id of ‘btn’ to be clicked before fetching the output. We do so by using the click function of javascript. The same could be accomplished by adding onClick to the button in the HTML.

The Final Act

In the last example, I’ll show you how to combine the the power of jQuery and PHP to bring in real HTML to the page. Grab good ‘ole output.php and modify it as follows

//output.php

echo '<h1>Hello AJAX</h1>';
echo '<p>This is a paragraph right after the Hello Ajax title</p>';

When you click on the button now, you get properly formatted HTML. Yay AJAX!

Please keep in mind that there are much more advanced ways of doing this (witin and without jQuery) that allow for much more granular control, yet this is an extremely simple but powerful way to get some AJAX rolling.

Bookmark It

Hide Sites

This quick intro is intended to give you a taste of how it works, the different sections, and give you enough of a kickstart to allow you to discover on your own. We’ll walk through the interface, and try out a few practical examples to give you a taste of the bug. Best of all, you can do all of it while reading this post.

First of all you need to install it.

Open it with F12, or click on the little bug at the bottom right corner of the browser.

Select HTML from the top bar and hover over the different elements. Notice how they are highlighted as you move from one to the next.

Select the CSS (right next to HTML), you can double-click any entry to modify it, or right-click and select ‘edit’. For example, look for the a selector and change text-decoration :   none to underline and see all the links suddenly change. Also, note that it auto-completes the property (fancy).

Firebug DOM menu

The DOM section is very useful, but also complicated to navigate if you don’t know what you are looking for. We’ll look at more of the DOM later on.

The Net section is simply cool. It might be disabled when you first click on it, but it’ll give you the option to enable if that’s the case. The initial subsection is All which shows a graphical representation of the aggregate of time it took to download each element on the page. You can also view the other sub-sections for CSS, Javascript, etc. Click on ‘clear’ at the top left of the Firebug pane, then refresh the page and see the section populate in real time.

Let’s give a second look at the HTML section. Look at the HTML tree and open up to the entry <div class=”container”> (html -> body -> div).  On the right pane you can see the CSS styles affecting the page, under Laytout there’s an on-the-fly box model (awesome for troubleshooting margins, padding, etc.) In the DOM section you can check out the DOM properties for each particular element.

For exmaple, on the left side select the  <title>tag (html -> head -> title). In the right panel look for the text entry and double-click on it. Change the title to the one of your choice and see the page renamed.

Saving the best for last, try the following. Click on Console, at the very bottom you should have a prompt that looks like >>>. Right there type “alert(“Hello NicDev”);” without the quotes, and press enter. Your script has just been run, you can imagine how handy this is to try JS on the fly.

Well, there’s a whole lot more to Firebug than what we went over today, but hopefully you feel comfortable enough to go tackle some of those tutorials and start churning out some awesome sites.

Bookmark It

Hide Sites