User Feedback

 Need runnning as a deamon, better upgrade process with no data loosing

 Better upgrade process. Still very manual.

 Change it to a software for normal users/admins with easy installation, update and backup features and combine it with an appserver by delivery

• Upgrade seen as a lengthy / complicated process

Top 5 Voted Issues

• 7 votes
  XWIKI-9920 Extension Manager add extension search should suggest only compatible versions
  
• 4 votes
  
  XWIKI-8321 Let the user know when a newer extension version is available
• 3 votes
  
  XWIKI-11502 Add a simulation feature to the distribution wizard
• 2 votes
  
  XWIKI-9112 Add a way to restart a skipped DW without restarting XWiki
• 2 votes
  
  XWIKI-8608 Allow to uninstall an extension without its backward dependencies

• We could replicate the virtual machine containing the instance; OR duplicate the folders, database, workdir and provide a way to make the dry run.

• Recommendation: Browse all the release notes from your version X to Y to see if there are things to modify.
• Automatically managing configuration changes
• Differences between Docker and Webapp update method:
  • Idea: Merge the configuration files and provide a differences view (either manually [GitHub+WinMerge] or from the DW).
  • Idea: Docker: "update script that does the copy and to copy also the original files and/or provide a diff or even better do the merge as we do it in the debian distribution" (Vincent).

Common configuration values for "production-ready" wikis (we might want to change / update the default values):

• Tomcat java opts variable
  • -Xmx1024m is not enough (edit setenv.sh)
• LDAP Authentication
  • Install LDAP App 
  • Configurations
    • xwiki.authentication.authclass=org.xwiki.contrib.ldap.XWikiLDAPAuthServiceImpl
    • xwiki.authentication.ldap.trylocal=1
• TLS/SSL configuration for Tomcat
• Short URLs
• Other:
  • xwiki.plugin.watchlist.automaticwatch=none
  • xwiki.plugin.image.defaultQuality = 0.8
  • openoffice.homePath and autostart
  • rendering.imageDimensionsIncludedInImageURL = false
  • Adding markdown to xwiki.rendering.syntaxes
  • Cache configuration xwiki.store.cache.capacity=500

• SOLR data is not deleted when upgrading XWiki docker image

• We should update our Java version need to run XWiki. Currently max is 8.

• DW is not launched in some cases. Solutions to manually trigger it or prevent accidental skipping.

• Some remaining configurations from the early versions which were incompatible with the current version

• Having deprecated pre 9.9 configurations
  xwiki.store.attachment.recyclebin.hint=file
• DW didn't add the XWiki.Extensions page, because of an attachment
• Many attachments reported missing after upgrade. Useful Attachment Checker.
• After the upgrade, the attachments disappeared. 
• Can’t find descriptor for the component

• Changing the default theme logo, that attachment blocked the DW installation process.

• PDF Export broken. Needs 3 way merge for xhtml2fo.xsl
• Different PDF Export after upgrade caused by bugs in dependencies + manual need to copy FONTS. PDFTemplate and Skins should be treated specially. 

• Checking database sanity. 
• Make sure the database has been migrated too (issues when schema comes from old version < 3.2)
• "Failed updating schema"

• "certain macros are broken (doctree), breadcrumbs are broken in the header section, and editing pages gives me a infinite spinning circle. If I spin down this instance, change the port number back to port 8080, then spin the instance back up, everything will work as intended."
  • Issue: "all the JavaScript code and the CSS styles are being cached by your browser. Try to clear the browser cache."
• "after upgrade, all the subpages under my wiki are gone, so are those things under Navigation"
  • "So make backups and make Shift + F5 your friend (at least until whatever the issue is gets fixed)"

Conflicting old extensions

• SEARCH: Having old Lucene Search Application installed, although it was replaced by the Solr Search Application some time ago. Needs manual uninstall.

• BLOG
  • Cannot upgrade Blog
  • Stale dependency

• NOTIFICATIONS
  • Missing notification properties in user objects
  • Duplicate versions (one installed in a subwiki not specified)

Upgrading bundled Contrib extensions

• For some extensions (like CKEditor) users are manually reminded to upgrade those extensions in intermediary versions
  • lots of manual upgrades of the CKEditor (in order to fix bugs or get the recent features)
  • great that the extensions are independent and do not need a full upgrade
  • we should notify the users using the notifications system.

• Some issues with extensions installed "on farm" or partially installed that have XAR dependencies from platform (example CKEditor 1.19)
• Manually upgrading the extensions installed "on farm" before proceeding to upgrade the wikis.
  • Apparently what Extension Manager does when it has to replace an extension with an "on farm" installation is that it applies "Uninstall" on each wiki and then re-installs the extension as "on farm". 

• XWiki admin user is removed from the XWikiAdminUser group. Rights are lost. Macros are broken.
  "The execution of the
  [velocity] script macro is not allowed. Check the rights of its last author
  or the parameters if it's rendered from another script"
  
• The best practice in DW when dealing with WebPreferences pages is to automatically apply MERGE

• Wiki Manager missing translations registered with a GLOBAL scope (hence requiring Programming Rights).

• By request or by mistake