Go to Top

Uploading a WordPress plugin to the WordPress svn [Windows]

So, you’ve just created a WordPress plugin and had it approved, great news, this guide will help you with uploading a wordpress plugin to WordPress svn.

However looking at the wordpress guide here on how to upload your plugin to the SVN can be very confusing, especially if you’re not very comfortable with the command line way of doing it or if you’ve never worked with svn before.

I’ve created this guide to help simplify the process of uploading a wordpress plugin to WordPress svn and hopefully make it easier for more people to create wordpress plugins.

This guide is for people using windows. When i’ve got my mac back up and running i’ll create another guide for mac users.

I’ve tried to make this guide as simple as possible for people to follow.


1) Ensure your plugin has been approved by wordpress.

2) Have the SVN url for your plugin given to you in the email when your plugin request was approved.

3) Download and install RapidSVN for windows from here: RapidSVN

4) A readme.txt for your plugin, created following the standard set by wordpress here. You can validate your readme.txt here using the WordPress Readme.txt Validator.


1) Open RapidSVN

2) Right click on bookmarks and select ‘Add Existing Repository’

3) Enter your Repository URL in the pop up box that comes up as given to you by WordPress when your plugin was approved.

4) Press ok, this will add your wordpress SVN as a bookmark on RapidSVN

5) Right click on the repository you have just added to your bookmarks and select ‘Checkout New Working Copy’. Enter a local path for where you want to store the plugin locally then press ok. This process will create a local copy of your svn. Which will allow you to add all your files to the correct folders.

6) Copy the files for your plugin along with the readme.txt for your plugin into the trunk directory on your local copy of the svn repository.

7) Once all the files are copied into your local directory you should see them all listed when you highlight trunk on your local bookmark.

8) Right click on trunk and go to ‘Commit’. Enter a log message e.g. Initial Upload, tick recursive and click OK.

9) Thats it, if you now browse to your plugins location you should be able to see it and download it. This may take a couple of seconds while WordPress refreshes it’s cache.

Hope this guide will help some people.

Questions, queries and comments are always welcome.

, , , ,

4 Responses to "Uploading a WordPress plugin to the WordPress svn [Windows]"

  • JayDeep Nimavat
    October 4, 2014 - 1:36 pm Reply

    Hello wordpress friend,

    I have created new version of “JDs Portfolio” plugin,

    I have done change,

    – deleted all folder and files from Repository trunk directory and uploaded new files and folder of new plugin version.

    – Created new directory 1.1 in Tags directory where 1.0 is already available and I uploaded all new files and folder of new plugin version in 1.1.

    The duration of uploaded new version plugin is more than one day.

    The problem is that it still give old version of plugin when anyone download it, and shows in Developer option as other version, as current version it display me old version 1.0.1 of JDs Portfolio plugin.

    Please help me to solve :
    How can I apply new version of plugin as current version?

    your good suggestion most appreciate,
    Thanks a Lot’s,

    • Jo
      October 4, 2014 - 1:57 pm Reply

      Hi JD,

      Your readme.txt in trunk still has the stable tag of 1.0, if you want to set 1.1 as the stable version just go ahead and change this. If trunk always holds the latest version and you don’t use it while developing you can set your stable version to trunk, personally I would recommend setting it to 1.1 then it will use the files from your tags folder.
      Hope this helps, let me know!


  • anymous
    April 27, 2014 - 8:18 am Reply

    Thanks, but My plugin’s trunk folder yet empty. And after commit I didn’t get any message. And my plugin’s files and folders have unversioned status.

    • Jo
      May 19, 2014 - 10:00 pm Reply

      So after you’ve committed it is still empty? What if you set the folder to under version control?


Leave a Reply

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

− 5 = four