Changes for page XWiki Upgrade Services

Last modified by Agnease on 2026/05/25 16:11

Manage
- Copy
Actions
- Export
- Print Preview
Viewers
- Source
- Siblings
- Content
- Comments
- Attachments
- History
- Information
- Likes

From 1.3 to 1.2 From 9.6 to 9.5

From version 9.5

edited by Agnease
on 2026/05/25 16:11

Change comment: There is no comment for this version

To version 1.3

edited by Agnease
on 2026/05/01 12:16

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Objects (0 modified, 0 added, 1 removed)
- Agnease.Code.SEODetailsClass[0]

Details

Page properties

Title

@@ -1,1 +1,1 @@
--XWiki Upgrade Services
++xwiki-upgrades

Content

@@ -1,126 +1,198 @@
  {{velocity}}
--#set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
--{{html clean="false"}}
--  ## PAGE HEADER
++  #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
++  {{html clean="false"}}
++
++  ## HERO
    <section class="hero hero-centered" aria-labelledby="hero-title">
      <div class="container hero-inner">
--      <div class="hero-kicker">
--        <i class="fa fa-refresh" aria-hidden="true"></i>
--        XWiki upgrade services
++      <h1 id="hero-title">XWiki Upgrades</h1>
++      <p class="lead">Safe, planned upgrades for production XWiki platforms.</p>
++
++      <ul class="benefits">
++        <li>Latest LTS versions</li>
++        <li>Security fixes</li>
++        <li>Extension checks</li>
++        <li>Minimal downtime</li>
++        <li>Rollback planning</li>
++      </ul>
++
++      <div class="hero-cta">
++        <a href="mailto:alex@agnease.com?subject=XWiki%20Upgrade%20Assessment">Request an upgrade assessment</a>
        </div>
--      <h1 id="hero-title">Safe XWiki LTS upgrades for production environments</h1>
++    </div>
++  </section>
++
++  ## INTRO
++  <section aria-labelledby="intro-title">
++    <div class="container">
++      <h2 id="intro-title">Upgrade XWiki with confidence</h2>
        <p class="lead">
--        Upgrade XWiki safely with a clear plan, compatibility checks and reduced production risk,
--        even for instances with custom extensions, integrations and workflows.
++        Agnease helps organizations upgrade XWiki instances with a focus on security, stability,
++        compatibility, and predictable execution.
        </p>
--      <div class="hero-actions">
--        <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an upgrade review</a>
--        <a class="btn btn-secondary" href="#upgrade-process">See the upgrade approach</a>
--      </div>
++
++      <p>
++        Whether your instance is one version behind or several years outdated, an XWiki upgrade should be treated
++        as a controlled technical operation, not a simple version change. The upgrade may affect installed
++        extensions, custom developments, authentication, PDF export, database behavior, scripts, and the
++        application server environment.
++      </p>
++
++      <p>
++        The goal is to keep your platform secure, stable, maintainable, and ready for future improvements
++        while reducing the risk of unexpected downtime or failed production upgrades.
++      </p>
      </div>
    </section>
--  ## WHY UPGRADES MATTER
--  #set ($upgradeReasonItems = [{
--    'title': 'Reduce security exposure',
++
++  ## WHY UPGRADE
++  #set ($whyUpgradeData = [{
++    'title': 'Security fixes',
      'icon': 'shield',
--    'content': 'Staying close to supported XWiki versions helps reduce exposure to known vulnerabilities and missing fixes.',
--    'items': [
--      'Review current version exposure',
--      'Plan upgrade to a supported version',
--      'Validate security-sensitive features'
--    ]
++    'content': 'Older versions may miss important fixes that were introduced in later XWiki releases.'
    },{
--    'title': 'Preserve compatibility',
--    'icon': 'cogs',
--    'content': 'Extensions, custom applications, authentication systems and infrastructure components need to remain compatible.',
--    'items': [
--      'Check installed extensions',
--      'Review custom code and scripts',
--      'Validate integrations after upgrade'
--    ]
++    'title': 'Stability improvements',
++    'icon': 'check-square-o',
++    'content': 'Regular upgrades reduce accumulated bugs and keep the platform easier to maintain.'
    },{
--    'title': 'Improve maintainability',
++    'title': 'Compatibility',
++    'icon': 'plug',
++    'content': 'Modern integrations, authentication systems, Java versions, databases, and application servers require careful compatibility planning.'
++  },{
++    'title': 'Lower future risk',
      'icon': 'line-chart',
--    'content': 'Smaller, regular upgrades are usually easier to control than large jumps after years of accumulated changes.',
--    'items': [
--      'Avoid long upgrade gaps',
--      'Document the current platform state',
--      'Prepare future upgrade cycles'
--    ]
++    'content': 'Frequent smaller upgrades are usually safer and more predictable than large delayed migrations.'
    }])
++
    <section aria-labelledby="why-upgrade-title">
      <div class="container">
--      <h2 id="why-upgrade-title">Why regular XWiki upgrades matter</h2>
--      <p class="section-intro">
--        An outdated XWiki instance can become harder to maintain over time. Security fixes, browser compatibility,
--        extension updates, platform changes and infrastructure requirements continue to evolve, while older versions
--        become more difficult and risky to upgrade.
--      </p>
--      <div class="pathways">
--        #foreach ($entry in $upgradeReasonItems)
--          <article class="pathway-card">
--            <div class="card-heading">
--              <div class="pathway-icon">
--                <i class="fa fa-$entry.icon" aria-hidden="true"></i>
--              </div>
--              <h3>$entry.title</h3>
--            </div>
++      <h2 id="why-upgrade-title">Why XWiki upgrades matter</h2>
++      <p class="lead">Regular upgrades help keep your XWiki platform secure, reliable, and easier to evolve.</p>
++      <div class="widgets">
++        #foreach ($entry in $whyUpgradeData)
++          <article class="widget">
++            <div class="icon" aria-hidden="true">
++              <i class="fa fa-$entry.icon"></i>
++              <h4>$entry.title</h4>
++            </div>
              <p>$entry.content</p>
--
--            <ul>
--              #foreach ($item in $entry.items)
--                <li>$item</li>
--              #end
--            </ul>
            </article>
          #end
        </div>
      </div>
    </section>
--  ## COMMON SITUATIONS
--  #set ($upgradeSituationItems = [{
--    'title': 'Old XWiki versions',
++
++  ## WHEN TO UPGRADE
++  #set ($whenToUpgradeData = [{
++    'title': 'Your XWiki version is old',
      'icon': 'clock-o',
--    'content': 'Instances that have not been upgraded for several months or years and require a careful upgrade path.'
++    'content': 'If your current version is more than one year old, the upgrade gap may already be significant.'
    },{
--    'title': 'Custom extensions and scripts',
--    'icon': 'puzzle-piece',
--    'content': 'Wikis with custom applications, Velocity scripts, macros, UI extensions, rights logic or business workflows.'
++    'title': 'You are not on the latest LTS',
++    'icon': 'refresh',
++    'content': 'Production instances should normally stay close to the latest suitable Long Term Support version.'
    },{
--    'title': 'Authentication integrations',
--    'icon': 'lock',
--    'content': 'LDAP, Active Directory, SSO, OIDC, SAML, MFA or custom login setups that must keep working after upgrade.'
++    'title': 'You use custom extensions',
++    'icon': 'cogs',
++    'content': 'Custom applications, scripts, macros, UI extensions, or Java components should be reviewed before upgrading.'
    },{
--    'title': 'Infrastructure changes',
--    'icon': 'server',
--    'content': 'Java, Tomcat, database, Docker, filesystem, reverse proxy or hosting changes required by newer versions.'
++    'title': 'Authentication is critical',
++    'icon': 'key',
++    'content': 'LDAP, Active Directory, OpenID Connect, SAML, or MFA integrations need careful validation during upgrades.'
    },{
--    'title': 'Business-critical features',
--    'icon': 'file-pdf-o',
--    'content': 'PDF exports, dashboards, structured data, templates, permissions, notifications and workflows that need validation.'
++    'title': 'Your wiki supports business processes',
++    'icon': 'sitemap',
++    'content': 'Instances used for intranets, procedures, documentation, approvals, or workflows deserve controlled upgrade planning.'
    },{
--    'title': 'Low-downtime rollout',
--    'icon': 'warning',
--    'content': 'Upgrade planning with backups, testing, rollback options and a controlled production deployment window.'
++    'title': 'You are preparing infrastructure changes',
++    'icon': 'server',
++    'content': 'Java, Tomcat, Docker, database, or operating system changes can make upgrade planning more important.'
    }])
--  <section class="services" aria-labelledby="situations-title">
++
++  <section class="services" aria-labelledby="when-title">
      <div class="container">
--      <h2 id="situations-title">Common situations we handle</h2>
--      <p class="section-intro">
--        XWiki upgrades are often simple in clean environments, but production instances usually include additional
--        constraints that need to be understood before touching the live system.
++      <h2 id="when-title">When should you consider an upgrade?</h2>
++      <p class="lead">
++        An upgrade is recommended when your XWiki instance is becoming outdated, exposed, or harder to maintain.
        </p>
++
        <div class="services-grid">
--        #foreach ($entry in $upgradeSituationItems)
++        #foreach ($entry in $whenToUpgradeData)
            <article class="service">
--            <div class="service-icon" aria-hidden="true">
--              <i class="fa fa-$entry.icon"></i>
++            <div class="service-icon">
++              <i class="fa fa-$entry.icon" aria-hidden="true"></i>
              </div>
++            <div class="service-body">
++              <h4>$entry.title</h4>
++              <p>$entry.content</p>
++            </div>
++          </article>
++        #end
++      </div>
++    </div>
++  </section>
++  ## WHAT AGNEASE HANDLES
++  #set ($upgradeScopeData = [{
++    'title': 'Assessment & planning',
++    'icon': 'search',
++    'content': 'Review the current version, environment, extensions, customizations, and target upgrade path.',
++    'items': [
++      'Current version and environment review',
++      'Recommended target version',
++      'Release notes and compatibility analysis'
++    ]
++  },{
++    'title': 'Extension & customization review',
++    'icon': 'puzzle-piece',
++    'content': 'Identify risks related to installed extensions, custom code, scripts, templates, and integrations.',
++    'items': [
++      'Installed extension review',
++      'Custom code impact analysis',
++      'Authentication and integration checks'
++    ]
++  },{
++    'title': 'Staging upgrade',
++    'icon': 'flask',
++    'content': 'Test the upgrade before production when a staging environment is available.',
++    'items': [
++      'Backup and restore validation',
++      'Upgrade execution in test environment',
++      'Troubleshooting and issue fixing'
++    ]
++  },{
++    'title': 'Production rollout',
++    'icon': 'rocket',
++    'content': 'Execute or guide the production upgrade with a clear plan and validation steps.',
++    'items': [
++      'Downtime and rollback planning',
++      'Production upgrade execution',
++      'Post-upgrade verification'
++    ]
++  }])
++
++  <section class="services" aria-labelledby="scope-title">
++    <div class="container">
++      <h2 id="scope-title">What Agnease handles</h2>
++      <p class="lead">
++        Upgrade support can cover the full process, from assessment to production rollout.
++      </p>
++
++      <div class="services-grid">
++        #foreach ($entry in $upgradeScopeData)
++          <article class="service">
++            <div class="service-icon">
++              <i class="fa fa-$entry.icon" aria-hidden="true"></i>
++            </div>
              <div class="service-body">
                <h4>$entry.title</h4>
                <p>$entry.content</p>
++              <ul>
++                #foreach ($item in $entry.items)
++                  <li>$item</li>
++                #end
++              </ul>
              </div>
            </article>
          #end
@@ -127,99 +127,200 @@
        </div>
      </div>
    </section>
++
    ## PROCESS
--  #set ($upgradeProcessItems = [{
--    'title': 'Review the current instance',
--    'content': 'Version, extensions, database, filesystem, authentication, custom code, logs and infrastructure constraints.'
++  #set ($processData = [{
++    'title': '1. Initial review',
++    'icon': 'info-circle',
++    'content': 'We review your current XWiki version, hosting environment, installed extensions, customizations, authentication setup, and known issues.'
    },{
--    'title': 'Define the upgrade path',
--    'content': 'Target version, intermediate steps if needed, compatibility risks, expected downtime and rollback options.'
++    'title': '2. Upgrade path',
++    'icon': 'map-signs',
++    'content': 'We identify the recommended target version and whether the upgrade should be direct, staged, or combined with infrastructure changes.'
    },{
--    'title': 'Prepare and validate',
--    'content': 'Backups, test upgrade when needed, extension checks and validation of critical XWiki features.'
++    'title': '3. Compatibility checks',
++    'icon': 'check',
++    'content': 'We review release notes, extensions, custom developments, authentication integrations, PDF export, and other sensitive areas.'
    },{
--    'title': 'Upgrade production',
--    'content': 'Controlled execution, post-upgrade checks, issue resolution and confirmation that key features still work.'
++    'title': '4. Backup and rollback plan',
++    'icon': 'database',
++    'content': 'Before production work, the database, permanent directory, application files, and configuration backup strategy should be clear.'
    },{
--    'title': 'Document next steps',
--    'content': 'Upgrade notes, observed risks, remaining recommendations and future maintenance guidance.'
++    'title': '5. Staging validation',
++    'icon': 'desktop',
++    'content': 'Whenever possible, the upgrade is tested in a staging environment to validate key pages, extensions, permissions, and workflows.'
++  },{
++    'title': '6. Production upgrade',
++    'icon': 'upload',
++    'content': 'The production upgrade is executed according to the agreed plan, with attention to downtime, rollback options, and validation.'
    }])
--  <section id="upgrade-process" class="split-section" aria-labelledby="process-title">
++
++  <section class="services" aria-labelledby="process-title">
      <div class="container">
--      <div class="split-grid">
--        <div class="split-copy">
--          <h2 id="process-title">A practical upgrade approach</h2>
--          <p>
--            The goal is not only to install a newer version. The goal is to move your XWiki instance forward
--            while protecting the data, configuration, customizations and business processes that already depend on it.
--          </p>
--          <p>
--            The upgrade is always prepared outside production first, using a staging environment or a temporary clone
--            of the live instance. This allows compatibility issues, extension problems, authentication changes and
--            custom features to be validated before the controlled production rollout.
--          </p>
--        </div>
--        <ol class="process-list">
--          #foreach ($entry in $upgradeProcessItems)
--            <li>
--              <strong>$entry.title</strong>
--              $entry.content
--            </li>
--          #end
--        </ol>
++      <h2 id="process-title">A structured upgrade process</h2>
++      <p class="lead">
++        The process is designed to reduce surprises and keep the platform operational.
++      </p>
++
++      <div class="services-grid">
++        #foreach ($entry in $processData)
++          <article class="service">
++            <div class="service-icon">
++              <i class="fa fa-$entry.icon" aria-hidden="true"></i>
++            </div>
++            <div class="service-body">
++              <h4>$entry.title</h4>
++              <p>$entry.content</p>
++            </div>
++          </article>
++        #end
        </div>
      </div>
    </section>
--  ## DELIVERABLES
--  #set ($upgradeDeliverableItems = [{
--    'title': 'Upgrade review',
--    'icon': 'search',
--    'content': 'Review of the current version, installed extensions, customizations, authentication and hosting constraints.'
++
++  ## COMMON SCENARIOS
++  #set ($scenariosData = [{
++    'title': 'Regular LTS upgrade',
++    'icon': 'calendar-check-o',
++    'content': 'For organizations that upgrade regularly and want to stay aligned with the latest stable XWiki release line.'
    },{
--    'title': 'Upgrade plan',
--    'icon': 'map',
--    'content': 'Recommended target version, risk areas, validation checklist, downtime expectations and rollback approach.'
++    'title': 'Delayed upgrade',
++    'icon': 'exclamation-triangle',
++    'content': 'For instances that have not been upgraded for one or more years and need a more careful compatibility review.'
    },{
--    'title': 'Post-upgrade validation',
--    'icon': 'check-circle',
--    'content': 'Verification of key pages, rights, authentication, extensions, jobs, PDFs, dashboards and custom applications.'
++    'title': 'Major platform transition',
++    'icon': 'random',
++    'content': 'For upgrades that also involve Java, Tomcat, Docker, database, or operating system changes.'
    },{
--    'title': 'Upgrade notes',
--    'icon': 'file-text-o',
--    'content': 'Practical documentation of the performed work, important decisions and recommended follow-up actions.'
++    'title': 'Custom application upgrade',
++    'icon': 'code',
++    'content': 'For XWiki instances with custom workflows, scripts, macros, PDF templates, or Java extensions.'
++  },{
++    'title': 'Authentication-sensitive upgrade',
++    'icon': 'lock',
++    'content': 'For platforms using LDAP, Active Directory, OpenID Connect, SAML, MFA, or other authentication integrations.'
++  },{
++    'title': 'Failed upgrade recovery',
++    'icon': 'ambulance',
++    'content': 'For organizations that already attempted an upgrade and encountered startup errors, broken extensions, or rendering issues.'
    }])
--  <section aria-labelledby="deliverables-title">
++
++  <section class="services" aria-labelledby="scenarios-title">
      <div class="container">
--      <h2 id="deliverables-title">What you can expect</h2>
--      <p class="section-intro">
--        The exact scope depends on your XWiki version, hosting setup and customizations, but an upgrade engagement
--        usually includes a clear technical review, a controlled upgrade plan and post-upgrade validation.
++      <h2 id="scenarios-title">Common upgrade scenarios</h2>
++      <p class="lead">
++        Agnease can help with both routine upgrades and complex migration situations.
        </p>
--      <div class="widgets">
--        #foreach ($entry in $upgradeDeliverableItems)
--          <article class="widget">
--            <div class="icon" aria-hidden="true">
--              <i class="fa fa-$entry.icon"></i>
++
++      <div class="services-grid">
++        #foreach ($entry in $scenariosData)
++          <article class="service">
++            <div class="service-icon">
++              <i class="fa fa-$entry.icon" aria-hidden="true"></i>
++            </div>
++            <div class="service-body">
                <h4>$entry.title</h4>
++              <p>$entry.content</p>
              </div>
--            <p>$entry.content</p>
            </article>
          #end
        </div>
      </div>
    </section>
--  ## CTA
--  <section class="cta-section" aria-labelledby="cta-title">
++
++  ## PLATFORM NOTE
++  <section aria-labelledby="platform-title">
      <div class="container">
--      <div class="cta-panel">
--        <h2 id="cta-title">Planning an XWiki upgrade?</h2>
--        <p>
--          Send your current XWiki version, target version if known, hosting setup and any custom extensions or integrations
--          that may affect the upgrade. A short description is enough to start with.
--        </p>
--        <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Request an upgrade review</a>
++      <h2 id="platform-title">Major version upgrades require planning</h2>
++      <p class="lead">
++        Some XWiki upgrades also require infrastructure-level preparation.
++      </p>
++
++      <div class="widgets">
++        <article class="widget">
++          <div class="icon" aria-hidden="true">
++            <i class="fa fa-server"></i>
++            <h4>Application server compatibility</h4>
++          </div>
++          <p>
++            Major XWiki versions may introduce changes that affect Java, Tomcat, Docker images,
++            database drivers, or deployment configuration. These changes should be reviewed before production rollout.
++          </p>
++        </article>
++
++        <article class="widget">
++          <div class="icon" aria-hidden="true">
++            <i class="fa fa-plug"></i>
++            <h4>Extension compatibility</h4>
++          </div>
++          <p>
++            Installed extensions and custom applications should be checked against the target version,
++            especially when the instance contains business-specific workflows or integrations.
++          </p>
++        </article>
++
++        <article class="widget">
++          <div class="icon" aria-hidden="true">
++            <i class="fa fa-shield"></i>
++            <h4>Security and stability</h4>
++          </div>
++          <p>
++            Staying close to the recommended LTS version helps reduce exposure to known issues and keeps
++            the platform easier to maintain over time.
++          </p>
++        </article>
        </div>
      </div>
    </section>
++
++  ## ASSESSMENT CTA
++  <section class="cta-section" aria-labelledby="assessment-title">
++    <div class="container">
++      <h2 id="assessment-title">Request an XWiki upgrade assessment</h2>
++      <p class="lead">
++        Not sure how far your instance is from the recommended version?
++      </p>
++
++      <p class="text-center">
++        Send your current XWiki version and a short description of your setup.
++        Agnease will review the situation and provide a practical upgrade recommendation.
++      </p>
++
++      <div class="widgets">
++        <article class="widget">
++          <div class="icon" aria-hidden="true">
++            <i class="fa fa-list"></i>
++            <h4>The assessment can include</h4>
++          </div>
++          <p>
++            Recommended target version, estimated upgrade effort, security and stability reasons to upgrade,
++            infrastructure considerations, extension risks, customization risks, and suggested next steps.
++          </p>
++        </article>
++      </div>
++
++      <p class="text-center contact-inline">
++        <a href="mailto:alex@agnease.com?subject=XWiki%20Upgrade%20Assessment">Request an upgrade assessment</a>
++      </p>
++    </div>
++  </section>
++
++  ## RELATED SERVICES
++  <section aria-labelledby="related-title">
++    <div class="container">
++      <h2 id="related-title">Related Agnease services</h2>
++      <p class="lead">
++        XWiki upgrades are often connected to maintenance, security, development, and integration work.
++      </p>
++
++      <ul class="benefits">
++        <li>Maintenance & support</li>
++        <li>Security review</li>
++        <li>Custom development</li>
++        <li>Integrations</li>
++        <li>Migrations</li>
++      </ul>
++    </div>
++  </section>
  {{/html}}
  {{/velocity}}

Agnease.Code.SEODetailsClass[0]

metaDescription

...	...	@@ -1,1 +1,0 @@
1		-Safe XWiki upgrade services for production instances, including LTS upgrade planning, extension compatibility, backups, rollback strategy and validation.

metaTitle

...	...	@@ -1,1 +1,0 @@
1		-Safe XWiki Upgrade Services for Production Instances \| Agnease