add_action('publish_page', 'wpcanyon_redirect_on_page_publish');
function wpcanyon_redirect_on_page_publish($post_ID) {
	header('Location: '.get_home_url().'/wp-admin/edit.php?post_type=page');
	exit();
}

add_action('publish_post', 'wpcanyon_redirect_on_post_publish');
function wpcanyon_redirect_on_post_publish($post_ID) {
	header('Location: '.get_home_url().'/wp-admin/edit.php?post_type=post');
	exit();
}

That’s all, hope you find it useful.

The solution is simple if you are using WP_Query, just add the max_num_pages as the second parameter for next_posts_link(). Like this:

next_posts_link('>', $custom_query->max_num_pages);

Change custom_query to whatever variable name you’re using when you’re calling new WP_Query();

So i finally decided to take a look at the code behind wp_nav_menu() and write up a simple code to make my work go a bit faster and easier from now on. So here it is:

add_filter( 'nav_menu_css_class', 'additional_active_item_classes', 10, 2 );

function additional_active_item_classes($classes = array(), $menu_item = false){

	if(in_array('current-menu-item', $menu_item->classes)){
		$classes[] = 'active';
	}

	return $classes;
}

Update:

After messing around with the $menu_item array i noticed that the whole snippet can be drastically simplified. Since the $menu_item array also holds the classes the menu item will have and “current-menu-item” class is not something that’s gonna differ from theme to theme since it’s defined by the core, doing a simple in_array() check for “current-menu-item” in the classes array will do the trick. Can’t get simpler then this.

You can skip right to the improved version if you want.

Original Snippet

Bellow you can see the original code with some comments added by me to help you (i guess) understand the code easier.

//Get data for page with the title of the new post.
//We'll later use this to check if it already exists, if it does we won't create it.
$page_check = get_page_by_title('Sermon Media');
$page_check_id = $page_check->ID;

//Declaring the data for our new page
$new_page = array(
	'post_type' => 'page',
	'post_title' => 'Sermon Media',
	'post_status' => 'publish',
	'post_author' => 1,
);

//If the page doesn't already exist create it
if(!isset($page_check_id)){
	wp_insert_post($new_page);
	//getting the data of our new page and assigning a page template for it.
	//If you're not going to use a custom template remove the next 3 lines
	$new_page_data = get_page_by_title('Sermon Media');
	$new_page_id = $new_page_data->ID;
	update_post_meta($new_page_id, '_wp_page_template','page-template.php');
}

Improving It

I found few ways to improve it, some are minor and some are very important. Let’s start…

Unnecessary database calls
Ok, this is very important. As it is now, every single time a page loads the snippet will be executing get_page_by_title() function. There is absolutely no need for that, we need the whole snippet to be executed only after the theme has been activated. Luckily, that’s very easy, here is how:

if (isset($_GET['activated']) && is_admin()){
    //the theme has just been activated, coding goes here
}

Title is needed 3 times
Important. As you can see the page title is used 3 times(lines 3, 9 and 19). There is a chance of mistyping it on one place and create a problem (even the person that added it to snipplr forgot to change it on the last line, it was still “Post Title”).

Page template – issue 1
After the snippet is added there are 3 more lines, they add a page template to the newly created page. What if you don’t want to assign a specific template to the page? In my opinion it’s better to have a variable at the top which will be empty by default, and if you wish you can add the template filename there.

Page template – issue 2
wp_insert_post() will return the id of the page, there is no need to use a special function to get something we already have. So simply instead of “wp_insert_post()” it’ll be “$new_page_id = wp_insert_post()” and we can remove the next 2 lines.

Final Snippet

if (isset($_GET['activated']) && is_admin()){

	$new_page_title = 'This is the page title';
	$new_page_content = 'This is the page content';
	$new_page_template = ''; //ex. template-custom.php. Leave blank if you don't want a custom page template.

	//don't change the code bellow, unless you know what you're doing

	$page_check = get_page_by_title($new_page_title);
	$new_page = array(
		'post_type' => 'page',
		'post_title' => $new_page_title,
		'post_content' => $new_page_content,
		'post_status' => 'publish',
		'post_author' => 1,
	);
	if(!isset($page_check->ID)){
		$new_page_id = wp_insert_post($new_page);
		if(!empty($new_page_template)){
			update_post_meta($new_page_id, '_wp_page_template', $new_page_template);
		}
	}

}

Final Words

I’m not saying that “MattStrange”, the original author, wrote a bad code. We all write something that can be improved, hell i don’t even want to take a look at the wpCanyon’s current theme source code, it was made long time ago and i’ll simply start working on a new theme these days, instead of rewriting 90% of the current one.

One very important aspect of a premium WordPress theme is the flexibility it offers to the users. That flexibility comes from the theme’s options panel. Some themes have ten options and some even have hundreds. But why doesn’t anyone allow the potential buyers to try the options out, make changes and see the full demonstration of a theme they are about to buy, not even WooThemes does that.

Why?

Well it’s quite simple, every time someone makes a change it will overwrite someone else’s changes and there is a big possibility that more people will be testing the options out at the same time and keep overwriting each other’s changes and wouldn’t be able to see how it works and behaves properly thus confusing everybody.

You probably have a blog, do you? Well imagine few more people making changes to it at the same time as you do, it’s like that. Stuff changes and you have no idea why, you didn’t change it.

So, How?

Well the idea is pretty simple, if you’re a theme/plugin developer you know that we have to add a prefix to our field names that go inside the database in order to avoid conflicts with other themes/plugins that could use the same names. For example, an option where the user inputs text he wants to be shown in the footer of a theme, we can call it “footer_text” but then it might conflict, so we add a prefix like “wpcp_”, “aviatic_” or anything else that we think should be unique or at least unlikely to be used by something else, so we get wpcp_footer_text.

Using that same method we can add the username of the user that makes changes as a suffix or prefix (doesn’t matter) so if a user with username “John” makes changes they will be saved and later retrieved as “wpcp_footer_text_John” and when a different user with username “Michael” makes changes it will be “wpcp_footer_text_Michael” so no conflicts will be made and no data will be overwritten.

Database Usage

For themes that have a big amount of options (like WooThemes or PliablePress) it will use a lot of data. For example 50 options changed by 100 users is 5000 rows in the database. But that’s not a big problem because WordPress can be set to delete the data after a certain time period.

Does It Really Work?

Well in theory it should work just fine, it’s pretty simple, i haven’t tested it yet but i started working on a little example and will update this post when it’s done. In the meantime if anybody is reading this let me know your thoughts.

Update: It Works

I just tested it and it works without a problem. I needed 2 minutes to alter a theme to support this, yes just 2 minutes, few lines of code. Check back later, i’ll throw in a demo so you can all test it out.

CSS hack

This hack is a simple CSS hack that allows you to change the height of the default 200px to a new fixed height.

add_action('admin_head', 'categories_list_height_css');

function categories_list_height_css() {
	echo'
	<style type="text/css">
		#category-all.tabs-panel{ height:500px; }
	</style>
	';
}

jQuery hack

This is a bit better hack because it will change the height dynamically to fit all the categories.

add_action('admin_head', 'categories_list_height_jquery');

function categories_list_height_jquery() {
	echo'
	<script type="text/javascript">
		jQuery(function($){
			$("#category-all.tabs-panel").height($("#categorychecklist").height());
		});
	</script>
	';
}

Both hacks go inside functions.php file inside your theme folder.

function top_comment_authors($amount = 5){

	global $wpdb;

	$results = $wpdb->get_results('
		SELECT
			COUNT(comment_author_email) AS comments_count, comment_author_email, comment_author, comment_author_url
		FROM
			'.$wpdb->comments.'
		WHERE
			comment_author_email != "" AND comment_type = "" AND comment_approved = 1
		GROUP BY
			comment_author_email
		ORDER BY
			comments_count DESC, comment_author ASC
		LIMIT '.$amount

	);

	$output = "<ul>";
	foreach($results as $result){
		$output .= "<li>".$result->comment_author."</li>";
	}
	$output .= "</ul>";

	echo $output;

}

Now you can call it anywhere in your theme using the top_comment_authors() function. By default it will show top 5 but if you want a different amount simply call it like top_comment_authors(7) which will show top 7 comment authors.

If you want to show more data in the listing you can use these:

• $result->comment_author_email the email address of the commentator
• $result->comments_count comments number of the commentator
• $result->comment_author_url the website address of the commentator

add_filter('next_posts_link_attributes', 'posts_link_attributes');
add_filter('previous_posts_link_attributes', 'posts_link_attributes');

function posts_link_attributes(){
	return 'class="styled-button"';
}

What actually this snippet does is adding the html you return in the function to the anchor.

<a href=’link’ HERE>

So you can add ID, classes and other attributes an anchor can have. By default it will only have the href attribute.

How to install WordPress Locally?

Adding A Custom Field Automatically On Post/Page Publish

Free Theme: Magazine Basic v2.6.1

Flattr Button for WordPress without a Plugin

20 Must Have WordPress Plugins For Every Website

A Refresher On Custom Taxonomies

5 Reasong Gravity Forms Makes Your From Plugin Look Like Crap

WordPress: From Kubrick to Twenty Ten

add_action('publish_page', 'add_custom_field_automatically');
add_action('publish_post', 'add_custom_field_automatically');
function add_custom_field_automatically($post_ID) {
	global $wpdb;
	if(!wp_is_post_revision($post_ID)) {
		add_post_meta($post_ID, 'field-name', 'custom value', true);
	}
}

That’s it. Hope this helps.