When using WordPress as a CMS, situations often arise where you need to display, add or update content on your WP site without turning to plugins. While bolting in some PHP alone can do the job, nothing is more seamless that the magic of jQuery’s AJAX.
QueryPosts.com is a new reference for developers that aims to be an even better WordPress code reference than the codex. Explore the site a little bit and you’ll find that function pages have tons of information, source, links to trac and github, and a list of similar and/or related functions.
When you’re migrating a WordPress site from one server to another, there’s a point where you just need to stop writing posts and making changes in the old location. Perhaps you’ve made your final backup before preparing to move the site. Or maybe you’re waiting for DNS to propagate, which can sometimes take up to 48 hours. This isn’t usually such a problem, but with a multi-author site you’ll need to get everyone on the same page.
Clutter. I hate it. Crap everywhere, post-it’s, scribbles, hamburger wrappings, fiftythree beer cans, a broken pencil, an iPhone charger, USB cable for unknown peripheral, a hand out from the local Thai place, two printed quotes, a dirty espresso cup, napkins, some coins, two iPads, a pen for the Wacom board nobody uses, and so on. Clutter. I really do hate it.
Tons of menu items and unnecessary options. I hate that too. Option pages for themes and plugins that are just over the top, settings for everything which leaves the end-user staggered and with nothing that truly helps.
The Daily WordPress Reference is a very handy WordPress email newsletter for developers. I only recently discovered it and subscribed immediately. Each newsletter contains one function, a description of what it does, usage, parameters, return values and a few examples of how to use it. At the end it links to the codex where you can find out more information.
You can view past issues of the newsletter on the Daily WordPress Reference signup page to see if you like the content they’re sending.
Here’s an example of what the newsletters look like in your inbox:
I’m going to start you guys off with a quote today, signed the always excellent Konstantin Kovshenin:
Is it considered “cool” to copy/paste all my plugins into my theme’s functions.php file?
Now why would he write something like that? It is part of a paragraph (obviously) that makes fun of all these “paste this code into your theme’s functions.php file” tutorials out there. Sarcasm all around, and you all know how I love that shit. And irony, irony is also great fun. Ironing, not so much.
There comes a time in every blogger’s life when they yearn to create their own WordPress widget.
They grow tired of the default selection of widgets that ship with WordPress, and try as they might, they just can’t find what they’re looking for in the WordPress Plugin Directory.
If this sounds like you, perhaps it’s time to step up your game and . . .
Getting started with widget development
At a minimum, you’ll need the following:
An understanding of the Widgets API
At least a passing familiarity with PHP scripting
If you pay much attention to trends and developments in the WordPress universe, you’ve no doubt heard something about the web programming technique known as Ajax, and how it can be used to make your WordPress site more dynamic, engaging and downright sexy.
If you haven’t, then it’s high time you got schooled.
The mighty Ajax
Prerequisites: If you have not read Part 1, you should do that now.
Class is in Session
Yesterday we got started with the first piece of the plugin puzzle, the header. This is what tells WordPress all about your plugin and also includes your license information. Today I will show you a little bit more about developing your own plugin.
If you are a theme “tweaker” or even a full-blown “frameworker”, Google Chrome has an extremely powerful tool that can make your life a whole lot easier. Chrome Developer Tools allows you to inspect and edit (in real time) any web site. Any edits you make will not of course be effected in reality, but the Developer Tools emulates the change in your browser window so that you can inspect the impact of your actions.