Skip to Content
Last modified by Agnease on 2026/05/26 10:58
From version 1.2
edited by Agnease
on 2026/05/01 11:42
Change comment: There is no comment for this version
To version 1.5
edited by Agnease
on 2026/05/12 14:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,121 +1,174 @@
1 -= Why Upgrade Your XWiki Instance to the Latest LTS Version? =
1 +/* ========== Resource / Article Pages ========== */
2 2  
3 -Your XWiki instance may be working well today, but if it is running an older version, it may already be missing important security fixes, stability improvements, compatibility updates, and platform enhancements.
3 +.resource-page {
4 + padding-top: 34px;
5 +}
4 4  
5 -Keeping XWiki aligned with the latest Long Term Support (LTS) version is not only a maintenance task. It is a practical way to reduce operational risk and keep your knowledge platform secure, reliable, and ready for future needs.
7 +.resource-header {
8 + padding: 40px 0 30px;
9 + border-top: none;
10 + background:
11 + radial-gradient(42rem 14rem at 50% 0%, @brand-bg 0%, transparent 70%);
6 6  
7 -{{toc start=2 /}}
13 + .resource-kicker {
14 + display: inline-flex;
15 + align-items: center;
16 + gap: 8px;
17 + color: @brand;
18 + background: fade(@brand, 8%);
19 + border: 1px solid fade(@brand, 18%);
20 + border-radius: 999px;
21 + padding: 6px 12px;
22 + margin-bottom: 14px;
23 + font-size: 13px;
24 + font-weight: 700;
25 + }
8 8  
9 -== Why regular XWiki upgrades matter ==
27 + h1 {
28 + max-width: 820px;
29 + margin: 0 auto 14px;
30 + text-align: center;
31 + line-height: 1.18;
32 + }
10 10  
11 -XWiki is actively maintained. With each release cycle, the platform receives bug fixes, security fixes, usability improvements, performance enhancements, and compatibility updates.
34 + .resource-summary {
35 + max-width: 780px;
36 + margin: 0 auto;
37 + color: @muted;
38 + text-align: center;
39 + font-size: 18px;
40 + line-height: 1.55;
41 + }
42 +}
12 12  
13 -When an instance remains on an older version for too long, the upgrade gap becomes larger. This can make future upgrades more complex, increase the risk of incompatibilities, and leave the platform exposed to issues that have already been fixed in newer versions.
44 +.resource-layout {
45 + display: grid;
46 + grid-template-columns: minmax(0, 760px) 280px;
47 + gap: 42px;
48 + max-width: 1080px;
49 + margin: 0 auto;
50 + align-items: start;
51 +}
14 14  
15 -A regular upgrade strategy helps keep your platform predictable and easier to maintain.
53 +.resource-content {
54 + color: @text;
55 + font-size: 16px;
56 + line-height: 1.68;
16 16  
17 -== Security should be a priority ==
58 + h2 {
59 + text-align: left;
60 + margin: 34px 0 12px;
61 + line-height: 1.28;
62 + }
18 18  
19 -Older XWiki versions may be affected by security vulnerabilities that have already been corrected in later releases.
64 + h3 {
65 + margin: 24px 0 8px;
66 + line-height: 1.3;
67 + }
20 20  
21 -Once security advisories and fixes become public, attackers can analyze the disclosed information and use it to target systems that are still running vulnerable versions.
69 + p {
70 + margin: 0 0 16px;
71 + }
22 22  
23 -This means that delaying upgrades can increase the window of exposure.
73 + ul,
74 + ol {
75 + margin: 0 0 18px;
76 + padding-left: 22px;
77 + }
24 24  
25 -Upgrading to the latest LTS version helps reduce this risk by applying the latest available fixes in a stable, production-oriented release line.
79 + li {
80 + margin: 6px 0;
81 + }
26 26  
27 -== Stability and compatibility improvements ==
83 + strong {
84 + color: @text;
85 + }
86 +}
28 28  
29 -Security is not the only reason to upgrade.
88 +.resource-note {
89 + border-left: 4px solid @brand;
90 + background: @brand-bg;
91 + padding: 16px 18px;
92 + margin: 22px 0;
93 + border-radius: 0 @radius @radius 0;
30 30  
31 -Newer XWiki LTS versions also include important improvements related to:
95 + p:last-child {
96 + margin-bottom: 0;
97 + }
98 +}
32 32  
33 -* platform stability
34 -* extension compatibility
35 -* authentication and integration support
36 -* user interface improvements
37 -* performance and reliability
38 -* bug fixes accumulated across multiple releases
39 -* better support for modern Java and application server environments
100 +.resource-checklist {
101 + margin: 18px 0 24px;
102 + padding: 0;
103 + list-style: none;
40 40  
41 -These improvements are especially important for organizations that rely on XWiki as a central knowledge base, intranet, documentation portal, or business process platform.
105 + li {
106 + position: relative;
107 + padding: 10px 0 10px 34px;
108 + border-bottom: 1px solid @line;
42 42  
43 -== Major platform transitions require planning ==
110 + &:before {
111 + content: "\f00c";
112 + font-family: FontAwesome;
113 + position: absolute;
114 + left: 0;
115 + top: 11px;
116 + color: @brand;
117 + }
118 + }
119 +}
44 44  
45 -Some upgrades are more significant than others.
121 +.resource-sidebar {
122 + position: sticky;
123 + top: 96px;
124 + border: 1px solid @line;
125 + border-radius: @radius;
126 + padding: 18px;
127 + background: #fff;
128 + box-shadow: @shadow-sm;
46 46  
47 -For example, the move from XWiki 16.x to XWiki 17.x introduced an important platform change: the migration to Jakarta EE. This also affects the application server layer, requiring environments such as Tomcat 10+ instead of Tomcat 9.
130 + h4 {
131 + margin: 0 0 10px;
132 + }
48 48  
49 -This type of upgrade should not be treated as a simple file replacement. It requires careful planning, compatibility checks, and proper validation.
134 + ul {
135 + margin: 0;
136 + padding-left: 18px;
137 + color: @muted;
138 + }
50 50  
51 -== A safe upgrade process ==
140 + li {
141 + margin: 8px 0;
142 + }
52 52  
53 -At Agnease, XWiki upgrades are approached as controlled technical operations.
144 + a {
145 + color: @brand;
146 + font-weight: 600;
147 + }
148 +}
54 54  
55 -A typical upgrade process may include:
150 +.resource-cta {
151 + margin-top: 36px;
152 + padding: 22px;
153 + border: 1px solid fade(@brand, 20%);
154 + border-radius: @radius;
155 + background: @brand-bg;
56 56  
57 -* reviewing the current XWiki version and infrastructure
58 -* identifying the recommended target LTS version
59 -* checking installed extensions and custom developments
60 -* reviewing authentication and integration dependencies
61 -* preparing a staging environment when needed
62 -* testing the upgrade before production
63 -* planning downtime and rollback options
64 -* executing the production upgrade
65 -* performing post-upgrade checks
157 + h3 {
158 + margin-top: 0;
159 + }
66 66  
67 -The goal is to minimize risk while keeping the platform secure, stable, and maintainable.
161 + p {
162 + color: @muted;
163 + }
164 +}
68 68  
69 -== What happens if upgrades are postponed? ==
166 +@media (max-width: 900px) {
167 + .resource-layout {
168 + grid-template-columns: 1fr;
169 + }
70 70  
71 -Postponing upgrades for too long can lead to:
72 -
73 -* increased exposure to known vulnerabilities
74 -* more difficult future upgrades
75 -* outdated dependencies
76 -* compatibility problems with newer integrations
77 -* unsupported or harder-to-maintain infrastructure
78 -* higher troubleshooting costs
79 -* increased risk during emergency upgrades
80 -
81 -Regular upgrades are usually easier, safer, and more cost-effective than large delayed migrations.
82 -
83 -== Who should consider an upgrade? ==
84 -
85 -You should consider planning an upgrade if:
86 -
87 -* your XWiki instance is not running the latest LTS version
88 -* your current version is more than one year old
89 -* your instance contains sensitive or business-critical information
90 -* you use custom extensions or integrations
91 -* authentication is connected to LDAP, Active Directory, SSO, OpenID Connect, or SAML
92 -* your platform is used as an intranet, knowledge base, documentation portal, or workflow system
93 -* you want to reduce long-term maintenance risks
94 -
95 -== Request an XWiki upgrade assessment ==
96 -
97 -If you are unsure where your XWiki instance stands, Agnease can help with a concise upgrade assessment.
98 -
99 -The assessment can include:
100 -
101 -* current version review
102 -* recommended target version
103 -* estimated upgrade effort
104 -* key security and stability reasons to upgrade
105 -* infrastructure considerations
106 -* extension and customization risks
107 -* recommended next steps
108 -
109 -Contact Agnease to review your current XWiki setup and plan a safe upgrade to the latest LTS version.
110 -
111 -{{html}}
112 -<p>
113 - <a class="btn btn-primary" href="/xwiki/bin/view/Contact/">Request an upgrade assessment</a>
114 -</p>
115 -{{/html}}
116 -
117 -== About Agnease ==
118 -
119 -Agnease provides professional XWiki services for organizations that rely on XWiki as a secure and long-term knowledge management platform.
120 -
121 -Services include XWiki upgrades, maintenance, troubleshooting, custom development, integrations, security-aware consulting, and long-term platform support.
171 + .resource-sidebar {
172 + position: static;
173 + }
174 +}