Hi Alex, On 10 Sep 2015 at 02:51:06, Alex Henrie ([email protected](mailto:[email protected])) wrote:
2015-09-05 3:17 GMT-06:00 [email protected] :
ok, I understand what you mean now: you’d like the ability to lock down existing applications, i.e. prevent users of them from making structural changes to them.
That’s a valid use case and we support it :)
Basically there are 2 use cases: * Letting users make changes to applications because this allows multiple users to develop collaboratively apps using XWiki. The idea is that of refactoring and an app is never ever finished and can always be improved. * However you may only want some experienced users or devs to do that and not anyone.
What happens is that the app has 2 types of wiki pages (aka documents): * Technical pages that make the app * Data pages which are created by the user when he/she uses the app
So what we do is that when we develop apps we usually create 2 spaces, one for the technical pages and one for the data pages. In this manner we can set permissions very easily on the space containing the technical pages so that only some authorized group or users have edit rights on them.
Maybe in your case all that is required is to ask the phenotips developers to not allow all users to have edit rights by default on the technical pages of this app (and restrict them to admins by default for example)?
PhenoTips already prevents ordinary users from editing technical pages, period. What I really want is to go a step further and only allow the inline form editor (editor=inline) to be used to edit data pages. I do not want users to be able to add classes, objects, or wikitext to pages (editor=class, editor=object, editor=wiki) outside of what the editor written specifically for PhenoTips would allow.
ok, that’s interesting. I don’t remember anyone voicing this concern but I can understand it. Indeed ATM, we provide a single Edit permission which allows any editor to be used (object, class, wiki, WYSIWYG, rights, etc). We could decide in the future to be more fine-grained, and provide a additional separate permission for Form editing (aka inline editing). Thus a User or Group could not have Edit rights in general and have only Form Edit rights. Maybe you could open a jira issue at http://jira.xwiki.org on this so that we remember it and discuss it/implement it in the future? (or whoever wants to submit a pull request/patch). Thanks -Vincent
Again, this feature is not a dealbreaker, but it could avoid abuse of the system.
-Alex