Loading...
 
Skip to main content

Features / Usability


Using Disallow access to the site

Greetings,

I'm a realitively new user to tikiwiki and have installed it successfully on my server. Ultimately, I would like to make tikiwiki private for my organization. I've messed around a little with 'disallow access to the site' and I seem to be having really mixed results. Most of the time I cannot login with either my account or the admin account. It's really weird, because sometimes I can log in without a problem. Is this a known bug or am I experiencing some kind of incompatiblity with my server?

Here's my server breakdown:

Macintosh G5 dual 2.0 GHZ processors
Mac OS X Server 10.3.8
PHP v. 4.3.6
mysql Ver 12.22 Distrib 4.0.18


Is there something that I'm misisng here?

Thanks,
John

'Disallow' is not the appropriate approach, IMHO. The correct way to do this is with group rights. Restrict the 'anonymous' group to as few rights as possible, while giving the 'registered' group more rights. You could then disallow registration from the login box; provide an email address to send registration details and then manually enter the details.

I went even further than this in my installation. I combined groups with categories in order to determine who has access to a page based on what groups they belong to and the way the page is categorized. I modified tiki-index.php to follow this logic:

Determine the number of groups the user viewing the page belongs to:

  • if it is 1, it must be 'Anonymous'. Therefore, display just the login box.
  • if it is 2, it must be 'Anonymous' and 'Registered'. Display a 'registration pending' screen.
  • if it is greater than 2, that means I have placed them in additional groups. Continue as normal. This entails a check of the page's categorization; if it is categorized, the user must belong to a group with the same name as the each one of the categories.


I have just finished implementing namespaces, where each page only needs to be unique within the namespace and each group has a certain set of rights (read, write, create, delete) to each namespace. This allows for the complete separation of internal content and customer content. Customers can create, modify, delete pages within their own namespace without even knowing about other namespaces. This, combined with the way I did categorization, will allow us to share documentation with customers in one namespace and allow them to create their own content in their own namespace.