Linux 软件免费装
Banner图

Svnless

开发者 kais1977
更新时间 2026年11月19日 05:45
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

publish developer release svn deploy

下载

1.0.0

详情介绍:

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:
  1. Upload the zip of your new version.
  2. The plugin checks it and shows exactly what will change online: files added, modified, deleted.
  3. 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 After publishing 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: Use the SVN password created in your WordPress.org profile (Account & Security), not the password of your WordPress.org account.

安装:

  1. Install the plugin from Plugins → Add New, or upload the svnless folder to /wp-content/plugins/.
  2. Activate it.
  3. 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.
  4. 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.

屏幕截图:

  • The check of a zip, with the list of changes.
  • Publishing, step by step.
  • The publication is done and checked.

升级注意事项:

1.0.0 First version.

常见问题:

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.

更新日志:

1.0.0