Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ThomasMortagne
	1	+XWiki.mflorea

Content

...	...	@@ -4,7 +4,7 @@
4	4
5	5	This is the release notes for [[XWiki Commons>>http://commons.xwiki.org]], [[XWiki Rendering>>http://rendering.xwiki.org]], [[XWiki Platform>>http://platform.xwiki.org]] and [[XWiki Enterprise>>http://enterprise.xwiki.org]]. They share the same release notes as they are released together and have the same version.
6	6
7		-This release brings the addition of a //tour// on the home page which describe the XWiki user interface to newcomers.
	7	+This release integrates CKEditor as the default WYSIWYG content editor and adds a //tour// on the home page to describe the XWiki user interface to newcomers.
8	8
9	9	= New and Noteworthy (since XWiki 8.1) =
10	10
...	...	@@ -20,11 +20,11 @@
20	20
21	21	Starting with this version we have a new WYSIWYG editor: the [[CKEditor>>extensions:Extension.CKEditor Integration]]. The integration with CKEditor was already available as an extension and now this extension is bundled with the standard XWiki distribution.
22	22
23		-{{image reference="ckeditor.png" width="600" /}}
	23	+{{image reference="ckeditor.png" width="600"/}}
24	24
25	25	The old WYSIWYG editor is still available and if you want to switch back to it you can do it from the "Edit Mode Settings" section in the wiki administration.
26	26
27		-{{image reference="defaultWysiwygEditorConfig.png" width="600" /}}
	27	+{{image reference="defaultWysiwygEditorConfig.png" width="600"/}}
28	28
29	29	== Miscellaneous ==
30	30
...	...	@@ -42,6 +42,10 @@
42	42
43	43	= For Developers =
44	44
	45	+== Associate Editors to Data Types ==
	46	+
	47	+This version introduces a new module that provides APIs to associate editors to data types. For instance you can associate a date picker to ##java.util.Date##, or a WYSIWYG editor to ##org.xwiki.rendering.block.XDOM##. There can be multiple editors available for a specific data type and the user or the administrator can configure the preferred one. Checkout the [[Edit Module>>extensions:Extension.Edit Module]] documentation for more details. This new API has been used to embed CKEditor as the default WYSIWYG editor.
	48	+
45	45	== Instance Filter improvements ==
46	46
47	47	* Instance Output Filter now support missing begin/end event on document locale and revision so input filter for which those two concept don't make sense don't have to send them anymore.
...	...	@@ -64,6 +64,7 @@
64	64	* [[httpasyncclient 4.1.2>>http://jira.xwiki.org/browse/XCOMMONS-1009]]
65	65	* [[JGroups 3.6.10>>http://jira.xwiki.org/browse/XWIKI-13532]]
66	66	* [[Less4j 1.17.2>>http://jira.xwiki.org/browse/XWIKI-13119]]
	71	+* [[Infinispan 8.2.3>>http://jira.xwiki.org/browse/XWIKI-13561]]
67	67
68	68	== Miscellaneous ==
69	69
...	...	@@ -104,13 +104,20 @@
104	104
105	105	When upgrading make sure you compare your ##xwiki.cfg##, ##xwiki.properties## and ##web.xml## files with the newest version since some configuration parameters may have been modified or 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.
106	106
107		-== Issues specific to XWiki <version> ==
	112	+== Issues specific to XWiki 8.2RC1 ==
108	108
109		-<issues specific to the project>
	114	+We refactored the way in which the editors are loaded for page content and TextArea properties. We're now using the new [[Edit API>>extensions:Extension.Edit Module]]. The following breaking changes have been done:
	115	+* ##textarea_text.vm## and ##textarea_wysiwyg.vm## Velocity templates have been removed. In case you have customized these templates you can port the changes to the new editor templates available in ##/templates/editors/xdom*.vm##
	116	+* ##$xcontext.getEditorWysiwyg()## has been deprecated and is now returning ##null## all the time (which translates into "no TextArea fields that need a WYSIWYG editor"). If you were using this method to customize the WYSIWYG editor then you can do the same from the new editor templates available in ##/templates/editors/xdom*.vm##
110	110
	118	+A side effect of this refactoring is that the Object and Class editors are now using the configured preferred editor, unless it is overwritten using the "editor" meta property.
	119	+* If you have a TextArea property that doesn't support wiki syntax then best is to configure the xclass to use the //PureText// editor for this property.
	120	+* If the TextArea property supports wiki syntax but it's mostly code (e.g. Velocity, HTML) then best is to configure the Text editor.
	121	+* Finally, if the TextArea property supports wiki syntax and it's mostly free text then best is to configure the WYSIWYG editor.
	122	+
111	111	== API Breakages ==
112	112
113		-The following APIs were modified since <project> <version - 1>:
	125	+The following APIs were modified since XWiki 8.1:
114	114
115	115	{{comment}}
116	116	Remove!