Murray--Just realized that you are the same Murray that answered my previous
post.
Now I am blushing ;-) When will women learn to keep their mouth shut?
But another question comes to mind..I have a client that actually requires
the same functionality Murray described and the only justification for
having
two wikis that I can think of is to have an read only internet wiki as a
public version
and a intranet open version. The intranet wiki is for the authors while the
internet
version is just a backup version displaying which ever pages you deem no
longer to be
a work in progress.
Unless the two wikis are copies of each other, you may run into a
maintainence
problem which defeats the effort. So just as registred users mark their
pages for deletion,
they could just as well mark their pages for publication. As such "done".
Administrators would be the only ones who get to publish the done pages on
the internet. Does jspwiki have the filtering capabilities to do this Janne?
And if so would this be advisable in your opinion?
On 7/11/07, Claudia Frers <[EMAIL PROTECTED]> wrote:
Murray,
With the requirements you set up, you might want to go with a CMS.
Wikis have evolved to mimic some of the features of a CMS but as Janne
explained a wiki is mainly a collaboration tool allowing certain pages to
be
members only. If you choose to have two wikis installations, users will
also
have separate search engines per wiki. I hope to be experimenting with
Multi
Wiki installations and IMHO, it takes a bit of coding skill and deployment
skill
to tackle your request because you are basically modifying typical wiki
behaviour to
your liking. May I suggest that you read the security section and the wiki
and cms
section of wikipedia's wiki article?
http://en.wikipedia.org/wiki/Wiki#Security
If you then still want to go multi wiki, I'd be happy to share my results
and help in what I can.
Claudia
On 7/11/07, Janne Jalkanen <[EMAIL PROTECTED]> wrote:
>
> > It shouldn't require an expert Java/JSPWiki programmer to tackle what
> > to my way of thinking is a very common implementation scenario. This
> > should be a configuration/installation issue, not a coding one.
>
> No. It is not a common scenario for a wiki. For *two* wikis
> perhaps, but not for a single one...
>
> If you think about it this way: page-level security is exactly what
> it means - *page* -level security. It's not *pageset* level security
> (which was never in the spec in the first place). If you have 2000
> pages, you need to have 2000 ACL's as well, and therefore it suits
> fine in the cases where default is open, and you just close some
> pages - or the default is closed, and you open some pages. But
> beyond that, it gets awfully complicated, and you really should
> consider deploying two wikis instead of one, if your security needs
> that.
>
> /Janne
> _______________________________________________
> This is the Jspwiki-users mailing list, in which we discuss the
> stable release (even-numbered, 2.4.x, 2.6.x), and user-issues.
> For development discussion, please join jspwiki-dev.
> http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users
> http://www.jspwiki.org/JSPWikiMailingList
>
_______________________________________________
This is the Jspwiki-users mailing list, in which we discuss the
stable release (even-numbered, 2.4.x, 2.6.x), and user-issues.
For development discussion, please join jspwiki-dev.
http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users
http://www.jspwiki.org/JSPWikiMailingList
