Question

I would like to move the user pages out from the Main-Web to another f.e. internal Web. I have an internel Web, I call it IntWeb, which has access-restrictions by the GROUP-Variable. So I want to move the pages out from Main to IntWeb. For first it seemt to be possible. Only that it seem to be necessary, that on the IntGroup-Page, the Members must stay Main.Users to access the IntWeb. That confuses a lot, and I don't like. Also, if from a user a page has moved. He can not see anymore the private data like e-Mail from other users. I really don't want the User-Pages in the Main Web, what can I do?

Environment

-- MathiasKrueger - 05 Jan 2007

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

It would also help to know, if it isn't possible to move the User-Pages in a convenient way.

-- MathiasKrueger - 06 Jan 2007

It is not possible to split up user homepages into several webs.

All user homepages and TWiki group topics need to be in the same web, by default the Main web. You can rename that to Users (or something else) and configure TWiki accordingly. Upgrade will not be that easy if you do that.

The easiest solution is to leave the Main web as is, and create another web (or webs) for your primary wiki content.

There are good reasons to keep the Main web open to all, for example so that people with similar interest can find each other, to provide feedback in the user homepages, and to teach users the wiki way of open collaboration. What is the reason to lock down the user homepages?

-- PeterThoeny - 07 Jan 2007

One reason for removing general access to user homepages, or even lists of users, is provided in the question RemoveGroupsAndUsersFromSidebar. Alternatively, an organisation may wish to incorporate TWiki in their public web presence without broadcasting personnel information.

It does seem to me that information about TWiki users is different from the other content listed in the index: it'd be nice to control access to it separately.

The solution of creating another web for primary content sounds good; thanks for the suggestion.

-- KiviShapiro - 16 Jul 2008