Publishing and then updating plugins on WordPress.org repository is a bit tricky on Mac. It is easier on Windows using TortoiseSVN svn client, not so on Mac as there is no Tortoise alternative svn client available, but you can use built in Mac terminal to publish and update WordPress plugins in the Plugin Directory.
The WordPress Plugin Submission Process
Let’s assume that you have already read the guidelines and instructions here.
Also that you have checked the availability of your plugin slug and name in the WordPress Plugin Directory.
Now that you have created the plugin, make sure it works, and validate its Readme file here.
Once your plugin ready, submit it here to WordPress directory and wait for the approval.
Once approved and having got access to svn repository, here are the steps to connect with svn repository and publish it on WordPress directory.
Step 1: SVN Check out
Create a directory named “wp-svn” in your Documents folder. Then open Terminal and type:
or simply drag the directory to terminal window. You will see the path in the terminal, write cd before it and you are in your working directory.
Once in the svn directory, enter this command in Terminal:
svn co http://svn.wp-plugins.org/your-plugin-name
Make sure you replace “your-plugin-name” with that of your own plugin slug provide you in your approval email from wordpress.org guys.
Step 2: Adding files
if you have added any new files from you last checkout, you must add them in the repository by running this command.
Before you can add files in an unversioned svn directory, you have to add the directory itself to the versioning:
svn add directory_name
For adding files:
svn add file1 file2
Normally svn add * works. But if you get message like svn: warning: W150002: due to mix off versioned and non-versioned files in working copy. Use this command:
svn add --force .
Step 3: Update Plugin Files
Using the checked out files in your local WordPress svn directory, make any changes to the files. once you have tested everything and ready to commit, you’re ready to check in. You should not commit to WordPress repository too often and not use it as dev repository, rather only publish the files when they are tested and ready for release.
Step 4: SVN Check in
Check in your changes by navigating to the plugin directory on your local machine. Either drag any file from your WordPress trunk directory into Terminal and the path will be added there or in Terminal, enter: cd ~/Documents/directory-path/your-plugin-name
Then from within your plugin trunk directory, check in the modified plugin by this command:
svn --username=UserName ci -m "Updating version 1.0.0"
Congratulations, your wordpress plugin has been released in directory if it was initial release, or has been updated whatever the case maybe.
In this last terminal command, the “UserName” is your username for the WordPress Plugin Directory, and “Updating version 1.0.0” is a comment that you can customize to specify or describe the update.
Step 5: SVN Tagging
Fifth step before plugin is completely published, you must tag the trunk version in repository by running following command.
svn --username=UserName copy https://plugins.svn.wordpress.org/your-plugin-name/trunk https://plugins.svn.wordpress.org/your-plugin-name/tags/1.0.0 -m "tagging version 1.0.0"
In above command 1.0.0 is the version number that you are tagging and your-plugin-name represents your plugin name. It must match with the wordpress plugin version number that you have released.
Step 6: SVN Update
One last step, you must update the local repo, svn update brings changes from the repository into your working copy. If no revision is given, it brings your working copy up to date with the HEAD revision.
svn update [name-of-directory], or
cdto that directory and type
Hope that helps!
hi, thanks a lot bro