Wiki source code of ReleaseNotesXWikiEnterprise20M2
Version 9.1 by Thomas Mortagne on 2009/07/30
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | #startfloatingbox() | ||
| 2 | *Contents* | ||
| 3 | #toc ("2" "4" "") | ||
| 4 | #endfloatingbox() | ||
| 5 | |||
| 6 | 1 Release Notes for XWiki Enterprise 2.0 Milestone 2 | ||
| 7 | |||
| 8 | Second milestone of the XWiki Enterprise 2.0 version ([Roadmap>enterprise:Main.Roadmap]). | ||
| 9 | |||
| 10 | 1.1 New and Noteworthy (since XWiki Enterprise 2.0 Milestone 1) | ||
| 11 | |||
| 12 | At a glance (see below for details): | ||
| 13 | * Lots of improvements and new features in the new WYSIWYG editor | ||
| 14 | * Lots of improvements and bugfixes in the rendering engine and the syntax converter | ||
| 15 | * Improvements for the blog application | ||
| 16 | * It's now possible to choose the content renderer to use when viewing a page | ||
| 17 | * New xwiki-properties module | ||
| 18 | * New Latvian translation | ||
| 19 | * New Swedish translation | ||
| 20 | * New Korean translation | ||
| 21 | |||
| 22 | 1.1.1 New Wiki rendering 2.0 macros | ||
| 23 | |||
| 24 | See [platform:DevGuide.WikiMacroTutorial]. | ||
| 25 | |||
| 26 | 1.1.1 Output syntax parameter | ||
| 27 | |||
| 28 | It's now possible to decide which renderer to use to print the document content. For example if you want to generate dome JSON page you can use "?outputSyntax=plain&xpage=plain" to make sure only the content is printed and there is no html syntax printed, just a plain text of what exactly was generated by a velocity macro (without macro markers html comments etc.) | ||
| 29 | |||
| 30 | See [URL parsing documentation>platform:AdminGuide.URL+resolution#HoutputSyntaxandoutputSyntaxVersion]. | ||
| 31 | |||
| 32 | 1.1.1 WYSIWYG improvements | ||
| 33 | |||
| 34 | * Add the ability to configure the colors displayed by the color picker | ||
| 35 | * Allow the page to link to to be searched for or selected from the most recently edited pages | ||
| 36 | * Component Manager should generate event when the component is registered instead of initialized | ||
| 37 | |||
| 38 | 1.1.1 Rendering improvements | ||
| 39 | |||
| 40 | * New Section editing | ||
| 41 | * Allow default document syntax to be specified in User profile configuration | ||
| 42 | |||
| 43 | 1.1.1 1.0 -> 2.0 syntax converter | ||
| 44 | |||
| 45 | * Converter should make sure code macro are forced standalone | ||
| 46 | * Converter should make sure to put $msg.get calls in {{html}} macros | ||
| 47 | * Converter should trim code macro content | ||
| 48 | |||
| 49 | 1.1.1 Component Manager api improvements | ||
| 50 | |||
| 51 | * Add way to directly provide the component instance when register it | ||
| 52 | * Add way to unregister component | ||
| 53 | |||
| 54 | 1.1.1 New xwiki-properties module | ||
| 55 | |||
| 56 | * Java bean populating support | ||
| 57 | * Java type conversion support | ||
| 58 | * Java bean validation support | ||
| 59 | |||
| 60 | Among other things this mean the following changes for the 2.0 macros: | ||
| 61 | * any case is supported for macros parameters names | ||
| 62 | * public fields are now supported (not only getters and setters) | ||
| 63 | * java macro parameters bean is validated agains JSR 303 (See ) | ||
| 64 | * macro properties java bean can implements RawProperties to get custom non converted parameters | ||
| 65 | * you can add support for any type conversion by implementing Converter component | ||
| 66 | * any Enum conversion is supported (no need to register each Enum subclass agains ConvertUtils anymore) | ||
| 67 | * support for Color conversion | ||
| 68 | |||
| 69 | See [Properties module documentation>code:Modules.PropertiesModule]. | ||
| 70 | |||
| 71 | 1.1.1 Miscellaneous UI improvements | ||
| 72 | |||
| 73 | * Improved document footer section | ||
| 74 | * Improved tag display and editing | ||
| 75 | |||
| 76 | 1.1.1 Important bugs fixed | ||
| 77 | |||
| 78 | * XWIKI-4033 - When saving after section edit entire page is overwritten | ||
| 79 | * XWIKI-4043 - Main.AllDocs not showing any documents in a farm | ||
| 80 | |||
| 81 | 1.1 Known issues | ||
| 82 | |||
| 83 | * [Bugs we know about>http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&&type=1&pid=10010&resolution=-1&sorter/field=updated&sorter/order=DESC] | ||
| 84 | |||
| 85 | 1.1 Backward Compatibility and Migration Notes | ||
| 86 | |||
| 87 | 1.1.1 General Notes | ||
| 88 | |||
| 89 | #warning("If you're running in a multiwiki setup you'll also need to define the property <tt>xwiki.store.migration.databases=all</tt> to your <tt>xwiki.cfg</tt> file or explicitly name all databases to be migrated as in <tt>xwiki.store.migration.databases=db1,db2,...</tt>.") | ||
| 90 | |||
| 91 | You may also want to [import the default wiki XAR>Main.Download] in order to benefit from improvements listed above. | ||
| 92 | |||
| 93 | #warning("Always make sure you compare your <tt>xwiki.cfg</tt> file with the newest version since some configuration parameters were added. Of note, you should add <tt>xwiki.store.migration=1</tt> so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.") | ||
| 94 | |||
| 95 | 1.1.1 API Breakages | ||
| 96 | |||
| 97 | The following APIs were modified since XWiki Enterprise 2.0M1: | ||
| 98 | |||
| 99 | * Rendering Module |
