<?php if (have_posts()) : while (have_posts()) : the_post();?>
   <div id="post-<?php the_ID(); ?>" <?php $even_odd = (++$j % 2 == 0) ? 'even-post' : 'odd-post'; post_class( $even_odd ); ?>
      <p><?php the_excerpt(); ?><>
   </div>
<?php endwhile; endif; ?>

Then in your CSS:

.odd-post {
	clear: both;
}

The following commands are basically notes to myself. I’m frustrated by the abundance of Git tutorials that speak in tongues.  I’m your average Web Developer with some PHP and CSS knowledge. I use these commands to manage a few repositories on GitHub.com. It’s taken me months to learn what you are about to read; so here you go – in plain English!

 *I assume you have already have both an account at GitHub.com and GIT installed. I am by no means an expert!*

Git BASH

BASH is the CLI (Command Line Interface) to manage your repositories on GitHub.

1) Navigate to the directory you wish to work in

cd the-directory/to-the/repo/

2) Initialize Git

This tells the program to monitor your folder

git init

3) Check file status

This will list files that were modified since the last commit.

git status -s

4) Add files to the upload queue

You have to do this one-by-one.

git add <filename>

You can also add an entire directory:

git add .

5) Commit

Commit takes a snapshot of all files. Any changes you make afterwards, will be noted next time you run status -s.

git commit -m 'enter release notes here'

6) Push (upload) files to your GitHub.com repository

git push -u origin master

or

git push

Git-GUI

Prefer to point and click? Download MsysGit. It will install both a CLI and GUI version of GIT.

1. Open Git-GUI
2. Select the directory of your repo
3. Edit your files…and when your ready to upload
4. Click “Rescan”
5. Click “Stage Changed”
6. Enter a Commit Message
7. Click “Push”

Other Git Stuff

Dealing with errors

When Git tells you it failed to push some refs, do:

git pull origin master

Now repeat steps 1-6.

Global Setup

If you’re setting up a new repository, you should follow the instructions here: Set Up at GitHub

 git config --global user.name "YOUR-GITHUB-USERNAME"
 git config --global user.email YOU@YOUR-EMAIL.COM

Next steps:

 mkdir NAME-OF-REPOSITORY
 cd NAME-OF-REPOSITORY
 git init
 touch README
 git add README
 git commit -m 'first commit'
 git remote add origin git@github.com:YOUR-GITHUB-USERNAME/YOUR-REPOSITORY-NAME.git
 git push -u origin master

Existing Git Repo?

 cd existing_git_repo
 git remote add origin git@github.com:YOUR-GITHUB-USERNAME/YOUR-REPOSITORY-NAME.git
 git push -u origin master

Further reading

• Git Cheat Sheet
• Git Reference
• Tortoise Client (Windows)
• MsysGit Client (Windows)
• Git-Tower (Mac)

Install GIT CLI on Ubuntu

sudo apt-get install git-core

Install a Git-GUI client (pick one)

sudo apt-get install gitk giggle git-cola git-gui gitg

The following will add the Facebook, Twitter, Google Plus, Pinterest, StumbleUpon, and LinkedIn horizontal icons above each post.

Step 1) Open functions.php and paste this:

add_action( 'genesis_before_post_content', 'child_social_media_icons', 5 );
/**
 * Social Media Icons
 *
 * @author Greg Rickaby
 * @since 1.0.0
 */
function child_social_media_icons() {
	if ( is_single() ) { ?>

	<div id="social-media-icons">
		<div class="facebook-button">
		<div class="fb-like" data-send="false" data-layout="button_count" data-width="100" data-show-faces="false"></div>
		<div id="fb-root"></div>
			<script>
				(function(d, s, id) {
					var js, fjs = d.getElementsByTagName(s)[0];
					if (d.getElementById(id)) return;
					js = d.createElement(s); js.id = id;
					js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=134944943249381";
					fjs.parentNode.insertBefore(js, fjs);
				}(document, 'script', 'facebook-jssdk'));
			</script>
		</div>

		<div class="twitter-button">
			<a href="https://twitter.com/share" class="twitter-share-button" data-url="<?php the_permalink(); ?>" data-text="<?php the_title(); ?>" data-via="YOUR-TWITTER-USERNAME">Tweet</a><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
		</div>

		<div class="gplus-button">
		<g:plusone size="medium" href="<?php the_permalink(); ?>"></g:plusone>
			<script type="text/javascript">
				(function() {
					var po = document.createElement('script'); po.type = 'text/javascript'; po.async = true;
					po.src = 'https://apis.google.com/js/plusone.js';
					var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s);
 				})();
			</script>
		</div>

		<div class="pinterest-button">
			<a href="http://pinterest.com/pin/create/button/?url=<?php the_permalink(); ?>&media=<?php echo genesis_get_image( array( 'format' => 'url' ) ); ?>" class="pin-it-button" count-layout="horizontal">Pin It</a><script type="text/javascript" src="http://assets.pinterest.com/js/pinit.js"></script>
		</div>

		<div class="stumbleupon-button">
			<su:badge layout="1"></su:badge>
				<script type="text/javascript">
					(function() {
						var li = document.createElement('script'); li.type = 'text/javascript'; li.async = true;
						li.src = window.location.protocol + '//platform.stumbleupon.com/1/widgets.js';
						var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(li, s);
					})();
				</script>
		</div>

		<div class="linkedin-button">
			<script src="http://platform.linkedin.com/in.js" type="text/javascript"> </script>
			<script type="IN/Share" data-url="<?php the_permalink(); ?>" data-counter="right"> </script>
		</div>
	</div>

<?php } }

Note: If you want to move the icons underneath a post, change:

add_action( 'genesis_before_post_content', 'child_social_media_icons', 5 );

to this:

add_action( 'genesis_after_post_content', 'child_social_media_icons', 5 );

If you want the icons to appear on both posts AND pages (but not the homepage) change:

if ( is_single() ) { ?>

to this:

if ( !is_front_page() ) { ?>

Step 2) Open style.css and paste this:

/* Social Media Icons
------------------------------------------------------------ */

#social-media-icons {
	display: block;
	height: 30px;
	width: 100%;
	margin: 0 0 10px 0;
	padding: 0;
}

.facebook-button {
	float: left;
	width: 90px;
}

.twitter-button {
	float: left;
}

.gplus-button {
	float: left;
}

.pinterest-button {
	float: left;
	width: 70px;
}

.stumbleupon-button {
	float: left;
	width: 100px;
}

.linkedin-button {
	float: left;
}

Last Update: 2012-04-16 – Add width: 90px; to Facebook button.

No need to install a plug in to display and highlight code in WordPress. Although some plug ins offer added functionality (like one click copy/paste), at the end of the day – you’re installing yet another plug in for something you can do with a few lines of CSS.

Step 1) Insert the following into style.css / custom.css

/* Code
------------------------------------------------------------ */

pre {
	background-color: #dbdbdb;
	font-family: "Consolas", "Bitstream Vera Sans Mono", "Courier New", Courier, monospace !important;
	font-size: 13px !important;
	font-weight: normal !important;
	font-style: normal !important;
	text-align: left !important;
	line-height: 20px !important;
	border-left: 3px solid #75DB75;
	padding: 10px;
	margin: 0 0 15px 0;
	overflow: auto;
}

pre::selection {
	background-color: #3399ff;
}

code {
	background-color: #FFFF9E;
}

• pre creates the “Code Box” by adding gray background, changing the font to something “code-like”, adding a border to the left side of the snippet box; and if your code is too wide for your margins, it will automatically create a scroll bar (like the above code box).
• pre::selection will cause browsers change the background color of items people highlight with their mouse.
• code will allow you to use the <code></code> HTML tag to "highlight" words (or code snippets) in sentences.

Step 2) When writing code, use the HTML editor (not Visual) and wrap your code snippet with a <pre></pre> tag:

<pre><?php some_function(); ></pre>

Step 3) When coding inside the <pre> tags, use the Less Than and Greater Than HTML Entities to start and finish HTML tags. The above code would look like this in the HTML editor:

<pre>&lt;?php some_function(); &gt;</pre>

That’s it!

Other options

• Github:Gist has an embed feature. You could copy and paste it into the HTML editor.
• Pastebin.com also has an embed feature. Both are free.

From Amazon:

We are excited to announce that we have reduced the Amazon S3 standard storage prices in all regions. With this price change, all Amazon S3 standard storage customers will see a reduction in their storage costs. For instance, if you store 50 TB of data on average, you’ll see a 12% reduction in costs. If you store 500 TB of data on average, you’ll see a 13.5% reduction in costs.

The price reduction applies to all of your standard storage- both existing storage and all new storage you add. Here is a summary of price changes for the US Standard region:

First 1TB – $0.140 -> $0.125

Next 49TB – $0.125->$0.110

Next 450TB – $0.110->$0.095

Next 500TB – $0.095->$0.090

Next 4000TB – $0.080 $0.080 (no change)

Over 5000TB – $0.055 $0.055 (no change)

The new lower prices for all regions can be found on the Amazon S3 Detail Page. New prices are effective February 1st.

I’m a 15 year radio veteran. I’ve seen the debate between high-end and low-end microphones both in-person and on message boards. Usually, the argument ends with snide comment like: “The Behringer is crap because it’s only $98 dollars!”… That’s not very scientific, so I wanted to study this on a technical level.

In my office is a Behringer B-1. I purchased it new in 2001 from zzounds.com. It’s widely known as a cheap, yet rugged starter microphone. I’ve use it to voice-track, cut voice-overs, and mic live instruments (the coolest being a 100 year-old cello). It’s a tough microphone. The kind of microphone you can toss into the backseat on the way to a gig and not think twice.

The Neumann TLM 103 is known as a high-end, yet affordable option for voice-over professionals. The Neumann name is known throughout the recording industry as THE microphone for vocals. It’s truly the Cadillac! There are three TLM 103′s in the building, one in each production room. Many of our DJ’s have them in their home studios too. Note: most radio stations wouldn’t dare spend $1,200 on a production room microphone.

What you’re about to see (and hear) is me talking into both microphones – unedited. To prove that I’m not swapping voice processors, you’ll even hear me changing out the microphones. (note: never unplug microphones before turning off the phantom power!)

I personally have no stake in the argument, I’m an engineer. I simply wanted to introduce a more technical point-of-view.

Technical Specifications

Behringer B-1

• Type: Condenser
• Frequency Response: 20 Hz – 20 kHz
• Pickup Pattern: Cardioid
• Diaphragm: 1-inch pressure-gradient transducer capsule
• Power: 48v Phantom
• Construction: Ultra low-noise transformerless circuitry
• Price $98.00 USD
• Website: http://www.behringer.com/EN/Products/B-1.aspx

Neumann TLM 103

• Type: Condenser
• Frequency Response: 20 Hz – 20 kHz
• Pickup Pattern: Cardioid
• Diaphragm: 1-inch pressure-gradient transducer capsule
• Power: 48v Phantom
• Construction: Ultra low-noise transformerless circuitry
• Price: $1,200 USD
• Website: http://www.neumann.com/?lang=en&id=current_microphones&cid=tlm103_description

I grabbed these specifications from each respective website. I’m not going to dive into exactly how they are made, or the quality of materials used…but on paper they should sound almost identical.

Test 1: Basic Home Studio

With this test, I’m recreating a (very) basic home studio. There’s no audio board, just the voice processor plugged into “Line-In” on the motherboard sound card. For both tests, the B-1 is set to “flat” as there is no low-frequency roll-off option on the TLM 103.

Equipment:

• Symetrix 528e Voice Processor
• On-Board High Definition Audio Card (Dell Optiplex 360)

Adobe Audition Screen-shot:

Average Frequency Response:

Behringer B-1

Neumann TLM 103

Test 2: Production Room

Now, let’s move into a real-live-working production room at a radio station. This room is “Prod 3″. It is used daily to voice-track shows and cut commercials. It features a flat-response 12-channel mixer, and a professional grade sound card – oh, and lots of foam on the walls.

Note: I used the same exact Voice Processor in each test. 

Equipment:

• Symetrix 528e Voice Processor
• Broadcast Tools ProMix 12
• Audio Science 4344 Sound Card

Adobe Audition Screen-shot:

Average Frequency Response: 

Behringer B1

Neumann TLM 103

Sound Check

• Listen: B1 vs TLM 103 – Home Studio (320kbps .mp3 – unedited)
• Listen: B1 vs TLM 103 – Production Room (320kbps .mp3 – unedited)

Conclusion

It’s obvious the production room environment sounds better. That has nothing to do with the board, and everything to do with the professional sound card.

IMHO: The B-1 sounds brighter and a bit “punchy”, while the TLM 103 sounds warm and more “mellow”. Overall, they’re not that far apart. (Really) That’s no surprise since their specifications and frequency responses are identical.

How? Quality of materials and parts used in construction.

What does that mean? Nothing. A Top-40 DJ might want to sound punchy, while a soft-rock DJ will want to sound warmer. Do you want to flaunt the name “Neumann” to owners of B-1′s on messages boards? Or do you want to have a fantastic sounding microphone for less than $100? In the end, it’s all about your budget and application.

A co-worker of mine, John Garrett, does voice-overs for a living. He started out with a Behringer B-1. He jokes all the time about how that “starter microphone” made him a living for a few years. (Last year he purchased a TLM 103).

My advice (and John Garrett’s) to up-and-coming voice-over artists is: Don’t worry about the microphone as much as the gear surrounding it.

• Buy a high-quality USB sound card. A Tascam US-144MKII or an M-Audio Fast Track. These will make your audio sound better – long before you hook-up the microphone
• Buy an industry standard voice processor like the Symetrix 528e. Adjust it to fit YOUR voice.
• Use sound dampening foam in your studio/room

When you’re both successful and have some extra cash, then take the leap and get the TLM 103. Just don’t expect gigs to flood in because you own a $1,200 microphone.

I’m told he smokes Marlboro Reds.

It’s a bit nerve racking, since the learning curve is so high. It’s all worth it when you see stats like this, and anyone familiar with configuring APC + PHP + W3 Total Cache will appreciate  this graph:

 (hint: there’s almost no fragmentation)

Update: Some of you have asked to see my setup and PHP configuration.

Amazon Large Instance

• Operating system – Ubuntu Linux 11.10
• Kernel - Linux 3.0.0-14-virtual on x86_64
• Processor - Intel(R) Xeon(R) CPU E5507 @ 2.27GHz, 2 cores
• RAM - 7.29 GB total
• Disk - 1.80 TB total
• Apache - 2.2.20
• PHP - 5.3.6
• APC – 3.1.9

My php.ini configuration

[APC]
apc.enabled = 1
apc.shm_segments = 1
apc.shm_size = 512M
apc.num_files_hint = 1000
apc.user_entries_hint = 4096
apc.ttl = 0
apc.user_ttl = 0
apc.gc_ttl = 3600
apc.cache_by_default = 1
apc.filters = "apc\.php$"
apc.mmap_file_mask = "/tmp/apc.XXXXXX"
apc.slam_defense = 0
apc.file_update_protection = 2
apc.enable_cli = 0
apc.max_file_size = 10M
apc.use_request_time = 1
apc.stat = 1
apc.write_lock = 1
apc.report_autofilter = 0
apc.include_once_override = 0
apc.localcache = 0
apc.localcache.size = 256M
apc.coredump_unmap = 0
apc.stat_ctime = 0
apc.canonicalize = 1
apc.lazy_functions = 0
apc.lazy_classes = 0

While this configuration works great for me, keep in mind, that my apc.shm_size is set to 512M because my server has almost 8GB of RAM.

Then removed over 41GB of crap!

(If you use a PC, you should run CCleaner at least twice a month.)

After updating all the browsers, plugins, and removed a bunch of malware…this rig is running great.

Turned out to be a jQuery conflict…but it’s an easy fix.

If you’re enqueing scripts with functions.php (or custom_functions.php) and using wp_print_scripts, then you’re doing it wrong. The folks at WordPress have officially stated that the preferred way to load scripts is by using: wp_enqeue_scripts.

If you see this inside functions.php, then this is the problem:

add_action( 'wp_print_scripts', 'load_my_scripts' );

One of your plug-ins could also be loading scripts using wp_print_scripts. If you’ve checked your functions.php and don’t see wp_print_scripts, then try disabling your plug-ins one-by-one until you media uploader works again. Then, report the erroneous plug-in to it’s author so he/she can make an adjustment.

Bottom line: The preferred method is, wp_enqueue_scripts:

//** Script Managment **//
add_action( 'wp_enqueue_scripts', 'load_my_scripts' );
function load_my_scripts() {
	  wp_deregister_script( 'jquery' );
	  wp_deregister_script( 'jquery-ui' );
	  wp_register_script( 'jquery', 'http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js' );
	  wp_register_script( 'jquery-ui', 'http://ajax.googleapis.com/ajax/libs/jqueryui/1.8.16/jquery-ui.min.js' );
	  wp_enqueue_script( 'jquery', 'http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js', array( 'jquery' ), '4.0', false );
	  wp_enqueue_script( 'jquery-ui', 'http://ajax.googleapis.com/ajax/libs/jqueryui/1.8.16/jquery-ui.min.js', array( 'jquery' ), '1.8.16' );
}