Soliciting comments for this tip-- is it accurate? Note: semi-public is
used in this context to mean a generally private wiki which exposes some
Suppose you have a wiki which contains private data (e.g., a company wiki
for developers-only), but you would like some pages to be public (e.g., the
latest bug fixes, releases, etc.). You can accomplish this using ACL. In
acl_rights_before = u"YourName:read,write,delete,revert,admin"
acl_rights_default = "+Known:read,write All:"
This makes the wiki private to anonymous users. However, users can still
create a wiki account, and then edit pages. To prevent this, login with your
admin account and edit the
Now the wiki is private, by default. To release a page publicly, simply add
to the top when editing (you can also add write features).
> Suppose you have a wiki which contains private data (e.g., a company wiki
> for developers-only), but you would like some pages to be public (e.g., the
> latest bug fixes, releases, etc.). You can accomplish this using ACL. [...]
Following your words, I would do it differentely.
Default ACL could be:
* All: none
The pages that you want to expose could have a special ACL:
* All: read
In this case, you must make a change from the default when you want to
publish something and this will improve the odds of not publish what
you don't want to.
However, care must be taken in order not to show links that go to
unpublished pages: it can be hard on users to send them to some place
only to banish them on it's door.
A different approach would be to make 2 wikis in a wikifarm (like
moinmoin and moinmaster).
In this way, some work can be duplicated, but each one will be safer
and more adapted to it's targeted users.
Just my half cent. :-)
Buenos Aires - Argentina.
Get latest updates about Open Source Projects, Conferences and News.