From version < 6.8 >
edited by Eduard Moraru
on 2019/09/24
To version < 8.1
edited by Ilie Andriuta
on 2019/10/01
Change comment: There is no comment for this version



Page properties
... ... @@ -1,1 +1,1 @@
1 -XWiki.enygma
1 +XWiki.iandriuta
... ... @@ -49,13 +49,9 @@
49 49  
50 50  {{language codes="ca, da, de, fr, ko, mr, pt_BR, ru, zh"/}}
51 51  
52 -{{comment}}
53 -TODO: uncomment and update with proper link when the report is ready.
54 -
55 55  = Tested Browsers & Databases =
56 56  
57 -{{include reference="TestReports.<test report page>"/}}
58 -{{/comment}}
54 +{{include reference="TestReports.ManualTestReportSummaryXWiki118RC1.WebHome"/}}
59 59  
60 60  {{comment}}
61 61  TODO: uncomment and update with proper links when the report is ready.
Release Date
... ... @@ -1,0 +1,1 @@
1 +2019-09-24 00:00:00.0
Is Released?
... ... @@ -1,1 +1,1 @@
1 -No
1 +Yes

This is the release notes for XWiki Commons, XWiki Rendering and XWiki Platform. They share the same release notes as they are released together and have the same version.

This release brings a more mature version of the edit conflict resolution UI, display of disabled users in the User Directory, more consistent UI by using Icon Themes in the Live Table and more streamlined template provider creation. Admins also benefit from the improvements added to the conflict resolution UI, but at the Extension Manager level, and get more help for making the right choices when wanting to delete a user (to avoid the mess of broken page rights). Developers now have multiple options for asynchronous rendering of various elements and more control over the rendering of templates.

New and Noteworthy (since XWiki 11.7)

Full list of issues fixed and Dashboard for 11.8.

For Users

Independent Conflict Resolution

We introduced few releases ago a mechanism to detect and handle conflict edition (i.e. when two users save changes on the same page) during page edition.
Starting with this release, the conflict edition window allows one more choice: to fix each conflict individually.
This new choice is marked as advanced since it's not something easy to handle.

When choosing the new option, the UI is updated to display the changes between the latest version saved and the current version the user is trying to save. At each place a conflict occurred, the changes display an orange bar and a blue area is reserved for the conflict resolution.
This blue area displays some text, and a select with several choices. The displayed text in the blue area is what will be used for fixing the conflict, you can see the text changing for each choice.

The conflict choices are the following:

  • current version (default): the conflict is fixed by getting the current changes
  • before your changes: the conflict is fixed by getting what was there before you starting to edit. Both latest version saved and your current changes would be lost for this conflict,
  • latest version saved: the change made on the latest version saved (the one you are conflicting with) are taken to fix the conflict
  • custom version: with this option, a text area is displayed to allow you to enter any new value to fix the conflict. Multiple lines can be entered.

If the choice text displays something in red, it is because no content is actually available for the chosen version to fix the conflict: usually it means the content in conflict will be removed with the choice made.