Hello again, I have finished updating the FAQ tutorial. You might need to clear your cache (Ctrl + F5 on most browsers) to see the updated screenshots. I have followed the updated tutorial myself and was able to successfully create a FAQ application. Thank you, Manuel On Wed, Aug 26, 2015 at 9:13 AM, Manuel Smeria <manuel(a)xwiki.com> wrote:

Hi, On Mon, Aug 31, 2015 at 8:39 PM, Alex Henrie <alexhenrie24(a)gmail.com> wrote: There is no such restriction or best practice. It all depends on what that page is used for and what are the objects inside that page used for as well. Some objects can be used to mark certain pages. Others can store extra data: structured content in general (defined in user created xclasses) or even page comments, tags, etc. Other objects can set the document's rights. Other objects can specify which is the sheet to apply when viewing or editing the current document. The document's content (what you call "A string of wikitext") can have static content or dynamic content (scripts/code) which can execute either independently of the objects in the page or by reading some data from those objects, processing it and/or displaying/presenting it as the (dynamic) content of the document you are viewing. There are enough cases when a document has both content and objects, as the ability to have structured content in your document is a very big plus in XWiki, compared to some other wiki platforms. XWiki is a flexible platform and it all comes down to the usecase you are using it for, i.e. what you want to achieve. Hope this helps, Eduard

Hi Alex, On 4 Sep 2015 at 19:56:31, Alex Henrie (alexhenrie24@gmail.com(mailto:alexhenrie24@gmail.com)) wrote: Indeed that’s the general premise of a wiki and that’s how it differs from other tools: collaborating and creating content is hard, which is why wikis make it easy for users to do so without having to ask for permissions. Notifications, history and rollback features are the way to provide oversight. In the huge majority of cases, no action is required and serendipity happens :) In XWiki, wiki pages can contain either unstructured data or structured data (xobjects). There’s no fundamental difference between both types of data and users should be free to add and modify any type of data (provided they have edit rights on the page). You mention “a page that is supposed to be wikitext-only”. Who says that? :) Who says that a page which starts with wiki text cannot be improved by having some part of it structured? I’ve done this countless of times to provide more features. I personally would find it a pity to arbitrarily restrict permissions to only some users. That’s not the principle of wikis at heart. I’d say: always try to be the most open, and if it causes problems then close down a bit if there’s no other way. In addition, some companies are used to the traditional way of working and would prefer to close down things a bit. Because XWiki is a flexible platform and because it’s an Enterprise Wiki, it has a strong permission model. Recently (in XWiki 7.2M1 and 7.2M2), we’ve added a new permission called the Scripting Permission and it’s possible to give it only to some users. See http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki72M1#HScr… and http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki72M2#HScr… I hope the rationale is more clear! (not sure if I explained it right :)). Thanks -Vincent

Hi Alex, On 5 Sep 2015 at 00:32:54, Alex Henrie (alexhenrie24@gmail.com(mailto:alexhenrie24@gmail.com)) wrote: 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)? Thanks -Vincent

On Thu, Sep 10, 2015 at 3:50 AM, Alex Henrie <alexhenrie24(a)gmail.com> wrote: The simplest thing you could do is to add a skin extension [1] that hides the unwanted edit modes, either through CSS or through JavaScript. The second option would be to customize the skin [2] and hide the options directly from the skin (server side, in the .vm files). This will still allow some users to directly use a hand-crafter URL (i.e. by bypassing the UI) to access the other edit modes, but those would be isolated cases and should not be an issue. Thanks, Eduard ---------- [1] http://platform.xwiki.org/xwiki/bin/view/DevGuide/SkinExtensionsTutorial [2] http://platform.xwiki.org/xwiki/bin/view/DevGuide/Skins

2015-09-10 5:26 GMT-06:00 vincent(a)massol.net <vincent(a)massol.net>et>: Done. http://jira.xwiki.org/browse/XWIKI-12555 -Alex