<
From version < 6.1 >
edited by Marius Dumitru Florea
on 2012/07/12
To version < 7.1 >
edited by Vincent Massol
on 2012/07/13
>
Change comment: Fix wrong lcoation

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.mflorea
1 +XWiki.VincentMassol
Content
... ... @@ -34,8 +34,10 @@
34 34  Always make sure you compare your ##xwiki.cfg## and ##xwiki.properties## files with the newest version since some configuration parameters were added. Note that you should add ##xwiki.store.migration=1## so that XWiki will attempt to automatically migrate your current database(s) to the new schema. Make sure you backup your Database before doing anything.
35 35  {{/warning}}
36 36  
37 -== New migration R40000XWIKI6990 ==
37 +== Issues specific to XWiki Enterprise 4.1.3 ==
38 38  
39 +=== New migration R40000XWIKI6990 ===
40 +
39 39  A new id migration procedure is now used per default. It provide a 200x speed improvement compare to the original one, but in some rare cases, it could failed to migrate your database properly. **It is really important that you keep a backup of your database ready in case of failure**. If you encounter an issue with this new faster procedure, you may want to try the older procedure by first restoring your original database, and by adding the following line in your xwiki.cfg before restarting xwiki.
40 40  
41 41  {{code}}
... ... @@ -46,7 +46,7 @@
46 46  
47 47  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.
48 48  
49 -== Comments stored with a custom mapping or custom annotation class ==
51 +=== Comments stored with a custom mapping or custom annotation class ===
50 50  
51 51  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##.
52 52  
... ... @@ -54,14 +54,10 @@
54 54  
55 55  Please see {{jira style="enum" url="http://jira.xwiki.org"}}XWIKI-8036{{/jira}} for more details.
56 56  
57 -== Custom displayers in the XWikiUsers class ==
59 +=== Custom displayers in the XWikiUsers class ===
58 58  
59 59  If you have added some custom displayers to new or existing fields in the ##XWiki.XWikiUsers## class, you need to check and make sure that they are written in the currently default wiki syntax. This is required because the XWikiUsers document will now always be forced to use the currently default wiki syntax, no matter what syntax you save it with. If your custom displayers are written in 1.0 syntax, for example, and the class document is in 2.1 syntax, they will not render.
60 60  
61 -== Issues specific to XWiki Enterprise 4.1.3 ==
62 -
63 -Nothing specific.
64 -
65 65  == API Breakages ==
66 66  
67 67  No breakage.

Get Connected