Eddie

I’m not sure if this comment is even going to get posted because I wrote an answer to gon and it hasn’t appeared. Then I wrote a separate comment about problems I’m having and what steps I took. It was long and detailed. As soon as I clicked on the “Add Your Opinion” button, I got a page saying Firefox couldn’t find this page or the comment. The Back button didn’t get me back to the comments–everything is gone.

Without dates below, I have no way of knowing whether these are from 2005 or more recent. Is the developer still looking at the comments and working on solutions?

In the tests, I put the absolute URL for where the blog is. The wording for this field is confusing. It says one or two URIs in the same space that require the same authname, username, and password. My site is not set up that way. A separate username and password is used for the blog. It is not the same as the FTP logon for the main site because I only want authors and contributors to the blog to have access to the blog and not the whole site.

Although I set the field pointing to the blog in the subdirectory, the .htpasswda3 file was created outside the blog directory. Assuming that most people will be working with a standalone WordPress installation, the .htpasswda3 file would normally be created in the root of the WordPress files. So I moved the file that was made outside the WordPress directory and put it into the WP root. Then I ran the test again and specified that link for the .htpasswda3 file in the WordPress directory.

I activated Password Protect wp-login.php and wp-admin. Then I tried to go to my blog and I keep getting an Authentication Required window that says: A username and password are being requested by http://www.domain.name. The site says: “Protected By AskApache” I’ve tried entering the FTP logon info but that isn’t accepted and I even tried the blog logon info even though the blog is not at that level. But nothing is accepted.

In addition, all the CSS styling for both the main site and the WordPress site is not being used. How would this plugin affect that?

I am hoping that this plugin will allow me to protect the WordPress directory, wp-login, and wp-admin from unwanted users and allow multiple registered authors, editors, and contributors to log on with a password. I’m going to remove the plugin until someone can tell me how to make it work with WordPress in a subdirectory. I am using WordPress 2.8.5.

That made the error message go away. In its place was a yellow box with the code that had been written to the .htaccess file.

im having a ERROR: Failed to create /home/user/.htpasswda3

my .htaccess is writable but i have a red box in
Digest Authentication Attempt and
2nd Digest Authentication Attempt

it may be the reason of my first error.

can i ask how to solve this?

I’m having problems however and I’m receiving this in the testing phase:

‘Bummer… you don’t have digest capabilities.’

and this is stopping the plugin from working.

What would cause this, and is it something I can do, or do I have to get onto my web host?

Thanks for any help with this.

is there anything i can do to change this?
best , sarah
Norway

Best regards from Berlin – Germany, Phil

PS:

File Permission Tests
 
If any of these checks fail this plugin will not work. Both your /.htaccess and /wp-admin/.htaccess files must be writable for this plugin, those are the only 2 files this plugin absolutely must be able to modify. If any of the other checks fail you will need to manually create a folder named askapache in your /wp-content/ folder and make it writable.
 
[ ] /wp-admin/.htaccess file writable
[ ] /wp-admin/.htaccess file writable
[ ] /kunden/sassen.org/.htpasswda3 file writable
[ ] Creating test folder
[ ] Test folder writable
[ ] Basic Auth htpasswd file writable
[ ] Digest Auth htpasswd file writable
[ ] .htaccess test file writable