Password protecting main domain, opening up add-on domains

[huggies]

Apologies, I already posted this question to an older thread, but I don't see it listed where it should be when sorted by "last post"...not sure if it's lost in the bulletin board somewhere, or if it's in an "archived" section.
========================

My main domain (I only have the one so far) is at the root of /public_html. I'm about to add an add-on domain as per the instructions in other threads.

However, my main domain has password protected the public_html root, and I do not wish the add-on domain to be password protected.

In other words
~/public_html/xxx -> password protected EXCEPT
~/public_html/add_on_domain/yyy -> This I want to be public.

I originally had the main domain password protected via cpanel's "password protect directories" functionality. I'm sure that in turn set the .htaccess appropriately.

If anyone can assist me with learning how to modify cpanel settings, or .htaccess such that I keep my main domain behind password, but open up my add-on domains, I'd be much appreciated. I'm a novice at modifying .htaccess

Don't mean to thread-hijack either...this thread seemed appropriate. Please let me know though and I can start a new thread.

Much thanks!

[Reverend]

I don't know if you found a resolution to this yet, but if not, here is what I would recommend.

Use your .htaccess file to redirect the primary domain to a subdirectory (public_html/directory).

It will be acting like an addon domain. So you can leave public_html open (which allows subdirectories to remain open) and still password protect your primary domain's site.

Does that make sense?

[Eriksrocks]

I don't know if you found a resolution to this yet, but if not, here is what I would recommend.

Use your .htaccess file to redirect the primary domain to a subdirectory (public_html/directory).

It will be acting like an addon domain. So you can leave public_html open (which allows subdirectories to remain open) and still password protect your primary domain's site.

Does that make sense?

Here is a Bluehost tutorial describing how to implement your solution.
http://helpdesk.bluehost.com/kb/inde...od_id=2&id=394

[huggies]

Sorry, somehow I missed the responses...thought I was subscribed by email.

Thanks for sure on getting back to me.

Following suggestions given above, I'd then have to move everything from the main domain into this new subfolder correct? In my case, the main domain is a wordpress install, so would that impact things like the associated database, etc?

[felgall]

The databases are completely separate from the hosting. Where the site is within the hosting that uses the database makes no difference as long as they are on the same server.

[Eriksrocks]

Following suggestions given above, I'd then have to move everything from the main domain into this new subfolder correct? In my case, the main domain is a wordpress install, so would that impact things like the associated database, etc?

If it impacts anything at all, which I highly doubt it will, it should be easy to correct.