Last modified by Thomas Mortagne on 2017/03/24

From version < 1.2 >
edited by Vincent Massol
on 2012/07/06
To version < 1.3 >
edited by Eduard Moraru
on 2012/07/10
Change comment: Mentioned the custom mapping for comments fixed issue.



Page properties
... ... @@ -1,1 +1,1 @@
1 -XWiki.VincentMassol
1 +XWiki.enygma
... ... @@ -39,6 +39,14 @@
39 39  
40 40  If you still encounter issues while migrating your data, please ask us on our user mailing list and do not forget to provide a link to your failing logs so we may provide helpful hints.
41 41  
42 +== Comments stored with a custom mapping or custom annotation class ==
43 +
44 +If you happened to use a custom mapping for storing ##XWiki.XWikiComments## objects in a separate table, you may have experienced problems with the migration ##R40001XWIKI7540##. Dealing with custom mappings is outside the scope of the migration so now, if such a custom mapping is detected, the migration is simply skipped. The migration is also skipped if you use a custom annotation class for your annotation objects, other than the default ##AnnotationCode.AnnotationClass##.
45 +
46 +If you are in one of the two cases above and the migration is skipped, you will want to make sure that the ##Annotations## docextra tab is still visible. To make it visible, set ##Administration > Look & Feel > Page Elements > Document metadata visibility > Show document annotations## to ##Yes##. You will continue to use your custom annotations (in the Annotations tab) or custom mapped comments (in the Comments tab) as before, without them being merged into one Comments tab, as it happens by default in the latest versions.
47 +
48 +Please see {{jira style="enum" url=""}}XWIKI-8036{{/jira}} for more details.
49 +
42 42  == Issues specific to XWiki Enterprise 4.1.3 ==
43 43  
44 44  Nothing specific.

Get Connected