It's really just me here, well, other than the occasional insights from a few forum veterans.. Unfortunately, I am likely the most IIS illiterate geek you'll ever find. Like me, my previous employers have always used Linux/Apache so I have never dealt with IIS.

Knowing what version of IIS would likely help me to helop you, as it is, this google search is all I really can provide.. but I must admit, I am terribly curious if it's even possible. .. Maybe I'll contact an old acquaintance.. he might know.

I was getting a 404 error on both the directory url and the admin url.
your above suggestion to edit your .htaccess file fixed the directory as followsd:-

<Files directory>
#ForceType application/x-httpd-php
#SetHandler application/x-httpd-php
SetHandler application/x-httpd-php5
#ForceType x-httpd-php
</Files>

and I can now see the sample directory in the browser however the admin directory (even when I can see that it has an index.php file via the FTP) continues to give the 404 error message.
The ADMIN .HTTACCESS file has the following:-

AuthType Basic
AuthName "Dew-NewPHPLinks Administration"
AuthUserFile "/home/poshcame/.htpasswds/public_html/resources/admin/passwd"
require valid-user


and the main .httaccess file in the root directory has this


# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress


I am surprised when this was installed by fantastico that it did not configure this correctly. (and suggest you ask them to configure it correctly for fantastico or take it off there).

Can you please advise what are the other settings required to make the admin panel work.

is it possible that your new software is not going to work when sites have a wordpress Blog?

Just so I'm clear on the situation.. you are browsing to
www.yoursite.com/resources/admin/ (with or without index.php should work)

and not ...
www.yoursite.com/resources/directory/admin/


Directives in a .htacess file affect all directories beneath them, even still
the rewrite rules from wordpress should not conflict. They basically say if you request something that isn't a file, or a directory, serve the ./index.php the ./ are the life savers.. if it were just / you would get your wordpress index.php , but ./
should serve the index.php from the requested directory.

I do find it odd that the AuthUserFile is in the directory you are trying to protect. Typically it would be outside of your browseable directories for security reasons. Also, it's usually named .htpasswd

Possibly thats what is causing the 404 ? Is there actually a passwd file in the admin directory? If so, it should contain the username and an encrypted version of the password. Ideally it would be chowned (owned) and chmod (permissions) so that only your web server can read it. Even still, since its in a browsable directory Apache will attempt to serve it if its requested, after authentication, which of course will fail.

Bottom line, the passwd file really shouldn't be there, its like locking your keys in your car. You need the keys to get to the keys so to speak.

As for me telling Fantastico what to do.. well they really just bundle Open source software for hosting providers to offer their customers. As I understand it, the hosting providers can pick and choose what apps they want bundled, and can tweak them to work under specific server conditions, although few if any actually do.

And of course .. after writing all that.. it dawns on me..

Try this..
Rename the admin directory to something.. well unique .. jellyfish for example. Rename the /jellyfish/.htaccess file to something like was.htaccess (basically removing password protection) then see if you can browse to /resources/jellyfish/index.php

If you can, then you could potentially leave it like that, but should probably take another shot at password protecting the directory. Either way, this appears to be an issue with how you have attempted to password protect the admin directory, rather than a conflict with wordpress's .htaccess .

Dont worry about responding. I have given up.
I just realised I dont have the time for a product in development. So I used a cheap commercial version that worked strait away.

I appreciate what your trying to do, but I thought if it was listed on Fantastico then, a software programe, would at least work straight out of the box, even if it was not feature rich.

Peoples attention span is getting less and less because of the internet?

Speaking of attention span..

I responded 4 minutes after you posted your dilemma.

Did you read what I wrote?

Your attempt to password protect the admin directory is likely what broke it....

"I am surprised when this was installed by fantastico that it did not configure this correctly. (and suggest you ask them to configure it correctly for fantastico or take it off there)."

This was my original point but the developer isn't who places the scripts in fantastico I don't think.

Spot