Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:Licenses.Code.AvailableTemplateProvidersFilter]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.
Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:Menu.MenuXWikiOrg]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.
Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:CKEditor.EditMenuEntry]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.
Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:SyntaxHighlighting.EnableSyntaxHighlighting]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.

Show last authors
1 Here are some excerpts of what users have said while filling the [[XWiki Product Survey>>Survey.ProductFeedback]].
2
3 * [[Feedback from 2022>>||anchor="2022"]]
4 * [[Feedback from 2021>>2021]]
5 * [[Feedback from 2020>>2020]] {{info}}The survey was broken between October 2019 and April 2020{{/info}}
6 * [[Feedback from 2019>>2019]] {{info}}The survey was broken between October 2019 and April 2020{{/info}}
7 * [[Feedback from 2018>>2018]]
8 * [[Feedback from 2017>>2017]]
9 * [[Feedback from 2016>>2016]]
10 * [[Feedback from 2015 and older>>Older]]
11
12 * Sent 28.06.2022 11:47:51:(((
13 > Text-formating like colored text or striked thru text, background colors should be available in WYSIWYG-editor. Now you have to switch to sourcecode to modify.
14
15 **Answer from Vincent Massol (XWiki Core Dev)**:
16 > This is done voluntarily to focus on content and promote style consistency in the wiki. However [[it can be turned on>>extensions:Extension.CKEditor Integration.WebHome||anchor="HStandardCKEditorFeatures"]].
17 )))
18 * Sent 21.06.2022 11:12:23:(((
19 > How to set permissions to read-only? Restrict the content of others' articles
20 > Detailed instructions in Chinese
21 )))
22 * Sent 31.05.2022 12:09:40:(((
23 > If xwiki can use less memory, and can run on machines like a raspberry pi 3B+, it'll have a brighter future, because some people who use it may want to run it on an energy-saving machine like a raspberry pi or a cheap but poor-performance VPS, etc.
24 > I think you can try to add a "lite flavor", it will not create an empty wiki, but only have basic wiki features, and administration tools. I also think you can try to add a "custom mode" when xwiki is installing, which will not only allow the webmasters to choose the features they want, instead of choose a flavor, but also let them can adjust the basic settings when xwiki is installing.
25 > P.S. I'm poor in English, if I made some mistakes like wrong grammer, please accept my "sorry" for that!
26 )))
27 * Sent 28.04.2022 16:40:35:(((
28 > Documentation is a bit random and hard to follow at times, or even non existent (or maybe not findable by me). e.g. I was trying to find what the various fields when creating a themes for flamingo where. I gave up.
29 )))
30 * Sent 04.04.2022 19:44:17:(((
31 > Oh, the syntax .... it's taken me a while to work out how to reference headings and anchors but I have got there. I've used Markdown and even nroff in the past, so I'm generally familiar with the non-WYSIWYG interface (and actually prefer it). I have looked all over for proper worked examples, but all I saw was a repeat of the syntax guide already on wiki.org. I'd really welcome a page or series of pages with worked examples so we can see how this is done. I'd even be happy to help build this.
32 > I'm using xwiki because a lot of our data is linked in multiple dimensions, so getting reports of how information is linked is actually more important than the information itself, in some circumstances. I'm hoping to be able to create dashboards based on the linkages. Let's see how far we get.
33 )))
34 * Sent 04.04.2022 20:40:47:(((
35 > Better support for multi-language. The Blog is not working in multiple languages, and the translation/maintenance of multi-language sites is not very user-friendly.
36 )))
37 * Sent 31.03.2022 11:08:18:(((
38 > Implement a access rights information section (e.g. in page header, cf. Confluence) that informs users whether page/subpages are restricted or not. Imrove the Like functionality: Let users see at first glance who liked a page Implement a gadget for a dynamic list of most popular pages/comments etc. (cf. Confluence) based on clicks, interactions and likes over time
39 > I greatly appreciate this gorgeous piece of software!
40 )))
41 * Sent 11.03.2022 09:32:14:(((
42 > XWIKI is very good as a collaborative documentation environment, it is more flexible and feature rich than Atlassian Confluence. But for a full replacement for Confluence, a very important functionality is still missing – customizable export by templates to PDF and DOCX / ODT formats. This feature is very important for documentation, because it allows you to automatically generate stylized documents from wiki articles. This is very important, as it allows the technical writing team to concentrate on the documents and not waste time on designing the appearance of documents for the customer. There are great add-ons for Confluence: - Scroll Word Exporter - Scroll PDF Exporter. This extensions allow you to fully customize the conversion of wiki articles from Confluence to DOCX and PDF formats. The Scroll Word Exporter extension allows you to load templates with styles created in MS Word and use them when converting to fully control the style of documents. It works amazing! In addition, there is an additional Scroll Exporter extension that allows you to flexibly customize the export for article fragments. And it's very helpful! If XWIKI has functionality like the Scroll Word/PDF Exporter, it will be a super feature for documentation and will allow many companies to completely transfer documentation from Confluence to the wonderful XWIKI!
43 )))
44 * Sent 22.02.2022 16:40:35:(((
45 > collapsible text boxes somewhat easier interface customization (e.g. font sizes in navigation and menu panels) installer can be confusing, especially when using the distribution wizard
46 )))
47 * Sent 03.02.2022 01:50:49:(((
48 > Quite honestly, I particularly like the Confluence product and am only moving away because I cannot put sensitive documentation in a cloud hosted solution. I would suggest using their product and take inspiration from what they do well to enhance your product. eg: -Be more windows friendly, most businesses use windows servers, and the setup process on windows is arduous. Consider packaging the setup into a full stack all-in-one installer and you would have more people complete a proof of concept they can take to sign off -simple things like the sections option in confluence is very useful to have built into the editor -have a non-dev/non-expert user review documentation for xWiki, for example, setting up templates (https://www.xwiki.org/xwiki/bin/view/Help/Templates/), useful function but when setting it up, the "template to use" field was not obvious that it was just a normal page that can be used as the template, and then you search for xwiki create a template you get the same help page that does not describe what the "template to use" actually is (alternatively you could name that field, "Page to use as template")
49 )))

Get Connected