Categories
WordPress

Adding your own WordPress Plugin

Having just created and submitted my first WordPress plugin, I thought I’d go through the process. And I have to say, WordPress don’t make it easy.

Assuming you have your plugin written and tested, you first need to submit it to WordPress for them to create a subversion repository (basically an archive where you can store it).

  1. Make sure you’re signed up (and signed in) to WordPress.org and head over to the Developer section within the Plugin Directory.
  2. From here, there’s an option named “Add Your Plugin“.
  3. You need to enter the name and description of your plugin and, optionally, a link to it.

That’s it for that. Now you need to wait for WordPress to send you a link to your repository.

Meantime, you need to create a readme.txt file to go with your plugin. This will not only be bundled with your download but will be used for your plugin entry on the WordPress site. What I didn’t know is that these files, although plain text, have a special markup language within them.

  1. WordPress provide an example, and I just took this and modified it appropriately.
  2. There is also complete documentation on the markup language used.
  3. Once you’ve written it, you can validate it.

So, now you have your plugin, a valid readme.txt and, hopefully, a repository URL from WordPress.Now it all got a lot fuzzier.

The WordPress instructions lept straight into a load of unexplained commands, not explaining, amonst other things, that you need SVN installed to use these. I came across another blog which recommended installing TortoiseSVN, which has a GUI interface. I did this but soon found the instructions on this alternative blog didn’t match what I was seeing (possibly a different version of TortoiseSVN?).

What I did was to use the Repo-browser context menu option. This provides you with a drag-and-drop interface to your repository (you use the URL that WordPress supplied plus your WordPress.org username and password). Head back to the WordPress site instructions on ensuring that you place your files in both the “trunk” and create another, versioned, copy under “tags”.

Once this was done my WordPress plugin page sprang to life, taking its details from my readme.txt file.

And that was it.

Categories
WordPress

Displaying code in WordPress

After experiencing some problems around displaying code in WordPress (mainly around the code lines being too long and wrapping off the side of the page) I installed Dean’s Code Highlighter.

Now, don’t get me wrong, this is an excellent plugin. However, I found a flaw in it after someone reported a problem with the WordPress plugin that I launched yesterday. They’d copy and pasted the example code from my instructions page and it didn’t work. It turns out that the code highlighter had taken my single quotes and converted them to open and closed single quotes. Which broke the code.

I had a good look at the plugin code but couldn’t easily work out a solution. In the end I realised that I simply didn’t need code highlighting so turned the whole thing off. Instead, I used a similar style and applied to the bog standard CODE wrap. The only down-side is that I have to wary of the line wrapping again.

Categories
WordPress

WordPress Tags

I’ve found – and I know others have too – that you can’t delete tags in WordPress from the tags management screen.

However, after recently upgrading my WordPress version I found that, after leaving my plugins disabled by accident, it would work. Enabling my plugins then broke the functionality. Unfortunately, my good fortune didn’t go as far as thinking to test it and try and work out which plugin is the cause.

So, yes, that’s the cause. But exactly what I’m not sure.

Next time I have some tags to delete and some times on my hand, I’ll try and work it out further.