WordPress: My First Plugin

I made my first WordPress plugin today. It’s very simple and for my own site only: It adds the script bits for the Piwik analytics of my personal blog. It showed me just how easy it is to create a plugin in WordPress. Normally, for clients, I’d just add additional functionality in the “functions.php” file, but for my personal site I’m using the new default theme for WordPress 3.0 (in part out of laziness and in part to try out some of the new features it introduced). I decided rather than modify the theme at all I’d create a plugin, and was happy with how easily and well it worked.

Creating a simple plugin involves creating a PHP file in the ‘plugins’ folder (in ‘wp-content’). It can be named anything, and could also go inside of a folder if multiple files are needed. The plugin file starts with a snippet like the following:

Plugin Name: nameOfPlugin
Plugin URI: http://pluginURI
Description: descriptionOfPlugin
Version: number
Author: authorName
Author URI: http://authorURI
License: licenseName

This could be followed by license information in comments as well. For a simple plugin like the one I made, it needs no license, so I said “Private” and has no plugin page, so I left that blank.

After that bit, you can add anything you might add to functions.php, usually connections to the various WordPress hooks. In my case, I wanted the Piwik script code to be output by “wp_footer()” in the template, so I added:

add_action('wp_footer', 'plgpiwikAddScriptTags');

which will run the function “plgpiwikAddScriptTags” when “wp_footer()” is run, then created a function that echo’s the appropriate script tags:

function plgpiwikAddScriptTags() {
<script>// piwik script stuff goes here, as well as other html stuff.</script>
        $fncContent = ob_get_contents();
        echo $fncContent;

I only output the tag if the user is not logged in and use the output buffer out of habit and for good measure, in case I want to do something with the resulting string.

I think I will use these plugins more often, perhaps for stuff that would otherwise go into “functions.php” but is not required by the theme. It allows separation of functionality and better control of updating with separate versions.

Find more information about writing WordPress plugins

Published by


I am a quiet person from Northeast Ohio. I work as a web developer. I like computers, music, and many other things.

Leave a Reply

Your email address will not be published. Required fields are marked *