![\"\"](\"https:\/\/www.withinweb.com\/info\/wp-content\/uploads\/2018\/01\/plug_200.png\")
<\/p>\n<\/p>\n
If you write a plugin for WordPress and want to make it available on WordPress.org, you have to use Subversion to handle revisions, versions and source control.<\/p>\n
There are a number of programs that you can use and which can be installed on a PC or a MAC. Many do use the command line which can be difficult for those not familiar with the particular commands. However, there are a number of client applications that have very good user interfaces which does make the process much easier.<\/p>\n
SilkSVN<\/strong> Windows Command Line Client.\u00a0https:\/\/sliksvn.com\/download\/<\/a> When I first began to look at WordPress and SVN, I wanted to use a visual method of updating. I wanted to click a button and for it to automatically do everything without thinking. However, I found that using a visual interface did not show the point of SVN and when I started to use a text interface, I found I understood the process much better. Also there is a lot of documentation available for the command line interface which is helpful when things go wrong.<\/p>\n The following are some notes that I have made over the years about using the command line system with WordPress which may help if you are having issues. It is based on the WordPress.org documentation but I have added in some extra points.<\/p>\n <\/p>\n As I use Windows I use SilkSVN<\/strong>.\u00a0 Download and install SilkSVN and in the cmd terminal (go to Windows Start and enter cmd.exe), type “svn” followed by the required commands. \u201csvn help\u201d will show help text and will show that SilkSVN is working.<\/p>\n The documentation that WordPress has produced is located here:<\/p>\n https:\/\/developer.wordpress.org\/plugins\/wordpress-org\/how-to-use-subversion\/<\/a><\/p>\n The only issue I have found when using SilkSVN<\/strong> is that you should use double quotes wherever it uses single quotes as in the standard SVN documentation.<\/p>\n Also, always make sure you change directory to where your local repository is located.<\/p>\n <\/p>\n On your computer, first create a local directory which will be your copy of the SVN repository.<\/p>\n In this document I will use my-local-dir to refer to the local directory.<\/p>\n Next, check out the pre-built repository using the co command:<\/p>\n <\/p>\n You will probably be asked your username<\/strong> and password<\/strong> which will be the one you were given when you registered for WordPress.org.<\/p>\n The above command will create a set of folders on your local computer in your local directory called “trunk”, “branches” and “tags”.<\/p>\n The “tags” folder is for your releases and will consist of a number of sub folders that correspond to your version numbers.<\/p>\n The “trunk” folder is where your development version is located.<\/p>\n Copy your files into the “trunk” folder and then you have to let subversion know you want to add the files into the repository:<\/p>\n <\/p>\n Now check in the changes:<\/p>\n <\/p>\n Now copy the trunk files to the required tag folder.\u00a0 In this example I am going to create a folder 1.0.0<\/p>\n <\/p>\n and commit the changes:<\/p>\n So now on the remote repository you should have your released files in the tag\/1.0.0 and your current working development files will also be in the “trunk” folder.<\/p>\n <\/p>\n We want to create a new version of our plugin so we: Essentially the method is the same as described above but with a few more checks.<\/p>\n On your local computer, make sure that your trunk files are up to date.<\/p>\n We can do this by using the SVN update command. (First, change your directory to where the SVN local directory is situated):<\/p>\n <\/p>\n Files in the remote repository are downloaded and update the local files.<\/p>\n Copy over the file or files to your local trunk folder and then let subversion know you want to add those files back:<\/p>\n <\/p>\n Now commit the changes:<\/p>\n <\/p>\n Now do a status display:<\/p>\n You can see the meaning of the status information further at the end of this article.<\/p>\n <\/p>\n At this point, you may have to delete files \/ folders by:<\/p>\n In some cases, you may have to use \u2013force to force the deletion.<\/p>\n <\/p>\n When you do:<\/p>\n you should now see those files\/folders marked for deletion.<\/p>\n <\/p>\n Deleting only deletes it form the local copy and only schedules if for deletion from the repository. You have to then commit the changes by:<\/p>\n <\/p>\n That updates the files in the trunk folder and deletes any marked files.<\/p>\n Now that you have the files checked in to the trunk folder, you can copy over the files to a tag folder as described above.<\/p>\n <\/p>\n You do this by:<\/p>\n <\/p>\n Now, as always, check in the changes.<\/p>\n <\/p>\n Use the assets folder for files like screenshots, banners and icons for wordpress.org site. Note that the assets folder is a separate folder in the root of the folder structure and is not a subfolder of the trunk or tag folder.<\/p>\n Update as the assets folder follows.<\/p>\n <\/p>\n Navigate to the local folder which is the root of the SVN, then enter:<\/p>\n The \u201cadd assets\/*\u201d identifies all files in the assets folder.<\/p>\n <\/p>\n After you add all your files, you need to check in the changes back to the central repository using ci:<\/p>\n <\/p>\n A useful command is \u201csvn status\u201d which gives information about the state of the repository.<\/p>\n <\/p>\n If you see ? in the list of files or folders, it means that they are not under svn control. In which case do \u201csvn add U<\/strong>: Working file was updated <\/p>\n If you get a message \u2018folder name\u2019 is scheduled for addition, but is missing then look at the following document:<\/p>\n https:\/\/benohead.com\/svn-file-scheduled-addition-missing\/<\/a><\/p>\n Also look at:<\/p>\n
\nTortoiseSVN<\/strong> for Windows which can be downloaded at https:\/\/tortoisesvn.net\/downloads.html<\/a>
\nVersions<\/strong> for the Mac which can be downloaded at http:\/\/versionsapp.com<\/a><\/p>\nCommand Line SVN<\/h3>\n
Starting a new plugin<\/h3>\n
my-local-dir \/ svn co https:\/\/plugins.svn.wordpress.org\/your-plugin-name my-local-dir\r\n> A my-local-dir\/trunk\r\n> A my-local-dir\/branches\r\n> A my-local-dir\/tags\r\n> Checked out revision 11325.\r\n<\/pre>\n
my-local-dir \/ svn add trunk\/*\r\n<\/pre>\n
my-local-dir \/ svn ci -m \"Check in to trunk\"\r\n<\/pre>\n
my-local-dir \/ svn cp trunk tags\/1.0.0\r\n> A tags\/1.0.0\r\n<\/pre>\n
my-local-dir \/ svn ci -m \"tagging version 1.0.0\"\r\n<\/pre>\n
Creating a new version<\/h3>\n
\n* Modify the readme.txt with the new version number.
\n* Modify the main php file with the new version number.
\n* Update the trunk folder so that it contains the latest files.
\n* Copy the trunk folder to a new tags folder using SVN.
\n* Check in the changes using SVN.<\/p>\nmy-local-dir \/ svn update\r\n<\/pre>\n
my-local-dir \/ svn add trunk\/*\r\n<\/pre>\n
my-local-dir \/ svn ci \u2013m \u201cadd new files to trunk\u201d\r\n<\/pre>\n
my-local-dir \/ svn stat\r\n<\/pre>\n
my-local-dir \/ svn delete \r\n<\/pre>\n
my-local-dir \/ svn stat\r\n<\/pre>\n
my-local-dir \/ svn ci -m \"New files update\"\r\n> Sending trunk\/my-plugin.php\r\n> Transmitting file data .\r\n> Committed revision 11327.\r\n<\/pre>\n
my-local-dir \/ svn cp trunk tags\/2.0\r\n> A tags\/2.0\r\n<\/pre>\n
my-local-dir \/ svn ci -m \"tagging version 2.0\"\r\n> Adding tags\/2.0\r\n> Adding tags\/2.0\/my-plugin.php\r\n> Adding tags\/2.0\/readme.txt\r\n> Committed revision 11328.\r\n<\/pre>\n
The assets folder<\/h3>\n
my-local-dir \/ svn add assets\/*\r\n>\u00a0 A assets\/sceenshot-1.png\r\n>\u00a0 A assets\/sceenshot-2.png\r\n<\/pre>\n
my-local-dir \/ svn ci -m \u201cAdd assets\u201d\r\n> Adding assets\/screenshot-1.png\r\n> Adding assets\/screenshot-2.png\r\n> Transmitting file data\r\n> Committed revision 1124545\r\n<\/pre>\n
Status Command<\/h3>\n
my-local-dir \/ svn stat\r\n<\/pre>\n
\nTo use this command as with all the other commands, you need to change directory on your local computer to the root folder of the SVN.<\/p>\n
\nG<\/strong>: Changes on the repository were automatically merged into the working copy
\nM<\/strong>: Working copy is modified
\nC<\/strong>: This file conflicts with the version in the repository
\n?<\/strong>: This file is not under version control
\n!<\/strong>: This file is under version control but is missing or incomplete
\nA<\/strong>: This file will be added to version control (after commit)
\nA+<\/strong>: This file will be moved (after commit)
\nD<\/strong>: This file will be deleted (after commit)
\nS<\/strong>: This signifies that the file or directory has been switched from the path of the rest of the working copy (using svn switch) to a branch
\nI<\/strong>: Ignored
\nX<\/strong>: External definition
\n~<\/strong>: Type changed
\nR<\/strong>: Item has been replaced in your working copy. This means the file was scheduled for deletion, and then a new file with the same name was scheduled for addition in its place.
\nL<\/strong> : Item is locked
\nE<\/strong>: Item existed, as it would have been created, by an SVN update.<\/p>\nProblems, problems, problems<\/h3>\n