Import in sub-wiki ruins page property "saved with programming rights"

There is a tricky way to install a package with Programming rights into wiki farm.

Now if you own the sub-wiki, you need to be sure that you either:

• install with a global user having PR and uncheck the backup pack option
• install with a global user having PR and keep the backup pack option but in this case make sure that the user defined in the XAR exists and has PR

Otherwise all imported pages would be saved without PR and scripts won't work until you resave them under the user with Programming Rights.

Look like worth fixing.

--------------------
Previous story from mailing list:

On Jan 17, 2013, at 7:09 AM, Haru <haru_mamburu@mail.ru> wrote:

> Hi, Vincent,
>
> Thanks a lot for clarification. Updated the manual: http://platform.xwiki.org/xwiki/bin/view/AdminGuide/ImportExport
>
> "If it's NOT backup package then the user is the current user"
>
> It's true for XE. But in XEM, in a sub-wiki local Admin User can not have Programming Rights, so importing XAR under local Admin as NOT backup will cause pages saved with no PR?

I think you're correct. Can someone verify this?

> So "NOT backup package" in wiki farm is useless and even HARMFUL for any local user. Am I correct?

Seems so…

Actually it's worse, just checked (thanks Andreas) and it appears that if your user isn't admin on the main wiki then the backup pack option is not going to have any effect at all when importing in a subwiki...

> "If it's a backup package then the user used is the one defined in the XAR. Usually it is XWiki.Admin"

I was wrong here. That used to be true but we've changed that some time ago and now the XARs that we package have xwiki:XWiki.Admin as the user.

> Will pages be saved with PR regardless the fact that local admin doesn't have PR?

No they won't. if the user in the XAR is "XWiki.Admin" then this user will be used and this user will not have PR on a farm.

Basically on a farm if you need to install some pages that require PR you'll need to install that XAR with a global user that has PR.

Said differently, ATM there's no way for a user on myxwiki.org to be able to properly install all XE pages (pages which require PR will fail to install properly).

Now if you own the wiki, you need to be sure that you either:

• install with a global user having PR and uncheck the backup pack option
• install with a global user having PR and keep the backup pack option but in this case make sure that the user defined in the XAR exists and has PR

Said differently we're pretty bad and we need to fix this…

Thanks
-Vincent

> Среда, 16 января 2013, 19:19 +01:00 от Vincent Massol <vincent@massol.net>:
>>
>> On Jan 14, 2013, at 4:09 AM, Haru < haru_mamburu@mail.ru > wrote:
>>
>>> Yes, there is a common problem: necessary pages are not saved with programming rights.
>>>
>>> There are several ways to fix it:
>>> 1. Make standard XAR import as backup package. As far as I understand, XWiki imports pages as already saved with programming rights. In this case there is no need in user with programming rights (as far as I understand XWiki)
>>> 2. Use Admin Tools application and run Programming Rights Check. In most cases it would help.
>>> 3. Open and save all these pages manually with a user with programming rights. "These pages" means all scripting pages that fails to run. In this case all "dependencies" you will have to search manually looking at source code.
>>>
>>> I had several cases, mainly in virtual wikis, were macroses, sripts, sheets, dashboards etc. were magically not working.
>>> Each time It happens, I find it not from the very beginning and cannot trace action-result dependencies.
>>> But sure, it looks very annoing to "debug" new wiki when users send me requests, that something is not working in the BRAND NEW virtual wiki out of the box.
>>> IMHO, it happens mainly after upgrade and new wiki creation, but I can't even guess what actions are giving such a results, that is why, I can't jira it as a bug. Looks unpredictable for me, because in 99% of cases I use user with programming rights to fulfil admin tasks, but it doesn't help much
>>>
>>> Some last cases I remember: Activity stream, AllDocs page refused to show Tree, Spaces macro refused to show spaces, dasboard etc.
>>>
>>> If someone will give a solution, how to fix ALL pages containing scripting all together (resaving with programming rights) and/or give a hint gow to avoid this, would appreciate much, because XWiki sometimes drives me crazy to make it running
>>
>> We had an issue in the past with the import and programming rights but it's been fixed a long time ago now.
>>
>> Basically all you need to do is ensure that the user used to save the page has PR:
>> * If it's NOT backup package then the user is the current user
>> * If it's a backup package then the user used is the one defined in the XAR. Usually it is XWiki.Admin. This means for ex that if you have wiki farm and you install the XAR in a subwiki that user may not exist in your local wiki (since it could be a global user on the main wiki).
>>
>> Note that pages requiring PR are supposed to also contain a XWiki.RequiredRightClass xobject so it should be easy to query them. If you find some that don't have this XObject please let us know. This XObject is just indicative and doesn't change permissions.
>>
>> Thanks
>> -Vincent
>>
>>> Воскресенье, 13 января 2013, 17:08 -08:00 от Regan Gill < reganfgill@yahoo.com >:
>>>> Hi,
>>>>
>>>> I updated the virtual wiki http://scservicesub.myxwiki.org with the xwiki-enterprise-ui-all-4.4-rc-1 and now the Activity stream on the dashboard doesn't show anything. I am wondering if I need someone with programming rights to do the import?
>>>>
>>>> I am used to running our wiki and now moving it to the virtual system and so many things seem to be hard to do....
>>>>