Hi Bit51
Tried your dev version on Plesk and still no joy.
I delete via ftp as I cannot get into the backend at all and try a clean reinstall without success.
When I try a manual re-install the error re-appears.
@bit51, I did not apply the dev version, sorry. If I choose to delete the 3.3 version and install the dev, will I have to reapply all of the settings?
@dukejames27 it will work just like any other upgrade. No settings will be overwritten (please do so only on a test machine though as I haven’t released it officially yet and don’t want you to run into any unforseen issues).
@darenj01 Darn. I don’t have any way to test with plesk. Can you change the slugs from “admin”/etc to something else? That had fixed it for others. If that doesn’t work please drop me an email offsite at info [at] bit51 [dot] com and we’ll see if we can’t do something else to fix it in that environment.
@bit51 will drop you an email mate. As intimated, I set it to hide backend and I can no longer get in at all, nor can I run a clean re-install of either version as it keeps retaining HIDEBACKEND as active and breaks.
I delete it via ftp and can get into admin but it will not let me reinstall clean…So no way of editing the slugs either:-(
@Bits51, I just applied installed the dev ontop of 3.3 but the “Hide Backend” feature does not work. When I go to the plugins list, Better Wp Security is still listed as version 3.3. Did you modify it to say “dev” within the version text?
If I wanted to roll back to 3.3, can I simplly install it on top of the dev?
I just tried the latest version of Better Wp Security, 3.4, but unfortunately, it’s still not working for me. The change log says that it fixed the ‘hide backend’ feature.
Out of curiousity, when the plugin attempts to modify the .htaccess file, does it provide an error if it couldn’t?
I’m going to try a new install of WordPress with better wp secured being the only plugin installed. I tried this with 3.3 with no success but perhaps with 3.4?
I installed WordPress fresh with the Better Wp Security 3.4.1 (update) plugin and everything worked fine. I used Xampp to do this test.
Then I went to my hosted site, updated to 3.4.1 and it still doesn’t work. I even tried disabling all of the other plugins, reseting my permalinks and changing the login slug.
I just don’t get it.
Who is your host? Maybe I can look into it from that angle..
I got it working. Knowing that it worked on Xampp, I thought real hard about what it is that I did. I allowed Better Wp Security to write to my Wpconfig.php and .htaccess files. A setting which I never chose on my hosted site. I thought it was able to do this from the way I read it on the Hide Backend page.
This feature will need to modify your site’s .htaccess file if you use the Apache webserver
I thought that the above message was a warning informing the administrator of the change to the .htaccess file and that it already had permissions to do so.
Would you please kindly change the writing on this page for the next version, informing users that they need to check off
Write to WordPress core files
.
Thanks for your continued help bit51.
Thread Starter
wps
(@timminstrader)
Hi Bit51,
Thank you for a great plugin that we always use.
We added one more layer of security to the back end using Dome9 Security.
Your Better WP Security together with Dome9 is the new Total WP Security.
Awesome, Cheers WPS
Hi,
I think I’m posting in the right thread. I’ve been getting login attempts from unknown individuals. They get locked out by IP, but I’d like to prevent them even getting to my login pages, so I attempted to activate the hide backend function.
I am using permalinks, and copied/pasted the generated code to my .htaccess file, but when I then logged out and tried to navigate to the new backend url to test logging back in, I just get a 404 error.
I’ve restored my old .htaccess file so can get back into my site, but wondered if anyone knew why I was getting 404s?
I’ve tried activating this several time, tried various admin urls, and always the same result.
:-/
PS – Other than this, Better WP Security is superb, I should say! 🙂
Just enabled hide back end. Didn’t take security key and now not able to access wp-admin. I have already removed “force ssl” at the backend. Any suggestions to help. Also if I delete BWPS from the backend will that help at all?.
hi- i am locked out of my wp site. changed backed to a different slug and it’s not working. i checked the wp_bwps_lockouts and there were no rows of data, so i guess it’s not a lockout situation. via ftp i downloaded and removed better wp security section of the .htaccess file, re-uploaded it, and it still isn’t recognizing the /wp-admin page; all it does is redirect to the homepage of the site, which is in a subfolder of my website because it is still under development. help? website is: http://www.thebrilliantassistant.com/witcraftpainting
can’t get to login page with /wp-admin
trying not to panic…help?
email is [ redacted, support is offered via the forum and not email ]
thanks
