Mike asked about adding the posts featured image (if available) in a column next to the title into core. And while that a great idea (and I think there is a trac ticket for that), I though it would be an easy plugin to create. So I started Sunday and finalized it some time this week when I got repository access and uploaded the first version.

So go grab it and let me know what you think.

The YouTube White Label Shortcode allows your to generate a shortcode with the proper inputs with the simple to use generator you’ll find in a metabox on your post and post edit screen. Grab the latest version here and let me know what you think.

After downloading plugin I noticed some of the scripts were not loading properly, so I quickly rewrote his plugin into a small class.

Super awesome!! That always bothered me. I don’t know why I didn’t think of this first.

You had some issues with it loading the proper files. So I quickly rewrote it for my own use, have a look and see if you’d like to apply the changes before you push to SVN.

My version – you still need his files

add_action( 'plugins_loaded', 'admin_bar_hover_activate' );

function admin_bar_hover_activate() {
	$hover = new Admin_Bar_Hover_Intent();
}

if ( !class_exists( 'Admin_Bar_Hover_Intent' ) ) {
    class Admin_Bar_Hover_Intent {

		const version	= '0.1';

		function Admin_Bar_Hover_Intent() {
			$this->__construct();
		}

		function __construct() {
			add_action( 'wp_print_scripts', array( __CLASS__ , 'enqueue_scripts' ) );
			add_action( 'init', array( __CLASS__ , 'enqueue_style' ) );
		}

		function enqueue_scripts() {
			if ( is_admin_bar_showing() ) {
				wp_enqueue_script( 'jquery' );
				wp_enqueue_script( 'hoverintent', esc_url( plugins_url( 'hoverintent.min.js', __FILE__ ) ), array( 'jquery' ), '1.0', true );
				wp_enqueue_script( 'rwi-adminbar-scripts', esc_url( plugins_url( 'rwi-adminbar-scripts.js', __FILE__ ) ), array( 'jquery' ), Admin_Bar_Hover_Intent::version, true );
			}
		}

		function enqueue_style() {
			if ( is_admin_bar_showing() )
				wp_enqueue_style( 'rwi-adminbar', esc_url( plugins_url( 'rwi-adminbar.css', __FILE__ ) ), null, Admin_Bar_Hover_Intent::version, 'screen' );
		}
	}
};

Just replace the text inside rwi-adminbar-hoverintent.php with the above code.

After some time I started to play with Blair’s PrettyLink and PrettyLinkPro on a few other domain I’ve got. Well with the latest version of tweetable (1.91.2.0) released this week I thought I check to see what was new and what I needed to modify in my pre-existing code. Turn’s out a new j.mp API was implemented, and that didn’t do much for me. I also recently just purchased frosty.me and thought it would be great to auto shirk links with my new short dot me domain using PrettyLink and tweetable.

Just link before we are going to be editing two files: ¹ mh_twitter_class.php and ² admin_menus.php.

File number 1

Find line 388 and add global $post; after the public function. You’ll also want to change the $shortener default value, by removing it completely, leaving $shortener ONLY!

public function shorten_url($the_url, $shortener, $api_key='', $user='') {
	global $post;

Find line 427 and add this code (the parts in bold were added). Be sure to replace the deleted variable with the one provided in your pretty link tool page.

	} elseif ($shortener=="yourls" && isset($api_key) && isset($user)) {
		//Pass a string in the form of "user@domain.com" as the username, and the password as the API key
		$yourls = explode('@', $user);
		$url = "http://{$yourls[1]}/yourls-api.php?username={$yourls[0]}&password={$api_key}&format=simple&action=shorturl&url={$the_url}";
		$response = $this->send_request($url, 'GET');

	/**
	 * @ added by Austin Passy
	 * @ link http://austinpassy.com
	 */
	} elseif ($shortener=="self") {
		$url = url_to_postid( $the_url );
		$response = get_home_url( '/?=' ) . $url;

	} elseif ($shortener=="self") {
		$url = url_to_postid( $the_url );
		if ( 'post' == get_post_type() )
			$shortlink = wp_get_shortlink();
		elseif ( 'page' == get_post_type() )
			$shortlink = home_url( "?page_id={$url}" );
		elseif ( 'attachment' == $post->post_type )
			$shortlink = home_url( "?attachment_id={$url}" );
		$response = $shortlink;

	} elseif ($shortener=="twitterfriendlylinks" && function_exists( 'twitter_link' ) ) {
		$url = twitter_link();
		$response = $url;
	} elseif ($shortener=="prettylinkpro" && function_exists( 'prlipro_pretty_link' ) ) {
		global $prli_blogurl;
		$url = "{$prli_blogurl}/index.php?action=prli_endpoint_url&k=445e75096450c647eb707s7c45545a56&url={$the_url}";
		$response = $this->send_request($url, 'GET');
	// END
	} else {
		$url = "http://is.gd/api.php?longurl={$the_url}";
		$response = $this->send_request($url, 'GET');
	}

File number 2

Find line 380 and add this code (the parts in bold were added):

	<option value="yourls" <?php if ($setting_url_shortener=='yourls') { echo 'selected="selected"'; } ?>>YOURLS</option>
    <?php
    /**
	 * @ added by Austin Passy
	 * @ link http://austinpassy.com
	 */ ?>
	<option value="self" <?php if ($setting_url_shortener=='self') { echo 'selected="selected"'; } ?>>SELF (?p=ID)</option>
	<option value="twitterfriendlylinks" <?php if ($setting_url_shortener=='twitterfriendlylinks' ) { echo 'selected="selected"'; } ?>>Twitter Friendly Links</option>
	<option value="prettylinkpro" <?php if ($setting_url_shortener=='prettylinkpro' ) { echo 'selected="selected"'; } ?>>Pretty Link Pro</option>
    <?php /**END */ ?>
	</select>
    <?php $error_class = ' style="background:#F3898C;border:1px solid #F00;color:#222;padding:5px 10px;"'; ?>
    <?php if ($setting_url_shortener=='twitterfriendlylinks' && !function_exists( 'twitter_link' ) ) { ?>
    <span class="description"<?php echo $error_class; ?>>Requires <a href="http://wordpress.org/extend/plugins/twitter-friendly-links/">Twitter Friendly Links</a>. Please install or change settings</span>
	<?php } ?>
    <?php if ($setting_url_shortener=='prettylinkpro' && !function_exists( 'prlipro_pretty_link' )) { ?>
    <span class="description"<?php echo $error_class; ?>>Requires <a href="http://frosty.me/pretty-link">Pretty Link Pro</a>. Please install or change settings</span>
	<?php } ?>
	<br />Specify which URL shortener should be used by Tweetable.
	</td></tr>

Now upload those two files, or if editing them inside of WordPress (by going to /wp-admin/plugin-editor.php/), and save them. Then apply the new changes in the Tweetable settings page and your done. Next time you post a entry the URL used will be your domain with the default ugly permalink, an ID or random number generated by Twitter Friendly Links or a shortlink with a possible different domain (like my frosty.me domain) by PrettyLink!

Grab the plugin here.

Removed

• Removed the settings page.
• Removed the shortcode [replace].
• Removed javascript and stylesheet files.

Added

• Added metabox controller to all post/page & post_type pages.
• Added a note after the content for users who are logged in on posts that are hidden from public view.

Future release/notes

• I’ve built in AJAX replacement, but haven’t had time to get it working cross browser. So for the time being, it’s a simple page refresh.
• Speaking of page refresh, the header already sent error should be fixed now.

If you’ve got anything to add or you notice any issues please let me know! And if this plugin has helped you in anyway please consider donating.

Adding a post to the CPT hellobar, and activating the plugin in the settings page will insert one random post from the post list in a fixed position at the top of the browser screen. Using jQuery the bar will drop down after about 5 seconds.

I’ve created a demo over at wpWag if you want to see a working copy.

Testing

Please take note that I am still testing this plugin, and have a long way to go before it’s where it needs to be. So if you’ve got suggestions, please feel free to leave your comments here or on the plugin page: austinpassy.com/wordpress-plugins/hellos-bar/.

The Future

This plugin is brand new and has some future planes.

1. Saved bar position with cookie settings.
2. Post and page per post ID.
3. Per post on/off toggle.
4. ….

You should see the new version soon enough. Some features include:

• Removal of the uninstall script.
• Removed wpads.
• Cleaned up options.
• Removed easing.js, farbtastic.js, dock.js
• Removed unused images.
• Added license.txt, readme.html.
• Added ability to move meta-boxes with the built in WordPress jQuery movables. Organize the layout, and even close/hide boxes. Note: I haven’t been able to figure out how to create a multiple column layout, it’s set with CSS right now. So if you move a box it will forever be changed.

Grab the latest version from WordPress

Important! Users will have to re-save their settings after updating to version 0.8.. The option name array’s changed and there for will delete your old options.

Maybe you know how to migrate old option names? If so let me know.

I wanted to collect some emails from parties who were interested in viewing the presentation and ask them if they might be interested in WordCampLA, since I am the lead organizer. The one you see on that page is modified for my use. I kind of put it out and forgot about it for a bit.

When I was putting together the sponsorship levels for WordCampLA I thought this may come in handy again. Last year I put the sponsorship levels in a zip file and put it up for download, but with didn’t know who was interested or who downloaded the files for that matter. So, I decided a page with hidden content would suit this particular situation best.

As of right now there are no options to control the plugin, though you do have a setting page where you need to activate it. There are some other things on that page but don’t really apply right now.

Use

Just input your shortcode before and after the content needing to be replaced like so:

[replace]xxxxxxxxxxxxxxxxxx[/replace]

There are also two shortcode options at his time, you can control who can view the content by entering capability="level_10" which by default is set at level 10, and the text that show before the form by entering text="Some text"

[replace capability="level_8" text="Hello"]xxxxxxxxxxxxxxxxxx[/replace]

Please leave any feedback or problems on this post or the Plugin page itself.

So how about adding a function into your theme that will auto correct any misspellings?

And now, the simple (redundant code)

function wpwag_spell_wordpress_correct($text) {
	$text = str_replace('Wordpress', 'WordPress', $text);
	$text = str_replace('wordpress', 'WordPress', $text);
	$text = str_replace('wordPress', 'WordPress', $text);
	$text = str_replace('word-press', 'WordPress', $text);
	$text = str_replace('wOrdpRess', 'WordPress', $text);
	$text = str_replace('wp', 'WordPress', $text);
	$text = str_replace('WP', 'WordPress', $text);

	return $text;
}

As you can see, we’re just copying multiple code, and trying to find all the matches in which one might write WordPress incorrectly.

So now, the more advances replacement

I’ve added to the function, so that it won’t replace wp inside of an image.

function wpwag_spell_wordpress_correct($text) {
	$ignore = '/([^<>]+)< [^>]+>|< [^>]+>([^<>]+)/'; //image pattern

	if ( preg_match_all($ignore,$text,$replace,PREG_PATTERN_ORDER|PREG_OFFSET_CAPTURE) ) {
		return $text;
	} else {

	$pattern[] = '/\bword[- ]?press\b/i';
	$pattern[] = '/\bWP\b/i';

	$replace = 'WordPress';

        //removed "foreach" as suggested by @utkarshkukreti here
	//foreach ( $pattern as $patterns )
		$text = preg_replace($pattern,$replace, $text);

	return $text;
        }
}

This code is using regular expression, and an array of patterns. The first is looking for words matching wordpress or word-press with case insensitive matches.
While the second is looking for case insensitive matches to WP.

Pretty simple so far

Now we need to add either of the above code to your theme’s function.php file, then add the necessary filter! To do so just add this line:

add_filter( 'the_content', 'wpwag_spell_wordpress_correct', 10, 1 );

Now, if you’d like, you can also replace incorrect spellings in other area’s of WordPress. For example just add in any of the following filters you’d like.

add_filter( 'comment_text', 'wpwag_spell_wordpress_correct', 10, 1 );
add_filter( 'the_title', 'wpwag_spell_wordpress_correct', 10, 1 );

Just to name a few

That’s it!

Now I’d also like to mention you can create this as a plugin, or even download the multiple plugins that are already out there that do this very thing.

1. WordPress Auto Correct
2. Ozh’ Correctly Spell WordPress
3. It’s WordPress

If you’re interested in adding this function as a plugin, just use the code below..

< ?php //remove space between '<' and '?'
/**
 * Plugin Name: WPWag's Spell WordPress Correctly
 * Plugin URI: http://wpwag.com/tips-tricks/auto-change-wp-and-incorrect-wordpress-spellings/
 * Description: Writes WordPress as it should be written. “WordPress”.
 * Version: 0.2
 * Author: Austin Passy
 * Author URI: http://austinpassy.com/
 */

function wpwag_spell_wordpress_correct($text) {
	/** advanced *don't match the following **/
	$ignore = '/([^<>]+)< [^>]+>|< [^>]+>([^<>]+)/'; //image pattern

	if ( preg_match_all($ignore,$text,$replace,PREG_PATTERN_ORDER|PREG_OFFSET_CAPTURE) ) {
		return $text;
	} else {

	$pattern[] = '/\bword[- ]?press\b/i';
	$pattern[] = '/\bWP\b/i';

	$replace = 'WordPress';

	//foreach ( $pattern as $patterns )
		$text = preg_replace($pattern,$replace, $text);

	return $text;
	}
}
add_filter( 'the_content', 'wpwag_spell_wordpress_correct', 10, 1 );
?>