Wordpress Safer Admin Plugin

Have you ever wondered how you can hide your Wordpress Admin Panel so possible attackers won’t be able to find it and gain access to your Wordpress site?

If you want to ensure that no one knows where your Wordpress Admin Panel is, then this WP Safer Admin Plugin is the right tool for you!

New version available! Version 1.4 – Works with Wordpress 3.3.2, too!

You must CHMOD 777 to .htaccess (create it if it doesn’t exist!)

Requirements

• PHP 5
• MySQL 5
• At least Wordpress 3.3.1
• .htaccess support
• .htaccess file must exist and must be writable
• ./wp-include/default-constants.php must exist and must be writable
• RewriteRules Enabled

The plugin goes through a series of automatic modifications in order to change your wp-admin directory to something only you know!

Completely safe and when de-activated/uninstalled restores the standard wp-admin directory.

Features:

• Full Information Logger (IP, Date Time of Event, Full Page URL , POST & GET Data)
• Plugins History so you will be able to know what Plugins have been activated/deactivated and who did it.
• Help File inside the Plugin
• Plugin Update Check
• Enable/Disable Logger & Plugins History feature

More about the Logger Feature

The Logger feature allows you to record all activity on your Wordpress site. It logs IP, Date Time of event, Full Page URL , POST & GET data (advanced), and Referrer (from what page user came from).

If you don’t want to consume a big part of your Server resources logging information, you can limit the total entries that can be logged.

For example you can set it to 200 entries and when the limit is reached, the older entry is replaced with the new one. By doing that you use specific amount of space and resources.

More about the Plugins History Feature

If you want to keep track of what plugins are being installed/uninstalled from your Wordpress site, then you’re going to love this! Every time a Plugin is activated/deactivated the Plugin creates an entry about the event so you can later check on it.

If you don’t want to consume a big part of your Server resources logging plugins history information, you can limit the total entries that can be logged. For example you can set it to 200 entries and when the limit is reached, the older entry is replaced with the new one.

By doing that you use specific amount of space and resources.

Support

Please read the Frequently Asked Questions (inside the ZIP ) first! All your questions are answered there!

If need further help check the Support Forums.