Description
Publishing a plugin on WordPress.org usually means installing an SVN program, learning its commands, copying files into trunk, creating a tag, and hoping you did not forget anything. Svnless does all of that from your WordPress admin, with buttons:
- Upload the zip of your new version.
- The plugin checks it and shows exactly what will change online: files added, modified, deleted.
- Type your SVN password and click Publish.
Everything goes online in one single commit: the files in trunk and the new version folder (tag), together. If anything goes wrong on the way, the upload is cancelled on WordPress.org and nothing is published. You never get half a release.
Add your plugin once (its slug and your SVN username), then publish its new versions whenever you want. The username is checked with WordPress.org when you add it, so a typing mistake is caught at once. You can switch to another plugin at any time.
No SVN program is needed on your server, and no command line: the plugin speaks the SVN protocol itself, in plain PHP, through the WordPress HTTP API.
Checks before anything is sent
- The zip must contain one folder named like your plugin.
- The “Version” of the main file must be the same as the “Stable tag” of readme.txt.
- A version already online is never changed: if it is identical, you get “nothing to send”; if it is different, you are asked to raise the version number.
- You cannot publish an older version than the one online by mistake.
- The PHP syntax of every PHP file (up to 1.5 MB each) is checked with PHP’s own parser (the code is never run).
- Hidden files (.git, .gitignore…), node_modules and archives are refused. Files made by macOS and Windows (.DS_Store, Thumbs.db) are left out.
- Damaged files are detected, and every file is checked again just before it is sent.
- Warnings for a missing or old “Tested up to”, a missing “Requires PHP” or “License”, a short description longer than 150 characters, a text domain that does not match the slug.
After publishing
- The plugin reads the new revision back from WordPress.org and compares it with what you sent.
- The My plugin page shows what is online: stable version, “Tested up to”, versions, last change.
Svnless Pro
Svnless Pro is a separate plugin for developers who maintain many plugins, sold on nuxwp.com. It adds page images (banners, icons, screenshots), a history with an e-mail after each publication, and a dashboard for several plugins side by side. This free plugin is complete on its own and does not need it.
Security
Your SVN password lets anybody publish code to every site that uses your plugins, so it is handled with care:
- By default, you type it at each publication. It is kept only in your open page while the publication is being sent, and never saved: not in the database, not in a log, not in a cache.
- It is never given to the WordPress HTTP functions or hooks that other plugins can watch or log: it is handed to the connection itself (cURL), at the very last moment, only for the WordPress.org address. It never appears in error traces either.
- Certificate checks are always on and redirects are never followed for these connections, even if another plugin tries to change that.
- Typing the password is refused when your admin is not using HTTPS.
- Optional: on a private site used only by you, you can put it in wp-config.php (
define( 'SVNLESS_PASSWORD', '…' );). It is then never shown and never stored in the database. The plugin warns you if the site looks like a live shop. - Only administrators can use the plugin, and every action is protected by a nonce and a capability check.
- The plugin only talks to WordPress.org:
https://plugins.svn.wordpress.org(the plugin files and your publications: certificate checks always on and no redirects, even if another plugin tries to change that) andhttps://api.wordpress.org(public plugin information, no account, no redirects). See “External services”. - Uploaded zips are never extracted: every file is read straight from the archive. Paths with “..”, absolute paths, symbolic links, password-protected entries and oversized archives are refused. Uploaded files are kept in a private folder and deleted after use (at the latest after two hours).
Use the SVN password created in your WordPress.org profile (Account & Security), not the password of your WordPress.org account.
External services
This plugin connects to WordPress.org only: the plugin repository (https://plugins.svn.wordpress.org), the Subversion server that hosts the plugins of the WordPress.org directory, and the WordPress.org plugin information API (https://api.wordpress.org/plugins/info/1.2/). These are the only outside services it uses, and it only connects when an administrator uses the plugin screens:
- Reading (no account): when you open the My plugin page, add a plugin, or check a zip, the plugin reads the public files of the plugin you added (list of files and their fingerprints, readme.txt, list of versions). WordPress.org receives your server’s IP address and the plugin slug.
- Account check (no account): when you add a plugin, change its SVN account, or click Refresh while the account has not been found on WordPress.org yet, the plugin reads the public information of that plugin (its owner and contributors) to catch a mistyped username. WordPress.org receives your server’s IP address and the plugin slug; your username is compared on your site and is not sent.
- Publishing: when you click Publish, the plugin sends your SVN username and password (HTTP Basic authentication over HTTPS), the files of your zip, and the commit message you chose.
The service is provided by WordPress.org: Privacy Policy, Plugin Directory Guidelines.
For developers only: when the SVNLESS_ENDPOINT constant is defined in wp-config.php, all the Subversion traffic (including the SVN username and password) goes to that test server instead of WordPress.org, and every Svnless page shows a warning. Nothing else can change this address. The account check still reads the public WordPress.org information.
The plugin pages also show links to wordpress.org, plugins.trac.wordpress.org and nuxwp.com; they are only opened when you click them. The picture that shows where to find the slug is included in the plugin (nothing is loaded from outside).
Installation
- Install the plugin from Plugins → Add New, or upload the
svnlessfolder to/wp-content/plugins/. - Activate it.
- Open Svnless → My plugin and add your plugin: its slug (the end of its wordpress.org address) and your SVN username. The picture on that page shows where to find the slug. The username is checked with WordPress.org before the plugin is added.
- Open Publish a version, choose the zip of the new version, click Check this zip, review the changes, type your SVN password and click Publish.
The plugin must already be approved on WordPress.org: this plugin publishes new versions, it does not submit new plugins.
FAQ
Do I need SVN or a terminal on my server?
No. The plugin speaks the SVN protocol itself, in PHP, over HTTPS. It needs the PHP “zip”, “dom”, “curl” and “tokenizer” extensions, which almost every host has.
What must the zip look like?
One folder named like the plugin slug, with the plugin inside: my-plugin/my-plugin.php, my-plugin/readme.txt, and so on. It is the same zip you would install on a site.
What happens to files I removed from my plugin?
They are removed from trunk, and the new version folder does not contain them. The page shows them in the “Deleted” list before you publish.
What if somebody changes the plugin online between my check and my click?
The plugin notices it and stops before sending anything, so you never overwrite a change you have not seen. Check the zip again to see the new differences.
What if the connection is lost while sending?
Nothing is visible on WordPress.org until the very last step. If the page is closed during the sending, the publication is listed under “Unfinished publications” on the My plugin page: open it to continue it or cancel it. If the connection is lost during the very last step, the plugin checks on WordPress.org whether the publication went through, and never sends it twice.
My server runs Nginx: are the uploaded files protected?
Uploaded zips are kept in wp-content/uploads/svnless-private/, in a folder with a random name, and deleted after use (at the latest after two hours). On Apache and IIS the folder is also closed to visitors automatically. On Nginx, add this rule to your server configuration:
location ^~ /wp-content/uploads/svnless-private/ { deny all; }
Where is the SVN password stored?
Nowhere, unless you choose to define it in wp-config.php yourself.
What if I type a wrong SVN username?
When you add the plugin, Svnless compares the username with the owner and contributors shown on the plugin page on WordPress.org. If it is not there, nothing is added and you can fix it. SVN usernames are case-sensitive: type yours exactly as you sign in to WordPress.org. A committer who is not listed on the plugin page can still be added: tick “I am sure” and add it again. For a plugin that is approved but not published yet, WordPress.org shows no owner, so the account is checked by WordPress.org at your first publication. You can change the account at any time with “Change SVN account” on the My plugin page. In every case, WordPress.org itself refuses a publication from an account that is not allowed, and nothing is sent.
Can I publish another plugin?
Yes. Remove the current plugin from Svnless (nothing changes on WordPress.org) and add the other one: its slug and your SVN username.
Does it support multisite?
Yes. On multisite, only super administrators can use it (publishing a plugin sends code to every site that uses it, network sites included), and the wp-config.php password is only used for super administrators. Each site keeps its own plugin. The capability can be changed with the svnless_capability filter.
Screenshots
Changelog
1.0.0
- First version: publish a version of your plugin (trunk + version folder in one single commit), checks before sending, SVN username checked with WordPress.org, what is online, verification after publishing.




