WordPress

Use jQuery to hide/reveal children of a WordPress page

I recently launched a beautiful website for Kurt Jurek, registered acupuncturist and herbalist. As some of you may know, Chinese medicine can be used to treat a huge amount of ailments. As a result when putting together content, the amount can be overwhelming and difficult to organize. Combine this with the need to use a CMS and you’re task is quite daunting. This is when adding a bit of JQuery to your WordPress theme helps.

My number one task when setting up WordPress as a CMS for a client is to make updates easy to understand. If clients need to use HTML in their admin, then I consider this a failure. WordPress in itself is quite easy for most people to grasp and understand and it should be the case at all times.
Continue reading »

Modifying the WordPress admin

I’ve been using WordPress to build 99.5% of my sites lately. Even if a particular client doesn’t need a blog or won’t be making frequent changes, I do like to provide the ability to update content if needs be.

As a result, the WordPress back end has too many features for such a client. After reading the tutorial from Six Revisions, I’ve been modifying the WordPress admin, but using the following:

/* Remove Posts and Tools from Admin menu items */
function remove_menu_items() {
global $menu;
$restricted = array(__('Posts'),__('Tools'),__('Comments'),__('Links'));
end ($menu);
while (prev($menu)){
$value = explode(' ',$menu[key($menu)][0]);
if(in_array($value[0] != NULL?$value[0]:"" , $restricted)){
unset($menu[key($menu)]);}
}
}

add_action('admin_menu', 'remove_menu_items');

Once added to my functions.php file, the menu items posts, tools, comments and links disappear. How handy is that?

Updates to the WordPress Comment Form

Justin Tadlock recently wrote a great post and tutorial aimed at theme developers. His article pointed out that with the release of WordPress 3.0, a new function for handing comment forms: comment_form(), was introduced.

This new function offers much more flexibility for plugin authors and is really easy to use. All you have to do is open up your comments.php file and locate this bit of code:

<div id="respond">

Lots of HTML code to output form elements.

</div>

and replace it with:

<?php comment_form(); ?>

You may also need to tweak your CSS, but overall, that’s the only change needed.

I took Justin’s advice and updated my basic theme and noticed a few things.

• The default title is Leave a Reply
• The default submit value is Post a Comment
• The comment after the form ‘You may use these HTML tags…‘ was added

In order to change these easily, I updated my function file with the following code:

<?php
//Change comment form defaults

add_filter( 'comment_form_defaults', 'basic_comment_form_defaults' );
        function basic_comment_form_defaults( $defaults ) {
                $defaults['label_submit'] = __( 'Submit' );
                $defaults['title_reply'] = __( 'Leave a Reply' );
                unset($defaults['comment_notes_after']);
                return $defaults;
        }
?>

Displaying latest and most popular blog posts in your WordPress footer

Fat footers are very handy for displaying additional information on your site. On a previous version of this website I used to display the latest blog posts, while on this newer version I opted to display the popular posts. I thought I would share these code snippets here.

Display Recent Blog Post

In your footer.php file, simply use the following code:

<ul>
<? query_posts('showposts=10');?>
<?php while (have_posts()) : the_post(); ?>
<li><a href="<?php the_permalink() ?>"><?php the_title(); ?></a></li>
<?php endwhile; ?>
</ul>

Simply change ‘showposts=10′ to whatever number you want to display more or less than 10 posts.

Display Most Popular Blog Posts

“Most popular” posts in this case is defined by the posts that have the most comments. In order to select these, the following pieces need to be used:

1. Add the following function to your function file:

function most_popular_posts($no_posts = 10, $before = '<li>', $after = '</li>', $show_pass_post = false, $duration='') {
global $wpdb;
$request = "SELECT ID, post_title, COUNT($wpdb->comments.comment_post_ID) AS 'comment_count' FROM $wpdb->posts, $wpdb->comments";
$request .= " WHERE comment_approved = '1' AND $wpdb->posts.ID=$wpdb->comments.comment_post_ID AND post_status = 'publish'";
if(!$show_pass_post) $request .= " AND post_password =''";
if($duration !="") { $request .= " AND DATE_SUB(CURDATE(),INTERVAL ".$duration." DAY) < post_date ";
}
$request .= " GROUP BY $wpdb->comments.comment_post_ID ORDER BY comment_count DESC LIMIT $no_posts";
$posts = $wpdb->get_results($request);
$output = '';
if ($posts) {
foreach ($posts as $post) {
$post_title = stripslashes($post->post_title);
$comment_count = $post->comment_count;
$permalink = get_permalink($post->ID);
$output .= $before . '&raquo; <a href="' . $permalink . '" title="' . $post_title.'">' . $post_title . '</a>' . $after;
}
} else {
$output .= $before . "None found" . $after;
}
echo $output;

In this function, I’ve set the number of posts to 10 – ‘$no_posts = 10‘. Just change this number to display more or less posts.

2. Insert the following in your footer.php

<ul>
<?php most_popular_posts(); ?>
</ul>

WordPress revision control

In an earlier post, I discussed the handy revision control plugin. Plugins are awesome and I truly have immense respect for plugin developers, but I do find them a bit tedious to maintain and sometimes a bit of an overkill.

I am constantly fiddling and updating over 30+ client sites at a time. If WordPress and plugin updates didn’t come out as frequently, I would be more than happy to load my sites with dozens of plugins, but I do find simpler non-plugin methods more handy.

I recently discovered that post revisions can be disabled or limited simply by adding the following bit of code to the wp_config.php file.

define('WP_POST_REVISIONS','5'); //Will limit revision to 5 revisions

define('WP_POST_REVISIONS','false'); //Disables revisions totally

Personally, I think that one line of code is better than a plugin.