18 Jun
2008
18 Jun
'08
4:04 a.m.
Hello,
Is there a way to restrict access to past versions only to Admin and/or
a selected "power users" group?
Greetings, Lilianne
18 Jun
18 Jun
10:05 a.m.
Hi Lilianne,
On Jun 18, 2008, at 4:04 AM, Lilianne E. Blaze wrote:
Hello,
Is there a way to restrict access to past versions only to Admin and/
or
a selected "power users" group?
I don't think this is possible out of the box. It also goes against
the wiki principle of openness.
Of course nothing prevents your from modifying the historyinline.vm
file to add a check on rights. Or create your custom skin that
overwrite the historyinline.vm file (easier for upgrades).
Thanks
-Vincent
3:03 p.m.
Vincent Massol wrote:
Hi Lilianne,
On Jun 18, 2008, at 4:04 AM, Lilianne E. Blaze wrote:
Well, yes and no.
It does go against traditional wiki ideas, but it could be useful in
Wiki-as-CMS scenario.
Hello,
Is there a way to restrict access to past versions only to Admin and/
or
a selected "power users" group?
I don't think this is possible out of the box. It also goes against
the wiki principle of openness.
Of course nothing prevents your from modifying the historyinline.vm
file to add a check on rights. Or create your custom skin that
overwrite the historyinline.vm file (easier for upgrades).
Thanks
-Vincent
Greetings, Lilianne
3:08 p.m.
On Jun 18, 2008, at 3:03 PM, Lilianne E. Blaze wrote:
Vincent Massol wrote:
Yes, I agree.
Is the solution I gave good enough for you for now? I don't see any
easy and generic way of adding this to the core. Creating a new
"History Right" would be too complicated for this right now. I think
we need to overhaul our rights system so that it can scale and then we
should probably add more rights (same as what JIRA is doing for issues
for example - It has 20 or so rights). Or course it makes xwiki more
complex to use too.
Thanks
-Vincent
Hi Lilianne,
On Jun 18, 2008, at 4:04 AM, Lilianne E. Blaze wrote:
Well, yes and no.
It does go against traditional wiki ideas, but it could be useful in
Wiki-as-CMS scenario. Hello,
Is there a way to restrict access to past versions only to Admin
and/
or
a selected "power users" group?
I don't think this is possible out of the box. It also goes against
the wiki principle of openness. > Of course nothing prevents your from modifying the
historyinline.vm
> file to add a check on rights. Or create your custom skin that
> overwrite the historyinline.vm file (easier for upgrades).
3:49 p.m.
Vincent Massol wrote:
On Jun 18, 2008, at 3:03 PM, Lilianne E. Blaze wrote:
Yes I think. It's more of a suggestion than a need on my part.
Vincent Massol wrote:
Yes, I agree.
Is the solution I gave good enough for you for now? I don't see any Hi Lilianne,
On Jun 18, 2008, at 4:04 AM, Lilianne E. Blaze wrote:
Well, yes and no.
It does go against traditional wiki ideas, but it could be useful in
Wiki-as-CMS scenario. Hello,
Is there a way to restrict access to past versions only to Admin
and/
or
a selected "power users" group?
I don't think this is possible out
of the box. It also goes against
the wiki principle of openness. easy and generic way of adding this to the core.
Creating a new
"History Right" would be too complicated for this right now. I think
we need to overhaul our rights system so that it can scale and then we
should probably add more rights (same as what JIRA is doing for issues
Will there be an option to make custom rights?
for example - It has 20 or so rights). Or course it
makes xwiki more
complex to use too.
Thanks
-Vincent
Greetings, Lilianne
3:55 p.m.
On Jun 18, 2008, at 3:49 PM, Lilianne E. Blaze wrote:
Vincent Massol wrote:
My full vision is that rights will be components in the new
architecture. An application (XAR) will be a set of pages but also
jars with components, external jars, skin extensions, interface
extensions. As such an application will be able to bring it Rights.
Actually exactly in the way jira is doing this right now. Thus the
Rights UI should be generic enough to accept any number of rights.
This is not the case right now and this is why I say we should make it
scalable.
Thanks
-Vincent
On Jun 18, 2008, at 3:03 PM, Lilianne E. Blaze
wrote:
Yes I think. It's more of a suggestion than a need on my part.
Vincent Massol wrote:
Yes, I agree.
Is the solution I gave good enough for you for now? I don't see any Hi Lilianne,
On Jun 18, 2008, at 4:04 AM, Lilianne E. Blaze wrote:
> Hello,
> Is there a way to restrict access to past versions only to Admin
> and/
> or
> a selected "power users" group?
I don't think this is possible out of the box. It also goes against
the wiki principle of openness.
Well, yes and no.
It does go against traditional wiki ideas, but it could be useful in
Wiki-as-CMS scenario. easy and generic way of adding this to the core.
Creating a new
"History Right" would be too complicated for this right now. I think
we need to overhaul our rights system so that it can scale and then
we
should probably add more rights (same as what JIRA is doing for
issues
Will there be an option to make custom rights? > for example - It has 20 or so rights). Or course
it makes xwiki more
> complex to use too.
>
> Thanks
> -Vincent
7:18 p.m.
Vincent Massol wrote:
Hi Lilianne,
On Jun 18, 2008, at 4:04 AM, Lilianne E. Blaze wrote:
That only hides the links, but in order to really prevent access to history, you must also
change
the code for com.xpn.xwiki.user.impl.xwiki.XWikiRightServiceImpl (or provide your own
RightService
implementation) to prevent accessing the /viewrev/ action.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hello,
Is there a way to restrict access to past versions only to Admin and/
or
a selected "power users" group?
I don't think this is possible out of the box. It also goes against
the wiki principle of openness.
Of course nothing prevents your from modifying the historyinline.vm
file to add a check on rights. Or create your custom skin that
overwrite the historyinline.vm file (easier for upgrades).
6031
days inactive
6031
days old
6 comments
3 participants
participants (3)
-
Lilianne E. Blaze -
Sergiu Dumitriu -
Vincent Massol