Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.jvelociter
	1	+XWiki.VincentMassol

Content

...	...	@@ -4,8 +4,12 @@
4	4
5	5	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.
6	6
7		-This is the thir release of the 4.x cycle ([[Roadmap>>Main.Roadmap]]).
	7	+This is the third release of the 4.x cycle ([[Roadmap>>Main.Roadmap]]).
8	8
	9	+{{warning}}
	10	+If you're upgrading from an older version and you use the new Distribution Wizard to upgrade your wiki pages you'll notice that it'll ask you to merge all pages that have been modified between your version and XWiki 4.2. This is because currently the Distribution Wizard doesn't know which version you have and thus asks you to perform the merge manually. This operation may take a long time (up to 20 minutes or so). Thus at the moment if you're upgrading from a previous version we recommend that you Cancel the Distribution Wizard and instead [[Import the new XAR>>platform:AdminGuide.Upgrade]]. This problem is [[reported in this issue>>http://jira.xwiki.org/browse/XWIKI-8252]] and should be fixed in the next release.
	11	+{{/warning}}
	12	+
9	9	= New and Noteworthy (since XWiki 4.1) =
10	10
11	11	== Extension Manager improvements ==
...	...	@@ -190,7 +190,7 @@
190	190	{{/groovy}}
191	191	{{/code}}
192	192
193		-== Default custom displayers for Easier customization of the way object fields are displayed ==
	197	+== Default custom displayers ==
194	194
195	195	While XWiki allowed to specify a custom display for a given field, it was impossible to change the way field types, such as //DateProperty// or //IntegerProperty//, are displayed in general. Now it is possible to define custom displayers at the farm or wiki level, which gives the administrators more power to change the look and feel of the wiki. For example, this allows to use HTML5 input types for dates and numbers, to use custom suggestions for //list of users// fields, or to always add a validation input for all the //password// field types.
196	196