ContentsThe [toc] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
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 Milestone 2
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.
