I think I've got MT installed properly. I can add entries, and edit existing entries. And when I rebuild, everything seems to go okay. But when I try to view the blog, I get a 403 error because the directory it is trying to view has no INDEX.HTML file...it's just an empty diretory. (I created the directory and CHMOD'd it 777) via WS-FTP.

Any ideas why the INDEX.HTML isn't getting written, even though I'm not getting an error?

Just to test things, I changed the directory name in the blog config to one that didn't exist, just to see what would happen. In that case, it flagged me during the build process that the directory could not be found. So I know it is finding the directory.

Thanks in advance for any tips you may have. Cheers!
Brent

403 isn't a "not found" error. It's a "permission denied" error.

Since you've already checked the directory permissions, take a look and make sure that your Local Site Path: and Site URL: values jive.

If the Site URL: is wrong, then all the "view" links in the admin interface will be pointing to the wrong spot.

Yeah...the 403 is a permission error. I think when the directory is lacking an INDEX.HTML file, it tries to display a list of the directory contents, but I believe my webhost has disabled that functionality for security reasons, and thus, if the directory does not contain an INDEX.HTML file, it shows a 403 permission error. If I explictly try to link to the INDEX.HTML and it isn't there, I get a 404 (as expected).

http://theacf.com/blog/ = 403
http://theacf.com/blog/index.html = 404

Still not really sure what to try, I know when it's building it must be finding the directory because I've tried using a bogus directory name and in that instance, it does give me a red error message that the directory isn't found.

I don't think it's the view links that are the problem. After building, I've used WS-FTP to look at the contents of the directory and it is indeed empty.

Thanks for the tips though! Cheers! Brent

OK...figured out the problem. The publish paths I had entered were relative to what I thought was my cgi-bin, but was in fact an alias for my cgi-bin. So it was publishing my stuff to a different directory. And since it didn't find the directory that I had designated there, it (wrongly or rightly) created one for me. If it had simply returned a "designated directory not found", I would have caught the error immediately. I'll split the blame with MT on this one ;-)