| 开发者 |
wolfdevs
realblackz |
|---|---|
| 更新时间 | 2026年10月4日 21:55 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wd-restrictions folder to /wp-content/plugins/By default, administrators have full access to everything. You can customize this in the settings.
Yes! Select multiple pages in the Pages tab.
They will be redirected to the URL you specify (defaults to homepage). You can also redirect to the login page or any custom URL.
Yes! Each restriction type (dashboard, pages, post types) can have its own redirect URL.
Absolutely! Any public post type will appear in the Post Types tab.
Yes! The plugin includes compatibility with popular caching plugins including WP Rocket, W3 Total Cache, WP Super Cache, and LiteSpeed Cache.
Create and publish a page containing [wd_restrict_login_form]. In Settings > WD Restrictions > Custom Login, select that page and enable custom login. Existing installations keep this feature disabled until configured. The page must not be password protected.
Forms submit to WordPress's native login endpoint. Errors, password-reset confirmation, reset links, recovery mode, and reauthentication use the native WordPress screens. The custom page exposes login_form and lostpassword_form hooks. Some security plugins require scripts or additional UI from the native screen; use the native fallback when needed. Compatibility with every CAPTCHA or two-factor plugin is not guaranteed.
Keep Native Login Fallback enabled and visit wp-login.php?wdr_native_login=1. This is available while logged out and still requires valid credentials. If necessary, add define( 'WD_RESTRICT_DISABLE_LOGIN', true ); to wp-config.php to disable all custom login behavior. This does not disable other access restrictions.
An explicit redirect_to destination takes priority. Otherwise Previous Page uses a local referring page when available, falling back to home. Login screens are excluded. Custom redirect URLs must be local unless their host is allowed by WordPress's allowed_redirect_hosts filter.
Exclude it from full-page caches and CDN caches. The plugin sends no-cache headers and signals supported cache plugins, but a cache serving an existing response before WordPress runs must be configured separately. Purge caches after changing the login page.