[support] Hiding a site, best practice?

[A-NO-NE Music]

Thank you so much both Bob and Carl for advices.  I realized there are some contents I want to be available to public, such as my students' multimedia project work showcase.  Feels like need to make content types private one by one.  Sigh.

--
- Hiro

Hiroaki Honshuku, A-NO-NE Music, Greater Boston
http://a-no-ne.com   http://anonemusic.com


On 2010/08/26, at 18:01, Bob Fishel wrote:

> You want "Secure Site" http://drupal.org/project/securesite
> 
> I use it for my devel site that I want public for multiple developers.
> 
>> From the module page
> "This module allows you to authenticate users with a browser-based
> password (HTTP Auth). You can restrict access to the site by role and
> choose to secure restricted pages or the entire site. This means the
> site will be inaccessible to search engines and other crawlers, but
> you can still allow access to certain users."
> 
> Basically just sticks a grey login block (I'm sure you can theme it if
> you want) that protects all content until a user logs in....
> 
> On Thu, Aug 26, 2010 at 4:02 PM, A-NO-NE Music <madflute at anonemusic.com> wrote:
>> Drupal 6.16 (at this moment)
>> Longtime Drupal user but not much of a PHP coder.
>> 
>> Since I am temporary leaving the college I have taught, I need to close the student portal site but I want the site to be still accessible to them.  In short, I need to hide this site from the public.
>> 
>> What I need is the home page to be showing only the login block and a short sentence or even placing iFrame from my other sites.  Once student logs in, they get the same website they are used to but its HOME needs not to be the public home page but their old homepage instead.
>> 
>> Any suggestion on how to proceed, other than making everything private one by one, would be appreciated.