| 开发者 | bytesvibe |
|---|---|
| 更新时间 | 2026年11月8日 00:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
manage_options capability on the site can enable/disable it and edit the whitelist at any time from Settings → WLock, and can deactivate the plugin like any other./wp-content/plugins/wlock, or install directly through the WordPress plugins screen.It's the folder name the plugin installs into under wp-content/plugins/, which is also the last part of its WordPress.org URL. For example, Akismet installs to wp-content/plugins/akismet, and its directory page is https://wordpress.org/plugins/akismet/ — so its slug is akismet.
No. Updates to anything already installed are never blocked, only fresh installs.
Yes, deliberately. Anyone with the manage_options capability can edit the whitelist or deactivate the plugin. WLock is a self-managed safeguard, not a hard lock against the site's own administrators.
Yes. The check runs after a package is unpacked, regardless of whether it came from the repository or a direct upload.
All settings are saved through WordPress's own Settings API, which handles the nonce and capability checks for you, and every value is sanitized on save and escaped on output. Only users with the manage_options capability can view or change the whitelist.