Problems with .htaccess support.

[RodG]

ZC it tells me that htaccess not supported even though the vhost config file allows overides. I just wanted to clear this error during install, thats all.

Apologies, but I need to be a little pedantic here. Although the ZC message reads like "There is a problem with .htaccess support on your server" this is *not* the same as saying .htaccess is *not* supported" . The difference may be subtle, but I can assure you that .htaccess *is* supported, it is just that ZC has performed a test (for security purposes) and determined that is just isn't working for some reason.

IOW - Supported but not working.

One of the reasons for the ZC to report this message is if you don't have the supplied .htaccess file in the /includes/ folder (which AFAIK is the only test made). This can *easily* happen if uploading the files via FTP and these files remain 'hidden' (by default, any file with a name starting with a '.' is a 'hidden file on *nix systems (I dunno about Windows, but that's unimportant here), so the 1st thing to check is to see if /includes/.htaccess does actually exist.

You have told us that it doesn't exist in the main directory (doesn't need it there), but unless I missed it, you've not told us whether one exists in the /includes/ directory or not - So the solution to your problem (clear the error) could be as simple as uploading this missing file.

The allowoveride none directive will have the same effect as missing .htaccess files, but you have assured us that your vhost config allows it, so that is *not* going to be the cause of your problem. The allowoveride directive for the default server (not a vhost) doesn't even come into play. It is effectively a different 'host' entirely - and as I detailed earlier, this is typically set to 'none' because strictly speaking there is no need for it (it is better to simply set the needed directives in the main config).

Assuming the vhost allowoveride is set to 'all' and assuming the /includes/.htaccess file does actually exist, and assuming it is an unchanged copy of the .htaccess supplied by Zencart, and assuming it is readable by the server process, then you won't be having this problem. The fact that you *are* having the problem means that at least one of these assumptions is incorrect. Only you are in the position to identify which it actually is.

My money is on the /includes/.htaccess file doesn't exist (and if it doesn't, please check on the *other* ZC-supplied .htaccess files to ensure they aren't also missing), because without these files to prevent access to *restricted* folders you are opening yourself up to a bucketload of abuse)

Please don't ignore the ZC warning. You *can* complete the installation in spite of this, and even fix the problem *after* the install (assuming you remember to do so), but you really, *really* shouldn't - The ZC check ensures that all is good. Fixing it after the install means that you need to do your own manual testing to ensure it is working and the site is secured.

Cheers
RodG

[pixelpadre]

htaccess files exist in other directories and are not hidden.

Looks like I will have to allow overides in httpd.conf in addition to vhost.conf

[RodG]

htaccess files exist in other directories and are not hidden.

Looks like I will have to allow overides in httpd.conf in addition to vhost.conf

That won't solve your problem.
Is there a reason that you failed to confirm whether /includes/.htaccess exists or not?

Also, I find it a bit disconcerting that you state that *other* .htacess files exist but they are not hidden because the "." in the filename is the *nix standard that defines a "hidden" file.

I'm seeking a solution to your problem. You appear to be defensive to my approach, so just two questions before moving on.
1. Does the file /includes/.htaccess on your server?
2. What are the permissions for this file (should be 644).

Cheers
RodG

[pixelpadre]

First sentence in my previous post answered the question that you said I didnt answer.

You didnt ask for the permissions originally, but yes they are all 644

When I say they are not hidden, I mean they are visable in my directory structure. Not using anything other than pure apache.

[RodG]

First sentence in my previous post answered the question that you said I didnt answer.

Hmmm, well no you didn't, and still haven't. It may have been implied as part of the "other directories" but I'm not willing to make that assumption. Historically I've wasted many hours going around in circles due to this kind of thing. Seriously, the .htaccess files in "other" directories are unimportant to the problem. The only important one is the one in the /includes/ folder and I really didnt think it too much to ask that you verify/confirm that this specific one exists.

You didnt ask for the permissions originally, but yes they are all 644

No, I didnt ask previously which is why I asked this time. Could you please confirm that you actually checked that permissions are 644 and that this wasnt from memory or possibly you just said it was 644 because that is what I said it should be?

When I say they are not hidden, I mean they are visable in my directory structure. Not using anything other than pure apache.

Im not sure what you mean about "pure apache", and "hidden" in this context does not mean they can't be seen in the directories. All files in all directories can be seen, even the hidden ones.

Anyway, lets try to move forward eh?
So, the file /includes/.htaccess exists, and it has permissions of 644 .... Next step is to set the permissions to 666 (temporarily) and edit the file by adding the words "hello world" right at the beginning of the file. save it.
Now point your webbrowser to yourstore.com/includes/

One of three things will happen. When you tell me the results that you are getting I will either be able to give a diagnosis, or will I be able to provide you with the next diagnostic step(s).

Cheers
RodG

[pixelpadre]

internal server error 500 page

[RodG]

internal server error 500 page

That's exactly what we want :)

What this is telling is us is that

1) Your allowoverrides are OK
2) The .htaccess file is in the correct location for purpose.
3) The .htaccess file is *currently* readable by the server process.
4) The .htaccess file is correctly named (Yes, I have seen cases where folk have renamed it for whatever reason and then wonder why it isn't working)


Next step. Same as b4, but leave the file permissions at 644. You should get the same 500 server error, so assuming you do - you should now remove the 'hello world' and resave the file.

FYI, The 'hello world' itself isn't important, pretty much any text that isn't recognized as valid syntax will cause the server 500 error. This is just a handy/useful trick/tip that will determine that the .htaccess file of interest is actually being used or not. If anything was amiss with those 4 points above, the file would be skipped and you'd be getting something *other* than the 500 server error.

So, now we know that all is good as far as finding and reading the .htaccess file you should now once again point your browser to

yourstore.com/includes/
While you are at it, also point it to
yourstore.com/includes/spiders.txt

If the *contents* of this .htaccess file are all correct, you *should* be greeted with a 'Forbidden' message for *both* tests. This is actually the response that the ZC installer is looking for - but since the problem you are having is failing this test that would imply that there is something not quite right with the contents of this file. This is what you'll need to investigate to seek a solution since all(?) other possibilities have been eliminated.

However, if you ARE getting all the expected results here - the plot thickens - We will no longer be looking at 'your' side of things - It means that for some reason or other the ZC installer is actually giving you a false report - I would even go as far to say just ignore it - The important thing at this stage is that *you* get the forbidden message when you point your browser to /includes/ and /includes/spiders.txt - After all, it is this that the ZC installer is testing for and if the installer is giving a false error report (which is where this is now headed) then there doesn't seem like there is anything that you can do to fix it anyway. Basically 'not your problem'

Cheers
Rod.

ps. I chose to use spiders.txt, the zc installer uses one of the .php files in the same folder. Both should be 'forbidden'