Last modified by Thomas Mortagne on 2017/03/24

<
From version < 39.1 >
edited by Marius Dumitru Florea
on 2016/07/12
To version < 40.1 >
edited by Marius Dumitru Florea
on 2016/07/12
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -86,7 +86,7 @@
86 86  
87 87  The following translations have been updated:
88 88  
89 -{{language codes="none, none"/}}
89 +{{language codes="fr, nl"/}}
90 90  
91 91  = Tested Browsers & Databases =
92 92  
... ... @@ -109,13 +109,20 @@
109 109  
110 110  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.
111 111  
112 -== Issues specific to XWiki <version> ==
112 +== Issues specific to XWiki 8.2RC1 ==
113 113  
114 -<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##
115 115  
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 +
116 116  == API Breakages ==
117 117  
118 -The following APIs were modified since <project> <version - 1>:
125 +The following APIs were modified since XWiki 8.1:
119 119  
120 120  {{comment}}
121 121  Remove!

Get Connected