<
From version < 13.1 >
edited by Denis Gervalle
on 2012/12/20
To version < 14.1
edited by Thomas Mortagne
on 2017/03/24
Change comment: Fix jira URLs

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dgervalle
1 +XWiki.ThomasMortagne
Content
... ... @@ -2,7 +2,7 @@
2 2  {{toc/}}
3 3  {{/box}}
4 4  
5 -{{error}}We've found an important issue in this release regarding the extension manager when installing JAR extensions that provide components or script services (see [[XCOMMONS-231>>http://jira.xwiki.org/browse/XCOMMONS-231]] and [[XCOMMONS-232>>http://jira.xwiki.org/browse/XCOMMONS-232]]). While adding UI support for installing an extension on the current wiki versus the entire farm we made a change on how extensions are installed in XWiki Enterprise, precisely, we started using the wiki namespace (even though XWiki Enterprise is a single wiki) to be consistent with what happens in multiwiki mode. Unfortunately this has revealed that the support for installing JAR extension is subwikis is not very good. Specifically, the script services defined in the installed extension are not properly registered and the components that perform dynamic component lookup (by having the component manager injected) cannot retrieve components from the namespace where the extension was installed, i.e. none of the components defined in the extension. This issue is fixed in 4.1.4 and 4.2 Milestone 1 releases, which we recommend using instead.{{/error}}
5 +{{error}}We've found an important issue in this release regarding the extension manager when installing JAR extensions that provide components or script services (see [[XCOMMONS-231>>https://jira.xwiki.org/browse/XCOMMONS-231]] and [[XCOMMONS-232>>https://jira.xwiki.org/browse/XCOMMONS-232]]). While adding UI support for installing an extension on the current wiki versus the entire farm we made a change on how extensions are installed in XWiki Enterprise, precisely, we started using the wiki namespace (even though XWiki Enterprise is a single wiki) to be consistent with what happens in multiwiki mode. Unfortunately this has revealed that the support for installing JAR extension is subwikis is not very good. Specifically, the script services defined in the installed extension are not properly registered and the components that perform dynamic component lookup (by having the component manager injected) cannot retrieve components from the namespace where the extension was installed, i.e. none of the components defined in the extension. This issue is fixed in 4.1.4 and 4.2 Milestone 1 releases, which we recommend using instead.{{/error}}
6 6  
7 7  {{error}}
8 8  Due to a mistake in the code, the R40001XWIKI7540 migration was being unintentionally skipped. This is now fixed and anyone that is upgrading should avoid this release and directly use 4.1.4 instead.
... ... @@ -9,7 +9,7 @@
9 9  {{/error}}
10 10  
11 11  {{warning}}
12 -If you are migrating from an earlier version than 4.0, and your database contains statistics collected using a version earlier than 2.2, you will probably encounter an issue during our automated database migration. To avoid that issue, you will need to clean up your statistics by executing some SQL commands described in issue [[XWIKI-8129>>http://jira.xwiki.org/browse/XWIKI-8129]]. Be sure to apply these before attempting the migration. If your are in doubt, apply it, these could not hurt. If you don't, you will face duplicate IDs errors during the migration process, and it will fail, preventing you to run your wiki.
12 +If you are migrating from an earlier version than 4.0, and your database contains statistics collected using a version earlier than 2.2, you will probably encounter an issue during our automated database migration. To avoid that issue, you will need to clean up your statistics by executing some SQL commands described in issue [[XWIKI-8129>>https://jira.xwiki.org/browse/XWIKI-8129]]. Be sure to apply these before attempting the migration. If your are in doubt, apply it, these could not hurt. If you don't, you will face duplicate IDs errors during the migration process, and it will fail, preventing you to run your wiki.
13 13  {{/warning}}
14 14  
15 15  This release fixes a serious issue preventing the migration from version 3.5.1 and earlier (especially when the wiki had statistics data in the database).
... ... @@ -19,7 +19,7 @@
19 19  
20 20  == Full Issue List ==
21 21  
22 -{{jira style="list" url="http://jira.xwiki.org" source="jql"}}
22 +{{jira style="list" url="https://jira.xwiki.org" source="jql"}}
23 23  Project in ("XWiki Commons", "XWiki Rendering", "XWiki Platform", "XWiki Enterprise", "XWiki Enterprise Manager") and fixVersion in ("4.1.3") and resolution in ("Fixed")
24 24  {{/jira}}
25 25  
... ... @@ -32,7 +32,7 @@
32 32  
33 33  = Known issues =
34 34  
35 -* [[Bugs we know about>>http://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=category+%3D+%22Top+Level+Projects%22+AND+issuetype+%3D+Bug+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC]]
35 +* [[Bugs we know about>>https://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=category+%3D+%22Top+Level+Projects%22+AND+issuetype+%3D+Bug+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC]]
36 36  
37 37  = Backward Compatibility and Migration Notes =
38 38  
... ... @@ -64,7 +64,7 @@
64 64  
65 65  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.
66 66  
67 -Please see {{jira style="enum" url="http://jira.xwiki.org"}}XWIKI-8036{{/jira}} for more details.
67 +Please see {{jira style="enum" url="https://jira.xwiki.org"}}XWIKI-8036{{/jira}} for more details.
68 68  
69 69  === Custom displayers in the XWikiUsers class ===
70 70  

Get Connected