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 improves the accuracy of the attachment list when viewing an older version of a document, adds the identifier of the cluster member in the footer when clustering is enabled, and adds various improvements for developers. This release contains security fixes, with the highest severity being 9.3/10.

New and Noteworthy (since XWiki 18.2.1)

Full list of issues fixed and Dashboard for 18.3.0.

For Users

Edit Image in BlockNote

 
The experimental BlockNote WYSIWYG editor integration now supports editing the image properties and changing the image source (including uploading a new image attachment). This is done by reusing the image wizard we developed for the CKEditor integration. There are still a lot of rough edges:

• images are not yet rendered in edit mode
• you can't easily insert a new internal (attached) image
• not all the image properties available on the image wizard are currently supported by BlockNote

We plan to improve this in the coming months.

Edit Macro in BlockNote

 
The experimental BlockNote WYSIWYG editor integration now supports editing the macro parameters and changing the macro. This is done by reusing the macro wizard we developed for the CKEditor integration (and which is used by the Dashboard as well). There are still a lot of rough edges though:

• some macros are not properly rendered in edit mode
• inline macros are not highlighted visually
• the edited content is not reloaded after a macro is updated
• you can't insert a new macro call (you can only edit existing macros calls)

We plan to improve this in the coming months.

Miscellaneous

• Page Extra Attachment Tab honors versions: The Attachment tab located in the Page Extra area now honors versions: when viewing a version, it displays the attachments that existed in that version, at that time.

For Admins

Cluster member identifier

 
The identifier of the cluster member is now printing in the footer as soon as clustering is enabled.

For Developers

• Client-side localization improvements: Client-side localization benefits from a few improvements:

  • When using the default resolver, localizations are now cached in the browser, avoiding translation keys to be resolved several times
  • A localization helper is available for Vue.js developer

• API extractor shared configuration: The default api-extractor configuration is now distributed in a dedicated package. See how-to use it in your packages.

• Jakarta Priority support: XWiki component API now supports jakarta.annotation.Priority. See Component Module for more details.

• tsdoc shared configuration: The default tsdoc configuration is now distributed in a dedicated package. See how-to use it in your packages.

Upgrades

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

Security Issues

Security issues are not listed in issue lists or dashboards to avoid disclosing ways to use them, but they will appear automatically in them once they're disclosed. See the XWiki Security Policy for more details.

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 18.3.0

HTML HEAD UIXP

The org.xwiki.platform.html.head UIXP is now injected by the skin which ensures that this UIXP is always injected. Before that change, if the user had an empty meta xproperty ("HTTP Meta Info" field in the Admin UI) and started adding something in it, then meta.vm was not used anymore and the UIXP was no longer injected and XWiki would fail in some places (like code using vue.js will fail, e.g., LiveData).

What you need to do when upgrading: Check that the following lines are not present in your "HTTP Meta Info" field, and if they are, remove them (otherwise the UIXP will be injected twice which should be harmless but still not good):

#foreach($uix in $services.uix.getExtensions("org.xwiki.platform.html.head", {'sortByParameter' : 'order'}))
  $services.rendering.render($uix.execute(), 'xhtml/1.0')
#end

API Breakages

The following APIs were modified since XWiki 18.2.1:

No breakage!

Credits

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

• Anca Luca
• ClementEXWiki
• LucasC
• Manuel Leduc
• Marius Dumitru Florea
• Mats
• Michael Hamann
• Pierre Jeanjean
• Raphaël Jakse
• Simon Urli
• Thomas Mortagne
• Vincent Massol