$valid = true; //innocent until proven guilty
$errors = array(); // errors array
$clean = array();

foreach($_POST as $key => $val)
{
	switch($key)
	{
		case 'first_name':
			// do validation
			if(validateString($val) == false)
			{
				$valid = false; // we're no longer valid.
				$errors[] = "You're missing your first name!"; // prime up an error message for our user
			}
			else
			{
				$clean[$key] = $val;
			}
			break;
		case 'last_name':
			// do validation
			break;
	}
}

if($valid == false)
{
	// show the form again, but with the error message
}
else
{
	// handle our clean array anyway we want (usually a DB insert)
}

?>

A: You're already off on the wrong foot. The reason? You're thinking you need a framework to get whatever you need done.

All too often I see posts on forums or on IRC: "What framework should I use for a large networking site, like MySpace?"

1) Comon, MySpace? Ugh.

2) If you have to ask, you're doing it wrong.

3) This question will spawn a thread of everyone promoting their own personal frameworks. E-Peen war ensues.

You're asking the wrong question. Some better questions might be:
"Is there a particular framework that out performs another?"
"How is performance gauged?"
"Does it allow Master to Slave databases?"
"Does it support Memcache?"
"What kind of templating system does it use?"
"What's the ease of development?"

As you drill further and further down into these questions, you're going to discover you will have to start making comprimises.

Some frameworks eat up less CPU, but does that mean it out performs?
For a large "networking site" you'll need hundreds of database servers, so really, does any framework handle that many "out of the box" ?
If you go, "Memcache - what's that?" - then you're already set up for fail. If you find a framework that does support clusters of MC servers, will it allow you to tailor it to your needs?
As far as templating systems go, generic Smarty won't cut it. You'll need to hack, strip and extend Smarty into all sorts of weird specific configurations for optimal performance.
Ease of development? Does it work well for you? How long will it take to hack your framework into a better performing set up? How much effort goes into training new devs on the project?

You're going to find yourself coming to a realization: You need to put in a lot of work.

Reaching out for a framework is a common misconception of Jr Developers. It's easy to grab for these frameworks beacuse you don't really understand what they do.

Don't get me wrong, some of the frameworks out there are great. And not every project requires custom built frameworks.

But there's two different leagues here. While you're playing in the minors - have fun with your frameworks, use Zend, CI, Symphony, what have you.

When it comes time to play in the big leagues, leave your AA and AAA crap at the door.

There's a difference between sites that serve 1 M Unique users a month, and those that serve over 10 M unique users a day, and that difference is not found in a box, or "off the shelve."

So here you go, my quick tip on what you really want to know about mod_rewrite.

If you want an actual explanation of what is going on here it's at the bottom.

Solution 1:

File: .htaccess

Options +FollowSymLinks
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.+) /index.php [L]

File: index.php

<?php
$urlArray = explode("/",$_SERVER['REQUEST_URI']);
array_shift($urlArray); // Gets rid of the blank first param.
?>


Now you have an array with all of your parts, and you can map them accordingly.

Solution 1.a (more elegant):
File: .htaccess

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

That version just checks to make sure the module is installed.

Solution 2:
If you have just a couple of pages that you want to look prettier:

File: .htaccess

Options +FollowSymLinks
RewriteEngine on
RewriteRule ^home$ index.php
RewriteRule ^about$ about.php

And you just keep adding RewriteRule's for each page. This is really only helpful when you just have a set of static looking pages for a site.

Explanation:

Options +FollowSymLinks

Tells Apache to follow sym links (usually on anyways...)

RewriteEngine on

Tells apache to turn on the RewriteEngine for this folder

RewriteCond %{REQUEST_FILENAME} !-f

Read this as: Condtion, If the file we're requesting is not a file...

RewriteCond %{REQUEST_FILENAME} !-d

Read this as: Condtion, If the file we're requesting is not a directory...

RewriteRule . /index.php [L]

Then Rewrite this url to index.php ([L] forces it to be the last redirect)

Too often I run into reviewing or helping a "professional" developer, and I can't help but mutter "you're doing it wrong..."

I feel the most important attribute that separates one developer from another is when they write for usability and maintainability.

So let's take a look at some extremely simple steps you can take to make your project's code more flexible.

1. For the love of all that there is, seperate your header and footer files. Yes, I'm still seeing this happen, often. All content that is above your generated page needs to go into a header file, and all the content below it into a footer file. So when you need to modify one line, you do it only once.

<?php
require_once(dirname(__FILE__).'/includes/header.php');
?>
<div id='content'>
<?php
	// script runs
?>
</div>
<?php
require_once(dirname(__FILE__).'/includes/footer.php');
?>

2. Create a function to generate your navigation. And when I say generate, I mean you give it some flexibility as well. This can be done even with the smallest of sites. Example:

<?php
$site_pages = array();
$site_pages[] = array('text' => 'home', 'link' => 'home.php');
$site_pages[] = array('text' => 'about', 'link' => 'about.php');
$site_pages[] = array('text' => 'partner', 'link' => 'http://www.example.domain.com/');

function buildNav($links)
{
	$output = '';
	foreach($links as $page)
	{
		$output .= "<a href=\"{$page['link']}\" title=\"{$page['text']}\">{$page['text']}</a>\n";
	}
 	return $output;
}
?>

The example above could easily be modified to allow optional values to the array, like 'enabled' => false to turn off a link. Or you could define a link "template", and use str_replace() to substitute values.

This means if you, or the customer (with any know how) can quickly update the links at any time. For more advanced sites/projects this can obviously become more complicated, but it saves even more time.

3. If you're not going to use OOP, at least use functions. Any common task or specific sequence should be placed in it's own function. An example would be our navigation function from #2. Another example would be running a query for a specific item. If you ever need to modify your table structure you'll regret having to hunt down all of your inline queries.

4. When you create 'admin' features, take the 5 minutes to create a function that actually checks if the person accessing that "super hidden" directory filled with scripts that just accept anything.

I've seen this happen even on large global community sites.

Some developers will stuff their admin scripts in a folder such as /admin/, and just assume that if data is posted there then it's ok.

The least you should do is place a session check, and place it in a function.

<?php
function isAdmin()
{
	if(!isset($_SESSION['user_name']) || !isset($_SESSION['user_id']))
	{
		return false;
	}
	else
	{
		$sql = "SELECT COUNT(*) as cnt FROM user_table WHERE user_id = ".intval($_SESSION['user_id']);
		// do the query, check it, etc.
		return true;
	}
}
?>

Then when it comes time to run your script, simply:

<?php
if(isAdmin() === false)
{
	die('Log back in');
}
?>

5. Create a wrapper for handling escape strings. If you're not using a database class (like PDO) to handle this, you'll need to do this.

Just assume that your client could have their PHP configuration change, or they change hosts, or any possible combination of changes take place.

Create a simple wrapper that will check of magic quotes, and escape for your database insert.

<?php
function cleanString($input)
{
	if(get_magic_quotes_gpc())
	{
		$input = stripslashes($input);
	}
	$output = mysql_real_escape_string(trim($input));

	return $output;
}
?>

6. Create a configuration file so you can update common yet critical variables. An example of this would be paths. Your system quickly gains adaptability if you just create a defines.php file, and place in there your simple variables.

The overall approach you should have to any project you take is that you should use an establish tool chain you have developed. It doesn't take much time or effort to create a simple set of classes that can handle just about any thing you need to create. If you wish to use functions, you can do the same. The idea is that you write once, and write it in such a manner that you can tweak it later on.

I find it interesting that someone could take the usage of CDN's as an act of an un neutral  web.

The act of handling certain traffic as more important than other traffic is the act of an un neutral web. Developers should consider these words carefully.

That's a thing of the past.

I'm super excited about this find. Maybe I'm the last to discover it, but it's just too awesome to pass up.

The project is called: PHP Simple HTML DOM Parser.

Literally, this takes almost all of the magic out of screen scraping. Here's an example from a quick and dirty login and grab my stats for ESEA.

require_once('simple_html_dom.php'); // get our class

define('COOKIE_JAR','./cookie/cookie'); // cookie jar for cURL
/**
* We need to set up our referrer and user agent, for cURL
**/
$referrer = "http://www.esportsea.com/";
$agent = "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4";
/**
* str = our direct link to our user page
**/
$str = "http://www.esportsea.com/users/<your user id>";
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL,$str);
curl_setopt($ch, CURLOPT_USERAGENT, $agent);
curl_setopt($ch, CURLOPT_REFERER, $referrer);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 0);
curl_setopt($ch, CURLOPT_COOKIEFILE, COOKIE_JAR);
curl_setopt($ch, CURLOPT_COOKIEJAR, COOKIE_JAR);
curl_setopt($ch, CURLOPT_TIMEOUT, '10');
$result = curl_exec ($ch);
curl_close ($ch);
// done with cURL
$html = new simple_html_dom(); // create our HTML object

$html->load($result);

$pug_stats = $html->find('#body-matches-pug table tr'); // load up pug stats

// this loops through each <tr>
$output = array();
foreach($pug_stats as $stat)
{
	$row['game'] 	= trim($stat->find('img',0)->title);
	$row['link'] 	= trim($stat->find('a',0)->href);
	$row['score']	= trim($stat->find('a',0)->plaintext);
	$row['srv'] 	= trim($stat->find('a',1)->href);
	$row['srv_txt'] = trim($stat->find('a',1)->plaintext);
	$output[] = $row;

}
echo "<pre>",print_r($output,true),"</pre>";
exit;

?>

And that's it.

Now take a look at that, and realize how much stuff I'm not forced to do.

I know this isn't some great new invention, loading the source into a DOM object and parsing it, but man, this almost eliminates the need to think about screen scraping entirely.

Enjoy.

I thought they were pretty interesting to watch, and it was nice to hear from MSN, Google, and Yahoo. It does make me wonder if black hat SEO really does have a chance?

Anyways, here are the direct links to the vids:

http://www.imbroadcast.com/video/53/Search-Engine-Spam-Part-1-Overview

http://www.imbroadcast.com/video/55/Search-Engine-Spam-Part-2-On-The-Page-Issues

http://www.imbroadcast.com/video/54/Search-Engine-Spam-Part-3-Link-Spam--Paid-Links

Hope you all enjoy.

I'm not really impressed.

I believe the beginner may benefit from this, but there's just so many gaping holes in the reference card... Like what about the GD library? Or perhaps cURL? File handling? XML?

Honestly, how could you call a reference card a PHP Reference Card without the most common uses listed? I think the card may be off to a good start, but please, release a new more complete version soon.

Final Verdict:

While it may be great for beginners, it's still lacking for the rest of us. I'll pass and keep php.net as my reference card.

Here's the basic idea.

You have your DOM, and with JavaScript, there are ways to manipulate nodes. Including adding new ones. When you want to add new elements to your DOM, you have to think about this in a few different steps.

First step, where am I placing this?
The reason for this is because you have to select an element to append your new element to. You can append it to the body, the head, or other element. So we start this off with the assumption that we have a div with the id of inner_content.

So we start out our JavaScript with:

var main_div = document.getElementById('inner_content');


Second step, what are we going to create?
Let's say we want to add another div with some text inside of it. So, we now create the new div, and append it to our main_div variable.

...
var new_div = document.createElement('div');
...


This div needs some attributes! So let's hop into that, the above snippet turns into:

...
var new_div = document.createElement('div');
new_div.setAttribute('id','sub_div');
new_div.setAttribute('class','mySubDivCssClass');
new_div.setAttribute('onclick','javaScriptFunction()');
...


Now we need to actually attach this item to our old div.

To do that we simply tell our main_div to append a child:

...
main_div.appendChild( new_div );
...


Now, say we want to add a text node... now that gets its own special tool.


var new_text = document.createTextNode('My New Text');


And now, just like before, we need to attach that to an item it belongs to.


new_div.appendChild( new_text );


Now, we end up with our code snippet looking something like this:


var main_div = document.getElementById('inner_content');
var new_div = document.createElement('div');
var new_text = document.createTextNode('My New Text');
// now set up our attributes
new_div.setAttribute('id','sub_div');
new_div.setAttribute('class','mySubDivCssClass');
new_div.setAttribute('onclick','javaScriptFunction()');
// now append the text to the new div
new_div.appendChild( new_text );
// now append our new div to our main div
main_div.appendChild( new_div );
// done.


And that's about as easy as it gets.

Hope this helps someone understand the order that is required when appending new children to the node list.

For more information:

http://www.w3schools.com/htmldom/
http://www.w3.org/TR/DOM-Level-2-HTML/
http://developer.mozilla.org/en/docs/Using_the_W3C_DOM_Level_1_Core

All too often I see on IRC & Forums people complaining/asking for help, regarding their mysql_query(). "It was working fine yesterday, now it''s broken." "Can someone tell me why this doesn''t work?" "Why doesn''t this work? It just doesn''t do anything."

People, you need to check for errors when you run a query. This is generally done like so:


$get = mysql_query($sql) or die (mysql_error());


Now, that in itself is rather simple to understand. If there are any error's with your query ($sql), your script will die() and tell you the error.

An even better implementation of this would be:


if(!$get = mysql_query($sql)) {
die("Get query evaluated to false. SQL : {$sql} MySQL Error: ".mysql_error());
}


Now, this is great for debugging purposes. It won't really fly on a live front end site. So you'd swap out the die() with:


if(!$get = mysql_query($sql)) {
error_log("Get query evaulted to false. SQL : {$sql} - MySQL Error: ".mysql_error());
} else {
/* Continue on with logic that relies upon this query */
}


Now, what happens is if your query failed, you will get an error_log message, and you do check your error logs? Right? Of course! I thought so.
Also, this ensures that only after we know our query was successful do we continue on with our logic that relies upon it.