Anyways, We wanted to make it so you had to login to be able to see anything. Essentially making it private. Luckily there is already a plugin out there and it is very small, and works magical to our needs, Private WP. But then I have to add it to every blog we have and activate it. But thankfully wordPress is smart and made a mu-plugins folder in wp-content. Whatever plugin you add in there gets activated and added to every blog in your install.

All you have to do is download the plugin and upload it to that folder and it is activated site wide.

This is the plugin, which is exactly how I would have done it.


function private_wp() {
if (!is_user_logged_in()) {
auth_redirect();
}
}

add_action('get_header', 'private_wp');


$rmcode = `find $dir -name "*.php" -type f |xargs sed -i 's###g' 2>&1`;
echo "Malware removed.
\n";
$emptyline = `find $dir -name "*.php" -type f | xargs sed -i '/./,$!d' 2>&1`;
echo "Empty lines removed.
\n";
?>

Completed.

If you upload this to the root of your website and open it up in the browser it will do as it says. I changed the $dir = “./”; to $dir = “./../”; so it went through all my websites at the same time. Took about 30 seconds or so. And it removed the injection from all my sites. Great

You can download this plugin here.

I am going to be submitting this plugin to the repository, I don’t suspect any updates to this anytime soon. But if there are, it will be there.


/*
Plugin Name: Disable new user email notifications
Plugin URI: http://www.tipsforwordpress.com
Description: Disables email notifications of new users registered on your blog
Author URI: http://westondeboer.com
Version: 1.0
*/

}
endif;
?>


With this plugin, I have learned so much about pluggable.php and am so excited about it! Things I didn’t know before.

Clients get confused when you install wordpress as a cms for them and they see add a new post, they always get confused with that. With this new feature where it says add a new client, or add new business. Clients will be able to understand easily what they need to do. This will also add the ability to organize much easier within categories and categories within categories.

To add a custom post type in wordpress 3.0 this would go into either a plugin or the functions.php file in your theme directory:


// This function is where the magic happens
function post_type_gallery() {

// This action shows the above function in the WordPress Dashboard
add_action('init', 'post_type_gallery');


With that you will have a custom post screen, Way easier than it was before! Everything posted in this gallery section will also only appear in the gallery edit posts section. It should look this this below:

Next will be how to add a custom field to this custom post. It is the same way as before, just a little bit of added code into the register_post_type.

WP Engineer goes a little more in detail about custom post types. More in detail about how to display certain boxes and what not. Definitely worth a read.

I have no uses for this as I can navigate to any area that I want to, pretty easily. Just putting it out there for other plugin/theme developers.


function my_favorite_action( $actions ) {

return $actions;
}
add_filter( 'favorite_actions', 'my_favorite_action' );


The only section that you need to edit is the edit-comments.php, and just point that to where you want the link to go. And the Manage Comments will be the text that is displayed.

Anyways May 1st is a long way away.

Using custom fields for comments is just like using custom fields for wordpress.

So instead of using: update_post_meta('postid', 'customfield', 'customfieldvalue');

We now use: update_comment_meta('postid', 'customfield', 'customfieldvalue');

So in your plugin or functions.php file you can just do this:

add_action('comment_post','comment_rating');
function comment_rating($comment_id) {
global $wpdb, $user_identity, $user_ID;
$star = $_POST['rating'];
update_comment_meta('postid', 'rating', $star);
}

Again you need to add a rating drop down in your comments.php file (example): <input type=”radio” name=”rating” id=”vote1″ value=”1″ />

// This is the filter that gets added to the content
add_filter( 'the_content', 'remove_first_image' );

// This is the function name
function remove_first_image($content) {
global $post, $posts;

// This is the pre replace that removes the first image
$content = preg_replace('//i',$matches,$post->post_content,1);
return $content;
}

You can see a working example at Barack Obama. The first image is called via catch_that_image and then the_title is displayed and then the_content after that.

This way Casey just keeps doing what he is doing without having to change any of the posts around that he already has done.

add_action(‘register_form’,'show_first_name_field’);
add_action(‘register_post’,'check_fields’,10,3);
add_action(‘user_register’, ‘register_extra_fields’);

function show_first_name_field(){
?>
<p>
<label>First Name<br/>
<input id=”user_email” type=”text” tabindex=”20″ size=”25″ value=”<?php echo $_POST['first']; ?>” name=”first”/>
</label>
</p>
<p>
<label>Last Name<br/>
<input id=”user_email” type=”text” tabindex=”20″ size=”25″ value=”<?php echo $_POST['last']; ?>” name=”last”/>
</label>
</p>
<?php
}

function check_fields($login, $email, $errors) {
global $firstname, $lastname;
if ($_POST['first'] == ”) {
$errors->add(‘empty_realname’, “<strong>ERROR</strong>: Please Enter in First Name”);
} else {
$firstname = $_POST['first'];
}
if ($_POST['last'] == ”) {
$errors->add(‘empty_realname’, “<strong>ERROR</strong>: Please Enter in Last Name”);
} else {
$firstname = $_POST['last'];
}
}
function register_extra_fields($user_id, $password=”", $meta=array())  {

$userdata = array();
$userdata['ID'] = $user_id;
$userdata['first_name'] = $_POST['first'];
$userdata['last_name'] = $_POST['last'];
wp_update_user($userdata);
}