Skip to Content
Last modified by Agnease on 2026/05/26 10:58
From version 8.3
edited by Agnease
on 2026/05/26 09:14
Change comment: There is no comment for this version
To version 1.8
edited by Agnease
on 2026/05/12 14:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,0 @@
1 -Why You Should Upgrade XWiki Regularly for Security and Stability
Content
... ... @@ -5,7 +5,7 @@
5 5   <section class="resource-header" aria-labelledby="hero-title">
6 6   <div class="container">
7 7   <div class="text-center">
8 - <div class="hero-kicker">
8 + <div class="resource-kicker">
9 9   <i class="fa fa-refresh" aria-hidden="true"></i>
10 10   XWiki upgrade guidance
11 11   </div>
... ... @@ -24,17 +24,6 @@
24 24   <div class="container">
25 25   <div class="resource-layout">
26 26  
27 - <aside class="resource-sidebar" aria-label="Page summary">
28 - <h4>In this guide</h4>
29 - <ul>
30 - <li><a href="#why-it-matters">Why upgrades matter</a></li>
31 - <li><a href="#upgrade-checklist">Upgrade checklist</a></li>
32 - <li><a href="#safe-process">Safe process</a></li>
33 - <li><a href="#common-mistakes">Common mistakes</a></li>
34 - <li><a href="#upgrade-rhythm">Upgrade rhythm</a></li>
35 - </ul>
36 - </aside>
37 -
38 38   <article class="resource-content">
39 39  
40 40   <p>
... ... @@ -150,15 +150,6 @@
150 150   review, staging validation, production rollout, documentation and follow-up.
151 151   </p>
152 152  
153 - <div class="resource-note">
154 - <p>
155 - Related resources:
156 - <a href="$xwiki.getURL('resources.xwiki-security-review')">what an XWiki security review should actually include</a>
157 - and
158 - <a href="$xwiki.getURL('resources.xwiki-custom-development')">how to keep XWiki custom development maintainable across upgrades</a>.
159 - </p>
160 - </div>
161 -
162 162   <div class="resource-cta">
163 163   <h3>Need help planning an XWiki upgrade?</h3>
164 164   <p>
... ... @@ -165,10 +165,22 @@
165 165   If your XWiki instance is outdated, customized or business-critical, the safest next step is to review
166 166   the current version, extensions, infrastructure and validation needs before planning the production upgrade.
167 167   </p>
168 - <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an upgrade review</a>
148 + <a class="btn btn-primary" href="$xwiki.getURL('services.xwiki-upgrades')">View XWiki upgrade services</a>
169 169   </div>
170 170  
171 171   </article>
152 +
153 + <aside class="resource-sidebar" aria-label="Page summary">
154 + <h4>In this guide</h4>
155 + <ul>
156 + <li><a href="#why-it-matters">Why upgrades matter</a></li>
157 + <li><a href="#upgrade-checklist">Upgrade checklist</a></li>
158 + <li><a href="#safe-process">Safe process</a></li>
159 + <li><a href="#common-mistakes">Common mistakes</a></li>
160 + <li><a href="#upgrade-rhythm">Upgrade rhythm</a></li>
161 + </ul>
162 + </aside>
163 +
172 172   </div>
173 173   </div>
174 174   </section>
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,1 +1,0 @@
1 -Learn why regular XWiki upgrades matter for security, stability, extension compatibility and long-term maintenance, especially for production XWiki instances.
metaTitle
... ... @@ -1,1 +1,0 @@
1 -Why You Should Upgrade XWiki Regularly for Security and Stability | Agnease