Skip to Content

Changes for page XWiki Upgrade Services

Last modified by Agnease on 2026/05/25 16:11
From version 2.1
edited by Agnease
on 2026/05/01 12:25
Change comment: Rollback to version 1.4
To version 9.2
edited by Agnease
on 2026/05/22 14:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -xwiki-upgrades
1 +XWiki Upgrade Services
Content
... ... @@ -2,111 +2,289 @@
2 2  #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 3  {{html clean="false"}}
4 4  
5 - ## COMPACT HERO
5 + ## PAGE HEADER
6 6   <section class="hero hero-centered service-hero" aria-labelledby="hero-title">
7 7   <div class="container hero-inner">
8 - <h1 id="hero-title">XWiki Upgrades</h1>
8 + <div class="hero-kicker">
9 + <i class="fa fa-refresh" aria-hidden="true"></i>
10 + XWiki upgrade services
11 + </div>
12 +
13 + <h1 id="hero-title">Safe XWiki LTS upgrades for production environments</h1>
14 +
9 9   <p class="lead">
10 - Safe, planned upgrades for production XWiki instances.
16 + Keep your XWiki instance secure, stable and compatible with a planned upgrade path, clear validation steps
17 + and reduced operational risk, even when it includes custom extensions, authentication integrations,
18 + business-critical pages, workflows, scripts, rights configurations and production constraints.
11 11   </p>
12 - <ul class="benefits">
13 - <li>Latest LTS</li>
14 - <li>Security fixes</li>
15 - <li>Extension checks</li>
16 - <li>Minimal downtime</li>
17 - </ul>
18 - <div class="hero-cta">
19 - <a href="mailto:alex@agnease.com?subject=XWiki%20Upgrade%20Assessment">Request an upgrade assessment</a>
20 +
21 + <div class="hero-actions">
22 + <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an upgrade review</a>
23 + <a class="btn btn-secondary" href="#upgrade-process">See the upgrade approach</a>
20 20   </div>
21 21   </div>
22 22   </section>
23 23  
24 - ## VALUE CARDS
25 - #set ($upgradeCards = [{
26 - 'title': 'Stay secure',
27 - 'icon': 'shield',
28 - 'content': 'Reduce exposure to known vulnerabilities fixed in newer XWiki versions.'
29 - },{
30 - 'title': 'Upgrade safely',
31 - 'icon': 'refresh',
32 - 'content': 'Plan the upgrade with backups, validation, rollback options, and minimal downtime.'
33 - },{
34 - 'title': 'Avoid compatibility surprises',
35 - 'icon': 'puzzle-piece',
36 - 'content': 'Review extensions, custom code, authentication, PDF export, and infrastructure before production.'
37 - }])
38 -
39 - <section class="compact-section" aria-labelledby="why-title">
28 + ## WHY UPGRADES MATTER
29 + <section aria-labelledby="why-upgrade-title">
40 40   <div class="container">
41 - <h2 id="why-title">Keep your XWiki platform current and reliable</h2>
42 - <div class="widgets compact-widgets">
43 - #foreach ($entry in $upgradeCards)
44 - <article class="widget">
45 - <div class="icon" aria-hidden="true">
46 - <i class="fa fa-$entry.icon"></i>
47 - <h4>$entry.title</h4>
48 - </div>
49 - <p>$entry.content</p>
50 - </article>
51 - #end
31 + <h2 id="why-upgrade-title">Why regular XWiki upgrades matter</h2>
32 +
33 + <p class="section-intro">
34 + An outdated XWiki instance can become harder to maintain over time. Security fixes, browser compatibility,
35 + extension updates, platform changes and infrastructure requirements continue to evolve, while older versions
36 + become more difficult and risky to upgrade.
37 + </p>
38 +
39 + <div class="pathways">
40 + <article class="pathway-card">
41 + <div class="pathway-icon">
42 + <i class="fa fa-shield" aria-hidden="true"></i>
43 + </div>
44 + <h3>Reduce security exposure</h3>
45 + <p>
46 + Staying close to supported XWiki versions helps reduce exposure to known vulnerabilities and missing fixes.
47 + </p>
48 + <ul>
49 + <li>Review current version exposure</li>
50 + <li>Plan upgrade to a supported version</li>
51 + <li>Validate security-sensitive features</li>
52 + </ul>
53 + </article>
54 +
55 + <article class="pathway-card">
56 + <div class="pathway-icon">
57 + <i class="fa fa-cogs" aria-hidden="true"></i>
58 + </div>
59 + <h3>Preserve compatibility</h3>
60 + <p>
61 + Extensions, custom applications, authentication systems and infrastructure components need to remain compatible.
62 + </p>
63 + <ul>
64 + <li>Check installed extensions</li>
65 + <li>Review custom code and scripts</li>
66 + <li>Validate integrations after upgrade</li>
67 + </ul>
68 + </article>
69 +
70 + <article class="pathway-card">
71 + <div class="pathway-icon">
72 + <i class="fa fa-line-chart" aria-hidden="true"></i>
73 + </div>
74 + <h3>Improve maintainability</h3>
75 + <p>
76 + Smaller, regular upgrades are usually easier to control than large jumps after years of accumulated changes.
77 + </p>
78 + <ul>
79 + <li>Avoid long upgrade gaps</li>
80 + <li>Document the current platform state</li>
81 + <li>Prepare future upgrade cycles</li>
82 + </ul>
83 + </article>
52 52   </div>
53 53   </div>
54 54   </section>
55 55  
56 - ## TWO COLUMN SUMMARY
57 - <section class="services compact-section" aria-labelledby="summary-title">
88 + ## COMMON SITUATIONS
89 + <section class="services" aria-labelledby="situations-title">
58 58   <div class="container">
59 - <h2 id="summary-title">Upgrade support for real XWiki environments</h2>
91 + <h2 id="situations-title">Common situations we handle</h2>
60 60  
61 - <div class="services-grid compact-grid">
93 + <p class="section-intro">
94 + XWiki upgrades are often simple in clean environments, but production instances usually include additional
95 + constraints that need to be understood before touching the live system.
96 + </p>
97 +
98 + <div class="services-grid">
62 62   <article class="service">
63 - <div class="service-icon">
64 - <i class="fa fa-exclamation-triangle" aria-hidden="true"></i>
100 + <div class="service-icon" aria-hidden="true">
101 + <i class="fa fa-clock-o"></i>
65 65   </div>
66 66   <div class="service-body">
67 - <h4>When to consider an upgrade</h4>
68 - <ul>
69 - <li>Your instance is not on the latest suitable LTS version</li>
70 - <li>Your current version is more than one year old</li>
71 - <li>You use custom extensions, scripts, or workflows</li>
72 - <li>You rely on LDAP, SSO, OIDC, SAML, or MFA</li>
73 - <li>You want to reduce security and maintenance risk</li>
74 - </ul>
104 + <h4>Old XWiki versions</h4>
105 + <p>
106 + Instances that have not been upgraded for several months or years and require a careful upgrade path.
107 + </p>
75 75   </div>
76 76   </article>
77 77  
78 78   <article class="service">
79 - <div class="service-icon">
80 - <i class="fa fa-check-square-o" aria-hidden="true"></i>
112 + <div class="service-icon" aria-hidden="true">
113 + <i class="fa fa-puzzle-piece"></i>
81 81   </div>
82 82   <div class="service-body">
83 - <h4>What Agnease handles</h4>
84 - <ul>
85 - <li>Current version and environment review</li>
86 - <li>Recommended target version</li>
87 - <li>Extension and customization checks</li>
88 - <li>Backup, staging, and rollback planning</li>
89 - <li>Production upgrade and post-upgrade validation</li>
90 - </ul>
116 + <h4>Custom extensions and scripts</h4>
117 + <p>
118 + Wikis with custom applications, Velocity scripts, macros, UI extensions, rights logic or business workflows.
119 + </p>
91 91   </div>
92 92   </article>
122 +
123 + <article class="service">
124 + <div class="service-icon" aria-hidden="true">
125 + <i class="fa fa-lock"></i>
126 + </div>
127 + <div class="service-body">
128 + <h4>Authentication integrations</h4>
129 + <p>
130 + LDAP, Active Directory, SSO, OIDC, SAML, MFA or custom login setups that must keep working after upgrade.
131 + </p>
132 + </div>
133 + </article>
134 +
135 + <article class="service">
136 + <div class="service-icon" aria-hidden="true">
137 + <i class="fa fa-server"></i>
138 + </div>
139 + <div class="service-body">
140 + <h4>Infrastructure changes</h4>
141 + <p>
142 + Java, Tomcat, database, Docker, filesystem, reverse proxy or hosting changes required by newer versions.
143 + </p>
144 + </div>
145 + </article>
146 +
147 + <article class="service">
148 + <div class="service-icon" aria-hidden="true">
149 + <i class="fa fa-file-pdf-o"></i>
150 + </div>
151 + <div class="service-body">
152 + <h4>Business-critical features</h4>
153 + <p>
154 + PDF exports, dashboards, structured data, templates, permissions, notifications and workflows that need validation.
155 + </p>
156 + </div>
157 + </article>
158 +
159 + <article class="service">
160 + <div class="service-icon" aria-hidden="true">
161 + <i class="fa fa-warning"></i>
162 + </div>
163 + <div class="service-body">
164 + <h4>Low-downtime rollout</h4>
165 + <p>
166 + Upgrade planning with backups, testing, rollback options and a controlled production deployment window.
167 + </p>
168 + </div>
169 + </article>
93 93   </div>
94 94   </div>
95 95   </section>
96 96  
97 - ## FINAL CTA
98 - <section class="cta-section compact-cta" aria-labelledby="assessment-title">
174 + ## PROCESS
175 + <section id="upgrade-process" class="split-section" aria-labelledby="process-title">
99 99   <div class="container">
100 - <h2 id="assessment-title">Request an XWiki upgrade assessment</h2>
101 - <p class="lead">
102 - Send your current XWiki version and a short description of your setup.
103 - Agnease will recommend the target version, estimated effort, and key risks to review.
177 + <div class="split-grid">
178 + <div class="split-copy">
179 + <h2 id="process-title">A practical upgrade approach</h2>
180 +
181 + <p>
182 + The goal is not only to install a newer version. The goal is to move your XWiki instance forward
183 + while protecting the data, configuration, customizations and business processes that already depend on it.
184 + </p>
185 +
186 + <p>
187 + The upgrade is always prepared outside production first, using a staging environment or a temporary clone
188 + of the live instance. This allows compatibility issues, extension problems, authentication changes and
189 + custom features to be validated before the controlled production rollout.
190 + </p>
191 + </div>
192 +
193 + <ol class="process-list">
194 + <li>
195 + <strong>Review the current instance</strong>
196 + Version, extensions, database, filesystem, authentication, custom code, logs and infrastructure constraints.
197 + </li>
198 + <li>
199 + <strong>Define the upgrade path</strong>
200 + Target version, intermediate steps if needed, compatibility risks, expected downtime and rollback options.
201 + </li>
202 + <li>
203 + <strong>Prepare and validate</strong>
204 + Backups, test upgrade when needed, extension checks and validation of critical XWiki features.
205 + </li>
206 + <li>
207 + <strong>Upgrade production</strong>
208 + Controlled execution, post-upgrade checks, issue resolution and confirmation that key features still work.
209 + </li>
210 + <li>
211 + <strong>Document next steps</strong>
212 + Upgrade notes, observed risks, remaining recommendations and future maintenance guidance.
213 + </li>
214 + </ol>
215 + </div>
216 + </div>
217 + </section>
218 +
219 + ## DELIVERABLES
220 + <section aria-labelledby="deliverables-title">
221 + <div class="container">
222 + <h2 id="deliverables-title">What you can expect</h2>
223 +
224 + <p class="section-intro">
225 + The exact scope depends on your XWiki version, hosting setup and customizations, but an upgrade engagement
226 + usually includes a clear technical review, a controlled upgrade plan and post-upgrade validation.
104 104   </p>
105 - <p class="text-center contact-inline">
106 - <a href="mailto:alex@agnease.com?subject=XWiki%20Upgrade%20Assessment">Request an upgrade assessment</a>
107 - </p>
228 +
229 + <div class="widgets">
230 + <article class="widget">
231 + <div class="icon" aria-hidden="true">
232 + <i class="fa fa-search"></i>
233 + <h4>Upgrade review</h4>
234 + </div>
235 + <p>
236 + Review of the current version, installed extensions, customizations, authentication and hosting constraints.
237 + </p>
238 + </article>
239 +
240 + <article class="widget">
241 + <div class="icon" aria-hidden="true">
242 + <i class="fa fa-map"></i>
243 + <h4>Upgrade plan</h4>
244 + </div>
245 + <p>
246 + Recommended target version, risk areas, validation checklist, downtime expectations and rollback approach.
247 + </p>
248 + </article>
249 +
250 + <article class="widget">
251 + <div class="icon" aria-hidden="true">
252 + <i class="fa fa-check-circle"></i>
253 + <h4>Post-upgrade validation</h4>
254 + </div>
255 + <p>
256 + Verification of key pages, rights, authentication, extensions, jobs, PDFs, dashboards and custom applications.
257 + </p>
258 + </article>
259 +
260 + <article class="widget">
261 + <div class="icon" aria-hidden="true">
262 + <i class="fa fa-file-text-o"></i>
263 + <h4>Upgrade notes</h4>
264 + </div>
265 + <p>
266 + Practical documentation of the performed work, important decisions and recommended follow-up actions.
267 + </p>
268 + </article>
269 + </div>
108 108   </div>
109 109   </section>
110 110  
273 + ## CTA
274 + <section class="cta-section" aria-labelledby="cta-title">
275 + <div class="container">
276 + <div class="cta-panel">
277 + <h2 id="cta-title">Planning an XWiki upgrade?</h2>
278 +
279 + <p>
280 + Send your current XWiki version, target version if known, hosting setup and any custom extensions or integrations
281 + that may affect the upgrade. A short description is enough to start with.
282 + </p>
283 +
284 + <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an upgrade review</a>
285 + </div>
286 + </div>
287 + </section>
288 +
111 111  {{/html}}
112 112  {{/velocity}}
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,0 +1,1 @@
1 +Safe XWiki upgrade services for production instances, including LTS upgrade planning, extension compatibility, backups, rollback strategy and validation.
metaTitle
... ... @@ -1,0 +1,1 @@
1 +Safe XWiki Upgrade Services for Production Instances | Agnease