So far this week, we have learned how to post from the front end. And we’ve expanded on that by allowing image uploads from the front end. We are going to go one step further today and add a meta box to our form. This way we can use the meta box to gather data and feed it into a custom field so we can use that data. The data can be just about anything, really use your imagination here. I’ll give some examples of stuff I’m thinking of, let’s get into it!
Yesterday we covered how to create a form on the front end which allows users to post. It’s time to expand on that idea in a couple of ways. Today we will cover how to allow images to be uploaded along with the post. And we will show show options, you can add the image(s) as attachments and display them with the post, you can assign an image as the_post_thumbnail featured image, or both (which is what I do). If you haven’t reviewed the above linked article, check it out. Now let’s add some image uploads!
Lately I’ve been working on another side project. A wine rating site that we hope to launch soon. But one of the requirements for the site was that once a wine rater logged in, they should have access to a form to rate wines. I didn’t want anyone to have to fuss with the back end of WordPress. I just wanted to present them with a simple form to fill out. Let’s look into how that’s done.
EDIT: I recently found out a better way to add post formats to a Twenty-Ten child theme, scroll to the bottom of the post to check it out!
As we announced yesterday, WordPress 3.1 was released. Hopefully you have all upgraded by now. If not, get to it. Remember to always keep your install up to date with the latest release. Not just for the cool new features, but for security too. Anyway, if you recently upgraded to 3.1, you may be asking yourself the same question as I see others asking. Where are my post formats? WordPress 3.1 promised lots of different post formats, where are they? Let’s answer that question and tell you how to get them going if you don’t have them.
Well, WordPress 3.1 has been out in the wild for hours now. I’m seeing the support requests trickle in, and there is already a very common issue. A strange white gap at the top of the page where the admin bar should be. Let’s fix that, or conversely, if you have the admin bar and hate it, let’s get rid of it!
I have taken a liking lately to Yoast’s SEO plugin. So far, it just plain works. Now I am not the type of guy to worry too much about this stuff. I apply little tweaks here and there and maybe it helps. But the plugin offers a lot of things I like, like bread crumbs, and easy access to my .htaccess file, and robots.txt. Only a few things have to change to enjoy this plugin. Let’s dig in to this.
I just finished a small overhaul of the twentyten theme, using my child theme. Just a few things I wanted changed to start with. So the next articles I write will cover all of that. How to do some real basic customizing. We’ll change the header size, add a background to widgets, widen the theme, etc. But the first thing I did, which is something I always do with my themes is to boot WordPress’ JQuery library in favour of Google’s. Here’s the how and why.
This is a very cool idea. A brand new WordPress plugin, from Mark Jaquith and WordPress. I highly recommend you install this plugin now, and keep it active and updated. The point of the plugin is not to negate the need to update WordPress itself. You still need to do that. Rather, this plugin provides an avenue for quickly applying patches to WordPress before an upgrade is available.
You can check out this thread on the forums to see one of the conversations that may have lead to this idea, or at least show a situation the plugin remedied. I think this plugin can be a very valuable tool if it remains active. And considering who is working on it, that looks like a very positive thing.
Just yesterday we made a post about how I keep my WordPress organized and portable. Then I read this cool article from Justin Tadlock, and I really dig it. Takes the idea I had of organizing your custom functions outside of functions.php and also the portability aspect, and really ramps it up. I’ll probably stick to my method as it’s what I’ve gotten used to. But I recommend reading the article. You can learn a bit about making all your functions into a custom plugin. If nothing else read the article to learn about the MU plugins folder. That’s must use, not multi user by the way!
So here is a little tip I thought I would throw out there for everyone. A way to keep your WordPress functions both organized, and fairly portable. I actually did this by accident, and only now realized how cool it was! We all know that functions.php is the place for your functions. And if you keep adding to it, eventually you can have over a thousand lines of code. It gets cumbersome and confusing! And what if you switch themes? Well check this out.