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.

<insert description of release here>

New and Noteworthy (since XWiki <version - 1>)

Full list of issues fixed and Dashboard for <full version here even for RC, e.g. 10.5>.

For Users

Empty Content Placeholder in WYSIWYG Editor

 
The WYSIWYG Editor shows a placeholder text when the edited content is empty and the text area is not focused. See the CKEditor Integration documentation for more information.

For Admins

Like feature disabling

 
It is now possible to disable the Like feature from the administration. Disabling it will preserve any existing Like data but hide them from the UI.

Miscellaneous

• New URL resource scheme for Reset password: The reset password and retrieve username features have been refactored to stop using wiki pages to work. The rationale is that these pages needed to be viewable by the guest user to work, thus making it impossible to protect the full wiki to guests (among other problems related to rights on these pages). Thus they have been re-implemented using dedicated URL schemes and components, and thus have had their URLs changed:

  • Reset password:
    • New URL: /xwiki/authenticate/reset 
    • Old URL: /xwiki/bin/view/XWiki/ResetPassword
  • Retrieve username:
    • New URL: /xwiki/authenticate/forgot 
    • Old URL: /xwiki/bin/view/XWiki/ForgotUsername

  The old XWiki.ResetPassword and XWiki.ForgotUsername wiki pages must not be used anymore, and any custom change perform in those pages won't be taken into account (you'll need to port your changes to Java since the new feature is coded in Java). However, the pages have been kept to ensure that using the old URLs will keep working for the time being: the pages now redirect to the new URLs.

For Developers

Wiki Macro priority

 
It's now possible to define the priority of a wiki macro (it used to only be possible for Java Macros). This is useful when you need your macro to be executed before or after other macros. When not specified the default priority is 1000.

Miscellaneous

• Controlling Transformations: It's now possible to control exactly which Rendering Transformations to execute when viewing a page. For example to execute only the macro transformation: http://localhost:8080/xwiki/bin/view/Sandbox/WebHome?transformations=macro.

• Allow to log deprecation warning in scripts: It's possible to log automatically a deprecation warning in a script, to inform users that some scripts might be removed in the future. This method checks the deprecation warnings configuration to only display the message if it is enabled.
  You can use it like this:

  ## First argument is the logger name, second is the message.
  $services.logging.deprecate("MyScript", "The script [MyScript] should not be used anymore")

  The output warning is displayed with a [DEPRECATED]  prefix.

• Raw Macro: When content is parsed, an XDOM tree is created. Sometimes you don't have any way to express the content you wish in that XDOM tree and you only wish that your content is output as is, when the XDOM is then rendered in a given syntax. You can use the raw macro for this need.

  Example:

  {{raw syntax="latex/1.0"}}
  \loadglsentries{glossary}
  \makeglossaries
  {{/raw}}

Moved Modules

<description deprecated, retired and moved projects>

Upgrades

The following runtime dependencies have been upgraded (they have a different release cycle than XWiki Commons, XWiki Rendering and XWiki Platform):

• Jodconverter 4.4.0

Translations

The following translations have been updated: 

• Language
• Language

Known issues

• Bugs we know about

Backward Compatibility and Migration Notes

General Notes

• When upgrading make sure you compare and merge the following XWiki configuration files since some parameters may have been modified, removed or added:
  • xwiki.cfg
  • xwiki.properties
  • web.xml
  • hibernate.cfg.xml
• Add xwiki.store.migration=1 in xwiki.cfg so that XWiki will attempt to automatically migrate your current database to any new schema. Make sure you backup your Database before doing anything.

Issues specific to XWiki 13.1RC1

Breaking OfficeConverter API

The interface #org.xwiki.officeimporter.converter.OfficeConverter# has been broken on purpose after an accepted proposal on the forum. This API was going to be broken because of the Jodconverter upgrade since the maintainer of the project moved their APIs to another package, so we took the opportunity to stop exposing in OfficeConverter classes coming from Jodconverter. Note that we introduced some new APIs to cover the usages we've seen for this API. Don't hesitate to open a feature request on Jira if some usages are not covered.

API Breakages

The following APIs were modified since <project> <version - 1>:

Credits

The following people have contributed code and translations to this release (sorted alphabetically):

<code contributors>