| 开发者 | kais1977 |
|---|---|
| 更新时间 | 2026年11月19日 05:45 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
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.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) and https://api.wordpress.org (public plugin information, no account, no redirects). See "External services".svnless folder to /wp-content/plugins/.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.
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.
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.
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.
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.
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; }
Nowhere, unless you choose to define it in wp-config.php yourself.
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.
Yes. Remove the current plugin from Svnless (nothing changes on WordPress.org) and add the other one: its slug and your SVN username.
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.