After a few months in the works I’m happy to announce Custom Metaboxes and Fields for WordPress version 0.9 is out and ready for consumption.

This is probably one of the large updates we have put out as it contains a lot of fixes, tweaks, and even a few nice additions. Taken straight from the readme, here’s a list of what new with 0.9!

• Cleaned up scripts being queued
• Cleaned up and reorganized jQuery
• Use $pagenow instead of custom $current_page
• Fixed CSS, removed inline styles, now all in style.css
• Fixed multicheck issues (issue #48)
• Fixed jQuery UI datepicker CSS conflicting with WordPress UI elements
• Fixed zeros not saving in fields
• Fixed improper labels on radio and multicheck fields
• Fixed fields not rendering properly when in sidebar
• Fixed bug where datepicker triggers extra space after footer in Firefox
• Added jQuery UI datepicker packaged with 3.3 core
• Added date time combo picker
• Added color picker
• Added readme.md markdown file

Bill and Norcross have put in a lot of time for past releases, so in this release I tried to pick up the slack as I hadn’t been as active.

If you are using 0.8 you should be able to upgrade without any issues. However it’s worth noting this release is for WordPress 3.3+ – if you have not upgraded to 3.3 do not use 0.9.

What’s next

The next version is going to be a good one, so definitely keep an eye out. You can take a peak at the To-do in the readme to get an idea of what’s on our radar. Specifically here’s a few things that are a priority in 1.0:

• Code cleanup. Since CMB has a rather large user base now, I figure we owe it to them to tidy up the code. This is going to be the #1 goal (but not the only) for 1.0.
• Improve inline documentation. This goes hand-in-hand with the first point.
• Move the jQuery datepicker and timepicker code inline and make each instance configurable with options passed through the array. This will allow multiple timepickers with different ranges, etc.
• Add array option for placeholder value. Now that most modern browsers support this (html5) it should be a no-brainer.
• Add array option for required elements. Like the previous point, this should be easy thanks to HTML5.

Props!

Special thanks to Gary Jones for some great feedback as well as tweaks, Bill for squashing a few bugs, and everyone who has been reporting bugs on GitHub.

Unlike the other CRMs out there I decided to create a custom post type for my contacts instead of doing a bunch of magic to use posts. In a few places throughout the app I needed to pull the total number of contact entries in the database.

Turns out, it is very easy to do! Just a few lines of code, which you can see below. Make sure and change contact to the name of your post type.

function ja_total_post_count() {
	global $wpdb;
	$numposts = $wpdb->get_var("SELECT COUNT(*) FROM $wpdb->posts WHERE post_type = 'contact'");
	if (0 < $numposts) $numposts = number_format($numposts);
	return $numposts;
}
// To use...
echo 'Number of total contacts: ' . ja_total_post_count();

The presentation I will be giving is titled Oops! Common WordPress mistakes (and more).

Let’s face it, much of our learning is done by trial and error. Wouldn’t it be awesome if someone would just tell us the errors and save us the time? We’ll take a look at common mistake by WordPress beginners and intermediates alike – and the correct solutions. Additionally we will also throw in some helpful tips and Q&A.

I think it’s going to be a great WordCamp. If you are going to be attending let me know, we’ll meet up and grab some drinks!

There are tons of new features in WordPress 3, if you want to read up on things this is the most comprehensive overview I have seen  on WP 3.

Expect a final release in the next 30-60 days!

So what exactly have I been up to?

- Planned a week long vacation to Disney World in May with my girlfriend.

- Scheduled a week long  4-wheeling trip in the Colorado Mountains this July.

- Started learning CodeIgniter and am 2/3 the way through writing my first fairly detailed web app. For the record, CodeIgniter is fantastic. If you need more than a basic website, and WordPress does’t fit the mold, I highly recommend looking into CodeIgniter.

- Began to play with the Genesis WordPress framework. I love to buy themes just to look under the hood and learn from the authors. I have purchased Thesis, Genesis, a variety of WooThemes themes,  and a few of Matt Brett’s themes. They each have their unique aspect to offer. Genesis is no different. The documentation is still in development right now, but it has very good potential. Definitely worth looking into.

- Built and developed a directory based website on the Genesis framework. The side is about 85% complete and it has been great and educational project. I’ll have a more detailed write up once the site officially launches.

- Read the 4 Hour Work Week by Tim Farris. As someone who was previously big into the affiliate marketing scene, this book is great. I learned a lot of things from it and it is also quite motivational. I don’t think everyone will because to relate to it, but I cetainly did. I look forward to re-reading it in the coming months. I’ll try to post a more detailed review soon. I also started Reading Crush It and Rework.

- Following the development of WordPress 3.0. This is going to be – hands down – the best release to date. WP 3.0 beta 1 will be released this weekend with the goal of a final release in the next 30-60 days. Custom post types, custom taxonomies, WPMU merger, and a new default theme (twentyten) are just a few of the awesome features WordPress 3.0 will bring to the table. I recommend you check out beta 1 when it comes out this weekend.

To say I been keeping busy is an understatement, but I can’t complain. I’ll have some more ideas for posts in the can, so there should be fresh content going up soon!

The short write up, titled Distributed WordPress admin account cracking, exposes a malicious script which was written specifically to crack WordPress admin passwords.

The acquired script is written in PHP and performs brute force cracking attempts to WordPress admin accounts

[...]

Now, the interesting thing about the script is that it allows distributed cracking. Information is saved in a MySQL database and the script actually connects directly to the main database. This allows the attacker to run many simultaneous scripts – each of them will take 200 new URLs and mark them with the brute forcer’s ID ($colo).

There is nothing new or revolutionary about this script. If you have a beefy password and are up-to-date (2.8.6 as of today!) there’s no reason to worry. But I believe this illustrates the importance of doing everything possible to secure your website.

In my last post, I embedded Brad’s WordPress security presentation he gave at WordCamp NYC. It contains simple yet effective ways to secure your WordPress installations – definitely worth a quick look.

I’ve had a few people ask me what are the quickest/easiest ways to get started securing their WP site. Almost every single thing in Brad’s presentation is important, but in my mind 2 things are the most important and can be executed in a matter of minutes.

Delete your ‘admin’ account. Yes, that’s right. Nuke it. Scripts such as the one mentioned above try to gain access to your website by logging into the admin account – the account with the user name ‘admin‘. Create a new account, something like RobSmith (or anything other than admin!), give it admin privileges, and then delete the default admin user. You will thank me later.

Don’t use wp_ as your default prefix. You probably don’t remember, but when you were flying through WordPress’s famous 5 click install one of the options it asked you for was the default WordPress prefix to use with the database. That’s right, I figured you didn’t remember. By default it’s set to wp_ – this should be changed. If you have already setup your blog, you can change it using some phpmyadmin trickery, but make sure you know what you are doing first.

As WordPress becomes even more mainstream (gasp!) it will continue to be attacked by script kiddies and other nefarious characters. However by staying up to date and taking the appropriate steps to secure your site, you really don’t have anything to worry about.

From the WordPress.org blog:

2.8.6 fixes two security problems that can be exploited by registered, logged in users who have posting privileges.  If you have untrusted authors on your blog, upgrading to 2.8.6 is recommended.

On another note, WordPress 2.9 is still scheduled for a final release at the end of November/early December. You can still download and test the latest WP 2.9 nightly build here.

Finally, WordPress MU received a few updates last week and is now up to 2.8.5.2.

Important Note:

This post is quite dated as it is from 2009. Everything mentioned below will still work, however, since this post was written there have been several plugins released that are worth considering first. Make sure and check out the list below!

• WP-Cycle
• Genesis Slider (requires the Genesis Framework)
• jQuery Slider

These are the ones I recommend. If these do not fit the bill there are tons to choose from on WordPress.org

Recently I had a project that needed to have a rotating banner on the main page. Most rotating banners out there are connected to feature posts or articles. WooThemes and some of Matt Brett’s projects often use this method.

This wasn’t going to cut it for me. I needed to have rotating banners that were not associated to any posts, could link off site, be updated/maintained by the client, and preferably not use any custom field voodoo. The last thing I wanted to do was use a post category since it would be major over kill.

So I came up with a solution that fit all my requirements above and works great. Figured I would share what I did in case anyone else needs a similar solution.

The rotating banners were accomplished using:

• jQuery
• jQuery Carousel plugin
• WordPress Link Manger

Let’s get started here.

Step 1: setup a link category

When you’re logged into the WP admin panel, click on Links on the left (under Media, above Pages). The Links section will expand and now we need to create a Link Category.

Add your Banner category

After you have added your Banner category (or whatever you decide to name it) you want to find the ID for that category. There are 2 ways you can do this. First, place you cursor over the category and look in browser status bar.

The second option is to use Sivel’s Simply Show IDs plugin which will tell you the ID. Either way, just make sure you note what the ID is for your category since we will need it later.

Step 2: add some banners

Now we will add some links to the category. Click Add New under Links.

The name and description is for your reference and will not be shown or used. Make sure you place the link in the category you created. Lastly you will need to put the location of the image in the Image Address field. The easiest way is to upload your banners using the WordPress Media manager. If you go that route your image location will be something similar to http://yoursite.com/wp-contents/uploads/11/09/banner.jpg.

Step 4: downloading  and moving jQuery Carousel

Now that we have the banner category created and some links/images in the category we need to get things setup behind the scenes.

First, download jQuery Carousel.

Secondly, unzip the files. You will see a bunch of files, most of which we won’t need.

Open up your theme folder (/wp-contents/themes/yourtheme/) and create a folder inside called js.

Now we need to move jquery.jcarousel.pack.js or jquery.jcarousel.js (look in the /libs/) to this folder. The path should be similar to /wp-contents/themes/yourtheme/js/jquery.jcarousel.pack.js

Note: It is up to you which version of jCarousel you use. I prefer the packed version since it is smaller and we will not need to do any editing.

After the jCarousel javascript file has been moved we need to move over the CSS. Open jquery.jcarousel.css, copy the contents, and paste it into your theme’s style.css.

So to recap, you should have:
/wp-contents/themes/yourtheme/js/jquery.jcarousel.pack.js
/wp-contents/themes/yourtheme/style.css (should contain the CSS from jquery.jcarousel.css)

Step 5: setting up jCarousel and jQuery

Once you have added the necessary jCarousel CSS to your theme’s style.css you will need to edit it to meet the dimensions of your banner.

/* @group jcarousel */

.jcarousel-banners {
 border: 1px solid #cfcfcf;
 margin:0 0 30px 0;
}

.jcarousel-container {
 position: relative;
}

.jcarousel-clip {
 z-index: 2;
 padding: 0;
 margin: 0;
 overflow: hidden;
 position: relative;
}

.jcarousel-list {
 z-index: 1;
 overflow: hidden;
 position: relative;
 top: 0;
 left: 0;
 margin: 0;
 padding: 0;
}

.jcarousel-list li,
.jcarousel-item {
 float: left;
 list-style: none;
 /* We set the width/height explicitly. No width/height causes infinite loops. */
 width: 578px;
 height: 130px;
}

/**
 * The buttons are added dynamically by jCarousel before
* the</pre>
<ul>
<ul>list (inside the</ul>
</ul>
<div>described above) and
 * have the classnames "jcarousel-next" and "jcarousel-prev".
 */
.jcarousel-next {
 display: none;
}
.jcarousel-prev {
 display: none;
}

.jcarousel-banners .jcarousel-list li,
.jcarousel-banners .jcarousel-item {
 position: relative;
 float: left;
 list-style: none;
 width: 578px;
 height: 130px;
}

.jcarousel-banners .jcarousel-container-horizontal {
 width: 578px;
}

.jcarousel-banners .jcarousel-clip-horizontal {
 width: 578px;
 height: 130px;
}

.jcarousel-banners .jcarousel-item {
 width: 578px;
 height: 130px;
}

Above is what the CSS looks like for my website. The size of the banners is 578x130px. Change this to the size of your banners. You might need to do some further tweaking later.

Now the CSS is done and jCarousel is in place we need to tell WordPress to use jQuery and jCarousel when it loads a page.

Open up functions.php inside your theme directory. You may have to create it if your theme does not have one. Now add this:

if (!is_admin()) {
wp_enqueue_script('jquery');
wp_enqueue_script('jcarousel','/wp-content/themes/yourtheme/js/jquery.jcarousel.js',false,false);
}

WordPress includes many scripts out of the box, one of them being jQuery, so there is no need for us to download it. The code snippet tells WordPress – as long as we are not in the admin panel – to load jQuery and the jCarousel script.

Step 6: finishing things up on the front end

Your banners have been created, the files have been moved, and WordPress now knows to use jQuery and jCarousel when a page loads – almost done!

The last thing we need to do is add the code to grab the banners and make them work.

Open up  index.php or home.php (the location you want to place your banners)  in your theme directory and use this snippet:

</pre>
<div id="banners">
<ul>
<ul><!--?php wp_list_bookmarks( 'categorize=0&category=49<&title_li=&before=
	<li-->&after=</ul>
</ul>
<ul>&show_images=1&show_description=0' ); ?></ul>
</div>
<pre>

This snippet will grab links you created earlier and only show the images. Make sure you change category=49 to your category ID.

Lastly, open header.php in your theme directory. Place the code snippet below in between the <head> </head> tags – usually right after you see wp_head();

jQuery(document).ready(function($) {
$('#banners').jcarousel({
scroll: 1,
auto: 4,
wrap: 'last',
animation: 'slow',
buttonNextHTML: null,
buttonPrevHTML: null
});
});

The jQuery that comes with WordPress runs in non conflict mode, which is why do not use the typical document ready call. jCarousel is very configurable, so I suggest you check out all the different options and make sure your settings are set for the functionality you desire.

Step 7: Profit.

That’s it! If you followed all the steps right you should have a rotating banner on your site.

I found this to be a better solution that any of the plugins I found. We didn’t have to do anything crazy, use posts, or write any plugins. Normally I would provide a demo of this in action but I have a feeling the client I did this for would rather not be mentioned.

If you have an questions or problems, feel free to leave a comment.

If you do expereince problems, a few things to double check/tweak:

• view your source to make sure WP is calling jQuery and jCarousel
• check to make sure you have the correct category ID
• modify the CSS if things don’t render correctly

The sessions are are lined up, there are a ton of great speakers, and many of the characters from #wordpress will be in attendance (*cough* sivel, ansi, jdingman, etc).

Not worried about airfare (Go Southwest! ha) or registration, however I am looking for help on lodging.

There is a hotel within walking distance that has a 15% discount, bringing it down to ~ $210/night. I wanted to see if anyone who was thinking about attending would want to maybe slplit a room.

Alternately, anyone have any other recommendations for places to stay? I’d prefer to not shell out $210 a night by myself unless I must. After all in Texas $210 a night would damn near get you a suite! Stupid inflation.