Get flash to fully experience Pearltrees
WordPress has a huge community with a active user base contributing in the form of excellent plugins, however most of the plugins are scattered all over the internet making it more and more difficult for users to find them and also for plugin authors to send out updates whenever there are any. However to solve the problem there is WordPress Extend , a place where plugin developers can add their plugins, making it easier for others to find them. It would be really good if more and more developers started using WordPress Extend to distribute their plugins, I would like to discuss a few benefits developers get when they add their plugins to WordPress extend to make that decision easier. Hint: If you are unaware of how to add your plugin to WordPress Extend, read our earlier tutorials. Here are the benefits of adding your plugin to WordPress Extend. Free Hosting Space
I was tinkering with a WordPress database the other day and was nosing around through some tables, looking for some statistical data which I never found, and noticed that a few of the tables were storing data in an unusual format (to me at least). Specifically one record I found looked like this: Whoa.
I’ve had a few patches committed to WordPress core in the last few versions, and have sadly neglected to do writeups about them so that others could take advantage of the new features. I hope to remedy that in the next few posts. First off, WordPress 2.9 has a new feature that allows you to add to the list of headers that are checked when you run either get_plugin_data() or get_theme_data() . For example: Let’s say you want to make a plugin that works with other plugins.
Use Classes in your WordPress plugins to increase code portability and reduce name conflicts – NerdaphernaliaOne of the most powerful features of WordPress is the huge community of developers making plugins that extend the software far beyond what the core application provides. It also allows people to add just what they want to use, rather than having a single bloated homogeneous download. There are drawbacks as well, of course. Any time a software package opens itself up to third-party additions, there is a potential for mischief. With WordPress, different plugins can end up stumbling over each other, as each is coded for the core but doesn’t anticipate other plugins. You can also have naming conflicts — when functions or variables in different plugins are given the same name.
If you’ve ever written a plugin for WordPress you’ve probably dealt with giving the end user options. Unless you’ve taken the low road and forced the user to directly edit the plugin file, “options” means a Settings screen in the WordPress admin, and most likely you are storing those options in the blog’s wp-options table. Over time, bloggers using various plugins can end up with hundreds of extraneous records in their options table * . If they ever stop using a plugin, or if they ever want to manually clear out options, this job can be made difficult by all the clutter, and the problem is made far worse when plugin authors add a new record for each separate setting in a plugin. Beyond the mess, plugins written this way generally make many more calls to the database than they need to, which adds unnecessary burden on the server.
Most WordPress plugins, if not all, have options (also known as settings) that are stored in the blog’s MySQL database, ready to be called upon when needed. In this tutorial we will explore three different PHP methods to store options. The first and most commonly used method is to save each option with separate variables. To save the option: We use the $_POST variable to save form data in a variable. The variable is then used to update an option. $variable = $_POST['option01']; update_option('my-plugin-options', $variable);
Post Formats Languages : English • 日本語 • Português do Brasil • Русский • 中文(简体) • 中文(繁體) • ( Add your language ) Intro Post Formats is a theme feature introduced with Version 3.1 . A Post Format is a piece of meta information that can be used by a theme to customize its presentation of a post. The Post Formats feature provides a standardized list of formats that are available to all themes that support the feature.
Template Tags Languages : English • Français • Português do Brasil • 日本語 • Русский • ไทย • Türkçe • 中文(简体) • 中文(繁體) • ( Add your language ) Template tags are used within your blog's Templates to display information dynamically or otherwise customize your blog, providing the tools to make it as individual and interesting as you are. Below is a list of the general user tags available in WordPress, sorted by function-specific category. For further information on template tags and templates in general, see the following:
Pluggable Functions Pluggable functions were introduced in WordPress 1.5.1 These functions let you override certain core functions via plugins . The most up-to-date list of core functions that WordPress allows plugins to override is available at wp-includes/pluggable.php . WordPress loads the built-in functions only if they are undefined after all plugins have been loaded. Pluggable functions are no longer being added to WordPress core. All new functions instead use filters on their output to allow for similar overriding of their functionality.
I have several WordPress plugins. They’re hosted on the WordPress.org plugin repository , but I also have a page for each plugin on my own site . I’ve found it tedious to have to update both places separately. Things get out of sync, or worse, I put off plugin updates because I loathe updating two places (with two different formats) with the same information. The WordPress plugin repository has an API. Let’s use it!
There has been a vigorous discussion going on regarding what data WordPress installs send to WordPress.org when doing update checks. Because WordPress (the software) doesn’t know whether a theme or plugin is listed in the WordPress.org repositories, it has to check them all, and let the repository sort it out. Some have expressed concern that private plugins developed for a single client could contain sensitive information in their headers, like contact information for the developer, etc. If you, as a plugin or theme developer, would like to exclude one of your plugins or themes from the update array, the following code will do the trick. For plugins:
Block-level comments are useful for commenting out an entire block of code in PHP, CSS, and other code contexts. The only problem with this is that when you go to re-activate this code, you have to change both the opening and closing comment markers. That’s a pain. While I was at WordCamp NYC last week, I saw Daisy Olsen using a very clever trick in her lightning round talk.
I love WordPress’ sidebar widgets. I also despise coding them. I love how they let me offload menial management tasks directly to clients, avoiding all the “Change this word to another word!”
I’ve had a bunch of people ask me how they could get started as a WordPress developer or consultant. Rather than answer them all individually and privately, I’m putting it up for all to see. Become involved with the development community Join the wp-hackers mailing list . Participate when you have something useful to say, or an interesting question/problem to pose to other WP developers.