Wiki source code of Download Form Feedback

Version 82.2 by Vincent Massol on 2018/03/30

version	line-number	content
1.1	1	Here are some excerpts of what users have said while filling the [[download form>>DownloadCode.DownloadFeedback]].
	2
82.2	3	* Sent 30/03/18 19:45:43:(((
	4	> The documentation is a bit difficult to follow. It is apparent that English is not the first language for many of the writers which makes for some ambiguous instructions.
	5	)))
82.1	6	* Sent 10/03/18 07:50:46:(((
	7	> - built-in integration with Slack
	8	> - better notifications handling / more options
	9	> - better RSS support: many services I've used with XWiki complain about RSS format problems
	10	)))
81.1	11	* Sent 02/03/18 23:31:34:(((
	12	> Hi there, using the latest flavor I am very happy with xwiki. However, I had to get my hands dirty deep in my debian to get things working smoothly. I find too bad the server takes 10 minutes to start because of a single stupid jar scanning files parameters (okay, that's tomcat). Documentation is too light IMHO and I had to scratch my head for some evenings to get it working with my nginx setup in reverse proxy.
	13	)))
80.1	14	* Sent 2/6/2018 9:55:59:(((
	15	> For some coustomizing features I'm missing more documentation or examples
	16	)))
79.1	17	* Sent 24/01/18 16:13:56:(((
	18	> Real markdown support. Currently this is very shaky, usable only for simple documents, but when it gets more complicated, formatting is weird. UI also suggests that I can change the formatting after the document has been created, but this rarely works.
	19	>
	20	> Good that i can be locally installed and programmed etc.
	21	)))
78.1	22	* Sent 11/12/17 11:42:45:(((
	23	> * when used as a knowledge base, it feels too heavyweight, complex, not very Wiki like, more like a full CMS, e.g. typing simple WikiLinks should create a link
	24	> * pages should be auto-saved
	25	> * MarkDown support by default
	26	>
	27	> like the professional and clean, Java based approach, very feature rich and evolved over a long time
	28	)))
76.1	29	* Sent 27/11/17 14:36:06:(((
	30	> To be fair, I am used to Confluence and MediaWiki (also Twiki, but not often).
	31	> I am running on Ubuntu 16.04 but simple things don't seem to work, like the Code macro. And it's very difficult to understand why. I am a software developer, and while I would like to take the time to debug, diving into the Wiki code (a productivity app) while attempting to document other projects just can't be a priority right now, so we'll probably move on to a different platform.
	32	)))
77.1	33	* Sent 17/11/17 21:30:00:(((
	34	> A simple documentation flavour (minimal set of pages and extensions)
	35	)))
75.1	36	* Sent 15/11/17 15:54:54:(((
	37	> For some reason I cannot see more than 2 subelement in the navigation menu.
	38	> Also, moving a page is a nightmare -> In the most cases, I can't. And I don't know why or how to achieve my goal. The only feedback is "Forbidden sign".
	39	)))
74.1	40	* Sent 11/11/17 14:40:56:(((
	41	> Some of the workflows seem a bit complicated, for example: create page, save it immediately, go and add attachments in view, edit the page again to link the attachments.
	42	>
	43	> Forms and Apps seem complicated - I tried making one but it didn't work as I expected. I probably need to do more reading about this.
	44	>
	45	> I looked at a number of wiki projects to use at work (we are replacing mediawiki) and XWiki was easily ahead of the others. It also won out over Confluence which I guess many people would see as the class-leading "enterprise wiki".
	46	>
	47	> Thank you for all the work over so many years to make this project such a success.
	48	)))
73.1	49	* Sent 02/11/17 01:55:34:(((
	50	> Option to change the name of the installed standard flavor (ie 'foobar' instead of 'xwiki')
	51	> Better documentation of updating / modifying navigation / panels.
	52	> Ordering of entries in navigation panel.
	53	)))
72.1	54	* Sent 20/10/17 17:12:48:(((
	55	> Some things are way too complicated in my opinion. What just comes to my mind:
	56	> - theming (css? less? velocity?)
	57	> - upgrading to a more recent version
	58	> ...
	59	>
	60	> Having wordpress in the back of my head, they're doing much better in simplicity. Of course, xwiki is a completely different story, with many, many great tricks under the hood :)
	61	>
	62	> The forum guys are great. I also appreciate the work you're putting into this - over all it's awesome!
	63	)))
69.4	64	* Sent 9/29/2017 23:43:46:(((
69.1	65	> I really liked the one step Windows installer for initial testing, but had to spend much more time getting the production capable combination up and running manually. I do like the Docker Containers though.
69.2	66	>
69.1	67	> Just want to say that the XWiki website is excellent and contains all the information one would need to get started. To me, XWiki is the best open source wiki engine I've come across. Thanks very much to the XWiki team for putting this together and making it available!
	68	)))
70.1	69	* Sent 28/09/17 08:19:39:(((
	70	> a visual document diff would be nice
	71	> friendlier looking than the terminal plus and minus style
	72	> e.g. https://github.com/GeertjanWielenga/netbeans-visual-diff-standalone/raw/dev/screenshots/diff-in-swing-app.png
	73	>
	74	> "?q=netbeans visual diff" led me to these
	75	> https://github.com/GeertjanWielenga/netbeans-visual-diff-standalone
	76	> https://github.com/cismet/netbeans-visual-diff-standalone
	77	> https://github.com/albfan/jmeld
	78	> http://plugins.jedit.org/plugins/?JDiffPlugin
	79	> https://stackoverflow.com/questions/2019089/java-gui-component-for-displaying-diffs
	80	>
	81	> Thank you for sticking with making what is, in my opinion, the most fully featured wiki available for folks that don't want mediawiki.
	82	)))
68.1	83	* Sent 9/24/2017 19:01:14:(((
	84	> - Do not redraw navigation tree each time i click some node.
	85	> - Include more features to editor. There are many of them now available only from "source" (for example text color) or from another editor, which in turns have another disadvantages.
	86	)))
71.1	87	* Sent 24/09/17 23:12:44:(((
	88	> Production version should have a graphical installer so it can be easily and quickly installed and setup. Otherwise depending on the user installing to know what they are doing to configure and get things working when they are looking for something simple and quick to setup to start using.
	89	)))
67.2	90	* Sent 9/17/2017 22:55:06:(((
	91	> Make it more user friendly
	92	)))
67.1	93	* Sent 11/09/17 16:16:26:(((
	94	> Social Login module is totally broken and not works, but in 2k17 year this module MUST HAVE.
	95	)))
66.1	96	* Sent 9/7/2017 0:14:33:(((
	97	> I'm very inexperienced, but it seems the editor is a little clunky to put a large set of names together. I would like some way of tagging entries and have them appear in a prompt list for example.
	98	>
	99	> I'm really happy with the product so far. It's very extensible. This is important because I'm not 100% certain what is the best layout for my pages.
	100	)))
65.1	101	* Sent 8/22/2017 13:33:29:(((
	102	> MathJax/Katex latex renderer instead of pictures
	103
	104	Answer from Vincent Massol (XWiki Core Dev):
	105
65.2	106	> I'm not an expert on this but the [[Formula Macro>>doc:extensions:Extension.Formula Macro]] has [[different configurations>>doc:extensions:Extension.Formula Macro\|\|anchor="HTechnicalinformation"]]. Wouldn't that fit your need?
65.1	107	)))
64.1	108	* Sent 8/16/2017 20:11:42:(((
	109	> During our evaluation phase I repeatedly installed on a virtual box based centos6 vm on my macbook. On some of the installations I didn't get the option to download a skin which made that installation useless. When we installed for actual use we didn't have that problem.
	110	)))
63.1	111	* Sent 23/07/17 14:58:01:(((
	112	> I am really enjoying using this (VERY) neat WYSIWYG Wiki... My only frustration is that, with the default skin, a lot of my screen real-estate is taken with headers and titles - leaving little room left for content without scrolling. (My web browser is usually 'zoomed in' - which exaggerates this.) I wish it were easier to quickly "try" some other skins, and find one that leaves more screen real-estate for my content.
	113	>
	114	> I am using XWiki for 'notes' and to tie together menus for various web applications.
	115	)))
62.1	116	* Sent 03/08/17 20:05:15:(((
	117	> Dashboard Design - Ready to start designs / Templates - improvement in navigation
62.2	118	>
	119	> Missing features: Professional project management with milestones, deadlines, effort, time measuring, UML diagram support
62.1	120	)))
61.1	121	* Sent 05/07/17 14:36:29:(((
	122	> I would like to have a nice list for IP-adresses (in our own develope-area), where everybody could check easily, which IP-adresses are in use or not.
61.2	123	> If something like this already exists, I could not find it yet. The List should have a Dropdown menue and a calculator, so you will see the available adresses.
61.1	124	)))
59.1	125	* Sent 6/12/2017 13:03:30:(((
	126	> If you kill the browser while a page is being moved, the wiki gets broken.
	127	)))
60.1	128	* Sent 02/06/17 17:17:31:(((
60.2	129	> finer granularity of rights and tasks. It's a pain to have to be admin just to edit templates or move pages around a wiki. Would be better to let us configure which access level corresponds to which rights/tasks.
	130	> ability to export/import templates, so they can more easily be shared across wikis
	131	> thanks for your work, team!
60.1	132	)))
58.1	133	* Sent 07/06/17 12:05:33:(((
	134	> Documentation must be updated and more detailled. Especially for Windows / MS SQL systems. Otherwise it's a great system.
	135	)))
57.1	136	* Sent 29/05/17 22:41:50:(((
	137	> Make it easier to have a Linux command-line installation. Or use another high-usability approach like a wizard.
	138	> I can't tell if your project is live from Linux Mint. I added the stable source, but can't pull up xwiki-*. Is your project alive, and if so, could I have current instructions to install it from the Linux command live?
	139	> (I'm sorry if it sounds rude to ask if you project is live, but I am extremely confused by the discrepancy between what the website claims and what I am (not) getting to show up using aptitude.)
	140	)))
55.1	141	* Sent 26/04/17 16:36:36:(((
	142	> 1- Speed
	143	> 2- Installation with Debian package is fine, but doing it manually is not as easy as expected.
	144	> 3- Missing: Viewing permissions and inherited permissions for users and groups (and subgroups) in a site-map or as a tree for single user or group
	145	> 4- Missing: Definition and distinction of groups and subgroups. I wanted to know, which way down it will be inherited and how to set it up (best practice)
	146	> 5- Missing: An alternative to the xwiki navigation entry
	147	> 6- Missing: List of orphaned pages
	148
	149	Answer from Vincent Massol (XWiki Core Dev):
62.1	150
55.1	151	> Regarding point 6, we no longer have orphaned pages now that we have nested pages! You always create pages in a hierarchy. That's why we removed the ability to see orphaned pages!
	152	> For points 1, 2, 5 we'd need more details.
	153	)))
54.1	154	* Sent 22/05/17 03:21:57:(((
	155	> The Extensions lack adequate descriptions. Mostly there is just a single line and I will have to install an extension just to understand what it does.
	156
	157	Answer from Vincent Massol (XWiki Core Dev):
62.1	158
54.1	159	> I don't find this to be a fair statement. The large majority of Extensions have nice descriptions. Also several Extensions are contributed by the XWiki community at large and not by the XWiki Dev Team so we don't control those. Could you let us know which specific Extension you find is lacking description?
	160	)))
53.1	161	* Sent 06/05/17 12:00:00:(((
	162	> Hello! There is very lack simple data backup. The lack of a simple backup of all data (via the web interface) greatly limits the use of Xwiki. Such a backup is available at Confluence.
	163	> Another disadvantage is a complicated backup and a complicated installation.
	164	)))
52.1	165	* Sent 22/04/17 22:47:10:(((
62.1	166	> speed, everything is so slooooooow, xwiki takes 5min to start after reboot (well actually I think this is "normal" for Java/Tomcat but that doesn't make anything better)
52.1	167	)))
51.1	168	* Sent 4/22/2017 5:09:10:(((
	169	> Would you please add digest-md5 in ldap Authentication，instead of simple?
	170	)))
49.1	171	* Sent 4/16/2017 10:12:55:(((
	172	> More Cookbooks. There is often a lack of documentation so I can not really use many features and functions. So I am starting now looking into the code. But this is time comsuming.
	173	> May be sell usefull apps or functions like the integration of onlyOffice where people have to pay something.
62.1	174
49.1	175	May be write a book or a wiki about how to use and extend xwiki. Give access to this for a fee. At the moment my impression and personal experience is that documentation is avaoid because of costs.
50.1	176
	177	Answer from Vincent Massol (XWiki Core Dev):
62.1	178
50.1	179	> Regarding OnlyOffice there's an [[OnlyOffice Paying Application>>https://store.xwiki.com/xwiki/bin/view/Extension/OnlyOfficeConnectorApplication/]]
49.1	180	)))
48.1	181	* Sent 4/11/2017 7:52:49:(((
	182	> It would be better to make it easy to add applicaiton . and when i make the link, The new page creation menu is not being on top-down menu over "Wiki Page , Attached File , Web page... , Email address ". So, If there is the new page or add page menu of them, It would be confortable.
	183	)))
47.1	184	* Sent 06/04/17 16:19:25:(((
	185	> simplified group / user management
	186	> simplified rights management
	187	> simplified upgrade
	188	>
	189	> There are too many branches (9.0 9.1 9.2 ...) while there are fewer maintenance releases.
	190	> it's hard to keep up; as there is no simple upgrade mechanism (except to export and import everything)
	191	> I know features are important (we make software), but stability and reassurance there are bugfixes is important as a user.
	192	>
	193	> But all in all: i'm trying to convince the company to quit confluence in favor of xWiki. So keep up the good work!
	194
	195	Answer from Vincent Massol (XWiki Core Dev):
62.1	196
47.3	197	> Regarding branches, we only [[support 3 branches>>xwiki:Main.Support]]:
47.4	198	> - the LTS branch. That's the one you should use to have a super stable version.
	199	> - the latest stable branch. new features but less stable than the LTS.
	200	> - the development branch. Work in progress
47.1	201	)))
46.1	202	* Sent 3/1/2017 9:31:17:(((
	203	> more simple and easy maintenance
	204	> Beautiful page design will attract more people
	205	)))
45.2	206	* Sent 2/24/2017 23:14:26:(((
	207	> Better and more complete user and admin documentation
	208	> Great job!
	209	)))
56.1	210	* 09/02/17 18:42:52:(((
62.1	211	> I would love to see indenting for non-list things, like text (including block text) and images. That really makes pages easier to read. Also, I would love more text formatting options, like simply setting the color of a section of text. I find that I (too) OFTEN have to resort to editing the source with "(% style="" %)" tags to achieve the look that I want. Normal users largely will not resort to that, so the resulting pages are much less impactful. Table properties could be expanded, for example to allow a background color on a row. Last, and most minor, would be an additional property on the image object to add a simple border. When a screen capture is done on the same background color that the wiki page uses, the lack of visible boundary can disrupt the impact of the graphic.
56.1	212	> The server hosting xwiki is in India, and I am in the U.S. I am surprised how well it performs. Not lightning fast, of course, but still very usable.
	213	)))
45.1	214	* Sent 2/6/2017 7:38:23:(((
	215	> I want to write mathematic formula using Xwiki. The mimetex.cgi, for example, would be fine to be integrated in Xwiki.
	216	> It's very comfortable using Xwiki. thank you!
	217
	218	Answer from Vincent Massol (XWiki Core Dev):
62.1	219
45.1	220	> You should try to use the bundled [[Formula Macro>>extensions:Extension.Formula Macro]].
	221	)))
44.1	222	* Sent 1/26/2017 19:53:34:(((
	223	> I'm a student, so I need some features like note-taking, using xwiki like a blog, previously I was using dokuwiki and tiddlywiki, some features from these personal wikis should be inherited to xwiki to use it for wide range of applications
	224	)))
43.1	225	* Sent 06/01/17 22:51:20:(((
	226	> Code format does not work, nor smalltext format and others, the format info is lost after preview or save.
	227	)))
41.1	228	* Sent 1/5/2017 22:40:12:(((
	229	> It won't install in Glassfish 4.1.1 it won't run in Tomcat 9. I've lost 2-3 days and would rather start over with something else, were it my decision
	230	> IT WONT INSTALL IN GLASSFISH 4.1.1 TOMCAT GIVES ERROR 11007 SO FAR IT'S A TIME SINK and THREATENING TO BECOME A QUAGMIRE
42.1	231
	232	Answer from Vincent Massol (XWiki Core Dev):
62.1	233
42.1	234	> I contacted Douglas and asked him to post on the list which he did and his problems were [[solved on the list>>http://xwiki.markmail.org/search/?q=from%3ADouglas+Landau]].
41.1	235	)))
40.2	236	* Sent 12/30/2016 11:44:43:(((
	237	> The migration works very badly that need to improve. More than 50% of pages are broken after migrated from 6.4 to 8.4
	238	)))
	239	* Sent 12/29/2016 20:58:53:(((
	240	> More than one Wiki setup, in a easy way to handle.
	241	)))
37.1	242	* Sent 30/11/16 14:04:59:(((
36.1	243	> Most enterprises (and even smaller organizations) use some kind of directory service for user authentication and group management (e.g. OpenLDAP, Microsoft Active Directory, Samba). XWiki currently (to my knowledge) supports static mapping between local XWiki Groups and LDAP (security) groups based on Distinguished Name (dn). Maintaining lots of such groups quickly becomes tedious as LDAP groups are created, removed, renamed, and relocated. This has to be kept synchronized with the static configuration within XWiki and is prone to errors. I suggest some kind of automated mechanism for supporting external (security) groups with a configurable key of various data types. As an example, in Active Directory, a possible attribute to use is the "objectGUID" (https://msdn.microsoft.com/en-us/library/ms679021(v=vs.85).aspx) which is a 16-byte value, since it is the same during an object's entire life cycle. That way, role management within XWiki can be centrally managed using already existing tools, aligning management with already established business processes.
	244
37.1	245	Answer from Thomas Mortagne (XWiki Core Dev):
62.1	246
40.1	247	> LDAP groups are not only LDAP DNs, you can also use LDAP filters and organization units. So in your case it would probably be something like ##XWiki.MyXWikiGroup=(objectGUID=someguid)##. See the examples in [[the xwiki.cfg file>>extensions:Extension.LDAP.Authenticator\|\|anchor="HGenericLDAPconfiguration"]].
37.1	248	)))
	249	* Sent 11/30/2016 6:56:27:(((
35.1	250	> Your official xwiki side is for me the reference. I can see several useful UI components there which I do not know how to reuse/build in my xwiki project. I’d like to have some kind of “showroom” where we can see list of available components and example how to build it.
37.1	251	)))
	252	* Sent 10/11/2016 3:58:(((
34.1	253	> I have recently tried your XWiki product with different deployment methods. In general XWiki works really well, quite easy to use, and the access to the source editing with XWiki syntax is powerful.
	254	> - Installation: should be more stable (I couldn't install in on a Linux docker container, even though I tried all types of DEB packages
	255	> - I haven't tried on a real Linux server). The Zip deployment on Windows works great though. Flexibity of choosing diffrent deployment methods is good, but if it's hard to keep all options work fine, I suggest only support Zip and WAR deployment, as these options should work for most normal usage scenarios.
	256	> - UX/UI: Generally, UX is good, the onboarding tutorial is nice and very useful. UI is quite modern and looks nice compared to other wiki softwares. However, few things could be improved: The organization of the left menu could be simplified a bit. UI should have more consistent look and feel (now it is flat UI here, 3D there, font size varies from place to place, etc.) Would be nice to see it in 100% Bootstrap 3. Also, the default formatting for tables could be improved. Comming from Confluence I miss the way they treat tables (and the whole editor in general): that is some kind of common sense that made table look/work good enough yet simple enough for almost all kind of uses. So when using XWiki I always add a simple grey background to all table header columns/rows (but it took a little bit of learning the xwiki syntax). And I still prefer the UI for creating table on Confluence.
	257	> - Security: for the on-premise delployment package, please don't use a default password for Admin, that's a very bad security practice (a lot of people will forget to change that password, see more here: https://www.owasp.org/index.php/Top_10_2013-A5-Security_Misconfiguration), I suggest dynamically generating amdin password when xwiki starts the first time, then print it out in the console or a local file, then force user to change it when they first log in.
37.1	258	)))
	259	* Sent 22/09/2016 19:15:22:(((
33.1	260	> Instead of refreshing the entire page as I navigate it would be nice if only the body of the page refreshed and the navigation stay static (unless I add a new page of course.)
	261	> I am quite happy with XWiki. Thanks for reaching out to me.
37.1	262	)))
	263	* Sent 9/14/2016 9:53:54:(((
32.1	264	> Richer right management, better debugging of wiki pages
	265	> Xwiki is the best wiki I tried until now !
37.1	266	)))
	267	* Sent 10/9/2016 19:23:32:(((
31.1	268	> On Xwiki8.2.1, link function of ckeditor doesn't work well. There is no setting in ckeditor link dialog about setting target="_blank". I feel it is better to use Xwiki7.4.x with ckeditor Extension & customize application-ckeditor-webjar-1.3.x.jar to full functional ckeditor. My main reason to use ckeditor is to avoid wiki tag setting like \|\|target="_blank" . Most of users want to use ckeditor Full function version, not want to use wikitag.
	269	> functionality of ckeditor in Xwiki8.2.1 is so cheap and disappointed. I hope to use Full Functionality of ckeditor.
37.1	270	)))
	271	* Sent 8/30/2016 10:46:56:(((
30.1	272	> Math Formula insertion function is desirable (like image insertion with mimetex.cgi etc)
	273	> I'm very happy to use Xwiki, it's very powerful and useful ! I will change to Version 8.2.1 soon.
37.1	274	)))
	275	* Sent 29/8/2016 10:12:52:(((
29.1	276	> Installation tool for the owne server.
37.1	277	)))
	278	* Sent 24/08/16 09:39:24:(((
27.1	279	> Provide more typed and strict API in Java
	280	> Clean the API
	281	> Provide simplified API allowing to manipulate the pages/objects like a graph
	282	> Simplify reference serialization
	283	> Allows to implement extension in Java directly in the wiki (like groovy extensions but allowing multiple files for the structure and linking jar to classpath)
	284	> Improve the documentation a lot
37.1	285	)))
	286	* Sent 2/8/2016 22:59:45:(((
28.1	287	> Easily customizable Horizontal Navbar, enabled by default (I still can't find how to do it). Update the Linux (Debian) installation instructions. I had a very difficult time installing on Ubuntu 16.xx and could not install at all on Ubuntu 14.04 LTS.
	288	> Enable changing the color theme depending on Wiki to make it a little more obvious what "Wiki" you are viewing at the moment. I'm sure this is possible. Perhaps I just don't understand it.
37.1	289	)))
	290	* Sent 25/7/2016 18:35:25:(((
28.1	291	> Simplify the view. less button and better locations. use a toolbar on the top of the page (like confluence)
	292	> Good project. I'm looking if it can fit to build a portal. I think yes. Confluence wiki is really easier to begin a knowledge base with non-IT people.
37.1	293	)))
	294	* Sent 24/7/2016 8:20:06:(((
28.1	295	> I want to use ckEditor with full functionality (i.e. full menu button), I hope it will be implemented in the following version of Xwiki ! I use mimetex.cgi to write math-formula, so Image insertion by url is preferrable.
	296	> I can't do my task without Xwiki now. I thank you all.
37.1	297	)))
	298	* Sent 20/7/16 14:53:53:(((
28.1	299	> Improve documentation (is somewhat outdated in some areas)
37.1	300	)))
	301	* Sent 29/04/16 05:31:47:(((
26.1	302	> Better documentation would do you a lot of good. You should also consider archiving all information related to older releases. You still have Version 2 documentation when you are at Version 8. It would make it much easier to update, read and learn from your documentation if is was limited to just the latest and greatest or at least the LTS release.
37.1	303	)))
	304	* Sent 27/04/16 14:59:29:(((
25.1	305	> To be able to group tags for a group of pages and not all at the same place mixed up
37.1	306	)))
	307	* Sent 17/03/16 12:29:15:(((
24.1	308	> Happy with the product, I wish that the upgrade process was simpler, like a one click installer like wordpress or joomla
37.1	309	)))
	310	* Sent 04/02/16 16:29:41:(((
23.1	311	> I would like to be able to paste an image into the wiki directly from the clipboard. Maybe that can be done, but I didn't find the extension that would allow that. I would not mind if the paste created an attachment, possibly asking me the name I want to give it. Currently, I have to paste into gimp or paint, save as a file, upload the file and then reference the attachment in the page so it will show.
	312	>
	313	> That brings up another point. Finding an extension that does what you want is difficult, and most extensions lack screen sample to show you what they do.
	314	>
	315	> More role based read/write access. There are pages we would like to limit update capability to a specific group of individuals, and even readability to to a group, and some open to everyone. We would like to be able to define the roles based on information found in AD.
37.1	316	)))
	317	* Sent 22/12/15 18:47:28:(((
22.1	318	> I lost security privileges when i migrate
37.1	319	)))
	320	* Sent 14/12/15 16:55:30:(((
21.1	321	> We would like to see the Search result page showing images, just like Google: text or image view.
37.1	322	)))
	323	* Sent 07/12/15 08:57:56:(((
20.1	324	> Suggest Improvements: Form builder for simple office application
	325	> Diagram draw utility - can by paid...some as glify, can be more simply, needed clickable objects (typical system architecture picture, after click on object I will redirected into specific pages...
37.1	326	)))
	327	* Sent 28/10/15 15:33:32:(((
19.1	328	> Extended Import/Export Feature
	329	> More Options to import or export pages or rights or configuration
37.1	330	)))
	331	* Sent 24/10/15 19:02:29:(((
18.1	332	> The classical wiki hierarchy is hard to establish. Up until latest version parent permissions inheritance was impossible.
37.1	333	)))
	334	* Sent 21/04/15 14:51:19:(((
17.1	335	> Si possible une recherche de documentation par arborescence de "thèmes" car la recherche par mot clés sous entend que l'on sait déjà comment vous nommez telle ou telle chose, ce qui n'est pas toujours le cas.
	336	> Plus d'exemples serait un plus.
	337	> Plus d'informations sur la gestion de droits éventuellement.
	338	>
	339	> Autre amélioration majeure : on peut interfacer Xwiki à un serveur de messagerie mais il serait très agréable de pouvoir interfacer sur un Intranet comme Sharepoint.
	340	>
	341	> Des remerciements pour votre solution qui est franchement excellente.
	342	> La documentation existante reste un point fort de votre projet, les modules également.
	343	> Cette application est très souple et a parfaitement répondu à mes besoins.
37.1	344	)))
	345	* Sent 22/02/15 21:32:43:(((
16.1	346	> out of the box themes that are "thin". Currently, all the widgets (form elements, title bars, etc) are very "thick" taking up too much screen real estate.
	347	> thanks for the project, and keep up the good work!
37.1	348	)))
	349	* Sent 22/02/15 01:42:20:(((
16.1	350	> For while, just: When you create a template based on another one, you can change the CSS styles. But if you specify the new style, all of the original rules are lost. Would be good if I could just add CSS rules, in addition to the existing ones
37.1	351	)))
	352	* Sent 17/02/15 09:45:03:(((
15.1	353	> Installer. You need an installer. You really should just be able to drop the war into Tomcat and figure the rest out via the web. There must be a way you can get hibernate to do this. Leaving the user with a horrible stacktrace is not a very nice welcome.
	354	>
	355	> I've got 12 years developing Java. It's been 24 hours. I'm still trying to get it running...
37.1	356	)))
	357	* Sent 12/12/14 16:52:00:(((
14.1	358	> The management and setup is a bit clunky. I love that there is an actual setup file, but once it is installed the setup of the look and the features of the wiki seems to be a bit more complicated than I would hope.
	359	>
	360	> I just installed it a few days ago, but so far it seems to be everything that I wanted. It was hard to find a product that included everything: Templates, searchability, tagging, Microsoft SQL integration, and most importantly AD integration and easy rights management.
37.1	361	)))
	362	* Sent 20/10/14 05:18:13:(((
13.1	363	> Easier way to restore and move wikis between servers … not too bad now, but could be lots easier … main issue is an export that includes all system pages that have been changed and manages their migration to new versions, a way of managing template.vm and css files that are modified (this has improved in the sense this becomes less and less necessary), Need a multi-level App in a minute interface, and better documentation, or at least more examples.
	364	>
	365	> Good job … been using for more than a decade
37.1	366	)))
	367	* Sent 13/09/14 11:23:45:(((
12.1	368	> (1) Add Task and Issue management
	369	> (2) Expedient means of generating pages from an Excel, CSV or XML file and a template.
	370	>
	371	> Oil and Gas Projects generate 10's thousands of volumes of documents: for example operating manuals, engineering drawings, reports of many types, memos, emails, time sheets, specifications. While some will be reviewed daily,many of these documents will never be looked at again for 10 years if ever. However, they need to be organized and accessible by users with minimal computer skills.
	372	>
	373	> My contractor is delivering a Data Warehouse using Oracle as its DB. The DW has a very cryptic GUI and is sufferingly slow with less than 5% of the material loaded and only 2 concurrent users. I'm investigating Plan B.
	374	>
	375	> After interviewing the user pool the most common interfaces they were comfortable with are: wikipedia, MS file manager, web browser. This confirms prior experience with Documentun based tools.
	376	>
	377	> If you have any thoughts, I'd like to hear them, articles to read are also appreciated.
37.1	378	)))
	379	* Sent 10/07/14 07:19:24:(((
10.1	380	> Provide more skins, & integrate workflows.
37.1	381	)))
	382	* Sent 20/06/14 15:50:53:(((
11.1	383	> It would be ideal if the WYSIWYG editor provided more features. Currently have to toggle to Edit > WIKI, to encapsulate HTML tags <span style="color:red">...
	384	>
	385	> Most users are visual learners breadcrumbs are helpful, but if you copied the Home > Document Index > Tree, into a collapse-able left-nav feature for the whole site, that would be ideal. (Only for the User defined pages).
	386	>
	387	> By the way thank you so much. The package is great. It makes life so much easier.
37.1	388	)))
	389	* Sent 28/04/14 10:29:08:(((
9.1	390	> I would suggest improving the upgrade process/documentation.
	391	> Documentation around upgrade processes is incomplete and mostly unhelpful. I cannot recommend your platform to anyone as it requires significant admin resource to upgrade to later versions. Investing significant time in creating and maintaining content stored in XWiki just means you have more headaches to upgrade or eventual migration to a different product.
	392	>
	393	> I'm fairly happy with XWiki when it's up and running but nothing is worth the pain and suffering you make your system admins go through at upgrade time.
37.1	394	)))
	395	* Sent 21/02/14 08:12:32:(((
8.1	396	> If you can increase the access speed, we will very thanks!
37.1	397	)))
	398	* Sent 17/02/14 23:19:00:(((
5.1	399	> It would be nice to see a more user-friendly interface. Lets take, for example, the cronjobs. Its a must feature, but its has also a geek interface.
	400	> The macro is another example. Its a great feature too, but only accessible to people who has some understanding about how XWiki works.
	401	> I would suggest you to search for a tool called Podio. It has a nice design and a very good User-interface, similar to Facebook. We're using it in my company to make work more organized and manageable. But the most important part is that all the workers can assimilate the interface quickly and, therefore, the learning curve is very soft.
	402	>
	403	> I dont know how to program in Java, but I would like to contribute with some ideas, at least. Im gone report some bugs too that I've found in my short experience with Xwiki. I hope it helps you in this great Project.
	404	>
	405	> Nonetheless, XWiki is a powerful tool and a Im very happy to have found such a great software. Thank you very much!
37.1	406	)))
	407	* Sent 10/02/14 01:27:23:(((
6.1	408	> Better default skin (responsive by default)
37.1	409	)))
	410	* Sent 03/02/14 13:59:12:(((
7.1	411	> The speed for mobile androids.
37.1	412	)))
	413	* Sent 19/12/13 06:13:55:(((
7.1	414	> I difficult to find/follow the user guide which often seems out dated
37.1	415	)))
	416	* Sent 09/11/13 13:36:02:(((
7.1	417	> I find the documentation not good. If one wants to accomplish some tasks it is very difficult to find the relevant documentation pages. Most of time things are documented but a lot of them I found them only by chance. There is also a lot of stuff which is deprecated in later versions. I think you should make the documentation more precise, concise and streamlined.
	418	>
	419	> Another point. The upgrade procedure is very tedious (I use the war-files). I would like to have something speedier and simpler.
	420	>
	421	> We use Confluence at Work. I bought the starter license for my intranet at home. Then I became aware of your project. For my private uses it is completely satisfactory - and it runs one my weak powered ARM-based linux home server with jdk 1.8, which the Atlassian product is not able to do.
	422	> Thanks for your great work !
37.1	423	)))
	424	* Sent 24/08/13 16:15:36:(((
3.1	425	> Improve upgrade process. I took me forever to figure out how to do this - which files I needed to copy over into my installation from the previous version, what else I needed to do (like enable xwiki.store.migration = 1.) I still don't know if I am I supposed to upgrade with the XAR file or not? I haven't, because I'm afraid it will cause data loss.
37.1	426	)))
	427	* Sent 17/09/13 10:39:31:(((
7.1	428	> Not so easy to program macros
37.1	429	)))
	430	* Sent 09/08/13 10:39:26:(((
4.1	431	> Make the default UI as more attractive
37.1	432	)))
	433	* Sent 31/07/13 12:42:58:(((
4.1	434	> Feedback application
	435	> Email Notification body of the email needs improvement. I didnt like it at all.
37.1	436	)))
	437	* Sent 30/07/13 21:09:28:(((
4.1	438	> Probably: more skins ?
	439	> Also, very important: better documentation !!!!
	440	> Well... a big thanks for all your efforts ! :-)
37.1	441	)))
	442	* Sent 21/06/13 09:42:52:(((
2.1	443	> The extensions page seems like a bit of a mess - are many of them outdated (meaning not compatible/relevant for the latest version of xwiki)?
37.1	444	)))
	445	* Sent 29/05/13 11:42:07:(((
1.1	446	> Make installation possible on Ubuntu from deb - it does not work at all. Always get "Could not initialize main XWiki context" no mater what I do
37.1	447	)))
	448	* Sent 23/05/13 15:39:28:(((
1.1	449	> I tried it on my local mac to create a base of my notes and materials around web development
	450	> I like in XWiki
	451	> - a lot of of plugins (skins, little useful plugins like columns)
	452	> - exellent administrative tools
	453	> - blog
	454	> - dynaamic search, it's great!
	455	> but think it need some improvements
	456	> - more handy visual editor (like in wordpress or typo3 6)
	457	> - set of styles in visual editor like in wordpress. I don't like insert and edit preformated text in special window
	458	>- i have not find how to create in visual editor a couple of my own styles and throw out h5, h6.
	459	> - basic skin like skin on your official site: it's have more strict design and more capacious and easy to read typographics.
37.1	460	)))
	461	* Sent 05/02/13 16:05:21:(((
1.1	462	> Live upgrade. Importers (I have a tikiwiki with 900+ pages that I want to bring into xwiki). Better documentation of the XAR format.
37.1	463	)))
	464	* Sent 07/01/13 07:26:20:(((
1.1	465	> 1) I would need a plugin for free dashboard (whiteboard). This would be very helpful to edit a page while learning for example is a similar way to a white paper where you can draw a chart, take notes and so on. For the beginning to have the functionality of a image editor would be enough. So i expect to edit in the web page images which in the end to be saved as image. Beside this o found almost everything i ever need. Thanks !
	466	> 2) The default interface i think is too complex. I would prefer it simpler (similar to wikipedia.org) not so many feeds, activity, and so on. Just settings link, add edit page / space and the page content, other part to be customization but not defaults. (It' fine how it is, that suggestion is personal thought)
37.1	467	)))
	468	* Sent 15/10/12 16:21:48:(((
1.1	469	> XWiki ist the technically best and most impressive Wiki and XWiki belongs the future. But you have to care about bringing your power to the customers and users. That means:
	470	> - Rating (!) and better maintainance of PlugIns/Apps
	471	> -> 'App' is not just a word, it is a religion. With the ApplicationManager you are doing everything right. But nobody knows what's good to try for a extension/plugin (ratings and commends is a must have) and...
	472	> - it should be perfect stable to add/remove these extensions
	473	> - no experimental things in the stable version. stable means stable.
	474	> All in all you are doing most of things right! With hiding technical documents and the brand new Distribution Manager (like it) you have responded the last XWiki survey. So there is nothing to add here, what is not in the survey ;)
37.1	475	)))
	476	* Sent 07/08/12 20:00:21:(((
1.1	477	> It's a powerful tool and I have selected by variety of tools that supports.
	478	> I have some problem with a migration from Confluence to XWiki. I'm not sure about origin of them, but sometimes throw a Java Heap space.
1.2	479	> I migrated 460 pages with a structure tree of four level of pages. Ramdomly I received heap space errors, and I'm trying to solve ot
37.1	480	)))
	481	* Sent 18/07/12 23:35:15:(((
1.1	482	> Tutorials in programming guide schould be in the latest syntax in both scripting language (Groovy and Velocity).
37.1	483	)))
	484	* Sent 20/06/12 12:16:30:(((
1.1	485	> I find the UI too cluttered, specially at the top, where it has too many menus and buttons. Things should be simpler, maybe some options could come to the bottom of the page and/or be hidden.
	486	> There should be a way to have spaces inside spaces, at least with 1 level of depth.
	487	> When showing changes i wish you could show them as "Space.Page" or "Space.ParentPage.Page". I say this because if we have "Space1.page" and "Space2.page" and we alter Space1.page in the widgets i see "page" and do not know at a glance in which space was it altered.
	488	> Overall i think the software as lots of potential and i'm pretty happy with it. I've been doing a pilot for our team intranet and we are going to keep using it. My goal is to have a production ready wiki in 2/3 months.
37.1	489	)))
	490	* Sent 17/03/12 06:38:03:(((
1.1	491	> Step by step. I am new.
37.1	492	)))
	493	* Sent 17/03/12 01:17:34:(((
1.1	494	> XWiki is great. We use it for the company intranet with great success - the only caveat is that it is generally slow, painfully so in some instances.
37.1	495	)))
	496	* Sent 01/03/12 16:47:28:(((
1.1	497	> More user-friendly wysisyg editor. More configuration tools to assist in migration/setup.
37.1	498	)))
	499	* Sent 22/02/12 08:09:34:(((
1.1	500	> NEED: MARK PART OF THE DOCUMENT AS "DO NOT PRINT THIS TO PDF/RTF/ETC"
	501	>
	502	> Parts of the document should be able to be marked as "do-not-print". We use them for the documentation, and provide documentation as prints to the end customers. However, there are parts which is needed only for internal use. Therefore we previously implemented our own macros like so:
	503	>
	504	> #no_print_start
	505	>
	506	> here is the internal documentation
	507	>
	508	> #no_print_stop
	509	>
	510	> With the most recent version this does not work, and it would be great to have this feature inbuilt somehow.
	511	>
	512	>I have tried for several times to contact the users-list, but it seems that mails do not reach the list. I have an issue with pdf export which causes the xwiki to fail if there is an image in the page.
37.1	513	)))
	514	* Sent 16/01/13 07:34:06:(((
1.1	515	> In my oppinion the biggest disadvantage is lack of Kerberos authentication. Second thing to improve is mechanizm of page templates, i.e. when many pages with similar content need to be created, but creating datamodel (objects) for page content is not necessary.
37.1	516	)))
	517	* Sent 14/07/12 21:45:03:(((
1.1	518	> Templates should be more simple.
	519	> Creation of snippets (macros) that can be added to many pages. If I change my snippet it will reflect in all pages. It should be more simple.
37.1	520	)))

Wiki source code of Download Form Feedback

Quick Links

Let us know

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected