Creating a private Plone site
This How-to applies to:
Any version.
This How-to is intended for:
Site Administrators
Note: The easiest way to do this is to run Plone 3 and use the specialized Intranet workflow instead of following this how-to. If you're using Plone 2.x, the below is the easiest way:
These are the steps to create a Private Plone site
- from the Zope Management Interface for my Zope site I added a Plone Site
- From the Plone Site root I went to the security tab and made it so that
Add portal memberwas only available to Manager and Owner with no Acquire. This removes theJoinbutton. - From the Plone Site root I went to
portal_workflow - Note that two workflows are actually used in Plone,
folder_workflowandplone_workflow - Go to the
Contentstab - Click on the
folder_workflow - Click on
Statestab - For each state listed:
- Click on the state name
- Click on the
Permissionstab - Change any
Anonymouschecked areas toAuthenticatedand noAcquire - Save the changes
- Repeat this for all the states
- Also do the above for the next workflow
plone_workflow - Back at the
portal_workflowpress theUpdate Security Settingsbutton to make sure the changes propagate through any existing items.
And that should be it!
People who have not logged in see the pleasant Plone "Please Log In" page for Home and Members. "No News Posted" under News. And searches come up with "nothing found".
Log in with a valid account and the news, home page, member list are all visible and the search returns items.
Complementing....
Only let the Access contents information as Anonymous with Acquire.
portal_memberdata
Actually, what I did was copy the folder_team_workflow and saved it as portal_memberdata_workflow. Then you can change folder_team_workflow to not acquire settings and move everything from anonymous to authenticated. Then in portal_memberdata_workflow I made sure to leave Access Content Information as anonymous, and set to acquire settings
this is awesome
thanks again for the info. this product is truly awesome.
When using a CMFMember Plone
So... if you are using a CMFMember Plone Site, this procedure has one difference.
Do not set the visible state for folder_workflow with only Authenticated. Let the original config.
Since you do this, the Plone will not be capable of access portal_memberdata methods and you'll got a error.
RGDS
WLT