From version < 2.1 >
edited by Vincent Massol
on 2009/06/03
To version < 3.1 >
edited by Vincent Massol
on 2009/06/03
< >
Change comment: Rollback to version 1.1

Summary

Details

Page properties
Content
... ... @@ -3,26 +3,30 @@
3 3  #toc ("2" "3" "")
4 4  #endfloatingbox()
5 5  
6 -1 Release Notes for XWiki Enterprise 1.9 Release Candidate 2
6 +1 Release Notes for XWiki Enterprise 1.9 Release Candidate 1
7 7  
8 -1.1 Summary of changes since XWiki Enterprise 1.9 Release Candidate 1
8 +First Release Candidate of the XWiki Enterprise 1.9 version ([Roadmap>enterprise:Main.Roadmap]).
9 9  
10 -TODO
10 +1.1 Summary of changes since XWiki Enterprise 1.9 Milestone 2
11 11  
12 -1.1 Modified XAR pages
12 +1.1.1 Default Syntax change
13 13  
14 -* Main/AllDocs.xml
15 -* Blog/RssCode.xml
16 -* Panels/RecentlyVisited.xml
17 -* Panels/Recently Created.xml
18 -* Panels/DocumentInformation.xml
19 -* Panels/MyRecentModifications.xml
20 -* Panels/Recently Modified.xml
21 -* Panels/Backlinks.xml
22 -* XWiki/OfficeImporterResults.xml
23 -* XWiki/OfficeImporter.xml
24 -* XWiki/OfficeImporterSuggest.xml
14 +#warning("The default syntax is now 'xwiki/2.0' which means that new documents will be created with this syntax")
25 25  
16 +Note that XWiki Enterprise documents (user profile, recent changes, etc) are still using the "xwiki/1.0" syntax, they will be migrated during the 2.0 release cycle.
17 +
18 +1.1.1 WYSIWYG Improvements
19 +
20 + * Ability to insert level 6 headings
21 + * Allow adding and editing lists in table cells
22 + * Allow adding complex content inside list items
23 +
24 +1.1.1 Important Bugs fixed
25 +
26 + * Many WYSIWYG bugs fixed
27 + * Many 2.0 syntax bugs fixed
28 + * Many 1.0 to 2.0 conversion bugs fixed
29 +
26 26  1.1 Known issues
27 27  
28 28  * [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]
ContentsThe [toc] macro is a standalone macro and it cannot be used inline

Release Notes for XWiki Enterprise 1.9 Release Candidate 2

Release Notes for XWiki Enterprise 1.9 Release Candidate 1

First Release Candidate of the XWiki Enterprise 1.9 version (Roadmap). 

Summary of changes since XWiki Enterprise 1.9 Release Candidate 1

Summary of changes since XWiki Enterprise 1.9 Milestone 2

TODO

Modified XAR pages

  • Main/AllDocs.xml
  • Blog/RssCode.xml
  • Panels/RecentlyVisited.xml
  • Panels/Recently Created.xml
  • Panels/DocumentInformation.xml
  • Panels/MyRecentModifications.xml
  • Panels/Recently Modified.xml
  • Panels/Backlinks.xml
  • XWiki/OfficeImporterResults.xml
  • XWiki/OfficeImporter.xml
  • XWiki/OfficeImporterSuggest.xml

Default Syntax change

The default syntax is now 'xwiki/2.0' which means that new documents will be created with this syntax

Note that XWiki Enterprise documents (user profile, recent changes, etc) are still using the "xwiki/1.0" syntax, they will be migrated during the 2.0 release cycle.

WYSIWYG Improvements

  • Ability to insert level 6 headings
  • Allow adding and editing lists in table cells
  • Allow adding complex content inside list items

Important Bugs fixed

  • Many WYSIWYG bugs fixed
  • Many 2.0 syntax bugs fixed
  • Many 1.0 to 2.0 conversion bugs fixed

Known issues

Common Migration notes

The default encoding was changed from ISO-8859-1 to UTF-8. If you were using the old default encoding and a database using character encodings, you must convert the database data, too, or switch XWiki back to the old encoding If you're running in a multiwiki setup you'll also need to define the property xwiki.store.migration.databases=all to your xwiki.cfg file or explicitly name all databases to be migrated as in xwiki.store.migration.databases=db1,db2,....

You may also want to import the default wiki XAR in order to benefit from improvements listed above.

Always make sure you compare your xwiki.cfg file with the newest version since some configuration parameters were added. Of note, 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.

Get Connected