Support » Plugin: Solid Security – Password, Two Factor Authentication, and Brute Force Protection » [Plugin: Better WP Security] Hide Backend Function Broken

Viewing 15 replies - 16 through 30 (of 61 total)
  • Many kudos for this outstanding plugin!

    I have a clue – and another bug. I relocated my user url from domain.com/xxx to domain.com When I tried to hide the back end I was told to enable permalinks, I was given the link domain.com/wp-admin.php, which is a bad link (BUG). I manually corrected to domain.com/xxx/wp-admin.php and selected the default permalink setting. This yields a .htaccess file that has nothing in it but comments. On returning to Hide back end, we go through the same process again. Eventually, I changed the permalinks to SEO-friendly, and now I am seeing good Hide Back End Options.

    HTH & Tnx

    WP 3.4.

    After enabling Hiding the Back End, the new links work, but the back end is not hidden.

    As I mentioned, I installed WP in domain.com/xxx, then changed the user URL to domain.com by changing Settings > Site Address (URL). See http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install for details. Note that this is NOT multisite installation. The admin link remained domain.com/xxx/wp-admin.php, as expected, and the main user page became domain.com.

    It looks like the plugin doesn’t get the memo that the locations have changed: published URLs are still in xxx, and plugin is writing to xxx/.htaccess.

    When I enable the SEO-friendly permalinks, WP writes to /.htaccess. When I enable “Hide Back End”, the plugin writes to /xxx/.htaccess.

    I’m using 3.2.6 and this feature hasn’t worked for me at all.

    I was honestly hoping that 3.3 would fix this issue but decided not to upgrade because another user mentioned in another thread that the “Ban Hosts” feature was removed. Of course on my Better WP Secutiy menu, it says “Ban Users”.

    @molandra, most of the options highlighted in yellow require .htaccess as does hide backend and ban users.

    @mr34101 can you email me offsite at info [at] bit51 [dot] com. Perhaps you can get me a temporary account that I can take a look and try to see what’s going on…

    @dukejames27 ban hosts/users is still there in 3.3. I would love to say that hide backend will work for everyone but, in over 50 sites, I haven’t been able to reproduce the bug. Same offer if you want to email me I would be happy to take a look for you.

    Bit51 are all 50~ sites using the same hosting company?

    Maybe the hide backend could be host related?

    It’s not working on one of my sites even though, the .htaccess is getting written to. I’m going to email you the .htaccess file.

    The hide back end function is broken! Tested on multiple sites!

    I’m using,

    Better WP Security has written the mod rules to my .htaccess file

    .htaccess File is Writable: No.
    wp-config.php File is Writable: No.

    Server Type: Apache
    Operating System: Linux

    So why is this not working?

    Is this problem because my .htaccess File & wp-config.php File is not Writable?

    Bug report: If hide backend option is not enabled,

    Register link will not work! BuyPower.co.uk/register

    He’re is my site: BuyPower.co.uk if anyone wishes to check this!

    Bug report: The hide backend option destroyed one of my sites to the point were I had to delete the domain and database and completely and start over.

    Hide backend option (WARNING USE WITH EXTREME CAUTION)

    Related problem – I cannot activate Permalinks? I cannot proceed to hide back end?

    @buypower the only thing hide backup does is write some rules to your .htaccess. It cannot do any damage that cannot be reversed by manually removing the rules from .htaccess. As for register, as that is part of the hide backend feature it will not work if the feature is not turned on.

    @opentosolve – Turn off the option to prevent writing to .htaccess in system tweaks. It turns off the ability for anything that doesn’t manually change options from writing to .htaccess

    @natetronn I use Greengeeks, AWS, a couple of hostgator sites, and I think there is at least one mediatemple site in there. Can you email me at info [at] bit51 [dot] com so that I might be able to get some info from you to track this down?

    I’ve got the problem where hide packed has locked me out of my site. Im on MediaTemple’s DV host. When I go to mydomain.com/login the host temperately forwards me to my domain.com:7080/wp-admin

    This has the effect of breaking the redirect and thus my access to my admin panel. This is VERY BAD!

    Please Help

    Richard

    im also not able to access the admin section of my site. i’ve already deleted the whole installation and database twice! i use this plugin on often and its the fist time ive come accross this error. ive changed my login url (which i always do). error on login is “No input file specified.” no other url’s work. the error seems to be in the htaccess file. it seems to be denying all files.does anyone know what it should be and wil it help if i edit it manually? ive deleted the plugin via ftp but i still cant get access 🙁

    It’s come to my attention that the issue here might be with an incompatibility with Plesk. Can some of you please confirm for me whether you are using Plesk or not?

    This is happening on mediatemple (gs)

    OK,

    Found two cases where problems could occur:

    1.) There has been a change in how WordPress processes the default admin slugs (wp-admin and wp-login.php) in WordPress 3.4 that is breaking the feature. I will be working on a work-around but I have to do so without the default 404 processing that I was using before which could take me a few days).

    2.) Hosts with Plesk, in particular Media Temple, are using their own redirect for admin. I do believe using a slug in the settings other than ‘admin’ should fix it. Please confirm if you can.

Viewing 15 replies - 16 through 30 (of 61 total)
  • The topic ‘[Plugin: Better WP Security] Hide Backend Function Broken’ is closed to new replies.