include_once(ABSPATH.'/wp-admin/includes/media.php');
	include_once(ABSPATH.'/wp-admin/includes/file.php');
	include_once(ABSPATH.'/wp-admin/includes/image.php');
	
//	$id is the id of the post being inserted
//	$name is actually the name of the form input that uploaded the file so WP can access it using $_FILE[$name]
	media_handle_upload($name,$id);

If you are inserting a new post, it makes sense to have the line $id = wp_insert_post($post_data); before this.

AJAX - it

I wanted to see how small you could make a fully functional AJAX script that worked cross-browser and degraded gracefully, so I went through an old custom AJAX script and made it as small as I possibly could. In the resulting AJAX scripts, the post version is 410 characters and the GET version is only 359 characters long. The scripts are fully functional and accept the following parameters: URL, DATA (in string form), and ELEMENT (to update).

The scripts could be a little smaller, but it would really kill readability.

“Get” AJAX Script

function a(l,d,u){
try{r = new XMLHttpRequest();}catch(e){try {r = new ActiveXObject('Msxml2.XMLHTTP');}catch(e){r = new ActiveXObject('Microsoft.XMLHTTP');}}
if(r){
r.onreadystatechange = function() {if (r.readyState == 4 && r.status == 200){document.getElementById(u).innerHTML = r.responseText;}}
r.open('GET', l+'?'+d, true);r.send(d);
}
}

“Post” AJAX Script

function b(l,d,u){
try{r = new XMLHttpRequest();} catch(e){try {r = new ActiveXObject('Msxml2.XMLHTTP');} catch(e){r = new ActiveXObject('Microsoft.XMLHTTP');}}
if(r){
r.onreadystatechange = function() {if (r.readyState == 4 && r.status == 200){document.getElementById(u).innerHTML=r.responseText;}}
r.open('POST', l, true);r.setRequestHeader('Content-type', 'application/x-www-form-urlencoded');r.send(d);
}
}

Combined AJAX Script

This combined script also accepts a fourth parameter ‘p’ that should evaluate true if the data is to be sent by post.

function a(l,d,u,p){
try{r = new XMLHttpRequest();}catch(e){try {r = new ActiveXObject('Msxml2.XMLHTTP');}catch(e){r = new ActiveXObject('Microsoft.XMLHTTP');}}
if(r){
r.onreadystatechange = function() {if (r.readyState == 4 && r.status == 200){document.getElementById(u).innerHTML = r.responseText;}}
if(p){r.open('POST', l, true);r.setRequestHeader('Content-type', 'application/x-www-form-urlencoded');}else{r.open('GET', l+'?'+d, true);}
}
}

Demo: (Sorry but you will have to go to the full page so the JavaScript is loaded.)
Click here to see the POST HTML of the homepage
Click here to see the GET HTML of the homepage
(they are the same)

The first step is to add the following to your current theme’s index.php loop after the line that looks like <?php while (have_posts()) : the_post(); ?>, but before any other code.

<?php $cat_temp = cat_loop();?>
	<?php if($cat_temp && is_numeric($cat_temp)){?>
		<?php include('loops/cat_'.$cat_temp.'.php');?>
	<?php }else{ ?>

Then add } just before the line endwhile.

The next step is to add the following to your theme’s functions.php file (you may have to create a file with the same name):

function cat_loop(){
	global $blog_id,$post, $wp_version;
		if($wp_version >= 2.3){
			global $object_term_cache;
			$array = $object_term_cache[$blog_id][$post->ID]['category'];
		}else{
			global $category_cache;
			$array = $category_cache[$blog_id][$post->ID];
		}
		while (list($cat) = each($array)) {
			if(file_exists(dirname(__FILE__).'/loops/cat_'.$cat.'.php')){
				return $cat;
			}
		}
	}

This can be modified to look at author’s also. Now the only thing you have to do is to create a folder named “loops” in your theme’s folder, and then create a new file with a new “loop” — excluding the while and endwhile parts — and name it cat_xxx.php where xxx is the id of the category the loops is for.

This can be repeated for single.php, archive.php, or anywhere else a custom loop is useful. You can even use something similar for individual posts or pages.

A post may be in multiple categories, but it will only use the first custom template it finds, so make sure the post is in only one specially styled category at a time.

To fix this you need to create the file and make sure that MySQL has access to it. (All commands need to be run as root)

Create the directory (if it doesn’t already exist).

sudo mkdir /var/run/mysqld/

Create the file by “touching” it.

sudo touch /var/run/mysqld/mysqld.sock

Set the ownership of the mysqld.sock file and folder to mysql.

sudo chown -R mysql /var/run/mysqld/

You can then start MySQL and breath easier.

For the “core”: I needed it to be able to queue effects to run one after another, but still be able to run effects synchronously with their own queues. Setting up the effects should take no more than a few lines, and the library should be easy adapted to the website or app it is currently running on. The library must also be cross browser, run well on lower end computers, and very very small (the main reason for creating it was as a replacement in a project for people who didn’t want to use jQuery or Scriptaculous just for the effects.) The core should be able to do everything with only being told the element’s ID, whether we are showing or hiding it (if applicable), and the effect to use. An added “feature” I wanted was something that could be used to create a tutorial, so no features could be used that were too fancy.

For the effects: I needed each individual effect to take no more than a few lines of setup, processing and finishing, so the framework needed to control everything, but each effect should be able to set its own duration using the framerate set. It should also be extremely simple to add new effects to the library.

The results: A library that is only 8KB in size (without compression or comments) or 2.9KB with natural (not gZip) compression and no comments with 4 built-in effects. While I’ll admit that the syntax to call effects isn’t as “pretty” as some of the other libraries, it is very simple, and queuing is powerful and easy to set up. If you want to jump ahead and see the finished product go here

This is just a demonstration post. The actual code will be explained in the future.

To test the effects library click here

The that group of effects was done with the following code:
AOI_eff.start('test_1', {'mode': 'show', 'eff': 'Expand', 'queue': ['hide::test_1::Fade','show::test_2::ScrollLeft::450','hide::test_2::ScrollLeft::50','show::test_1::Fade::25']} );

Something a little more interesting: here or the same thing, but with opposite displays here or the same thing, but the effects depend on the display. here

The onClick commands for those effects are, respectively, as follows.

AOI_eff.start('test_3', {'mode': 'show', 'eff': 'Expand', 'delay': 75, 'queue': ['show::test_4::Fade','show::test_5::ScrollLeft','show::test_6::SlideUp::50']} ); AOI_eff.start('test_5', {'mode': 'show', 'eff': 'Expand', 'delay': 75, 'queue': ['show::test_3::Fade']} );
AOI_eff.start('test_3', {'mode': 'hide', 'eff': 'Expand', 'delay': 75, 'queue': ['hide::test_4::Fade','hide::test_5::ScrollLeft','hide::test_6::SlideUp::50']} ); AOI_eff.start('test_5', {'mode': 'hide', 'eff': 'Expand', 'delay': 75, 'queue': ['hide::test_3::Fade']} );
AOI_eff.start('test_3', {'eff': 'Expand', 'delay': 75, 'queue': ['::test_4::Fade','::test_5::ScrollLeft','::test_6::SlideUp::50']} ); AOI_eff.start('test_5', {'eff': 'Expand', 'delay': 75, 'queue': ['::test_3::Fade']} );

As you can see this is still a work in progress, but I think over time it will improve greatly.

function find_path($loc,$dir=0){
	for($i = 0; $i < 10; $i++){
		if($dir){
			if(is_dir($ladder.$loc)){
				return $ladder;
				break;
			}
		}elseif(is_file($ladder.$loc)){
			return $ladder;
			break;
		}
		$ladder .='../';
	}
}

This code is NOT user-input safe: any checks you do should be hard coded otherwise you might as well just give out your passwords.

Time passed. People began realizing that XHTML wasn’t the save all and be all that it was supposed to be: some popular browsers (cough: IE) couldn’t even properly render its content type of application/xhtml+xml, so developers were stuck calling it XHTML and pretending that it was truly XHTML+XML, but they were really just dishing out HTML that was properly formatted.

This is not to say that the “XHTML rush” ™ was bad or that it didn’t advance technologies and the semantic nature of programming: it, with the help of CSS, helped to banish the hack and slash methods that were intrinsic in the 1990′s because people started realizing what each tag really meant and peer pressure abounded. In the end, however, all it did was make people aware of the rules that were already there, and in the process forced users to break other rules.

Finally the stigma of using semantically-correct HTML, inside the industry, is wearing off (although outside of it XHTML is still a buzz-word) and developers are realizing that XHTML wasn’t really the thing to use—instead it was just a good, clean language to use when it was needed, and some are slowly trickling back to serving just plain-ol’ HTML— albeit it this time with clean markup and remembering the lessons XHTML taught us.

Well it is on the verge of happening again: X/HTML 5.0 and XHTML 2.0 are both in development, and they both are trying to make their own mark on the browser space, but in the process they are just going to cause more trouble because the last time the (X)/HTML wars began XHTML 1.0 was, on the surface, HTML 4.0 with a few more rules. However, this time they are trying to go in separate directions, and the problem is that they both are doing some things correctly. (If you haven’t been keeping up with developments and want to read a comparison on what is and is not being done correctly read xhtml.com’s X/HTML 5 Versus XHTML 2)

While the competition will be good, in some ways, and the professionals will reason out the best language to use and why, the fame wars are going to start up again, so be ready for it and get out your favorite fan-boy insults because only one language is going to survive.

This rant was brought to you by the letter X and the number 3. Oh and in case you are wondering, this site is perfectly valid XHTML using the XHTML 1.1 DTD being served as text/html with .html extension.

UPDATE `table` SET `field` = REPLACE(Field,'change_me','to_me');

Or specifically for the tags:

UPDATE `wp_tags` SET `tag` = REPLACE(tag,'_',' ');

WordPress looks first for special files and then defaults to the index.php file (as shown in this diagram). We can take advantage of this by using only an index.php file and then using conditionals to modify it. While it seems that this method would render the code less readable, it is actually far more readable, and far easier to modify.

Your theme should start off a header.php, footer.php, sidebar.php and an index.php. These files are the “code” files and are fairly self-explanatory, and at this point the only question should be whether you add just the header portion of the file to the header.php or everything including the calls to get_sidebar()—the same goes for the footer.php depending on your theme. This depends on how you use your them, if you plan to integrate it with bbPress and use the same header and sidebars, you should add everything before the normal loop to the header. However, we will focus on things outside of the header (this includes the navigation menus and such) and just focus on the_loop.

A “normal” index page looks a little like this. (Taken from the default WordPress theme.)

<?php get_header(); ?>

	<div id="content" class="narrowcolumn">

	<?php if (have_posts()) : ?>

		<?php while (have_posts()) : the_post(); ?>

			<div class="post" id="post-<?php the_ID(); ?>">
				<h2><a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title(); ?>"><?php the_title(); ?></a></h2>
				<small><?php the_time('F jS, Y') ?> <!-- by <?php the_author() ?> --></small>

				<div class="entry">
					<?php the_content('Read the rest of this entry &raquo;'); ?>
				</div>

				<p class="postmetadata">Posted in <?php the_category(', ') ?> | <?php edit_post_link('Edit', '', ' | '); ?>  <?php comments_popup_link('No Comments &#187;', '1 Comment &#187;', '% Comments &#187;'); ?></p>
			</div>

		<?php endwhile; ?>

		<div class="navigation">
			<div class="alignleft"><?php next_posts_link('&laquo; Previous Entries') ?></div>
			<div class="alignright"><?php previous_posts_link('Next Entries &raquo;') ?></div>
		</div>

	<?php else : ?>

		<h2 class="center">Not Found</h2>
		<p class="center">Sorry, but you are looking for something that isn't here.</p>
		<?php include (TEMPLATEPATH . "/searchform.php"); ?>

	<?php endif; ?>

	</div>

<?php get_sidebar(); ?>

<?php get_footer(); ?>

For most themes, the page and single pages look the same: the only part that really changes is the_loop itself, and even then the changes are usually minor, so if you want to change something outside the_loop, you have to change it in all files. However, by operating the majority of display elements out of the main files, we can make it infinitely extensible without overloading the end-user with large amounts of code to sort through.

The index.php file for the theme I use is very short and easily read.

<?php get_header(); ?>
	<div id="wrap">

		<div id="content">

			<?php if (have_posts()) : ?>

				<?php
					if(is_home()){

						include (TEMPLATEPATH . '/index-loop.php');

					}elseif(is_page() || is_single()){

						include (TEMPLATEPATH . '/single-loop.php');

					}else{

						include (TEMPLATEPATH . '/archive-loop.php');

					}
				?>

			<?php else :?>
				<h2 class="center">Not Found</h2>
				<?php include (TEMPLATEPATH . '/not-found.php');?>
			<?php endif; ?>

		</div>

		<?php get_sidebar(); ?>

	</div>

<?php get_footer(); ?>

If we break it down: it calls the header, adds the two structural divs, and checks to see if there are any posts (of any kind). If there are no posts it includes an error page before including the sidebar, closing the divs and calling the footer. This part of the page is fairly normal and is used in most themes—not only is it used in most themes, but most of the main files all have this same code–every single theme file calls the footer, sidebar and header, shows an error message if there are no posts to display. This is a lot of wasted space. If you suddenly want to change the name of something or move the sidebars, you have to change every file which is just pointless. The difference in my index.php file is that there isn’t a full loop. It checks if there are posts using have_posts(), but where you would normally see a loop it just has some conditional statements, and for each condition, a different loop is included.

Each of the loops is in a different included file. (The loops are shown below, but just notice the similarities and major differences.)

Index loop:

<?php while (have_posts()) : the_post(); ?>
		<h2 id="post-<?php the_ID(); ?>" class="b">
			<a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title(); ?>"><?php the_title(); ?> </a>
		</h2>

		<div class="main main_border">

			<small>
				Posted on <?php /*backslashes escape chars*/ the_time('l \t\h\e jS \o\f F, Y \a\t g:i a ') ?> in <?php the_category(', ') ?> <?php edit_post_link('Edit','-');?>
			</small>

				<?php the_content('Continue reading "'.the_title('', '', false).'"')?>

			<div class="small box">
				//Some comment and UTW stuff				
			</div>	
		</div>
<?php endwhile; ?>

<div class="main" style="width:99%;">
	<div class="main-nav-left" style="float:left;width:49%;"><?php posts_nav_link('','','&laquo; Previous Entries') ?></div>
	<div class="main-nav-right" style="float:right;width:49%; text-align:right;"><?php posts_nav_link('','Next Entries &raquo;','') ?></div>
</div>

single-loop.php (handles both singles and pages because there is only a tiny difference between the two)

<?php while (have_posts()) : the_post(); ?>

	<h2><?php the_title();?></h2>


	<small>
		<?php if(!is_page()){ /*Only difference between pages and singles*/?>

			Posted on <?php /*backslashes escape chars*/ the_time('l \t\h\e jS \o\f F, Y \a\t g:i a ') ?> <!-- by <?php the_author() ?> -->in <?php the_category(', ') ?> <?php edit_post_link('Edit','-');?>

		<?php }else{?>

			<?php edit_post_link('Edit','-');?>

		<?php } ?>
	</small>

	<div class="main">

		<?php the_content('Read the rest of this entry &raquo;'); ?>

		<?php wp_link_pages(); ?>

		<div class="small box">

			//some comment and UTW stuff

		</div>

		<?php posts_nav_link(' &#8212; ', __('&laquo; Previous Page'), __('Next Page &raquo;')); ?>

	</div>

<?php endwhile; ?>

And the archive-loop.php which handles categories, date archives, tags, searches etc.

<?php $post = $posts[0]; // Hack. Set $post so that the_date() works. ?>

	<?php /* If this is a category archive */ if (is_category()) { ?>

		<h2> Reading about <?php single_cat_title(); ?></h2>

 	<?php /* If this is a daily archive */ } elseif (is_day()) { ?>

		<h2>Archive for <?php the_time('F jS, Y'); ?></h2>

	<?php /* If this is a monthly archive */ } elseif (is_month()) { ?>

		<h2>Archive for <?php the_time('F, Y'); ?></h2>

	<?php /* If this is a yearly archive */ } elseif (is_year()) { ?>

		<h2>Archive for <?php the_time('Y'); ?></h2>

	<?php /* If this is a search */ } elseif (is_search()) { ?>

		<h2>The Search Results For "<?php echo $s;?>"</h2>

	<?php /* If this is an author archive */ } elseif (is_author()) { ?>

		<h2>Author Archive</h2>

	<?php /* If this is a paged archive */ } elseif (isset($_GET['paged']) && !empty($_GET['paged'])) { ?>

		<h2>Archives</h2>

	<?php } ?>


	<div class="main" style="width:99%;">
		<div class="main-nav-left" style="float:left;width:40%;"><?php previous_posts_link('&laquo; Previous Entries') ?></div>
		<div class="main-nav-right" style="float:right;width:40%; text-align:right;"><?php next_posts_link('Next Entries &raquo;') ?></div>
	</div>


	<?php while (have_posts()) : the_post(); ?>

	<h3 class="b"><a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link a <?php the_title(); ?>"><?php the_title(); ?></a></h3>

	<div class="main main_border <?php echo anth::styles();?>">

		<small>
			<!-- Posted <?php the_time('j F Y') ?>  by <?php the_author() ?> -->
			<?php if(function_exists('UTW_ShowTagsForCurrentPost')){?>
				<span class="utwtags">Keywords: <?php UTW_ShowTagsForCurrentPost("commalist") ?></span>
			<?php } ?>
			<?php edit_post_link('Edit','-');?>
		</small>

			<?php the_excerpt() ?>

	</div>

<?php endwhile; ?>

<br/>

	<div class="main" style="width:99%;">
		<div class="main-nav-left" style="float:left;width:40%;"><?php previous_posts_link('&laquo; Previous Entries') ?></div>
		<div class="main-nav-right" style="float:right;width:40%; text-align:right;"><?php next_posts_link('Next Entries &raquo;') ?></div>
	</div>

The actual loops in each of these files starts with <?php while (have_posts()) : the_post(); ?>, and you will notice that all the loops are similar with only a few cosmetic changes, the major difference is in the archive page which uses a large conditional block to set the title text, but this could have been done on the index.php page and used a completely different loop if you needed it.

Okay, so you get down to here and wonder why you haven’t heard anything new. well once we start using custom loops the possibilities are endless.

For example, as I posted about recently, on my index I use a special loop for items that are in the Asides category, but only on the index page, so inside of my is_home) conditional statement I also add the code:

<?php $in_cat = cat_loop();?>
	<?php if($in_cat){?>
		<?php include('cat_'.$in_cat.'.php');?>
	<?php } ?>

Which calls the function: (added to the functions.php file)

function cat_loop(){
	global $blog_id,$post, $wp_version;
		if($wp_version >= 2.3){
			global $object_term_cache;
			$array = $object_term_cache[$blog_id][$post->ID]['category'];
		}else{
			global $category_cache;
			$array = $category_cache[$blog_id][$post->ID];
		}
		while (list($cat) = each($array)) {
			if(file_exists(dirname(__FILE__).'/cat_'.$cat.'.php')){
				return $cat;
			}
		}
	}

Basically the function loops through all the categories a post is in and if there is a custom loop for a category it uses it. This can easily be extended for author ids, name or anything else that you can test.

Let’s review: use as little repeated code as possible because when you do lots of tricks are available to you.

Some things the remember: all lists are block level elements which means they can contain almost any other element and still retain validity.

Definition lists

Definition lists do not seem to be the appropriate element because a comment is not strictly a definition, however, if you take the W3C’s name for the dd element, (definition description) it appears that it could also be used for comment lists. Structurally, however, the definition list fits perfectly with the standard comment.