.htaccess propagates to add-on domains

[shacker23]

Hmmm... a user has a main domain protected with .htaccess -- working fine.

Then they add an add-on domain, which of course is installed under public_html. The password protection propagates to the add-on domain, which they don't want password protected.

Apache is working properly - .htaccess is working as it should, as far as apache is concerned. IMO, this is a problem with the way cPanel sets up add-on domains (Plesk handles this better - add-on domains go into their document root rather than sharing one with the main domain).

Meanwhile, is there a way to turn off password protection for the add-on domain?

I asked a similar question regarding mod_rewrite a while ago for another client:
http://forums.cpanel.net/showthread.php?t=47574

The answer there was to turn off mod_rewrite for that subdir. But I can't figure out how to turn off password protection for subdirs. Ideas? The only other alternative I can think of would be to move the main domain to public_html/maindomain and the add-on to public_html/addondomain. This would require editing httpd.conf and reconfiguring their MovableType installation. Doable, but would prefer to avoid if possible.

Thanks,
Scot

[chirpy]

AFAIK, that's going to be the only option - moving the DocumentRoot in httpd.conf for the addon domain to a higher level.

[Spiral]

There is an easier way ....

Create a .htaccess file in the add-on domain folder

(If it has it's own .htaccess, it will superceed the main site .htaccess)

Another cleaner but somewhat more complicated solution would be
to move the add-on folder to the main root folder of the account
on the same tier as public_html and then update the httpd.conf
to point the add-on domain to that location.

Doing it this way, the add-on domain functions totally separate and
is no longer effected by any settings of the main domain.

If you use this option, don't forget to restart Apache after updating
the /etc/httpd/conf/httpd.conf file.