Download Form Feedback - Older

 I lost security privileges when i migrate 

 We would like to see the Search result page showing images, just like Google: text or image view. 

 Suggest Improvements: Form builder for simple office application
 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... 

 Extended Import/Export Feature
 More Options to import or export pages or rights or configuration 

 The classical wiki hierarchy is hard to establish. Up until latest version parent permissions inheritance was impossible. 

 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.
 Plus d'exemples serait un plus.
 Plus d'informations sur la gestion de droits éventuellement.

 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.

 Des remerciements pour votre solution qui est franchement excellente.
 La documentation existante reste un point fort de votre projet, les modules également.
 Cette application est très souple et a parfaitement répondu à mes besoins. 

 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.
 thanks for the project, and keep up the good work! 

 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  

 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.

 I've got 12 years developing Java. It's been 24 hours. I'm still trying to get it running... 

 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.

 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. 

 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.

 Good job … been using for more than a decade 

 (1) Add Task and Issue management
 (2) Expedient means of generating pages from an Excel, CSV or XML file and a template.

 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.

 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.

 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.

 If you have any thoughts, I'd like to hear them, articles to read are also appreciated. 

 Provide more skins, & integrate workflows.

 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">...

 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).

 By the way thank you so much. The package is great. It makes life so much easier. 

 I would suggest improving the upgrade process/documentation.
 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.

 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. 

 If you can increase the access speed, we will very thanks!

 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.
 The macro is another example. Its a great feature too, but only accessible to people who has some understanding about how XWiki works.
 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.

 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.

 Nonetheless, XWiki is a powerful tool and a Im very happy to have found such a great software. Thank you very much!

 Better default skin (responsive by default) 

 The speed for mobile androids.

 I difficult to find/follow the user guide which often seems out dated 

 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.

 Another point. The upgrade procedure is very tedious (I use the war-files). I would like to have something speedier and simpler.

 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.
 Thanks for your great work ! 

 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.

 Not so easy to program macros

 Make the default UI as more attractive

 Feedback application
 Email Notification body of the email needs improvement. I didnt like it at all.

 Probably: more skins ?
 Also, very important: better documentation !!!!
 Well... a big thanks for all your efforts ! :-)

 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)?

 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

 I tried it on my local mac to create a base of my notes and materials around web development
 I like in XWiki
 - a lot of of plugins (skins, little useful plugins like columns)
 - exellent administrative tools
 - blog
 - dynaamic search, it's great!
 but think it need some improvements
 - more handy visual editor (like in wordpress or typo3 6)
 - set of styles in visual editor like in wordpress. I don't like insert and edit preformated text in special window
- i have not find how to create in visual editor  a couple of my own styles and throw out h5, h6.
 - basic skin like skin on your official site: it's have more strict design and more capacious and easy to read typographics.

 Live upgrade. Importers (I have a tikiwiki with 900+ pages that I want to bring into xwiki).  Better documentation of the XAR format. 

 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 !
 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)

 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:
 - Rating  and better maintainance of PlugIns/Apps
 -> '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...
 - it should be perfect stable to add/remove these extensions
 - no experimental things in the stable version. stable means stable.
 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

 It's a powerful tool and I have selected by variety of tools that supports.
 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.
 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

 Tutorials in programming guide schould be in the latest syntax in both scripting language (Groovy and Velocity).

 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.
 There should be a way to have spaces inside spaces, at least with 1 level of depth.
 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.
 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.

 Step by step.  I am new.

 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.

  More user-friendly wysisyg editor.  More configuration tools to assist in migration/setup.

 NEED: MARK PART OF THE DOCUMENT AS "DO NOT PRINT THIS TO PDF/RTF/ETC"

 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:

 #no_print_start

 here is the internal documentation

 #no_print_stop

 With the most recent version this does not work, and it would be great to have this feature inbuilt somehow.

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.

 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. 

 Templates should be more simple.
 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.