Last modified by Thomas Mortagne on 2017/03/24

<
From version < 57.1 >
edited by Marius Dumitru Florea
on 2013/09/13
To version < 59.1 >
edited by Vincent Massol
on 2013/09/18
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.mflorea
1 +XWiki.VincentMassol
Content
... ... @@ -8,7 +8,7 @@
8 8  **The support of XWiki Enterprise Manager is stopped**. XWiki Enterprise now comes with the ability to create subwikis by default, see below.
9 9  {{/warning}}
10 10  
11 -<insert description of release here>
11 +The second milestone of the 5.2 release comes with multiwiki support enabled by default: users are able to create new wikis without the need to install additional extensions. This is possible because the Workspace Application has been integrated in XWiki Enterprise. Besides this, the new release brings a Solr-based live search (to replace the one based on Lucene) and the ability to track active XWiki installs. Developers will be interested by the new WikiStream framework. As with other releases this one has a lot of bug fixes (92) and improvements (33) which make it worth trying.
12 12  
13 13  = New and Noteworthy (since XWiki 5.2 Milestone 1) =
14 14  
... ... @@ -167,9 +167,15 @@
167 167  Always make sure you compare your ##xwiki.cfg## and ##xwiki.properties## files with the newest version since some configuration parameters were added. Note that you should add ##xwiki.store.migration=1## so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.
168 168  {{/warning}}
169 169  
170 -== Issues specific to XWiki <version> ==
170 +== Issues specific to XWiki 5.2 Milestone 2 ==
171 171  
172 -<issues specific to the project>
172 +* XWiki now creates a unique identifier in the database (this is used by the new Active Installs module and will be used in the future by the Extension Manager to identify your instance for example). You need to verify that your ##hibernate.cfg.xml## file has the following mapping definition next to the existing mapping definitions:(((
173 +{{code}}
174 +...
175 + <mapping resource="instance.hbm.xml"/>
176 +...
177 +{{/code}}
178 +)))
173 173  
174 174  == API Breakages ==
175 175  

Get Connected