Using Subversion to Upload WordPress Repository Plugins


Websites Providing the Best Work from Home Business Opportunities After you create your WordPress plugin, the next step is approval from WordPress. WordPress Developer Center hosts forums, learning centers, FAQs and other developer tools. You must first register for a WordPress developer account.

The developer account gives you access to all things related to WordPress development, and it has a section where you can submit your plugin to the WordPress repository. The WordPress repository is where blog owners can browse the latest additions and conveniently install the plugin to their blog software.

How to Use Subversion with Windows

A free interface application is available called TortoiseSVN. This application makes it easy for Windows users to upload to the WordPress change control server. When you receive the WordPress email accepting your plugin (submitted after you create your account), a link is given to your repository directory. There are two main directories in your repository:


Trunk: The trunk directory contains your current version. This directory packages your files, so WordPress users can download the plugin to their blog.

Tags: The tags directory is where you set up versions. You create a directory such as “1.0” and save the current, stable version of your plugin.

Use the TortoiseSVN to connect to the WordPress plugin subversion repository address sent in your confirmation email.

How to Use the Version Control System

After you create a WordPress plugin and test its stability, upload all files (including the mandatory readme.txt) to the Subversion “trunk” directory using TortoiseSVN.

Move to the “tags” directory. Create a directory that matches the currently stable version. For instance, if this is the first promotion of the plugin, create a directory labeled “1.0.” Upload the files a second time to this directory.

Creating Updates in Subversion

The next time you upload an update for your code, create a new directory in the Subversion “tags” directory. For instance, your next plugin release can be “2.0.” The readme.txt in your plugin directory must match the versions listed in the tags directory. Additionally, the WordPress comments section in your main code must match the plugin version.

The comments, readme.txt and directory names all match, so Subversion is triggered to update the plugin information listed in the repository list when users browse new available WordPress plugins.

After you get used to the change control software, uploading and managing your WordPress plugins is a breeze. You can also roll back changes, if you receive several bug reports on a new plugin release. Rolling back changes is the main advantage for using version control software

Comments are closed.