Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -90,14 +90,7 @@ 90 90 91 91 = Tested Browsers & Databases = 92 92 93 -{{warning}} 94 -The QA Tests are executed after the release has been done. Thus, they are being prepared now and will be published soon. 95 -{{/warning}} 96 - 97 -{{comment}} 98 -TODO: uncomment and update with proper link when the report is ready. 99 99 {{include reference="TestReports.ManualTestReportSummaryXWiki82RC1"/}} 100 -{{/comment}} 101 101 102 102 = Known issues = 103 103 ... ... @@ -112,10 +112,12 @@ 112 112 == Issues specific to XWiki 8.2RC1 == 113 113 114 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: 108 + 115 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 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## 117 117 118 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. 113 + 119 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 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 121 * Finally, if the TextArea property supports wiki syntax and it's mostly free text then best is to configure the WYSIWYG editor.