A must have plugin for wordpress blogs
By using Hide Login+ you can simply change most important URLs that are being accessed every day, keeping them safe and secret.
For those upgrading from previous version: please check installation steps
- No need to modify
wp-config.phpany more (see installation steps)
.htaccessbackup file is created before changes take effect (named
- Recoded to be latest WordPress version compatible
- Have secured and hidden login page
- Customized URLs for the most important parts of your WordPress installation
- Control access over
- Easy back-to-defaults ability without frustration
- Define custom URL slug for login, logout, registration, lost password & admin pages
- Able to prevent access to
- See your
.htaccesscontent after changes have been successfully updated.
Revert to default configurations on plugin deactivation (or easily via a second method)
This won’t secure your website perfectly, but if someone does manage to crack your password, it can make it difficult for them to find where to actually login. This also prevents any bots that are used for malicious intents from accessing your
wp-login.phpfile and attempting to break in.
- Upload the
hide-logindirectory to the
- Activate the plugin through the ‘Plugins’ menu in WordPress
- Set the options in the Hide Login+ settings page
If you are upgrading from previous versions please remove below lines from
wp-config.phpif there are any:
define(‘ADMIN_COOKIE_PATH’, SITECOOKIEPATH . WP_ADMIN_DIR);
- Is something gone horribly wrong and your site went down?
- There are 2 methods and you only need to go with one:
1- Deactivate plugin. Done!
2- There is a backup file of
.htaccessin the root directory of your WordPress installation named
.htaccess.backup. You only need to remove your
.htaccessfile and rename backup file from
.htaccess. Also rename
pluginsdirectory to something else. Done!
- Are you interested to collaborate with me on Hide Login+?
- Find me on
- Find me on
Учасники та розробники
“Hide Login+” — проект з відкритим вихідним кодом. В розвиток плагіну внесли свій вклад наступні учасники:Учасники
* Added delete_option on plugin activation to avoid later confliction
* No more need to modify `wp-config.php` for changing admin URL slug * Reduced and optimized `.htaccess` rules * `.htaccess` backup file is created in the same directory * All plugin options are cleared completely on deactivation * Many more bug & minor fixes and compatibilty issues done
* Changed some default options at activation to avoid 500 Server internal error * Restrictions on using default slugs like `wp-admin` for admin slug that made confliction * Optimized code readablity and stability * Solved fatal error caused by `check_admin_referer()` * Tested over wordpress 3.6
* Completely rewrote. * All rewrite rules will apply with wordpress buil-in functions * Remove plugin rewrite rules automatically on deactivation to wordpres default rules * Works with all permalink structures * Droped some useless options and codes and improved functionality * Now Setting page menu is at root * Tested Over the latest WordPress version(3.5.1)
* Fix an issue with hide mode capability
* Fix .htaccess query commands * Automatic removing and adding htaccess output to .htaccess file * Strong security key function * Added compatibility fix with WordPress installations in a directory like www.blog.com/wordpress/ * Added ability to disable plugin from its setting page * Added ability to attempt to change .htaccess permissions to make writeable * Added wp-admin slug option (can't login with it yet though) * htaccess Output rules will always show even if htaccess is not writeable * added ability to create custom htaccess rules * Added Register slug option so you can still allow registrations with the hide-login. (If registration is not allowed, this option will not be available.) * Security Key now seperate for each slug so that those registering cannot reuse the key for use on login or logout * Added better rewrite rules for a hidden login system. * Removed wp-login.php refresh redirect in favor of using rewrite rules for prevention of direct access to the file.