More extensions coming fast. What you see here today will be different tomorrow.
RCA Joomla Extension Refactoring Protocol
The refactoring protocol Joomla never created.
Built by someone who couldn't afford for it not to exist.
A complete, battle-tested 9-phase framework for migrating and refactoring Joomla extensions from J3 to J6 — written by someone who lived every failure mode documented within it.
This is not a tutorial. And it's not for beginners. It is a protocol — the kind you write when you've broken enough production sites to know what 'mandatory' actually means.
v3.6 · Current 9 Phases 37 Substitutions 19 Maxims Living Document J4 · J5 · J6
What This Document Is
The RCA Joomla Extension Refactoring Protocol is a structured, authoritative reference document for developers and agencies who need to refactor, rebuild, or migrate Joomla extensions from J3/J4/J5 to full Joomla 6 compliance.
It is not a set of tips. It is not a YouTube tutorial transcript. It is a working protocol — the internal standard used by ReCreatingAnew on every extension we build or refactor — now documented, organized, and made available for other developers to use.
Every rule exists because something broke without it. Every checklist item was added because it was skipped once, with consequences. Every section on "what goes wrong" was written from direct experience, not speculation.
This is the document that would have saved 40+ hours of avoidable debugging if it had existed when we started.
What's Inside
- 9-phase refactoring process — audit to JED submission
- 37 documented deprecation substitutions with exact replacements
- 19 GinA's Maxims — hard-earned lessons at key decision points
- SR_RTFM — the mandatory rule with a 5-version post-mortem case study
- SR_LIN — Linux/Ubuntu/Virtualmin server fundamentals for Joomla
- SR_AUTOENABLE — exact modern InstallerScriptInterface pattern
- Full JED 4 compliance checklist + pre-submission checklist
- Annotated links to all Joomla official migration & developer docs
- RCA Refactor Classification System — risk, pricing & scope framework
- RCA Pattern Registry — 6 documented anti-patterns with fixes
- Weekly Sunday digest — notable changes, zero noise
- Immediate ⚠️ alerts for time-sensitive protocol corrections
What "Battle-Tested" Actually Means
Every protocol claims to be best-practice. Most mean: we read the docs and wrote it down. This one means something different.
This document was written during the active, live development of a Joomla 6 production platform — recreatinganew.com. Every rule was either already known from 18 years of Joomla experience, or was added immediately after something broke, with a root cause explanation.
SR_RTFM documents five successive failed versions of a plugin installer that all broke the same way — because the Joomla Developer Manual wasn't consulted first. The fix took 20 minutes once it was. The lesson is now Maxim #0, permanently encoded so it cannot be skipped again.
SR_LIN exists because a file ownership conflict between gina:gina and recreatinganew.com:recreatinganew.com silently failed for a week before the root cause was fully understood. It is now a complete standalone section on Linux/Ubuntu server fundamentals.
You are not reading theory. You are reading scar tissue.
Why 9 Phases, Not a Checklist
Typical "Best Practice" Article
- A list of things you should probably do
- No ordering, no dependencies between steps
- No explanation of what breaks if you skip something
- Written by someone who didn't necessarily ship anything
- "Updated" means the publish date changed
RCA Protocol
- 9 phases that must execute in order — each builds on the last
- Every rule flags what breaks without it
- Root cause explanations, not just directives
- Written during live J6 production development
- Updated when something breaks — with documentation of what it was
Who This Was Written For
You are migrating extensions from Joomla 3 (or early J4) to Joomla 6. You are doing this seriously — for clients, for income, or for your own platform. You have hit at least two of these:
- A PHP 8.x fatal that "worked fine" in PHP 7.4
- A deprecated
Factory::getDBO()that silently returned null - A
Joomla tmp/permission error that made no sense until it did - An extension that installed disabled and you didn't know why
- A ZIP that "failed to extract" even though the file was fine
- A modal that worked in J3 and silently failed in J4 with no error
If two or more of those look familiar: this protocol is for you.
Also written for:
- Agencies onboarding junior developers who need a codified standard
- Freelancers who want to stop re-learning the same J6 gotchas
- Solo developers who manage their own Linux servers
Not written for:
- Beginners installing their first Joomla site
- Front-end theme designers who don't write PHP
- Developers who don't intend to touch the Joomla backend
What Makes It Different
| Feature | Blog post / tutorial | Random GitHub gist | RCA Protocol |
|---|---|---|---|
| Covers J3 → J6 specifically | Rarely | Sometimes | ✅ Complete |
| PHP 8.x compatibility notes | Occasionally | Rarely | ✅ Throughout |
| Server-level Linux/Virtualmin coverage | Never | Never | ✅ SR_LIN |
| Root cause explanations | Almost never | Never | ✅ Every rule |
| Post-mortem case studies | Never | Never | ✅ SR_RTFM, SR_AUTOENABLE |
| JED 4 compliance checklist | Not in one place | No | ✅ Full reference |
| Living document + weekly update digest | No | No | ✅ Included |
The thing you can't get anywhere else: The 37 documented substitutions are not in the Joomla docs. They are not in any blog. They were discovered, diagnosed, and fixed one by one during actual migration work. There is no shortcut to acquiring this list except breaking the same things we already broke. We broke them for you. You get the list.
This Document Is Not a Static PDF
The RCA Joomla Refactoring Protocol is a living document. It is updated when a new breaking change is discovered, a rule is corrected based on battle-testing evidence, a new standing rule is added, or a JED requirement changes.
Your license includes:
- Current version delivered at purchase
- All updates for 12 months from purchase
- Every correction and addition in that window
- Weekly Sunday digest notifications
- Immediate ⚠️ alerts for time-sensitive corrections
- Permanent access to final version at license end
Sample Changelog Entry — v3.2
Fixed: SR_PKG Step 3 — the actual failure mode is re-zipping into an existing archive. Rule now mandates: rm the old ZIP before building a new one.
Added: SR_LIN — complete Linux/Ubuntu server fundamentals for Virtualmin.
Added: SR_RTFM — consult the Joomla Developer Manual FIRST. With a 5-version post-mortem.
About the Author
GinA has been building with Joomla since 2008. She manages a five-node Ubuntu server farm from home in Sidney, Maine — multiple production domains, reverse proxy, full SSL — entirely self-administered.
She debugged commercial Lotus Notes and Lotus Domino code in 1999, completed MCSE training out of sequence while helping other students, and spent one full year implementing a Zero Access Encryption plugin for outgoing mail — alone, without help.
She spent 4.7 years as a Senior Litigation Paralegal: 45+ complex civil litigation cases, $562,000+ in firm settlements, and two pro se petitions to the United States Supreme Court drafted independently.
She is also a certified QuickBooks ProAdvisor who passed the certification in a single day, then forensically reconstructed 21 years of broken HOA financials — 15,129 Undeposited Funds transactions, $155,000 in unexplained balances — in 12 working days.
"The best thing anyone can do for me is tell me I can't do something — because I'll prove them wrong, and I'll have fun doing it."
This protocol is Exhibit A. The full biography is included in the document.
Choose Your License
All licenses include the complete document and 12 months of updates.
Personal
Single developer · 1 active project
$497
per year
- ✓ Full protocol document
- ✓ 12 months of updates
- ✓ Weekly digest
- ✓ 1 developer, 1 project
MOST POPULAR
Agency
Up to 5 developers · unlimited projects
$997
per year
- ✓ Full protocol document
- ✓ 12 months of updates
- ✓ Weekly digest
- ✓ Up to 5 developers
- ✓ Unlimited client projects
Enterprise
Unlimited developers · white-label permitted
$1,997
per year
- ✓ Full protocol document
- ✓ 12 months of updates
- ✓ Weekly digest
- ✓ Unlimited developers
- ✓ Unlimited projects
- ✓ White-label permitted
All prices in USD. Annual license. Renews at the same rate. Cancel any time before renewal.
Add Tutorials to Any Plan
Hands-on Joomla development tutorials taught by GinA — covering extension refactoring, server administration, and J6 migration workflows. Included automatically with Agency and Enterprise licenses.
Agency and Enterprise licenses include Tutorials automatically. Personal license holders add separately. Standalone Tutorials (no Protocol required): $297/yr or $27/mo.
Free Version Available
A condensed read-only preview — covering Phase 1 audit, the SR_RTFM standing rule, and the 37 substitution index — is available for free download. No account required.
Download Free Preview →