3 Feb
2014
3 Feb
'14
11:26 a.m.
On 3 Feb 2014 at 11:16:15, Denis Gervalle (dgl@softec.lu(mailto:dgl@softec.lu)) wrote:
On Mon, Feb 3, 2014 at 10:56 AM, vincent(a)massol.net
wrote:
I hope I’m wrong :) I’ve based my mail on what I saw on a subwiki I own on myxwiki.org
which I had upgraded using a local users and where I saw that all features that were
requiring PR were broken. Now myxwiki.org is on 5.2 so this was the DW of 5.2. Maybe we
fixed/changed something after that.
Would be interesting to retest if someone has a subwiki on myxwiki.org that has not been
migrated.
I guess we could also upgrade myxwiki.org to 5.4RC1 and retest it and at the same time try
to find issues that could be fixed either quickly for 5.4 final or for 5.4.1. I wanted to
wait for 5.4 final before upgrading myxwiki.org but if we think this issue shouldn’t exist
we might want to upgrade sooner.
Thanks
-Vincent
Hi guys,
I’ve just realized that on farm wiki like myxwiki.org we have an
important issue when we upgrade the WAR.
When local admins log on their wiki they get the DW, they follow it and
then they find their wiki is broken in several places:
- search/search suggest not working
- activity stream stays empty
- reset password feature doesn’t work
- etc
The problem is that the local admin users do not have PR on subwikis and
since we have several pages requiring them, this breaks their upgrades.
Isn't it a bug ? Shouldn't any user having access to the DW be able to
execute it properly, disregarding its own rights ?
Is there a recent change that cause the DW to make its operation based on
the current user, that was not there before ?
I had always thought that the DW will keep package content author in place,
like any other meta.
Is this wrong ? This is a
pretty serious problem since they have no way of doing a proper
upgrade and this doesn’t do good advertising for xwiki...
What can we do in the short term (for 5.4.1 for example since I believe
this is something really urgent to fix)?
Only solution I can think of (which should be pretty quick) would be to
look at all pages requiring PR in our default XE XAR package and replace
those with specific API calls.
> WDYT?
>
> Thanks
> -Vincent