Last modified by Thomas Mortagne on 2023/10/13

Hide last authors
Vincent Massol 1.1 1 {{box cssClass="floatinginfobox" title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
Denis Gervalle 17.1 5 {{warning}}
Thomas Mortagne 46.1 6 If you are migrating from an earlier version than 4.0, and your database contains statistics collected using a version earlier than 2.2, you will probably encounter an issue during our automated database migration. To avoid that issue, you will need to clean up your statistics by executing some SQL commands described in issue [[XWIKI-8129>>]]. Be sure to apply these before attempting the migration. If your are in doubt, apply it, these could not hurt. If you don't, you will face duplicate IDs errors during the migration process, and it will fail, preventing you to run your wiki.
Denis Gervalle 17.1 7 {{/warning}}
Sorin Burjan 30.1 9 {{warning}}
Thomas Mortagne 46.1 10 If you are upgrading to this version from an older version which uses Lucene 3.x, you have to manually delete the lucene directory in the xwiki data directory. For example, that could cause Lucene to loop endlessly while trying to index pages, among other things. This is caused by the Lucene migration to 4.0 (see [[XWIKI-8404>>]]).
Sorin Burjan 30.1 11 {{/warning}}
Vincent Massol 1.1 13 This is the release notes for XWiki Platform, XWiki Enterprise and XWiki Enterprise Manager. They share the same release notes as they are released together and have the same version.
Vincent Massol 44.1 15 This release is the last stabilization release for the 4.x cycle with improvements on Distribution Wizard, SOLR Search and App Within Minutes.
Vincent Massol 1.1 16
Vincent Massol 38.1 17 = New and Noteworthy (since XWiki 4.4.1) =
Vincent Massol 1.1 18
Thomas Mortagne 46.1 19 [[Full list of issues fixed and Dashboard for 4.5>>]].
Vincent Massol 45.1 20
Marius Dumitru Florea 16.1 21 == Distribution Wizard improvements ==
23 When upgrading from an old version that didn't have the distribution wizard, the wizard doesn't know what user interface (XAR) was previously installed (imported). This information can help the Extension Manager merge automatically the wiki pages from your database with those from the new version of the user interface.
25 The distribution wizard will first ask you if you are performing an upgrade.
27 {{image reference="DW-previousUiUpgradeQuestion.png"/}}
Marius Dumitru Florea 23.1 29 Then you need to select the user interface version that was previously installed.
Marius Dumitru Florea 16.1 30
Marius Dumitru Florea 23.1 31 {{image reference="DW-previousUiForm-01.png"/}}
Marius Dumitru Florea 16.1 32
Marius Dumitru Florea 23.1 33 The distribution wizard determines the id of the previously imported XAR based on the selected version.
35 {{image reference="DW-previousUiForm-02.png"/}}
37 You can edit the suggested id if you know you had a different user interface previously installed.
39 {{image reference="DW-previousUiForm-03.png"/}}
Marius Dumitru Florea 16.1 41 Finally you need to repair the specified user interface extension. This will mark the extension as installed (update the extension index without actually importing the wiki pages from the XAR).
43 {{image reference="DW-previousUiExtension.png"/}}
Marius Dumitru Florea 27.1 45 {{image reference="DW-repairPreviousUiExtension.png"/}}
Marius Dumitru Florea 16.1 47 Next you can install the new version of the user interface.
Marius Dumitru Florea 10.1 49 == Translatable AppWithinMinutes apps ==
Vincent Massol 1.1 50
Marius Dumitru Florea 10.2 51 The AppWithinMinutes wizard is now generating a document translation bundle for the application which allows you to translate class field pretty names, list values (for static list fields) and live table columns names. If you have an existing application that was created with AppWithinMinutes you just have to edit and save it to get the new translation bundle.
Vincent Massol 1.1 52
Marius Dumitru Florea 10.1 53 If your wiki is setup for multilingual support then on the application home page, in the application menu, you now have an entry to translate the application. The link takes you to the document translation bundle.
55 {{image reference="AWM-translateAppMenu.png"/}}
57 When editing an application you now have the option to update the translation bundle. Note that for the moment the translation bundle (its default language) is regenerated so you may lose translation keys you added yourself. In the future we want to update the translation bundle preserving the custom keys.
59 {{image reference="AWM-updateTranslationsOption.png"/}}
61 See the [[AppWithinMinutes documentation>>extensions:Extension.App Within Minutes Application]] for more information.
Eduard Moraru 33.3 63 == Experimental Solr search improvements ==
65 === Remote Solr instance support ===
67 You can now configure the Solr search to use a remote Solr instance instead of the embedded server that runs in the same JVM with XWiki. To do that, you have to:
68 - set the ##solr.type## property inside the ##WEB-INF/ file from the default value of "embedded" to "remote"
69 - set the ##solr.remote.url## property to the URL where your remote server can be accessed.
71 Note: don't forget to uncomment (remove the leading # character) the properties when setting their values. If you do forget, the default values will be used instead of yours.
73 There can be various reasons (security, performance, economy, etc.) why you would want to use a remote server instead of the embedded one, but you will have to make sure that you are using (or building on top of) the Solr configuration that XWiki knows how to work with.
74 Once XWiki is started with ##solr.type## set to ##remote##, you can go to the ##XWiki.SolrSearchAdmin## page inside your wiki (main wiki, if using a multiwiki setup) and download the attached file. If contains the structure of your the Solr home directory that you can use for your remote instance. Just unzip it in a directory and set that directory to be your Solr home for your remote server.
76 === Improved multilingual support ===
78 In order to properly index content of various languages and, as a consequence, obtain better search results, we have chosen the single-index-multiple-fields approach.
80 This means that, a couple of interesting multilingual index fields (title, doccontent, comment, objcontent, propertyvalue and attcontent) are now configured as field aliases that get automatically expanded at query time to all their configured multilingual variations. Each language "variation" is of the form ##fieldName_language## (title_en, title_fr, title_ro, etc...) and contains the content indexed in a language-specific way. There also exists a ##fieldName_ml## field "variation" that is used as a form of backup, for languages outside the list of already configured ones, but is also useful in everyday queries since it does lighter analysis on the content.
82 Example: a query on (title:test) gets converted to (title_ml:test | title_en:test | title_ro:test | title_fr:test | ...)
84 Additionally, attachments, objects and object properties are now indexed for each of the languages of the translations of the original document to which they belong. This now allows them to be found when searching for content in a translation of a document and not just content in the language of the original document, as it was before.
Vincent Massol 1.1 86 == Miscellaneous ==
Vincent Massol 7.1 88 * The message sender is now using the new user/group picker.(((
Marius Dumitru Florea 4.1 89 {{image reference="messageSender-userPicker.png"/}}
Vincent Massol 7.1 90 )))
91 * The create and manage workspace forms are now using the new user picker.(((
Marius Dumitru Florea 6.1 92 {{image reference="createWorkspace-ownerAndMembers.png"/}}
Vincent Massol 7.1 93 )))
Marius Dumitru Florea 29.1 94 * You can now add or invite multiple users at once to an workspace, and the user name field uses the new user picker.(((
95 {{image reference="workspace-administration-users-add-invite.png"/}}
96 )))
Marius Dumitru Florea 12.1 97 * We improved the way changes are displayed by emphasizing the in-line changes.(((
98 {{image reference="unifiedDiff.png"/}}
99 )))
Thomas Mortagne 46.1 100 * Support for searching content in Java Class file attachments [[has been temporarily dropped>>]].
Vincent Massol 7.1 101 * Markdown syntax support has been completely rewritten, fixing several existing bugs.
Vincent Massol 33.2 102 * The home page (##Main.WebHome##) can now safely be edited by any user who has edit permission (In earlier releases, the AJAX suggest feature for tags would unexpectedly break if users not having Programming Rights edited the page).
Thomas Mortagne 47.1 103 * PostGreSQL support for multiwiki mode (see Backward Compatibility notes below and the [[PostGreSQL installation instructions>>Documentation.AdminGuide.InstallationPostgreSQL]]).
Vincent Massol 1.1 104
Thomas Mortagne 46.1 105 See the [[full list of JIRA issues>>]] fixed in this release.
Vincent Massol 1.1 106
107 = For Developers =
Thomas Mortagne 35.1 109 == Embed translations in JAR extension ==
Vincent Massol 1.1 110
Thomas Mortagne 34.1 111 It's now possible for any JAR to come with it's own translation bundle. For that you need to provide at the root of the JAR a set of based translations. See [[Localization Module>>extensions:Extension.Localization Module]] for more.
Vincent Massol 1.1 112
113 == Deprecated and Retired projects ==
Vincent Massol 38.1 115 No project was retired.
Vincent Massol 1.1 116
117 == Upgrades ==
Vincent Massol 38.1 119 No library was upgraded.
Vincent Massol 1.1 120
121 == Miscellaneous ==
Andreas Jonsson 25.1 123 * It is now possible to delegate programming rights directly to a filesystem template to allow it to access the privileged API by adding the template name to the set defined in DefaultPrivilegedTemplateRenderer. Such a template cannot currently access the context document, but this restriction will most likely be removed in 5.0.
Vincent Massol 1.1 125 = Translations =
127 The following translations have been updated:
Vincent Massol 42.1 129 {{language codes="fr,ru,ko,sv"/}}
Vincent Massol 1.1 130
131 = Tested Browsers & Databases =
133 Here's the list of browsers tested with this version (i.e. browsers that we've tested as working - Check the list of [[supported browsers>>dev:Community.BrowserSupportStrategy]]):
135 {{velocity}}
136 ## name = iexplorer, firefox, chrome, safari, opera
137 {{/velocity}}
Manuel Smeria 44.2 139 {{browser name="iexplorer" version="8"/}}
141 {{browser name="iexplorer" version="9"/}}
Vincent Massol 38.1 143 {{browser name="firefox" version="17"/}}
Vincent Massol 1.1 144
Manuel Smeria 44.2 145 {{browser name="firefox" version="18"/}}
Vincent Massol 1.1 147 Here's the list of databases tested with this version (i.e. databases that we've tested as working - Check the list of [[supported databases>>dev:Community.DatabaseSupportStrategy]]):
149 {{velocity}}
150 ## name = hsqldb, mysql, postgresql, oracle, opera
151 {{/velocity}}
Vincent Massol 36.1 153 {{database name="hsqldb" version="2.2.9"/}}
Vincent Massol 1.1 154
Manuel Smeria 44.2 155 {{database name="oracle" version="11.2"/}}
Vincent Massol 36.1 157 {{database name="postgresql" version="8.4.12"/}}
Vincent Massol 1.1 159 = Known issues =
Thomas Mortagne 46.1 161 * [[Bugs we know about>>]]
Vincent Massol 1.1 162
163 = Test Report =
165 You can check the [[manual test report>>TestReports.WebHome#<anchor to test report>]] to learn about what was tested and the results on various browsers.
167 = Backward Compatibility and Migration Notes =
169 == General Notes ==
Denis Gervalle 17.1 171 {{warning}}
174 {{/warning}}
Vincent Massol 1.1 176 You may also want to [[import the default wiki XAR>>Main.Download]] in order to benefit from all the improvements listed above.
178 {{warning}}
179 Always make sure you compare your ##xwiki.cfg## and files with the newest version since some configuration parameters were added. Note that you should add so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.
180 {{/warning}}
Denis Gervalle 17.1 182 {{warning}}
Thomas Mortagne 46.1 183 If you are migrating from an earlier version than 4.0, and your database contains statistics collected using a version earlier than 2.2, you will probably encounter an issue during our automated database migration. To avoid that issue, you will need to clean up your statistics by executing some SQL commands described in issue [[XWIKI-8129>>]]. Be sure to apply these before attempting the migration. If your are in doubt, apply it, these could not hurt. If you don't, you will face duplicate IDs errors during the migration process, and it will fail, preventing you to run your wiki.
Denis Gervalle 17.1 184 {{/warning}}
186 {{warning}}
187 If you have encountered an issue with the migration, you may need to start over from a backup. Be careful that during the migration, two new tables have been created (in each xwiki database for a farm) and should be dropped when you restore a backup of a database coming from a version earlier than 4.x. These two tables are DATABASECHANGELOG and DATABASECHANGELOGLOCK. These should only be removed if you restore a pre-4.x database schema. Mixing an old database with these two tables will surely cause issue during schema updates (liquibase checksum failure).
188 {{/warning}}
Vincent Massol 1.1 190 == Issues specific to XWiki 4.5M1 ==
Vincent Massol 38.1 192 * Changes in the experimental Solr implementation
193 ** The file now contains solr specific configuration, please make sure to merge it with your own. If you were previously using the ##search.solr.home## property to specify your own index directory, you need to use the new ##solr.embedded.home## property, as specified in the file.
194 ** The Solr index and configuration files have suffered major changes. When upgrading, you need to delete the ##<permanentDirectory>/solr## directory so that Solr can reinitialize it with the new configuration and index structure. Also, a reindexation is obviously required.
Thomas Mortagne 46.1 195 * The new default mode for PostGreSQL is the ##schema## mode, i.e. new wikis are created as schema. Previously the default was ##database## but [[there are still issues with it>>]]. The configuration is done in ##hibernate.cfg.xml## by setting {{code}}<property name="xwiki.virtual_mode">schema|database</property>{{/code}}.
Vincent Massol 1.1 196
197 == API Breakages ==
Vincent Massol 38.1 199 The following APIs were modified since XWiki 4.4.1:
Vincent Massol 1.1 200
Vincent Massol 43.1 201 * New method to access bundle:(((
Vincent Massol 1.1 202 {{code language="none"}}
Vincent Massol 43.1 203 org.xwiki.localization.LocalizationManager: Method 'public org.xwiki.localization.TranslationBundle getTranslationBundle(java.lang.String, java.lang.String)' has been added to an interface
Vincent Massol 1.1 204 {{/code}}
Vincent Massol 43.1 205 )))

Get Connected