Hi, Vincent,
Thanks a lot for clarification. Updated the manual:
"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? So "NOT backup package" in wiki farm is useless and even HARMFUL for any
local user. Am I correct?
"If it's a backup package then the user used is the one defined in the XAR.
Usually it is XWiki.Admin"
Will pages be saved with PR regardless the fact that local admin doesn't have PR?
Среда, 16 января 2013, 19:19 +01:00 от Vincent Massol <vincent(a)massol.net>et>:
On Jan 14, 2013, at 4:09 AM, Haru < haru_mamburu(a)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(a)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....
Thanks,
Regan
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Kind regards,
Dmitry
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users