New Pro + Launch: pick a template and our developers set up your site in 2 business days.
See how it works
Case studies / Case study
NorCal CarciNET Community Non-profit · Patient support

CiviCRM on Joomla 6 for a Cancer Nonprofit

NorCal CarciNET Community takes donations, runs fundraising pages and handles event sign-ups through CiviCRM. We moved the whole site to Joomla 6 and kept every CiviCRM form working.

CiviCRM upgrade Joomla 4 → 6 Extension updates
NorCal CarciNET Community website and CiviCRM back end on Joomla 6
ClientNorCal CarciNET Community
TimelineFrom December 2025
ScopeCiviCRM · Joomla 6 Upgrade
Results

What changed for the team

0

CiviCRM core files changed. All Joomla 6 fixes live in extensions and hooks, so CiviCRM updates install as usual.

J4 → J6

Joomla upgraded, design kept. Same template and content, now on the current Joomla version.

2

Sites on one solution. The same CiviCRM-on-Joomla-6 work now also runs the WARMTH site.

The challenge

CiviCRM ships for Joomla 5. The site had to move to Joomla 6.

NorCal CarciNET Community is a Northern California 501(c)(3) for people living with neuroendocrine tumors and their families. Donations, the Oakland Running Festival fundraising pages, event pages and the newsletter sign-up all run on CiviCRM.

CiviCRM’s Joomla package targets Joomla 5, and official Joomla 6 support is still an open task in CiviCRM’s own tracker. Patching CiviCRM core would have worked once and broken at the next update.

Goal: make CiviCRM work safely on Joomla 6 and upgrade the site, without breaking future CiviCRM updates.

Our approach

Fix it outside the core, then prove it survives an update

  • Review versions & dependenciesJoomla, PHP and CiviCRM versions, and every extension the site relies on.
  • Joomla 6 compatibility via extensions & hooksStarting from CiviCRM’s Joomla 5 package – no core file modifications.
  • Test the CiviCRM update cycleInstalled a CiviCRM update and checked every fix was still in place.
  • Upgrade the site to Joomla 6Existing template kept; DPCalendar, JCE, Akeeba Backup and Phoca Download updated and tested.
  • Harden the CiviCRM cronAfter the host flagged heavy database load from cron, the job got a hard time limit so runs can’t pile up.
Timeline

Key dates

Nov 2025InquiryTwo CiviCRM sites need Joomla 6.
Dec 2025Quote & kick-offScope agreed: CiviCRM on Joomla 6, then both sites upgraded.
Mar 2026Cron hardenedTime limit added to the CiviCRM cron job.
Tech stack

What we worked with

Joomla 6 CiviCRM DPCalendar JCE Editor Akeeba Backup Phoca Download

Running CiviCRM on an older Joomla?

Tell us your Joomla and CiviCRM versions. We reply within one business day with a plan and a quote.

Cron Job Starts