| 开发者 | nitspatel |
|---|---|
| 更新时间 | 2026年7月29日 15:06 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-login.php to a slug you choose, such as /my-login/. Requests to wp-login.php, and requests to /wp-admin/ from anyone who is not logged in, are redirected to the home page (or shown a 404, your choice) instead of reaching a login form.
This does not change any core files, database table, or rewrite rules. It intercepts the request early and serves WordPress's own login logic at your chosen URL, so every feature of the normal login screen, including lost password, registration, and logout, continues to work exactly as before, just at a different address.
Features
/wp-login.php by default. It is not a replacement for strong passwords, two-factor authentication, or a login rate-limiting plugin, and it should be used alongside those, not instead of them.
devorbit-login-shield folder to /wp-content/plugins/, or install directly through Plugins > Add New in your WordPress admin.Connect to your site via FTP/SFTP or your hosting file manager and delete or rename the devorbit-login-shield folder inside /wp-content/plugins/. This deactivates the plugin immediately and restores normal access to /wp-login.php and /wp-admin/.
Because the "Public login links" setting is on. Those links are generated from your login URL, so any page that renders one, such as the Meta widget or a comment form set to require registration, would print your custom URL in its HTML for anyone to read. With the setting on, the links are removed instead. Turn it off under Settings > DevOrbit Login Shield if your site needs a visible login link.
Yes. The password form posts to wp-login.php?action=postpass, which only sets a cookie and redirects, so that one request is allowed through. It never renders a login form.
It works on a per-site basis. Network admin (/wp-admin/network/) access is not restricted by this plugin.
No. Requests to admin-ajax.php and admin-post.php are always allowed through, whether or not the visitor is logged in.
No. It stores two small options (your chosen slug and your preferred blocked-request behaviour) and removes them automatically when the plugin is deleted.