Category: Joomla

  • Joomla PHP 8.6 Compatibility: Supported Versions, Security Fixes and What to Do Now

    Joomla PHP 8.6 Compatibility: Supported Versions, Security Fixes and What to Do Now

    Last updated November 20, 2026. Checked against php.net, the Joomla Security Centre, the Joomla roadmap and the joomla-cms GitHub repository on that date. We will update this guide when Joomla announces PHP 8.6 support.

    Short answer: PHP 8.6 was released on November 19, 2026 (php.net), but no Joomla release supports it yet. Joomla 6.2, the current version, officially runs on PHP 8.3 to 8.5 and recommends PHP 8.4 (Joomla technical requirements). On PHP 8.6, Joomla 6.2.0 throws deprecation notices and session warnings that can break the admin login when error display is on. Keep live sites on a patched PHP 8.4 or 8.5 (8.4.28 or 8.5.13, released November 19), and test PHP 8.6 on a staging copy only.

    The more urgent issue is security. In October 2026 PHP fixed PHP2Shell (CVE-2026-109618 and CVE-2026-109619), two critical flaws that let a stranger run code on a server without logging in. CISA added both to its list of actively exploited vulnerabilities on October 26. A second batch of PHP security fixes followed on November 19. Joomla itself also fixed 26 core security issues in August and September 2026. Joomla’s own fixes don’t reach Joomla 3 or Joomla 4, and neither version can move to the PHP branches that keep getting fixes after 2026.

    What to do, in order: 1) put PHP on 8.4.28, 8.5.13, 8.3.37 or newer, 2) update Joomla to 6.2.0 (or at least 5.4.10), 3) update every extension, 4) keep production off PHP 8.6 until a Joomla release says it supports it, 5) if you are on Joomla 3 or 4, plan the upgrade now. Each step is explained below, with a separate checklist for extension developers.

    Key facts at a glance

    QuestionAnswer (November 20, 2026)Source
    Is PHP 8.6 released?Yes, PHP 8.6.0 on November 19, 2026. Active support to Dec 31, 2028, security fixes to Dec 31, 2030.php.net supported versions
    Does Joomla 6.2 support PHP 8.6?Not officially. Requirements list PHP 8.3.0 minimum and 8.4 recommended. PHP 8.5 has been fully supported since 6.0.2.Joomla manual, 6.0.2 release notes
    When will Joomla fix PHP 8.6 warnings?Not dated. The main core fix (pull request #48520) is labeled for Joomla 6.3, scheduled for April 13, 2027, and is still open.PR #48520, Joomla roadmap
    What is the recent security issue?PHP2Shell: two critical PHP flaws (CVSS v4.0 9.2) fixed on October 21, 2026, plus more PHP security fixes on November 19.php.net advisory
    Safe PHP builds today8.5.13, 8.4.28, 8.3.37, 8.2.36 or 8.6.0PHP 8 changelog
    Safe Joomla builds today6.2.0 (latest), 6.1.4+, or 5.4.9+ (5.4.10 is the latest 5.x)Joomla Security Centre
    Joomla 3 and 4End of life, no Joomla security fixes. Joomla 3 is certified only up to PHP 8.0 (end of life); Joomla 4 recommends PHP 8.2, which loses support Dec 31, 2026.Joomla manual (archived)

    What is the security issue, in plain English?

    PHP is the engine that runs Joomla. Every page of your site, the home page, the contact form and the administrator login, is built by PHP on your web server. Your hosting company installs PHP, not Joomla.

    PHP2Shell is a fault inside that engine. When a request makes PHP run out of memory or fail at the wrong moment, PHP can leave scraps of the old request behind. An attacker can send carefully built web requests that make PHP reuse those scraps and run the attacker’s own commands. No password or account is needed. php.net says the risk covers every PHP installation that serves web pages, and it is highest on Apache with mod_php, where a working attack runs before any application code (php.net, October 21, 2026).

    Think of Joomla security as the lock on your office door. PHP2Shell is a broken lock on the building’s front door that also opens the service corridor behind every office. A stronger office lock does not help. Only the building manager, your host, can fix it, by installing the fixed PHP release.

    How could it harm an unpatched Joomla site?

    Once someone can run commands on your server, they can do roughly what your site can do. These are the usual outcomes of that level of access on any hacked site:

    • Defaced or redirected pages: visitors see the attacker’s content or get sent to spam or scam sites.
    • Hidden malware: code tucked into template files or the database that infects visitors or shows spam links to Google.
    • Stolen data: user accounts, contact-form submissions, orders and customer details copied from your database.
    • Admin takeover: new Super User accounts created directly in the database, bypassing your passwords and two-factor login.
    • Search and hosting damage: Google’s “This site may be hacked” warning, lost rankings, and hosts suspending accounts that send spam.

    Joomla extensions, security plugins and strong passwords cannot block a flaw that sits one layer below Joomla. If your site has already been hit, our hacked Joomla repair guide covers cleanup step by step. For a host-by-host patching walkthrough (cPanel, Plesk, VPS), see our PHP2Shell patch guide.

    Does Joomla support PHP 8.6?

    Not yet. As of November 20, 2026, no Joomla release note, security announcement or requirements page lists PHP 8.6. The Joomla 6.x technical requirements show PHP 8.4 as recommended and PHP 8.3.0 as both the supported and enforced minimum. The upcoming 6.2.1 release, a release candidate since November 17 and scheduled for November 24 (roadmap), contains no PHP 8.6 changes in its changelog.

    That is normal. Joomla announced full PHP 8.5 support in 6.0.2 and 5.4.2, about seven weeks after PHP 8.5 came out (Joomla 6.0.2 & 5.4.2 release notes). Expect a similar pattern for PHP 8.6, but no date has been announced.

    What actually happens when Joomla 6.2 runs on PHP 8.6?

    A tester who ran Joomla 6.2 on a PHP 8.6 pre-release got Joomla’s “An error has occurred” page instead of the administrator (issue #48494). The output showed three problems:

    • Session handler warnings. PHP 8.6 now emits a warning for any class that implements SessionHandlerInterface without the create_sid() and validateId() methods (PHP 8.6 deprecations). Joomla’s session handlers live in the separate Joomla Framework package (joomla/session 4.0.0 in Joomla 6.2.0) and don’t have them yet. The fix is tracked in joomla-framework/session issue #69.
    • “Headers already sent”. Because those warnings were printed to the screen, PHP could no longer set the session cookie. That is what stopped the admin from loading.
    • A spl_object_hash() deprecation in PluginHelper, which runs on almost every request.

    We downloaded the official Joomla 6.2.0 full package and searched it for functions that PHP 8.6 deprecates. In Joomla’s own code we found six spl_object_hash() calls in four files, one is_integer() call, and strcoll() calls in the bundled joomla/string package. Bundled third-party libraries contain more spl_object_hash() calls. These match the list a contributor posted to the PHP 8.6 tracking issue #48218 on November 19.

    Where (Joomla 6.2.0)PHP 8.6 changeEffect
    libraries/src/Plugin/PluginHelper.php lines 178 and 225spl_object_hash() deprecatedDeprecation notice on almost every page load
    libraries/src/Cache/Controller/CallbackController.php line 201spl_object_hash() deprecatedNotice when callback caching runs
    libraries/src/Log/Log.php lines 249 and 252spl_object_hash() deprecatedNotice when callback loggers are added
    plugins/system/debug/.../ProfileCollector.php line 182spl_object_hash() deprecatedNotice with the debug plugin on
    com_guidedtours/src/Model/TourModel.php line 562is_integer() deprecatedNotice in Guided Tours
    libraries/vendor/joomla/session/src/Handler/*Session handlers without create_sid()/validateId()Warning at class load; required in PHP 9.0
    libraries/vendor/joomla/string/src/StringHelper.phpstrcoll() deprecatedNotice during locale-aware string compares

    Deprecation notices are not errors. With error display off, as it should be on a live site, they only go to the log and the site keeps working. The danger is a server, or a developer, with error display switched on. That is why PHP 8.6 belongs on staging for now.

    Which Joomla versions support which PHP versions?

    Use this matrix to find where your site stands. Joomla data comes from the 6.x, 5.x and 4.x/3.x (archived)

    Matrix of Joomla 6.2, 5.4, 4.4 and 3.10 against PHP 8.1 to 8.6 showing which combinations are supported
    requirements pages and the Joomla roadmap.

    JoomlaSupport statusMinimum PHPRecommended PHPPHP 8.5PHP 8.6
    6.2 (6.x)Supported. Bug fixes to Oct 17, 2028, security to Oct 16, 20298.3.08.4Yes, since 6.0.2Not yet supported; staging only
    5.4Security fixes only, until Oct 12, 2027 (5.4.10 was the last bug-fix release)8.1.08.3Yes, since 5.4.2Not announced
    4.4End of life. Security support ended in October 2025 (last release 4.4.14)7.2.58.2NoNo
    3.10End of life since Aug 17, 2023; extended LTS ended Feb 17, 20255.3.108.0NoNo

    Which PHP versions are patched and supported?

    Support dates are from php.net supported versions. Fixed versions are from the PHP 8 changelog

    Timeline of PHP 8.2 to 8.6 support end dates with the minimum patched build for each branch
    and the October 21 advisory.

    PHP branchActive support untilSecurity fixes untilPHP2Shell fixed inLatest security releaseUse with Joomla 6.2?
    8.6Dec 31, 2028Dec 31, 2030Fixed before release (8.6.0 RC4 onward)8.6.0 (Nov 19, 2026)Staging only for now
    8.5Dec 31, 2027Dec 31, 20298.5.128.5.13 (Nov 19, 2026)Yes
    8.4Dec 31, 2026Dec 31, 20288.4.278.4.28 (Nov 19, 2026)Yes, recommended
    8.3Ended Dec 31, 2025Dec 31, 20278.3.368.3.37 (Nov 19, 2026)Yes (minimum)
    8.2Ended Dec 31, 2024Dec 31, 20268.2.358.2.36 (Nov 19, 2026)No (Joomla 5.4 only)
    8.1 and olderEnd of lifeEnd of lifeNo official releaseNoneNo

    PHP 8.2 loses all security support on December 31, 2026, so a Joomla 5.4 site on PHP 8.2 has about six weeks before its PHP stops getting fixes.

    How has the security issue been addressed?

    PHP: the October 21 emergency release

    The PHP security team gave one day’s notice on October 20 and shipped PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 on October 21, 2026. Both flaws are rated critical, CVSS v4.0 9.2 (GHSA-w8hw-w9fx-j79w, GHSA-6wmf-4rv5-p3rp):

    • CVE-2026-109618, “RCE via OOM corruption”: when PHP runs out of memory mid-request, request data can be left half-initialized, and the cleanup step then trusts it. Oversized multipart uploads with huge numbers of headers or empty file fields are among the documented triggers.
    • CVE-2026-109619, “RCE via stale global state”: internal state from one request can survive after its memory is freed, and the next request on the same PHP worker can use it.

    The fix in every branch is the same changelog line: “Avoid state corruption via bailout.” PHP also published minimal source-only patches for 7.4, 8.0 and 8.1 for people who build PHP themselves, but no official releases for those end-of-life branches (php.net). On October 26, CISA added both CVEs to its Known Exploited Vulnerabilities catalog, which means it has evidence of active exploitation.

    PHP: the October 23 follow-up and November 19 security releases

    On October 23, php.net advised setting session.upload_progress.enabled=0 until the next release because of a related, unlikely session issue (CVE-2026-115560). After a “critical” pre-announcement on November 18 (php.net), PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on November 19, alongside PHP 8.6.0, which includes the same fixes. php.net says the critical issues in this batch need non-default configuration or uncommon setups. Those most relevant to Joomla hosting:

    CVEProblemWho should care
    CVE-2026-126714Partially overwritten session files can lead to remote code executionSites using file-based PHP sessions
    CVE-2026-115560Session serializer mismatch can lead to remote code executionServers that switch the session serializer at runtime
    CVE-2026-129496Timezone cache use-after-free can lead to remote code executionAll branches 8.2 to 8.6
    CVE-2026-129538PHP-CGI out-of-bounds read and write during PATH_INFO correctionHosts running PHP as CGI
    CVE-2026-129289 / 129291PHP-FPM request smuggling; PHP-FPM local privilege escalationMost VPS and managed hosts (PHP-FPM)
    CVE-2026-128090PHAR OpenSSL signature bypass via algorithm downgradeAnything that verifies signed .phar files

    The full list, more than a dozen CVEs per branch, is in the PHP 8 changelog. If your host patched for PHP2Shell in October, you still need this November update.

    Joomla: 26 core security fixes in August and September

    Joomla cannot patch PHP, but the Joomla Security Strike Team has been busy with Joomla’s own code. Joomla 6.1.3 and 5.4.8 (August 18, 2026) fixed 10 issues, and Joomla 6.1.4 and 5.4.9 (September 29, 2026) fixed 16 more (release notes, Security Centre). Joomla 6.2.0 and 5.4.10 shipped after both and include them. The most serious:

    Joomla advisoryCVEImpactAffectedFixed in
    [20260914] MFA bypass through “remember me” cookiesCVE-2026-92227High4.0.0 to 5.4.8, 6.0.0 to 6.1.35.4.9 / 6.1.4
    [20260909] SSRF vectors in core extensionsCVE-2026-92222High4.0.0 to 5.4.8, 6.0.0 to 6.1.35.4.9 / 6.1.4
    [20260905] Arbitrary directory deletion via cache purgeCVE-2026-90915High4.0.0 to 5.4.8, 6.0.0 to 6.1.35.4.9 / 6.1.4
    [20260902] Unauthorized account creation via profile.saveCVE-2026-90907Moderate1.5.0 to 5.4.8, 6.0.0 to 6.1.35.4.9 / 6.1.4
    [20260915] / [20260916] InputFilter XSS filter bypassesCVE-2026-92231 / 92232Moderate1.5.0 to 5.4.8, 6.0.0 to 6.1.35.4.9 / 6.1.4
    [20260807] MFA authentication bypassCVE-2026-73337High4.0.0 to 5.4.7, 6.0.0 to 6.1.25.4.8 / 6.1.3
    [20260810] Unrestricted upload of SHTML filesCVE-2026-73373High1.0.0 to 5.4.7, 6.0.0 to 6.1.25.4.8 / 6.1.3

    Look at the “Affected” column. Several of these go back to Joomla 1.5 or 1.0, which includes every Joomla 3 site. Those sites will never get a fix.

    What changed in Joomla 6.2 for security

    Joomla 6.2 adds a security flag for extension updates: developers can mark a release with a severity from None to Critical, and flagged updates are highlighted in System → Update → Extensions and on the dashboard (Joomla 6.2 release notes, PR #48127). The flag was backported to 5.4.9. Joomla 6.2 also adds XOAuth2 for SMTP, so the site no longer has to store your mail account password (see our Joomla SMTP OAuth2 guide).

    What changed in PHP 8.6 that matters to Joomla?

    PHP 8.6 is a feature release. Headline additions are partial function application, a \Time\Duration class, an Io\Poll API, clamp(), a SortDirection enum and default values for readonly properties (release announcement). Joomla core can’t use any of that syntax until PHP 8.6 becomes Joomla’s minimum. What affects Joomla sites today is the smaller print:

    • Safer session defaults. session.use_strict_mode and session.cookie_httponly are now on, and session.cookie_samesite defaults to Lax. Joomla 6.2.0’s session code doesn’t set its own SameSite value, so the new default applies unless your php.ini sets one. Test anything that returns to your site with a cross-site POST, such as some payment gateways and single sign-on providers.
    • Session handlers must implement create_sid() and validateId(), or PHP warns now and fails in PHP 9.0.
    • Deprecated functions include spl_object_hash(), is_integer(), is_long(), is_double(), doubleval(), strcoll(), metaphone(), the mb_ereg*() family and mb_split(), mysqli_get_charset() and mysqli_stmt_init() (full list).
    • Deprecated syntax: return inside finally, returning a value from __construct() or __destruct(), a third argument to define(), and let, is or _ as names.
    • Stricter functions: many now throw ValueError for invalid flags, out-of-range values or NUL bytes, including array_filter() with a bad mode, file_exists() and is_file() with NUL bytes, and number_format() with out-of-range decimals (backward-incompatible changes).
    • Quieter failures are now visible: trim() also strips form feeds, and fclose(), file_put_contents() and copy() return false when flushing fails instead of ignoring it.

    What exactly should Joomla site owners do?

    Work through these steps in order. Steps 1 to 4 are urgent. Steps 5 and 6 are about PHP 8.6.

    Step 1: Find your exact Joomla and PHP versions

    In the Joomla administrator, open System → System Information. The System Information tab shows the PHP version, and the Joomla version is shown on the same page. Write down the full number, for example 8.4.27, not just 8.4. The last number decides whether you are patched. If you can’t log in, your hosting control panel shows the PHP version per domain.

    Step 2: Get PHP onto a November 19 build

    You are patched for PHP2Shell and the November fixes only on 8.5.13, 8.4.28, 8.3.37, 8.2.36 or 8.6.0 or newer. Linux distributions often backport fixes without changing the version number, so on a VPS also check your distribution’s security notices. On shared hosting, ask your host directly: “Is my account’s PHP built with the November 19, 2026 security fixes?” If your site runs PHP 8.1 or older, there is no official fix. Move to PHP 8.3 or newer, which for Joomla 3 and 4 also means upgrading Joomla (see below).

    Step 3: Update Joomla core

    Go to System → Update → Joomla and install 6.2.0, or 6.2.1 once it ships (scheduled for November 24). If you are staying on Joomla 5 for now, install 5.4.10, the last bug-fix release; 5.4 gets security fixes only until October 12, 2027 (Joomla 5.4.10 notes). Back up first. If an update fails, our guide to fixing Joomla update errors covers the usual causes.

    Step 4: Update every extension and watch for the security flag

    Open System → Update → Extensions, check for updates, and install them. On Joomla 6.2 and 5.4.9+, updates marked as security releases are highlighted, so do those first. Remove extensions you no longer use; an abandoned extension is a common way in.

    Step 5: Keep live sites on PHP 8.4 or 8.5 for now

    PHP 8.4 is Joomla 6’s recommended version and PHP 8.5 is fully supported. Both get security fixes until the end of 2028 and 2029. There is no security reason to rush to PHP 8.6: the November 19 releases bring 8.4 and 8.5 up to the same security level.

    Step 6: Test PHP 8.6 on a staging copy

    1. Make a full copy of the site (files and database) on a staging subdomain, protected with a password.
    2. Switch only the staging copy to PHP 8.6.
    3. In System → Global Configuration → Server, set Error Reporting to “Maximum” on staging so notices are visible. Never do this on the live site.
    4. Test the administrator login (including two-factor), front-end login, forms, search, cart and checkout, payment returns and any single sign-on.
    5. Check the PHP error log and Joomla’s log folder, and note each warning’s file path. Paths under an extension’s folder tell you which developer to contact.
    6. Move the live site only after a Joomla release states PHP 8.6 support and your key extensions have done the same.

    On the live site, keep Error Reporting at “System Default” or “None” and make sure your host has display_errors off. That single setting is what turns harmless deprecation notices into a broken login.

    What do Joomla extension developers need to do?

    Most PHP 8.6 work is small, mechanical changes. The examples below come straight from PHP 8.6’s deprecation list, and the first two are code Joomla 6.2.0 itself ships. Keep extension code compatible with PHP 8.3, Joomla 6’s minimum: don’t use PHP 8.6-only syntax such as partial application or readonly defaults until Joomla raises its minimum.

    1. Replace spl_object_hash() with spl_object_id()

    // Before: Joomla 6.2.0, libraries/src/Plugin/PluginHelper.php
    $dispatcherHash = spl_object_hash($dispatcher);
    
    // After: same uniqueness, an int instead of a string, no PHP 8.6 notice
    $dispatcherId = spl_object_id($dispatcher);

    If the value is used as an array key or concatenated into a cache key, cast it with (string) where a string is expected. This is the change proposed for core in PR #48520.

    2. Drop the old type-check aliases

    // Before (deprecated in PHP 8.6)
    if (\is_integer($pk)) { /* ... */ }
    $price = doubleval($input);
    if (is_long($n) || is_double($x)) { /* ... */ }
    
    // After
    if (\is_int($pk)) { /* ... */ }
    $price = floatval($input);
    if (is_int($n) || is_float($x)) { /* ... */ }

    3. Give custom session handlers create_sid() and validateId()

    If your extension ships its own session storage, add both methods now. PHP 9.0 will make them part of SessionHandlerInterface.

    final class MySessionHandler implements
        \SessionHandlerInterface,
        \SessionIdInterface,
        \SessionUpdateTimestampHandlerInterface
    {
        // open(), close(), read(), write(), destroy(), gc() as before
    
        public function create_sid(): string
        {
            return bin2hex(random_bytes(16)); // 32-char ID from a CSPRNG
        }
    
        public function validateId(string $id): bool
        {
            // Return true only if this ID already exists in your storage.
            return $this->exists($id); // your own storage lookup
        }
    
        public function updateTimestamp(string $id, string $data): bool
        {
            return $this->touch($id); // refresh the stored timestamp
        }
    }

    4. Stop returning from finally blocks

    // Before: deprecated, and it silently swallows the exception
    try {
        $result = $model->save($data);
    } finally {
        return $result ?? false;
    }
    
    // After: cleanup in finally, return after it
    try {
        $result = $model->save($data);
    } finally {
        $this->releaseLock();
    }
    return $result;

    5. Move from mb_ereg functions to PCRE with the u modifier

    // Before (deprecated; Oniguruma is no longer maintained)
    $slug  = mb_ereg_replace('[^\p{L}\p{N}]+', '-', $title);
    $parts = mb_split('\s+', $text);
    
    // After
    $slug  = preg_replace('/[^\p{L}\p{N}]+/u', '-', $title);
    $parts = preg_split('/\s+/u', $text);

    6. Convert objects before array-only functions

    // Before (deprecated: passing an object where an array is expected)
    $query = http_build_query($filterObject);
    array_walk($registryObject, $callback);
    
    // After
    $query = http_build_query(get_object_vars($filterObject));
    $data  = get_object_vars($registryObject);
    array_walk($data, $callback);

    7. Replace other deprecated calls

    // strcoll() / SORT_LOCALE_STRING  ->  intl Collator
    $collator = new \Collator('en_US');
    $cmp = $collator->compare($a, $b);
    
    // mysqli_stmt_init() + prepare()  ->  prepare() in one step
    $stmt = $mysqli->prepare('SELECT id FROM #__my_table WHERE alias = ?');
    
    // spl_classes()  ->  Reflection
    $classes = (new \ReflectionExtension('spl'))->getClassNames();
    
    // Constructors must not return values
    public function __construct(private DatabaseInterface $db) {} // no "return $this;"

    8. Find everything in one pass

    Run this from your extension’s root folder to list the deprecated calls covered above:

    grep -rnE --include='*.php' \
      'spl_object_hash\(|\bis_integer\(|\bis_long\(|\bis_double\(|\bdoubleval\(|mb_ereg|mb_split\(|strcoll\(|SORT_LOCALE_STRING|spl_classes\(|metaphone\(|stmt_init\(|get_charset\(|implements[^{]*SessionHandlerInterface' .

    Then run your test suite on PHP 8.6 with error_reporting=E_ALL and display_errors=1, and add 8.6 to your CI matrix next to 8.3, 8.4 and 8.5. Static grep can’t find the new ValueError throws or the session cookie changes, so click through the extension’s real workflows too.

    9. Flag your security releases

    When you ship a security fix, add the new tag to that version’s entry in your update XML so Joomla 6.2 and 5.4.9+ highlight it:

    <update>
        <name>My Extension</name>
        <element>com_myextension</element>
        <type>component</type>
        <version>2.4.1</version>
        <security>3</security> <!-- 0 None, 1 Low, 2 Medium, 3 High, 4 Critical -->
        <!-- downloads, targetplatform, etc. as usual -->
    </update>

    If you’d rather hand the porting work to someone who does it daily, our Joomla development team, which maintains 125 Joomla extensions, can audit and update custom extensions for PHP 8.6 and Joomla 6.

    Still on Joomla 3 or Joomla 4? Upgrade now

    Joomla upgrade path from 3.10 to 4.4, 5.4 and 6.2 with supported PHP ranges, plus a four-step action checklist

    This is where the risk is concentrated. Joomla 3.10 is certified for PHP 8.0 at most (Joomla manual), and Joomla 4.4 lists PHP 8.2 as recommended. Every PHP branch that got the PHP2Shell fix is 8.2 or newer, and PHP 8.2 itself loses support on December 31, 2026. Joomla 3 and 4 also get no fixes for the Joomla core flaws above, several of which reach all the way back to Joomla 1.5.

    • Staying on Joomla 3 or 4 means either an end-of-life PHP with no official PHP2Shell fix, or a newer PHP that the old Joomla was never built for, which usually means white screens and 500 errors.
    • Joomla 6.2 runs on PHP 8.3 to 8.5 today, gets security fixes until October 16, 2029, and will be the version that gains PHP 8.6 support.
    • The path is 3.10 → 4.4 → 5.4 → 6.2. You can’t skip a major version. Templates and extensions are usually the deciding factor, not core.

    Our Joomla 3 to 6 upgrade guide walks through each hop, the free Joomla 6 compatibility check shows which extensions are ready, and common Joomla upgrade issues covers the errors people hit most. If you want it done for you, with the site tested on a patched PHP before go-live, that is exactly what our Joomla upgrade service covers.

    What is the new course of action? Key dates

    DateWhat happensWhat you do
    NowPHP 8.2.36 / 8.3.37 / 8.4.28 / 8.5.13 and Joomla 6.2.0 / 5.4.10 are the safe buildsPatch PHP, update Joomla and extensions
    Nov 24, 2026Joomla 6.2.1 and 5.4.11 scheduled; Joomla 6.3.0 Alpha 1Install 6.2.1 / 5.4.11 after a backup
    Dec 31, 2026PHP 8.2 security support ends; PHP 8.4 moves to security-onlyMove any PHP 8.2 site to 8.4 or 8.5
    Apr 13, 2027Joomla 6.3.0 scheduled; the core spl_object_hash() fix is labeled 6.3Recheck PHP 8.6 support in the release notes
    Oct 12, 2027Joomla 5 security support endsBe on Joomla 6 before this date
    Dec 31, 2027PHP 8.3 security support ends (Joomla 6’s minimum)Run Joomla 6 on PHP 8.4 or newer

    Dates are from the Joomla roadmap (last updated November 17, 2026) and php.net. Joomla notes its schedule can change.

    Our recommendation for the next few months: run Joomla 6.2 on a fully patched PHP 8.4 or 8.5, subscribe to the Joomla Security Centre feed and php.net news, and move to PHP 8.6 in 2027 once a Joomla 6.x release and your extensions confirm support. Developers should fix PHP 8.6 deprecations now, while they are only notices.

    Frequently asked questions

    Is Joomla 6.2 compatible with PHP 8.6?

    Not officially. Joomla 6.2 supports PHP 8.3 to 8.5 and recommends 8.4. On PHP 8.6 it shows deprecation notices and session warnings, and with error display on, the admin login can fail. Use PHP 8.6 on staging only until a Joomla release announces support.

    Which PHP version should I use for Joomla right now?

    PHP 8.4 (8.4.28 or newer) for Joomla 6, or PHP 8.5 (8.5.13 or newer). PHP 8.3.37 works but its security support ends December 31, 2027. Joomla 5.4 can also use 8.3, 8.4 or 8.5.

    Does updating Joomla fix PHP2Shell?

    No. PHP2Shell is a flaw in PHP itself, so only a fixed PHP build closes it: 8.2.35, 8.3.36, 8.4.27, 8.5.12 or newer, and ideally the November 19 releases. You still need to update Joomla for its own fixes.

    Is PHP 8.6 more secure than PHP 8.5?

    Not in a way that matters today. PHP 8.6.0 and 8.5.13 carry the same November 19 security fixes. PHP 8.6 adds safer session defaults, but a patched 8.4 or 8.5 is just as safe to run.

    Can Joomla 3 run on a patched PHP version?

    Not in a supported way. Joomla 3.10 is certified up to PHP 8.0, which gets no official fixes, and Joomla 3 itself has had no security updates since 2023. The lasting fix is upgrading to Joomla 6.2.

    Will Joomla 5.4 get PHP 8.6 support?

    Joomla hasn’t said. Joomla 5.4 is in security-only mode until October 12, 2027, so new PHP support isn’t guaranteed. Plan the move to Joomla 6 instead.

    How do I know if an extension works on PHP 8.6?

    Check the developer’s changelog or the Joomla Extensions Directory for a PHP 8.6 statement, then test it on a PHP 8.6 staging copy with error reporting at Maximum. Warnings naming the extension’s folder point to code that needs updating.

    What is the Joomla security flag for updates?

    A Joomla 6.2 feature, backported to 5.4.9, that lets developers mark an update as a security release with a severity from None to Critical. Flagged updates are highlighted in the update manager and on the dashboard.

    Sources

  • Joomla Cache Not Clearing Properly

    Joomla Cache Not Clearing Properly

    If Joomla still serves the same HTML after System → Maintenance → Clear Cache, you did not fail to click the button. The File folders are not writable, the Cache Handler is Redis, Memcached, or APCu (so emptying cache/ does nothing), or the System – Page Cache plugin (and anything in front of it) is still holding a copy. Clear Cache and Clear Expired Cache are different jobs. This article is the broom. If the broom works but guests still see yesterday for 15 minutes, that is Cache Time and extra layers: Joomla cache showing old content.

    On Joomla 4, 5, and 6 the UI is System → Maintenance → Clear Cache and Clear Expired Cache. Both are com_cache. Settings are System → Global Configuration → System → Cache Settings: System Cache (OFF / Conservative / Progressive), Cache Handler, Cache Time, optional Path to Cache Folder. Official overview: Cache. Programmer notes: caching views and modules. File storage default: cache/ and administrator/cache/ (the programmer manual also notes administrator/cache as a default location in that document; Global Configuration Path to Cache Folder overrides when set).

    CLI (same component, no browser): php cli/joomla.php cache:clean and php cli/joomla.php cache:clean expired. Official examples: Using the CLI and Purge Expired Cache.

    Take a backup before you chmod a live cache/ tree or switch handlers. Try handler changes on staging.

    Four cache layers compared: Clear Cache removes all groups in the current Cache Handler, Clear Expired Cache removes only items past Cache Time, the System - Page Cache plugin can still serve old HTML to guests, and a CDN or reverse proxy keeps its own copy until purged there

    Delete All on File cache cannot empty Redis. A still-enabled Page Cache plugin will refill guest HTML on the next hit.

    What you will learn

    • Clear Cache vs Clear Expired Cache vs turning the plugin off
    • Why cache/ permissions block both write and delete
    • What happens when Cache Handler is Redis or Memcached
    • Why Page Cache “comes back” after a successful clear
    • How to confirm which handler Joomla is actually using
    • When FTP-deleting files is safe (File handler only)

    Clear vs expired vs plugin vs CDN

    Action Removes When it looks like “not clearing”
    Clear Cache → Delete All All groups in this handler Handler is Redis but you emptied cache/ in FTP
    Clear Cache → one group That group only You cleared com_content while Page Cache still has the URL
    Clear Expired Cache Only items past Cache Time You expected instant publish. Unexpired items should remain
    Disable System – Page Cache Stops new full-page snapshots You cleared views but the plugin still serves the old page
    CDN purge Edge copies Joomla already cleared, Cloudflare did not

    Expired items are not deleted the instant they expire. They sit until purge, full clear, or overwrite. That is why a huge cache/ folder can coexist with “I already clicked clear expired.”

    Step 1: Confirm the Cache Handler in Global Configuration

    System → Global Configuration → System → Cache Settings → Cache Handler.

    Handler Where the copy lives Clear Cache in admin Deleting cache/*.php in FTP
    File cache/ and administrator/cache/ (or custom path) Yes, if PHP can write those dirs Same store. Last resort if admin clear fails
    APCu PHP shared memory on this node Yes, if APCu is working No effect
    Memcached Memcached server Yes, if Joomla can talk to it No effect
    Redis Redis server Yes, if Joomla can talk to it No effect

    If the dropdown says Redis and you “cleared” by deleting files, you did not clear Joomla’s cache. You cleared an unused directory. Use the admin button or cache:clean, and confirm Redis is up (PING → PONG on the server if you have CLI). A down Redis can also mean Joomla cannot store or delete.

    Memcached in Joomla has historically been labelled experimental in some Global Configuration UIs. If you did not set it up on purpose, do not switch to it on production to “fix” clear. Stay on File unless the host provided Redis/Memcached and you tested on staging.

    On a cluster, File and APCu are per node. Clearing node A leaves node B’s copy. Shared Redis or Memcached is the design for that. Official programmer cache docs call this out for File/APCu vs shared handlers.

    Step 2: Fix permissions on cache/ (File handler)

    PHP must create, overwrite, and delete files in the cache path. If the folder is owned by another user, mode 555, or immutable, Clear Cache appears to run and the next request rebuilds or fails to delete. Symptoms:

    • Clear Cache lists groups but sizes never drop
    • Site errors about unable to write cache
    • FTP shows old files still there after Delete All

    Typical approach (host-specific: follow their PHP user, not a random 777 blog post):

    1. Backup.
    2. On staging, compare owner of cache/ with owner of a file PHP just wrote (a new article image upload, or configuration.php after a Global Configuration save).
    3. Restore writable directories (often 755) and files PHP should replace. Do not chmod the whole Joomla root to world-writable.
    4. Click Delete All again. Confirm files disappear.

    If Path to Cache Folder is set to a custom path in Global Configuration, you are fixing that path, not necessarily ./cache/.

    administrator/cache/ is a second tree. Admin-side cache groups live there. Clear Cache should cover both when the handler is File. If only one tree is writable, you get “half cleared” behaviour.

    Step 3: Use Maintenance Clear Cache, not a random extension screen

    People click System and miss Maintenance. They empty a template “compile” folder, or a page-builder cache, or Cloudflare, and say “Joomla clear does nothing.”

    The Joomla broom is:

    1. System → Maintenance → Clear Cache → Delete All (or selected groups).
    2. If you only wanted garbage collection: Clear Expired Cache.
    3. Confirm Cache Handler again. The Maintenance screen may show a Storage column (File vs the memory handler).

    There is no separate “Maintenance cache” vs “System cache” engine. Maintenance is the com_cache UI. Global Configuration is the policy.

    CLI from the site root (SSH), after backup, on staging first if you are unsure:

    • php cli/joomla.php cache:clean
    • php cli/joomla.php cache:clean expired

    If CLI clears Redis but the web UI does not, the web PHP user cannot reach Redis (socket permissions, wrong host, different configuration.php). Align the handler settings; do not run two configuration.php copies.

    Step 4: Page Cache plugin still on (and still winning)

    You can Delete All view cache and still lose as a guest because System – Page Cache stores a full HTML page and will recreate it on the next anonymous hit. That is correct plugin behaviour, not a broken delete.

    Flow of a guest request: the System - Page Cache plugin sends its stored HTML before Joomla rebuilds the page, so edits only show after that stored copy is cleared

    If the old page returns after a clear:

    1. Confirm you tested logged out. Logged-in users skip Page Cache, so an editor thinks “it cleared” while guests still get the snapshot until you actually deleted the page group and they miss CDN.
    2. Clear Cache again, then immediately disable System – Page Cache on staging and retest guests. If guests are fresh only when the plugin is off, the plugin was the remaining store (or it refilled from a still-stale inner cache: clear inner first, then plugin).
    3. Check Use Browser Caching on the plugin. That pushes staleness into the browser. Joomla Clear Cache will not evict Chrome’s disk cache. Hard refresh is required.

    If you need Page Cache for speed, leave it on, exclude volatile menu items, and treat Clear Cache as a deploy step. Do not leave it on, refuse to clear it, and call Joomla broken.

    Cloudflare in front: Joomla can clear Redis and still lose to the edge. Purge Cloudflare. That is a layer issue, covered in the old content post. Here the tell is: origin curl headers already show new HTML while the browser on the orange-cloud hostname shows old.

    Step 5: Prove the next write lands in the same store

    After a successful clear:

    • File: new files appear under cache/ on the next guest hit (if System Cache or Page Cache is on). Empty forever means nothing is storing (cache OFF, plugin off, or unwritable).
    • Redis: cache/ may stay empty. That is success. Use Redis CLI or the host panel to see keys if you must.
    • Progressive vs Conservative does not change whether clear works. It changes what gets stored next. Wrong module after a good clear is Progressive behaviour, not a stuck disk.

    If you recently moved hosts, $cache_handler in configuration.php may still say redis while this server has no Redis. Joomla then cannot clear what it cannot connect to. Set Handler back to File on staging, save, clear, retest. Do not edit core to force a handler.

    Five checks in order: confirm the Cache Handler, fix cache/ folder permissions for the File handler, run Clear Cache in System → Maintenance, check the System - Page Cache plugin, and prove the next write lands in the same store

    Handler first. Then cache/ permissions. Then Clear vs Expired. Then the Page Cache plugin. Then other nodes and the CDN.

    Key takeaways

    1. Clear Cache deletes the current handler’s groups. FTP on cache/ only matches File.
    2. Clear Expired Cache is supposed to leave unexpired items. That is not a bug.
    3. Unwritable cache/ or administrator/cache/ makes delete and write fail. Fix ownership, not 777 on the whole site.
    4. Redis/Memcached/APCu ignore file deletes. Use admin or cache:clean, and a reachable server.
    5. Clusters: File clear is per node unless you use a shared handler.
    6. System – Page Cache will refill guest HTML. Disable it on staging to prove the layer. Use Browser Caching is a browser problem.
    7. Backup first. Switch handlers on staging. Keep old content layers in mind when origin is already new.

    Related Joomla troubleshooting

    Frequently asked questions

    Why is Joomla cache not clearing when I click Delete All?

    Either PHP cannot delete in the File path, or Cache Handler is not File (Redis, Memcached, APCu), or you cleared Joomla while Page Cache or Cloudflare still had a copy. Check the handler dropdown before you chmod anything.

    What is the difference between Clear Cache and Clear Expired Cache?

    Clear Cache removes groups now (fresh and expired). Clear Expired Cache removes only items past Cache Time. Use Clear Cache when you need the new article immediately.

    Can I delete the cache folder in FTP?

    If Handler is File, deleting the contents of cache/ and administrator/cache/ is the same class of action as Delete All (do not delete the folders if Joomla expects them). If Handler is Redis, FTP does nothing useful. Backup first. Prefer the Maintenance screen.

    Does Redis need a separate clear in Joomla?

    Joomla Clear Cache should flush through the Redis handler when PHP can connect. If the web UI cannot reach Redis, files will not help. Fix host, port, socket, and the Cache Handler fields. Test on staging.

    Why does old HTML return right after a successful clear?

    The next guest request rebuilds Page Cache from still-stale inner data, or the plugin served a copy you did not drop, or the CDN never purged. Disable Page Cache on staging to isolate. Then see the old-content article for guest vs login.

    Where are Joomla 4, 5, and 6 cache settings?

    System → Global Configuration → System → Cache Settings. The broom is System → Maintenance → Clear Cache. The plugin is System → Manage → Plugins → System – Page Cache.

    Is 777 on cache/ the fix?

    No. Match the PHP user the host documents. World-writable cache is a security hole. Staging first if you are changing modes at all.

    Conclusion

    When Clear Cache “does nothing,” believe the handler and the filesystem before you believe Joomla is haunted. File needs a writable cache/. Redis needs a live Redis. Page Cache and Cloudflare are allowed to look like a failed clear if you only emptied the wrong store. Once the broom works, put Conservative cache and Page Cache back on using speed up Joomla, and purge layers on publish.

    If permissions and Redis are a mess on production, Joomla support and maintenance is cheaper than chmod roulette.

  • Joomla Cache Showing Old Content

    Joomla Cache Showing Old Content

    If you published in Joomla and still see the old page, you are looking at a cache layer, not a failed save. The copy can sit in Conservative or Progressive view/module cache, in the System – Page Cache plugin (guests only), in Cloudflare or another CDN, or in the browser. Logged-in users and guests often see different HTML. Clear the layer that actually served the response. This article is “stale content.” If the Clear Cache button does not change storage at all, use Joomla cache not clearing properly.

    Joomla 4, 5, and 6 expose cache under System → Global Configuration → System (Cache Settings): OFF, ON Conservative caching, ON Progressive caching, plus Cache Handler and Cache Time. Whole-page HTML is the System – Page Cache plugin, documented separately in Joomla Cache. Programmer view of the three mechanisms: Caching components and modules. Page Cache serves logged-out visitors. Logged-in requests rebuild. That single fact explains “I see the new article, my boss does not.”

    Cloudflare (and Varnish, LiteSpeed, nginx reverse proxy) sit in front of Joomla. Joomla’s Clear Cache cannot purge them. Official Cloudflare purge: Purge cache.

    Stale HTML can live in Joomla, Page Cache, Cloudflare, or the browser

    Four layers. Guests hit Page Cache and CDNs. Logged-in users skip Page Cache. Progressive cache is the usual “wrong module” layer.

    What you will learn

    • Which Global Configuration cache mode you are on (and why Progressive looks “stuck”)
    • How Page Cache differs from Conservative caching
    • Why guests and logged-in users disagree
    • How browser cache and “Use Browser Caching” hide a good origin
    • How to purge Cloudflare without guessing
    • When stale content is working as designed (Cache Time still valid)

    The layers, in the order you should blame them

    Layer Who it hits Where to clear
    Browser That one person Hard refresh, private window. Check plugin Use Browser Caching
    Cloudflare / CDN / reverse proxy Everyone at the edge CDN purge or development mode. Not Joomla Clear Cache
    System – Page Cache plugin Guests only Clear Cache (page group) plus disable or exclude if it keeps winning
    Conservative system cache Views/modules per Joomla’s cache IDs (includes access levels) System → Maintenance → Clear Cache
    Progressive system cache More aggressive module reuse Switch to Conservative on staging, then clear
    File vs Redis/Memcached/APCu Wherever Cache Handler points Clearing files does nothing if the handler is Redis. See the sister article

    Official plugin note: Page Cache keeps serving until Cache Time in Global Configuration expires, unless you delete that cache. Default Cache Time in the Cache tutorial is 15 minutes.

    Step 1: Prove it is cache, not a second page

    Confirm you edited the article that the URL actually loads (right menu item, right language, right category blog vs single article). Then:

    1. Open the URL in a private window, logged out.
    2. Open the same URL logged in.
    3. Compare.
    Logged out Logged in Likely layer
    Old New Page Cache and/or CDN. Guest HTML is frozen
    Old Old Conservative/Progressive, CDN, or browser. Or you are not hitting the article you saved
    New Old Unusual. Different menu/ACL, or a personalised module cache. Check Progressive and per-module caching

    If a private window logged out is new and your normal browser is old, it is browser cache. Hard refresh. If the Page Cache plugin has Use Browser Caching enabled, the visitor’s browser is allowed to keep the page until headers expire. Joomla cannot remotely smash that copy. Leave Use Browser Caching off unless you accept that.

    Step 2: Read System Cache: Conservative vs Progressive

    System → Global Configuration → System → Cache Settings.

    OFF: Joomla is not keeping view/module cache. If you still see old HTML, it is Page Cache, CDN, browser, or a proxy. Global OFF does not disable Cloudflare.

    ON – Conservative caching: Views and modules cache with context (pages and access levels). Modules may set Advanced → Caching to Use Global or No caching. Official Cache doc: enable Conservative, then set modules you want cached to Use Global.

    ON – Progressive caching: Official docs: turn it on in the same System Cache dropdown. It is more aggressive. Module-level No caching is not a reliable guest escape hatch under Progressive (documented across Joomla cache explainers and the programmer manual’s progressive vs conservative split). Symptom: a module from another page, or a module that should have updated. Fix: set System Cache to Conservative on staging, Clear Cache, retest logged out.

    Do not jump to Progressive to “fix stale.” Progressive makes more cache, not less.

    Cache Handler File stores under cache/ (site) and administrator/cache/ (admin). Redis/Memcached/APCu store in memory. The dropdown is the source of truth, not the folder you happened to empty in FTP.

    Step 3: Check the System – Page Cache plugin

    System → Manage → Plugins → System – Page Cache.

    Enabled means guests can receive a full HTML snapshot of the URL. That snapshot includes component and modules. It is supposed to be stale up to Cache Time. After you publish:

    1. System → Maintenance → Clear Cache → Delete All (or the page cache group if you can identify it).
    2. Reload logged out.

    If it is immediately old again, something in front (CDN) re-cached, or Cache Time is so short you are confused with a different bug. If it never updates until you disable the plugin, the plugin is the layer. Use Excluded Menu Items / Exclude URLs for pages that must always be live (login, contact, cart), as the Cache documentation’s page-cache section implies by design: a full page snapshot is the least flexible option.

    Page Cache does not apply the way people think for logged-in users. Do not use a super-admin window as proof that guests are fresh.

    Step 4: Purge Cloudflare (and any other CDN) on purpose

    If DNS is proxied through Cloudflare, you have at least two caches. Joomla Clear Cache is not a Cloudflare API call.

    In Cloudflare: purge that URL, purge everything (heavier), or enable Development Mode while you test. Docs: Purge cache. Then retest logged out.

    Other stacks (LiteSpeed cache plugin, Varnish, nginx proxy_cache) need their own purge. If you do not control the CDN, ask the host which cache sits in front.

    Page rules that “cache everything” on HTML will fight Joomla. Bypass /administrator/ always. Bypass or respect origin headers for HTML if you need instant publishes.

    Step 5: Clear Joomla cache the official way, then retest guests

    System → Maintenance → Clear Cache deletes groups (or Delete All). Clear Expired Cache only drops items past Cache Time. Expired files can sit on disk until purge. If you need the new article now, use Clear Cache, not only expired.

    After a template or override change, Delete All. After a routine article save, core often fires cache-clean events, but Page Cache and CDNs still need the steps above.

    Retest:

    1. Private window, guest: must match the editor.
    2. Logged-in: already skipped Page Cache.
    3. Phone on cellular: often a different CDN POP or a ruthless browser cache.

    If Clear Cache reports success but Redis still serves old HTML, you did not fail to publish. The handler was not File. That failure mode is cache not clearing.

    Speed after a correct clear: speed up Joomla. Do not disable all cache forever because one guest saw a 15-minute-old home page. That is Cache Time doing its job.

    Five stale-content checks: guest vs login, Progressive, Page Cache, CDN, browser

    Guest vs logged-in first. Then Progressive vs Conservative. Then Page Cache. Then Cloudflare. Then the browser.

    Key takeaways

    1. Stale public HTML is a layer problem. The article in the database can already be new.
    2. Page Cache is guest-only. Compare private-window guests to your logged-in editor.
    3. Conservative is the usual System Cache. Progressive is the usual wrong-module stale.
    4. Cloudflare does not listen to Joomla Clear Cache. Purge the CDN separately.
    5. Use Browser Caching on Page Cache moves staleness into the visitor’s machine.
    6. Cache Time (minutes, default 15 in core docs) means “old” can be correct until expiry.
    7. If storage never changes when you click Clear, switch to the not-clearing article.

    Frequently asked questions

    Why does my Joomla site show old content after I publish?

    A cache still holds the previous HTML. For guests that is often System – Page Cache or Cloudflare. For modules on the wrong page, Progressive caching is a frequent cause. Clear the matching layer and retest logged out.

    Do logged-in users see Joomla Page Cache?

    The System – Page Cache plugin is built to serve logged-out visitors. A logged-in Super User is a bad test for what the public sees. Use a private window without logging in.

    What is the difference between Conservative and Progressive caching?

    Both are System Cache modes in Global Configuration. Conservative respects per-module Use Global vs No caching more the way people expect. Progressive caches modules more aggressively and is a common source of stale or misplaced module output. Official options: OFF, Conservative, Progressive.

    How do I clear Joomla cache in Joomla 4, 5, and 6?

    System → Maintenance → Clear Cache, then Delete All or selected groups. Settings live under System → Global Configuration → System. Expired-only cleanup is Clear Expired Cache.

    Does Cloudflare cache Joomla HTML?

    If the zone is proxied and the page is eligible, yes. Purge in Cloudflare. Joomla’s cache/ folder is not the edge cache. See Cloudflare’s purge documentation.

    Should I turn cache off to stop old content?

    Only as a short staging test. Turning everything off makes the front end slow. Prefer Conservative, sensible Cache Time, Page Cache exclusions, and CDN purge on publish.

    Why is the home page old but the article URL is new?

    Different cache IDs and often a cached home module or Page Cache entry for /. Clear all, purge the home URL at the CDN, and check Progressive if a module is showing yesterday’s list.

    Conclusion

    Old Joomla content after a save means a layer still has the previous response. Split guest vs logged-in, then Progressive vs Conservative, then Page Cache, then Cloudflare, then the browser. Clear that layer. Keep cache on for speed once publish-and-purge is a habit. The how-to for performance is speed up Joomla. The how-to when the broom itself is broken is cache not clearing.

  • Joomla Admin Dashboard Is Slow

    Joomla Admin Dashboard Is Slow

    A slow Joomla administrator is usually update-site HTTP pings, Debug System left on, a locking session handler, too many modules on the Home Dashboard, or a long chain of enabled administrator plugins. It is not the same problem as a slow public site. Atum (the default admin template) is rarely the root cause. The Home Dashboard and com_installer talk to the network. The public Page Cache plugin does not save you here, because it is for guest HTML on the site, not for /administrator/.

    Joomla 4, 5, and 6 paint the control panel with administrator modules. Sample data, backup dashboards, and extension “cpanels” add more tiles. Each tile is work. Separately, the installer update finder (com_installer / Joomla Update) contacts update sites. Dead or slow vendor URLs sit there until PHP times out. That matches what people see as “Checking extensions…” hanging on the dashboard. Core discussed this class of delay when update checks moved to AJAX on the control panel (joomla-cms discussion of update checks): expired update cache means one HTTP call per update server.

    Filesystem PHP sessions can also serialise admin clicks (exclusive lock on the session file until the request ends). That is PHP behaviour, and it shows up with multiple admin tabs. Joomla’s own tracker has pointed people at the Database session handler when Filesystem locking bites (session start / Filesystem). Test handler changes on staging after a backup.

    Administrator slowness: update pings, dashboard modules, debug, session

    Public cache will not fix /administrator/. Look at update sites, Home Dashboard modules, Debug System, and the session handler.

    What you will learn

    • Why Atum is usually innocent
    • How update sites and com_installer stall the dashboard
    • That unpublished modules and disabled plugins do not run (and what still does)
    • How Debug System makes every admin page heavier
    • How to try Database vs Filesystem sessions without guessing on production
    • How this differs from a slow Joomla front end

    Admin slow vs site slow

    Where it hurts Typical causes Not the first lever
    Home Dashboard / every admin view Update site pings, dashboard modules, debug, session locks, admin plugins System – Page Cache, Cloudflare HTML cache
    Public articles only Images, cache off, TTFB, site plugins Uninstalling administrator modules
    Both Host CPU, PHP version, Debug System Yes, disk “Install a new admin template first”

    If the public site is also slow, run the front-end diagnosis in parallel. Do not skip this article because you already turned on Conservative cache. That setting does not cache the administrator UI the way people hope.

    Step 1: Confirm it is administrator, not the whole origin

    Open a public URL logged out. If that is fast and /administrator/index.php is not, stay here. In the browser Network panel on the dashboard, watch:

    • The document TTFB for administrator/index.php
    • XHR/fetch calls to Joomla Update and installer update find (option=com_joomlaupdate, option=com_installer with task=update.find)
    • Long-pending requests to third-party hosts (vendor update XML)

    If those installer calls sit in pending for many seconds, you have an update-site problem until proven otherwise. If the document itself is slow with no update XHR, look at debug, sessions, and PHP.

    Use staging for experiments. Take a backup before you disable update sites or switch session handlers.

    Step 2: Audit update sites (com_installer), not the template

    Atum is the core administrator template. A slow dashboard on stock Atum is almost never “pick a new admin theme.” Third-party admin templates can add JS, but start with installer traffic.

    System → Install → Update Sites (Joomla 4+ System dashboard: Install → Update Sites). You will see one row per extension update server, plus Joomla core.

    What you find What to do
    URLs for extensions you uninstalled years ago Remove or disable those update sites
    A vendor domain that times out in the browser Disable that site. Contact the vendor or replace the extension
    Dozens of sites after a “template club” history Disable unused ones. Core Joomla update site stays
    Dashboard fast after they are disabled You confirmed the ping tax

    Then System → Update → Extensions (or Installer Update) and use Check for Updates once. If that screen is slow but Content → Articles is fine, the diagnosis is still update HTTP, not “Joomla admin is generally broken.”

    Installed extensions live under administrator/components/, plugins/, modules/, components/. A crowded extensions tree means more update sites if those extensions registered one. Uninstall what you do not use (backup first). Unpublishing a module does not remove its update site. Disabling a plugin stops it running. It may still have an update site until you clean Update Sites.

    Do not disable the Joomla core update site to “make admin fast.” You need core security releases.

    Step 3: Cut Home Dashboard modules (the administrator cpanel)

    The Joomla 4+ Home Dashboard is a module chrome. Extra “cpanel” tiles from backup tools, documentation, and sample data all load on that view.

    System → Manage → Administrator Modules (client: Administrator). Unpublish tiles you do not need on the Home Dashboard. Unpublished administrator modules do not render. That is the correct way to slim the cpanel.

    Do not confuse this with Site modules. Unpublishing a site footer module will not speed /administrator/.

    Sample data packs are a frequent source of extra admin modules. If you installed sample data on a real site, remove the sample dashboard modules you do not use.

    Step 4: Turn off Debug System on production

    System → Global Configuration → System: Debug System = No for live administrator work. Server tab: Error Reporting = System Default (not Maximum or Development) on production.

    Debug System Yes was the right move for a white screen. Left on, it prints query lists and debug chrome on administrator pages. That is extra work every click. It is a common “we fixed the outage and now admin is awful” leftover.

    Step 5: Test the session handler, then enabled plugins

    System → Global Configuration → System, Session section: Session Handler. Common options you will actually see: PHP / Filesystem-style, Database, and Redis when the extension and server exist. Exact labels follow your Joomla version.

    Filesystem (PHP files) can lock: one slow admin AJAX holds the session file, other tabs wait. Database is the documented alternative when that happens. Change this on staging first. Changing session handler logs people out (new store). Backup configuration.php and the database.

    If sessions are fine and update sites are clean:

    1. List enabled plugins (System → Manage → Plugins). Sort by Status.
    2. Disabled plugins do not execute. You do not need to hunt unpublished plugins for CPU.
    3. Enabled system plugins still run on administrator requests when they subscribe to those events. Temporarily disable non-core ones on staging and retest a heavy screen (Extension Manage, Module list).

    A huge plugins/ folder of disabled leftovers is disk clutter and update-site clutter. It is not per-request PHP unless something is still enabled.

    PHP version still matters. Joomla 5 wants 8.1+; Joomla 6 wants 8.3+. Admin on an undersized PHP worker pool feels like “Joomla is slow” when the origin is queued. That is hosting, same as the front end. Recipe overlap: speed up Joomla for origin capacity, upgrade if the stack is ancient.

    Five admin checks: update sites, dashboard modules, debug, session, enabled plugins

    Installer pings first. Then cpanel modules. Then debug. Then session handler. Then enabled plugins.

    Key takeaways

    1. Slow /administrator/ is not fixed by System – Page Cache or Cloudflare HTML cache.
    2. Atum is the default admin template. Update sites and dashboard modules are likelier than a template swap.
    3. com_installer / Joomla Update will wait on every live update site. Disable dead vendor URLs.
    4. Unpublished administrator modules do not render. Disabled plugins do not run. Enabled leftovers and leftover update sites still cost you.
    5. Debug System Yes belongs off on production after you finish an outage.
    6. Filesystem sessions can lock multi-tab admin. Try Database on staging. Expect a log-out.
    7. If the public site is also slow, diagnose it separately.

    Related Joomla troubleshooting

    Frequently asked questions

    Why is the Joomla admin dashboard slow when the site is fast?

    The administrator does not use guest Page Cache. The Home Dashboard loads administrator modules and often waits on update-site HTTP. The public site can be cached at the edge while /administrator/ still talks to PHP, the database, and vendor URLs.

    Do unpublished extensions still load in the administrator?

    Unpublished modules do not render. Disabled plugins do not run. Extensions that are still installed can still have Update Sites, and enabled plugins still run. Clean Update Sites and uninstall what you do not need. Do not assume unpublished equals gone.

    Is Atum making my Joomla 4, 5, or 6 admin slow?

    Usually no. Atum is core. Profile the dashboard network tab for installer XHR before you buy an admin template. A third-party admin template can add its own cost, but it is not the first check.

    How do update sites slow com_installer?

    Check for Updates requests each update server whose cache expired. One dead host can stall the dashboard or the update view until PHP gives up. Disable that row under Update Sites and retest.

    Should I enable Debug System to find admin slowness?

    Briefly, on staging, if you need query times. On production it makes every page heavier. For update-site stalls, the Network panel is the clearer tool.

    Will changing session handler to Database speed up admin?

    It can, when Filesystem session locks are the bottleneck (many tabs, long requests). It is not a universal accelerator. Test on staging. You will need to log in again.

    Does Cloudflare cache the Joomla administrator?

    You should not cache /administrator/ at the CDN. If someone did, you get stale admin HTML and odd logins, not a speed win. Bypass admin in Cloudflare page rules. Public speed is the front-end article.

    Conclusion

    Treat a slow Joomla admin as a control-panel problem: update pings, dashboard modules, debug left on, session locking, enabled plugins. Leave Atum alone until those are clean. Take a backup, use staging for session and plugin tests, and keep the core update site enabled.

    If you want someone else to keep update sites and PHP current, that is Joomla support and maintenance.

  • Why Is My Joomla Website Slow?

    Why Is My Joomla Website Slow?

    A slow Joomla front end is usually oversized images, cache left off, a high Time to First Byte (TTFB), heavy extensions, or hosting that cannot hold PHP and MySQL at the same time. Diagnose those causes here. When you know which layer is slow, follow the fix list in How to speed up a Joomla website. This article is the checklist. That article is the recipe. It is not a white-screen outage, and it is not a slow administrator (that is a different pipeline).

    TTFB is the wait before the first byte of HTML arrives. If that is already hundreds of milliseconds to seconds, compressing CSS later will not save you. If TTFB is fine and the page still crawls, look at image bytes and third-party JavaScript. Joomla cache (Conservative / Progressive, Cache Handler, System – Page Cache) sits in the middle: off means every guest pays full PHP and SQL; on means you must still watch freshness (separate posts).

    Official cache behaviour: Joomla Cache documentation and the programmer notes on caching views and modules. PHP floors: Joomla 4 / 5 / 6 technical requirements (Joomla 5.4, Joomla 6). Recommended PHP memory is at least 256MB. That is a floor, not a speed guarantee.

    Front-end slowness stacks: images, cache, TTFB, extensions, hosting

    Measure TTFB first. Then weigh image transfer. Then check whether Joomla cache and Page Cache are even on for guests.

    What you will learn

    • How to split “slow HTML” (TTFB) from “slow assets” (images, JS, CSS)
    • What “cache off” actually means in Global Configuration vs the Page Cache plugin
    • Why huge images dominate front-end time even on a tuned PHP box
    • How to spot an extension tax without guessing
    • When hosting (CPU, I/O, PHP workers, distance to DB) is the real cause
    • Which Infyways guide to open once you know the cause

    Front end vs administrator vs down

    Symptom Article
    Public pages take seconds, admin is fine This checklist, then speed up Joomla
    /administrator/ crawls, public site is acceptable Joomla admin dashboard is slow
    White screen, 500, or error page Joomla website suddenly stopped working
    Page loads fast but shows yesterday’s article Joomla cache showing old content

    Do not tune cache on production as your first experiment if you have never taken a backup. Use staging for Progressive cache and for turning Page Cache on.

    Step 1: Measure TTFB and what the browser actually downloads

    Open the public URL in a private window while logged out. Logged-in users skip the System – Page Cache plugin by design (it serves guests only). If you test while logged in, you will call the site “uncacheable” when guests would have been fine.

    In the browser Network panel:

    1. Reload with cache disabled (or hard refresh once to see uncached assets, then a second load for repeat-view).
    2. Note the document request: status, waiting (TTFB), total time.
    3. Sort by size. Note images, then JS, then CSS.
    4. Note third-party hosts (fonts, tags, chat, maps). Those are not Joomla cache.

    If the HTML document’s TTFB is already slow, stop blaming Cassiopeia’s CSS. Work the server/PHP/SQL/extension path. If TTFB is short and a 3 MB hero PNG is 80% of the waterline, that is an image problem. Joomla Media stores illustrations under images/ (not the media/ folder used for extension JS/CSS). Docs: Managing Media.

    Record three URLs: home, a heavy article, a category blog. One slow template position can hide on the home page only.

    Step 2: Check whether Joomla cache is off

    System → Global Configuration → System (Cache Settings):

    Setting What it does on the front end
    System Cache OFF No conservative/progressive view and module cache. Every guest rebuilds those pieces.
    ON – Conservative caching Views and modules can cache. Per-module Advanced tab can set Use Global or No caching. Default path for most sites.
    ON – Progressive caching More aggressive module caching. Module “No caching” does not protect guests the way people expect. Test on staging.
    Cache Handler File (default, cache/ and administrator/cache/), or APCu / Memcached / Redis when those PHP extensions and servers exist.
    Cache Time Minutes. Default in core docs is 15.

    Full page HTML is not this dropdown. That is the System – Page Cache plugin: System → Manage → Plugins, find System – Page Cache, enable it. Official Cache doc: enable it under Plugins; it keeps serving until Cache Time expires. It is the fastest layer and the least flexible. Leave it off on staging until you exclude login, cart, and forms.

    Cloudflare (or another CDN) is yet another layer in front of Joomla. Cache off in Joomla plus Cloudflare “cache everything” is a freshness problem. Cache off in Joomla plus Cloudflare bypass is a speed problem. Do not mix the two diagnoses.

    If System Cache is OFF and Page Cache is disabled, you have a cause. The recipe to turn them on safely is in speed up Joomla, not here. If they are ON and the site is still slow, cache was not the bottleneck. Keep going.

    Step 3: Weigh images and media

    Front-end slowness is often bytes, not PHP. Check:

    • Full-width photos uploaded at camera resolution (several megabytes each)
    • PNG used where JPEG or WebP would do for photographs
    • Slideshows that load every slide up front
    • Background images in the template CSS pointing at huge files
    • Missing width/height causing layout delay (Core Web Vitals), which is not TTFB but feels “slow”

    Joomla 4+ can resize on insert in Media, but it will not shrink files you pasted as raw URLs in a custom HTML module. Template folders after a switch can also leave you loading two image trees. Broken images are a different article: Joomla images not loading. Here the files load. They are just too big.

    Do not invent a compression ratio. Look at the Network size column. If one image is larger than the HTML, CSS, and JS combined, that is the first front-end fix in the speed-up guide.

    Step 4: Count the extension tax

    Every enabled plugin runs on the request types it is subscribed to. Unpublished modules do not render. Disabled plugins (enabled = 0) do not run. Installed-and-forgotten enabled plugins still run. That is the usual surprise.

    On staging (backup first):

    1. Note the TTFB of a logged-out URL.
    2. Temporarily disable non-core system and content plugins you can name (analytics duplicates, old SEF, unused security scanners, leftover editors).
    3. Measure again.

    If TTFB drops, you found a class of cause. Re-enable one by one. Do not disable core plugins as a bundle. Do not do this fishing trip on production.

    Other extension tells:

    • A template that loads many extra JS libraries on every page
    • Chat, heatmap, and A/B snippets in index.php or Custom HTML
    • A page builder adding a large CSS/JS payload to articles that are “just text”

    Core edits to “make it faster” are how sites get stuck. Keep changes in a child template and non-core customisation.

    Step 5: Ask whether hosting can run this PHP and this database

    Hosting is the rest of TTFB when cache is on, images are reasonable, and plugins are few:

    • PHP workers exhausted (queueing)
    • Slow disk for File cache and sessions
    • Database on another host with high latency
    • PHP below the version Joomla recommends (old PHP can be slower and unsupported)
    • Shared neighbours saturating CPU
    • Geographic distance (TTFB includes network)

    Joomla 5 wants PHP 8.1+ (8.3 recommended). Joomla 6 wants PHP 8.3+ (8.4 recommended). Staying on an ancient PHP “because it works” is both a security and a performance dead end. Upgrade path: Joomla upgrade.

    Debug System Yes on production adds query lists and overhead to every page, public and admin. If someone left it on after a white-screen incident, turn it off. Error Reporting Maximum belongs off too.

    Cloudflare can hide origin TTFB for cached HTML (you see the edge). Test with a cache bypass or Cache-Control that misses, or you will think the origin is fast when only the CDN is.

    Five front-end checks: TTFB, cache, images, extensions, hosting

    Logged-out private window. Then TTFB, cache settings, image bytes, enabled plugins, origin hosting.

    After you know the cause

    Open How to speed up a Joomla website and apply the matching section. Do not turn on Progressive caching and Page Cache in the same hour on production without staging. If stale HTML appears afterward, that is cache showing old content. If Clear Cache does not change files, that is cache not clearing.

    Ongoing care (PHP, updates, not leaving debug on): Joomla support and maintenance.

    Key takeaways

    1. Split TTFB (HTML generation) from asset weight (images, JS). They are different jobs.
    2. Test logged out. System – Page Cache does not serve logged-in users.
    3. System Cache OFF plus Page Cache disabled is a real, common cause. Confirm it in Global Configuration and Plugins.
    4. Conservative vs Progressive vs Page Cache vs Cloudflare are different layers. Only one of them may be your bottleneck.
    5. Enabled plugins and bloated media dominate many “Joomla is slow” tickets. Disabled plugins are not the tax. Enabled leftovers are.
    6. Hosting and PHP version set the floor. Cache cannot fix a saturated origin.
    7. Use this article to name the cause. Use the speed-up guide to apply the fix.

    Frequently asked questions

    Why is my Joomla website slow on the front end?

    Most often: large images, Joomla cache and Page Cache left off, high TTFB from PHP/SQL/extensions, or hosting. Measure TTFB and transfer size in a logged-out private window before you change settings.

    Does turning on Joomla cache always make the site fast?

    No. System Cache (Conservative or Progressive) caches views and modules. Whole-page speed for guests needs the System – Page Cache plugin as well, and it still will not shrink a 4 MB photo. Official Cache docs describe those as separate switches.

    Should I test speed while logged into Joomla?

    Not if you care about visitors. Page Cache is guest-only. Logged-in TTFB is a different number. Use a private window signed out for the public diagnosis.

    Is Progressive caching faster than Conservative?

    It is more aggressive on modules. It is also a common source of the wrong module on the wrong page. Start with Conservative on staging. Progressive is not the first diagnosis step.

    Can Cloudflare make Joomla look fast while origin is slow?

    Yes. Edge cache serves old HTML quickly. Bypass cache or check origin logs when you need the real TTFB. Cloudflare will not fix admin, and it will not fix uncached HTML generation.

    Why is the site slow only on mobile?

    Sometimes the same huge images. Sometimes a mobile-only script. Sometimes a host or CDN geo path. Compare the same URL’s document TTFB and image bytes on desktop vs mobile throttling. Do not assume Joomla “detects mobile” unless you enabled Platform Specific Caching.

    Where do I go for the actual speed fixes?

    How to speed up a Joomla website. This page is causes. That page is the how-to.

    Conclusion

    A slow Joomla front end is a measurement problem first. Logged-out TTFB, image bytes, cache switches, enabled plugins, then hosting. Name the layer, then apply the speed-up recipe. Do not flatten all four into “we need Redis” before you have looked at a 3 MB PNG.

  • Joomla Website Suddenly Stopped Working

    Joomla Website Suddenly Stopped Working

    When a Joomla site suddenly stops working, treat it as a last-change problem, not a mystery. A white screen, an HTTP 500, or a red system error page almost always follows a PHP version bump, a bad .htaccess rule, an extension install, or a failed update. Turn error reporting on, read the stack (or error.php), and undo that change on a backup. This is for a site that is down. If the site loads but crawls, use the slow-site diagnosis instead.

    A page that used to render and now returns nothing is PHP dying before Joomla can print HTML. A 500 is the same class of failure with the web server covering the message. Joomla can also show its own error page when the CMS still boots: the system error page (red background) or the template error.php layout. Official recovery starts with Debug System and Error Reporting, then the stack. See the Joomla User Manual: Fatal errors and the Joomla 4 docs mirror J4.x:FatalError.

    Do this on a backup, and test destructive checks (rename .htaccess, disable plugins in the database) on staging first when you have a copy. Production is not the place to discover that mod_rewrite was the only thing keeping URLs alive.

    White screen, HTTP 500, and Joomla error.php are three faces of the same outage

    White screen means PHP failed with display_errors off. 500 is the server wrapping that failure. error.php means Joomla still booted far enough to render an error layout.

    What you will learn

    • How to tell a white screen from a 500 from a Joomla error.php page
    • Why the last change (PHP, .htaccess, extension, update) is the first clue
    • How to turn on Debug System when the administrator is dead
    • Which PHP versions Joomla 4, 5, and 6 actually require
    • How to test .htaccess without burning production
    • How to disable a bad extension from #__extensions if admin will not load
    • What to revert after the site is up

    White screen, 500, and error.php

    What you see What it usually means First move
    Blank white (or empty) page PHP fatal with display_errors off. Joomla never printed output. PHP error log, then Debug System in configuration.php
    HTTP 500 from Apache or nginx Same class of failure. The server hid the PHP message. Same, plus the vhost / host error log
    Red system error page Serious error before the site or admin template rendered Read the message. Enable debug if it is incomplete
    Template-styled error page Error in content code. Joomla used templates/{name}/error.php or templates/system/error.php Read the message and stack. Do not “fix” the crash by rewriting error.php

    Joomla’s error.php is an error layout, not a debugger. Core documents it as independent of the CMS plugin chain: no <jdoc:include />, no modules. Override path: copy templates/system/error.php into the active template. Docs: Custom error pages. If a custom error.php was edited badly, it can make a recoverable error look like a total outage. Compare it to the stock file from the same Joomla package before you chase plugins.

    If the public site is down but /administrator/ still loads, you still have Global Configuration. If both are down, you edit configuration.php over SFTP or the host file manager.

    Step 1: Take a backup and name the last change

    Before you rename files or toggle plugins, snapshot files and the database. Host backup, Akeeba, or both. Write one sentence: “The host moved us to PHP 8.3 last night,” or “We installed extension X,” or “We turned on URL rewriting,” or “We ran a Joomla update.”

    Typical last changes that take a site down:

    • Host PHP upgrade or a MultiPHP selector change
    • Joomla or extension update
    • New plugin, module, or template
    • .htaccess edit (security generator, RewriteBase, custom deny rules)
    • Disk full, inode limit, or a restored backup that missed configuration.php

    If you cannot name a change, check the host’s PHP version history and the Joomla #__extensions enabled / install dates anyway. Hosts often bump PHP without telling you. That is still a last change.

    If the site is on an old Joomla 3 stack that a host just moved to PHP 8, the fix is not a one-line patch in core. Plan a proper Joomla upgrade.

    Step 2: Confirm PHP matches this Joomla version

    Joomla will fatal on a PHP that is too old or on a jump your extensions never saw. Minimums below are from the Joomla project’s technical requirements (Joomla 4.x, 5.x, and 6.x tables). Recommended versions are what the project tests against.

    Joomla PHP minimum PHP recommended (project tables) Source
    4.x 7.2.5 8.2 Hosting setup
    5.x 8.1.0 8.3 Joomla 5.4 technical requirements
    6.x 8.3.0 8.4 Joomla 6 technical requirements

    Required PHP modules listed there include json, simplexml, dom, zlib, gd, and mysqlnd or pdo_mysql (or pdo_pgsql). Recommended memory limit is at least 256MB.

    If administrator still loads: System → Information → System Information (and the PHP Information tab). If it does not: phpinfo in a throwaway file on staging, or the host’s MultiPHP / Select PHP Version screen. Then compare to the table. A Joomla 5 site on PHP 7.4 will not boot. A Joomla 4 site whose third-party plugin is not PHP 8.3-ready will white-screen after a host bump even when core is fine.

    Do not “fix” a PHP mismatch by editing core files. Switch PHP on the host (or staging) to a version that matches both Joomla and the installed extensions. Then update or replace the extension.

    Step 3: Turn on Debug System and Maximum error reporting

    If administrator works: System → Global Configuration. System tab: Debug System = Yes. Server tab: Error Reporting = Maximum. Save. Reload the broken URL. You want a stack trace, not a prettier blank page.

    If administrator is dead, edit configuration.php in the site root. Official steps:

    1. If the file is 444 / read-only, set it to 644 so you can write.
    2. Set $debug to true and $error_reporting to 'maximum'.
    3. Save. Reload the broken URL.

    That wording is from the Fatal errors manual. After you save Global Configuration later, Joomla sets configuration.php back to read-only. That is intended.

    Read the first frame that is not core bootstrap. A path under plugins/, modules/, components/com_something (not com_content / com_users unless you overrode them), or a template html/ override is the usual culprit. The official advice if you can name the extension: disable it. If admin is down, in phpMyAdmin (or equivalent) open #__extensions, find that row, set enabled to 0. Do not disable core Joomla extensions as a fishing trip.

    Also read the PHP error log the host provides. A fatal that happens before Joomla loads configuration.php never appears in the Joomla debug console.

    When you are done, set Debug System back to No and Error Reporting back to System Default. Leaving Maximum on a public site leaks paths.

    Step 4: Test .htaccess on staging, not by deleting production

    Apache 500s after “Use URL Rewriting” or after a security .htaccess generator are common. Joomla ships htaccess.txt. Enabling rewriting is: rename htaccess.txt to .htaccess, then Global Configuration → Site → Use URL Rewriting. Official walkthrough: SEF URLs on Apache. If mod_rewrite is missing, turning rewriting on is a 500. If RewriteBase is wrong for a subdirectory install, same class of failure.

    Do not delete .htaccess on the live site to “see what happens.” Copy the site to staging, or at minimum copy .htaccess to .htaccess.bak and keep that backup off to the side.

    On staging:

    1. Confirm you have the backup copy.
    2. Rename .htaccess to .htaccess.bak (Apache then ignores it).
    3. Reload. If the site returns (often with /index.php/ in URLs), the rules were the problem.
    4. Restore stock rules from the htaccess.txt that matches this Joomla version. Do not paste a Joomla 3 file onto Joomla 5.
    5. If you use a subdirectory, set RewriteBase to that folder as the SEF docs describe.
    6. Only then turn Use URL Rewriting back on and retest.

    Extra Deny / Rewrite blocks from security tools belong in the “last change” list. Test those on staging too. A rule that forbids a PHP file you actually need is a 500, not a permissions mystery.

    nginx does not use .htaccess. If the host is nginx, a rename test proves nothing about rewrite. Use the vhost config and the host error log instead.

    Step 5: Read error.php, then disable the bad extension

    If you get a template-styled error page, open the active template’s error.php only to read what it prints. Compare with templates/system/error.php. You are looking for the exception message and file path, not a design tweak.

    Once the stack names an extension:

    • Administrator working: disable the plugin/module/component there.
    • Administrator dead: #__extensions.enabled = 0 for that row.
    • Override involved: a layout in templates/{template}/html/ can fatal after a Joomla update if the parent view changed. Rename the override folder on staging (do not delete until you know). Safe customisation belongs in a child template, not in core. See customize Joomla without editing core.

    The User Manual also points at the Forum Post Assistant (FPA), a standalone PHP script the Joomla Forum uses. Install it only while debugging, in the site root, then remove it when you clean up. It is not a substitute for a backup.

    Disk space, memory, and script timeouts are on the official cause list too. A full disk makes Joomla look “suddenly dead” after a cache or log spike. Check the host panel before you rewrite configuration.php a third time.

    Five checks when Joomla suddenly stops

    Order: last change, PHP version, debug/stack, .htaccess on staging, then disable the named extension.

    What this article is not

    This is not “why is Joomla slow.” A slow site still responds. Diagnose that in Why is my Joomla website slow and fix it with How to speed up a Joomla website. Admin-only slowness is Joomla admin dashboard is slow.

    If you cannot get a stack and cannot afford more downtime, that is a restore-from-backup moment, then a staged replay of the last change. Joomla support and maintenance is the human version of that loop.

    Key takeaways

    1. A white screen and a 500 are usually the same PHP fatal. error.php means Joomla still booted far enough to render an error layout.
    2. Name the last change first: PHP version, .htaccess, extension, or update.
    3. Match PHP to the official table for Joomla 4, 5, or 6, and to your third-party extensions.
    4. Enable Debug System and Maximum error reporting in Global Configuration, or set $debug and $error_reporting in configuration.php when admin is down.
    5. Test .htaccess by renaming a copy on staging after a backup. Restore from this Joomla version’s htaccess.txt.
    6. Disable the extension named in the stack. Use #__extensions if the administrator will not load. Do not disable core as a guess.
    7. Turn debug off when you are done. Remove FPA. Put configuration.php back to how Global Configuration saves it (read-only).

    Frequently asked questions

    Why is my Joomla site a white screen of death?

    PHP hit a fatal error and display_errors is off, so you get no HTML. Enable Debug System and Maximum error reporting, or set $debug to true and $error_reporting to 'maximum' in configuration.php, then reload and read the stack and the PHP log.

    What does an HTTP 500 mean on Joomla?

    The web server failed to complete the request. On Joomla that is commonly a PHP fatal, a .htaccess / rewrite problem, or a missing mod_rewrite after Use URL Rewriting was enabled. Check the server error log and the same debug steps as a white screen.

    How do I enable Joomla debug if I cannot log in to administrator?

    Edit configuration.php in the site root. Make it writable if it is 444, set $debug to true and $error_reporting to 'maximum', save, reload. That is the official path in the Fatal errors user manual.

    Should I delete .htaccess to fix a 500?

    No. Copy it to .htaccess.bak and test the rename on staging (or after a verified backup). If the site returns, replace rules from this version’s htaccess.txt and fix RewriteBase if Joomla lives in a subdirectory.

    Where is Joomla error.php?

    Stock file: templates/system/error.php. If the active template has its own error.php, Joomla uses that instead. It displays the error. It is not where you patch the bug. See Custom error pages.

    Can a PHP version change take Joomla down overnight?

    Yes. Hosts change MultiPHP without a Joomla update. Joomla 5 needs PHP 8.1 or newer. Joomla 6 needs PHP 8.3 or newer. An old plugin can still fatal on a newer PHP even when core is compatible.

    Do I edit core PHP to get the site back?

    No. Disable the extension, restore the backup, or roll PHP back to a compatible version. Core edits vanish on the next update or block the update. Use overrides and a child template for lasting changes.

    Conclusion

    A Joomla site that “just died” almost never died of boredom. It died of the last change. Backup, name that change, match PHP, turn the errors on, test .htaccess on staging, then disable what the stack names. When the page renders again, turn debug off and keep the backup until the next day behaves.

    If you are still on a Joomla version the host will not run, schedule the upgrade on a clone, not as a panic edit on production.

  • Joomla Extension Installed but Not Working

    Joomla Extension Installed but Not Working

    A Joomla extension is installed but not working when files exist (or a zip succeeded) and the site still has no working feature: the package is undiscovered, the row is disabled, the database schema never ran, PHP is too old or too new, a menu type was never created, or a module instance was never published. “Installed” in the installer message is not the same as enabled, assigned, and given a menu item. This is a readiness checklist, not a 500 hunt and not a two-plugin conflict hunt.

    If the administrator or site is a 500, stop: find which extension causes a 500. If two enabled add-ons fight, use extension conflict. If the zip never finished, stay in System → Install → Extensions and read the installer message. This page assumes the installer said success, or you uploaded files by SFTP, and the feature is still dead.

    Installer success message next to a disabled plugin and no menu item

    A green install is a database row and files. The feature still needs Discover or enable, schema, PHP, a menu type, and often a module you create by hand.

    What you will learn

    • The difference between Upload, Discover, and Enable
    • How to see the extension in System → Manage → Extensions
    • When System → Maintenance → Database (Update Structure) is the real fix
    • How to match PHP version to the extension’s requirements
    • One check for Behaviour – Backward Compatibility on Joomla 5 (not a full compatibility essay)
    • Why a component can install with no menu item type until you create one
    • Why a package’s module is not on the page until you create and assign it

    Official: Installing an extension, Help5.x Discover, Version update, database check.

    Installed, discovered, enabled, configured

    State What is true What you still must do
    Files on disk only You unzipped into components/ or plugins/ Discover then Install
    Installer success #__extensions row exists Enable plugins, create menu, create module
    Enabled plugin enabled = 1 Check ordering, access, and that you enabled the right plugin in a package
    Component enabled Admin menu may show it Create a menu item of that type for the site
    Module type exists You can pick it under New Module New, publish, position, assignment
    Schema out of date Files newer than SQL Maintenance → Database → Update Structure

    Most “not working” tickets are the right-hand column, not a corrupt zip.

    Step 1: Find the row in Manage Extensions

    1. System → Manage → Extensions.
    2. Search the extension name and the com_, mod_, plg_ element if you know it.
    3. Confirm Status (enabled). A lock icon means protected core. Third-party rows should be enableable.
    4. Open the details. Note type (component, module, plugin, package, library, file).

    A package installs several rows. The component can be enabled while the plugin that injects the feature is disabled. Filter by the package name and enable every non-core row the vendor documents.

    If the search is empty, the installer did not register the extension. Either the zip failed silently (host upload limit) or someone copied folders by FTP. Go to Step 2. Do not keep uploading the same zip on top without checking Discover.

    Step 2: Discover is not Enable

    Discover is for files already on the server that Joomla does not have in #__extensions. Official help: Extensions: Discover.

    Use it when:

    • The package was too large for the web uploader, so you extracted into components/com_example, administrator/components/com_example, media/com_example, and language folders as the installing guide describes.
    • A deploy process copied a git checkout of an extension into those paths.

    Then:

    1. System → Install → Discover (some sites label this under Manage → Discover).
    2. Toolbar Discover.
    3. Tick the extension. Install.

    Discover does not turn a disabled plugin on. It creates the row. Then you enable in Manage Extensions or Plugins.

    If Discover finds nothing, the files are in the wrong tree (nested extra folder, or site files only without administrator files). Fix the paths. Do not invent a second copy under tmp/ and expect Joomla to see it.

    Normal small zips should go through System → Install → Extensions (upload). Discover is the exception path.

    Step 3: Enable the plugin (packages hide this)

    System → Manage → Plugins. Search the vendor or feature name.

    Many components ship:

    • A system plugin that loads language or routing
    • A content plugin that prints a button or shortcode
    • An actionlog or privacy plugin you can leave off

    If the system plugin is disabled, the component admin screen may open and the site view stays empty. Enable it. Then check Access on any module the package added.

    Installer sample data sometimes creates an unpublished module. Published component + unpublished module = “not working” on the frontend.

    Step 4: Fix the database schema

    If the Home dashboard warns that the database is out of date, or the extension errors about a missing table or column:

    1. System → Maintenance → Database.
    2. If problems are listed, select the extension and Update Structure.

    That replays skipped SQL. It is the documented fix after a partial Joomla or extension update: Version update, database check.

    If Update Structure fails, the extension’s sql/updates files may not match the database engine, or a previous update died. Restore a backup and reinstall on staging. Do not create tables by hand unless the vendor gives you SQL.

    A component that “installed” but never ran install.sql (Discover on incomplete files, or a failed package) will 500 or show empty lists. That can look like “not working.” Check error_log if the view fatals: 500 article.

    Step 5: Match PHP version (and host extensions)

    Open System → Information → System Information (site and PHP tab). Note PHP version.

    Open the extension’s documentation for minimum PHP and maximum tested. Joomla 5 itself needs a current PHP (see technical requirements for the Joomla version you run). An add-on that last shipped for PHP 7.4 will not run on PHP 8.3.

    Also check System → Manage → Warnings and System Information for missing PHP modules (intl, gd, mbstring, zip). The installer may have succeeded while runtime needs curl for an API.

    Host “PHP selector” can differ between the site and CLI cron. A plugin that works in admin and fails on cron is often two PHP versions.

    Step 6: One Joomla 5 compatibility plugin check

    On Joomla 5, core ships Behaviour – Backward Compatibility (plg_behaviour_compat). It loads Joomla 4 class aliases so older extensions can run. Official note: Compatibility plugin.

    Check, do not redesign your stack around it:

    • System → Manage → Plugins, search Backward Compatibility or compat.
    • If a Joomla 4-era extension is installed and this plugin is disabled, enable it on a staging copy first and test. The Joomla docs warn that disabling it on production can fatal old extensions, and that you may need the database to turn it back on.
    • If you are preparing Joomla 6, this plugin must be disabled before that upgrade, and you need extensions that do not rely on it. That is an upgrade project, not this article.

    This is one checkbox in the “installed but dead” list. It is not a substitute for a vendor’s Joomla 5 build. Prefer an updated extension. Do not treat the compat plugin as a permanent architecture.

    Joomla 5.4 also installs Behaviour – Backward Compatibility 6 for the later jump. Do not disable that in a way the Joomla 6 migration guide forbids. Read Compatibility plugins (5.4 to 6) when you upgrade. For “not working today on Joomla 5,” the plg_behaviour_compat enable check is enough.

    Step 7: Create the menu item (missing menu type)

    A component can install a menu item type (Articles → Archived Articles is the core example). Your add-on is the same. Until you create Menus → your menu → New and select that type, the site has no URL.

    Symptoms:

    • Administrator component works. Frontend 404 or Home never changes.
    • You look for a module. The feature is a component view, not a module.
    • The type is missing from the New Menu Item list: the component is disabled, Discover never ran, or the XML submenu / menu section failed. Reinstall or Discover. Confirm the component is enabled in Manage Extensions.

    Create the menu item, set Access, set a template style if needed, save. Open that URL. Do not expect the installer to inject a menu item on a production menu. Many packages do not.

    If the type appears but the view is empty, you may still need to create records inside the component (a first category, a first item). That is configuration, not a failed install.

    Step 8: Create and publish the module

    Content → Site Modules → New. If the module type is in the list, the module type is installed. A type in the list is not an instance on the page.

    Packages often do not create a published module. You must:

    1. New → pick the type.
    2. Set Position to a name the template actually prints (position not showing if the slot is empty everywhere).
    3. Menu Assignment (wrong pages if it appears in the wrong place).
    4. Publish. Public access. Language All or the right language.

    If the type is not in New Module, the module file never installed (package incomplete, or you only installed the component zip). Install the full package. Discover if you dropped modules/mod_example by hand.

    Editor buttons (editors-xtd) are plugins, not modules. Enable them under Plugins. They will not appear as Site Modules.

    Language, ACL, and cache (short)

    • Install the extension’s language pack if the vendor ships one, or you will see KEY_NAMES as titles. For core string tweaks, language overrides.
    • Super User sees a module a Guest does not: Access.
    • Clear cache after enable. Page cache can hide a module you just published.

    Custom fields inside an extension are not core article fields. Core article fields have their own empty-frontend guide: custom fields not showing.

    Warnings, update sites, and a second install attempt

    System → Manage → Warnings (or Installer warnings) lists environment problems Joomla already detected: PHP version, missing modules, memory. If a warning names the same constraint the vendor lists, fix the host before you reinstall the zip. Reinstalling will not add intl.

    System → Update → Update Sites (or Manage → Update Sites): if the extension installed from a URL and later “does nothing” after you expected a patch, Rebuild the update sites, then System → Update → Extensions. An old build that “installed fine” on Joomla 5 can still be a Joomla 4 package. The update site is how you learn a Joomla 5 zip exists.

    If you install twice, Joomla may refuse or may leave the first schema in place. Prefer Uninstall (after a backup) then install the matching Joomla 5 package, over copying folders on top of a half Discover. Uninstall removes #__extensions rows. It can drop the extension’s tables. That is why the backup exists.

    A library or file package can install with no admin menu. The feature then lives inside another component. Read the vendor’s “where to click after install” once. Searching Site Modules for a library is a dead end.

    Checks: Manage row, Discover, enable, schema, PHP, menu, module instance

    Files and a green installer are the start. Enable, schema, PHP, menu type, and a published module instance are the rest.

    Key takeaways

    1. Installer success means a registry row. It does not mean enabled, schema-current, or on a menu.
    2. Discover registers FTP-copied files. Enable turns plugins on. They are different buttons.
    3. Packages hide a disabled system plugin. Search Plugins after every component install.
    4. Maintenance → Database → Update Structure when files and SQL diverged.
    5. Check PHP version and System Information warnings before you blame Joomla.
    6. On Joomla 5, confirm Behaviour – Backward Compatibility if the add-on is old. Prefer a native Joomla 5 build. This is one check, not a strategy.
    7. Components need a menu item type you create. Modules need a New instance, position, and assignment.
    8. If it 500s, leave this checklist and read the log. If it works alone and fails with a neighbour, that is a conflict.

    When a vendor package is registered but the live site still has no menu, no module, and no plugin enabled, a maintainer can finish the wiring: Joomla support and maintenance.

    Frequently asked questions

    Why is my Joomla extension installed but not working?

    The zip registered files, but a plugin is still disabled, Discover was skipped after an FTP copy, the schema is behind, PHP does not match, or you never created a menu item or module instance.

    What is the difference between Discover and Enable?

    Discover finds manifests on disk and creates #__extensions rows (then you click Install on that screen). Enable turns an existing row on. Uploading a zip uses Install Extensions, not Discover.

    Do I always get a module on the page after install?

    No. You often get a module type. You still click Site Modules → New, publish it, and assign a position and pages.

    Why is there no menu item type for my component?

    The component is disabled, not fully discovered, or you are looking at the wrong client (site vs administrator). Enable the component, run Discover if files were copied, reinstall the package, then Menus → New.

    Should I disable the Joomla 5 compatibility plugin to test?

    Only on staging, and only if you can re-enable it in the database when admin dies. For an old extension that is “not working,” try enabling the plugin first. Plan a real Joomla 5 build before Joomla 6.

    Update Structure did nothing. Now what?

    Confirm you selected the extension that listed errors. If SQL still fails, restore a backup and reinstall on staging. Do not drop random tables on production.

    Could this be a template problem?

    Yes, if it is a module in a position the template does not print, or an override that errors. Check position names and child-template overrides after the extension is enabled and assigned.

  • PHP2Shell (CVE-2026-109618/109619): How to Patch Joomla & WordPress Sites

    PHP2Shell (CVE-2026-109618/109619): How to Patch Joomla & WordPress Sites

    Last updated Nov 20, 2026. We will update this guide as hosts and Linux vendors ship fixed packages.

    Short answer: PHP2Shell is the name for two critical flaws in PHP itself, CVE-2026-109618 and CVE-2026-109619. Both are rated CVSS v4.0 9.2 and can let an attacker run code on your server without logging in. The only complete fix is to run PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12 or newer, released on 21 October 2026 (php.net advisory). Nothing in Joomla or WordPress fixes it, and no plugin or extension does either. If your site runs PHP 8.1 or older, there is no official fixed release: you need to move to PHP 8.3 or later, or get a patched package from your Linux vendor.

    The fix in five steps: 1) find the PHP version your site actually serves, 2) get it onto a fixed build, 3) confirm the fix is really running, 4) add the interim hardening if you are still waiting, 5) plan an exit if your host will not move. Each step has its own section below, with steps for cPanel, Plesk, CloudLinux, VPS servers, Joomla 4, 5 and 6.2, and WordPress.

    What is PHP2Shell, in plain English?

    PHP is the engine that runs Joomla and WordPress. Every page of your site, from the home page to the admin login, is built by PHP on your web server. PHP is installed by your hosting company, not by you and not by your CMS.

    PHP2Shell is a fault in that engine. A stranger can send your server one specially crafted web request, just like a normal visit but built to trigger the fault. The server can then run the stranger’s commands. No password is needed and no account is needed.

    Because the fault sits in PHP, it hits before Joomla or WordPress even starts. Your admin password, two-factor login, security plugin or Joomla access rules never get a say. php.net confirms there is a working attack that triggers before any application code runs on the most common Apache setup.

    An analogy: your Joomla or WordPress security is the lock on your apartment door. PHP2Shell is a broken lock on the building’s front door, and it opens the service corridor behind every apartment. A better apartment lock does not help. The building manager, your host, has to replace the front-door lock, which here means installing the fixed PHP release.

    What can happen to your site if you ignore it?

    Running commands on your server means an attacker can do roughly what your site itself can do. These are the usual results of that kind of access on any hacked site, not specific reported PHP2Shell cases:

    • Defacement. Your pages are replaced or altered with the attacker’s content.
    • Hidden malware or spam. Code is slipped into your files or database that redirects visitors, shows spam links or infects visitors’ browsers.
    • Stolen data. The site can read its own database, so customer details, orders, contact form submissions and user accounts can be copied.
    • Your server attacks others. The site is used to send spam email, host phishing pages or attack other websites, often without you noticing.
    • Google warnings and lost rankings. Google may label the site This site may be hacked in search results or show a red browser warning, and visitors and rankings drop while that lasts. See Google’s Security Issues report help.
    • Hosting suspension. Hosts commonly suspend accounts that send spam or host malware, which takes the whole site offline.
    • Cleanup cost and downtime. Removing malware, restoring backups, resetting every password and asking Google for a review takes time and money, and data that was stolen cannot be taken back.

    If you sell online, handle bookings or collect personal data, a breach can also bring legal duties to report it to customers or regulators, depending on where you and they are.

    Which PHP versions are safe, and which are not?

    Check the first two numbers of your PHP version (the branch), then the last number (the patch level). Versions are from the PHP 8 changelog, the CERT-FR alert and NVD; support dates are from php.net’s supported versions and end-of-life pages.

    Your PHP branchVulnerableFixed inBranch support (php.net)What you do
    8.58.5.11 and below8.5.12Active support to 31 Dec 2027Update to 8.5.12
    8.48.4.26 and below8.4.27Active support to 31 Dec 2026, security to 31 Dec 2028Update to 8.4.27
    8.38.3.35 and below8.3.36Security fixes only, to 31 Dec 2027Update to 8.3.36
    8.28.2.34 and below8.2.35Security fixes only, ends 31 Dec 2026Update to 8.2.35, then plan 8.3+
    8.1AllNo official releaseEnd of life since 31 Dec 2025Move to 8.3+ or use a vendor backport
    8.0, 7.x, 5.xAllNo official releaseEnd of lifeMove to a supported branch
    8.6RC3 and earlierRC4 and later, including 8.6.0Released 19 Nov 2026Update to 8.6.0; do not run release candidates in production

    PHP 8.6.0 was released on 19 November 2026 with the PHP2Shell fixes (included since RC4), and php.net also shipped security releases 8.2.36, 8.3.37, 8.4.28 and 8.5.13 that day.

    The PHP team also published minimal source-only patches for 7.4, 8.0 and 8.1 for people who compile PHP themselves. They are not releases, and a shared hosting panel cannot offer them.

    Still on Joomla 3? Why patching PHP is not an option

    This is the hardest case, and it is worth being precise about. Joomla’s official technical requirements list PHP 8.0 as the recommended version for Joomla 3.x, and no newer PHP version is listed. Joomla 3 support ended on 17 August 2023, and the extended LTS version ended on 17 February 2025, so Joomla 3 gets no more updates to make it work on newer PHP. Joomla volunteers on the official Joomla forum report that 3.10 does not work on PHP 8.2 or later and is unreliable on 8.1. Every branch that received the PHP2Shell fix is 8.2 or newer. Put those facts together and no officially supported Joomla 3 setup can run a patched PHP release.

    What about the stopgaps? Each one helps a little and costs something:

    OptionWhat it gets youWhere it falls short
    Source-only backports for 7.4, 8.0, 8.1The PHP2Shell fix for people who compile PHP themselvesNo releases and no binaries. Shared, reseller and most managed hosts cannot install them, and you take on maintaining a custom PHP build.
    Vendor or distribution backport (for example a Linux LTS package)A patched PHP 8.0 or 8.1 from a vendorOnly on servers you or your host control at the OS level, often paid, and only covers PHP. Joomla 3 itself still gets no security fixes.
    Interim php.ini settings and a WAFFewer known attack pathsphp.net says they do not make an installation safe, and WAF rules can be bypassed by direct-to-origin traffic.
    Forcing Joomla 3 onto PHP 8.2+A patched PHPUnsupported: expect white pages, 500 errors and broken extensions, which is why hosts that move clients forward often break Joomla 3 sites.

    So the risk of staying is not only PHP2Shell. It is that every future PHP or Joomla vulnerability lands on a site with no supported fix. The lasting fix is to move the site to Joomla 6.2, which requires PHP 8.3 or newer, so it runs on a branch that gets security releases until at least the end of 2027. Joomla does not allow skipping straight from 3 to 6: the path is 3.10 → 4.4 → 5.x → 6.x, and our Joomla 3 to 6 upgrade guide walks through each hop. Run the free Joomla 6 compatibility check first to see which extensions have Joomla 6 versions and which need replacing; that list is what decides how long the move takes. If you would rather have the migration done for you, that is what our Joomla upgrade service covers.

    Old WordPress on PHP 7.4 or 8.1? WordPress is gentler: current WordPress still runs on PHP 7.4 but recommends 8.3 or greater. Update WordPress core, plugins and themes first, then switch the branch as in Step 2b. Plugins abandoned by their authors are the usual blocker, so replace them before the switch.

    How do the two flaws work?

    Both flaws are about what PHP leaves behind when a web request ends badly. According to the NVD descriptions supplied by the PHP security team:

    • CVE-2026-109618: when PHP runs out of memory mid-request, some internal request memory can be left uninitialised. The cleanup step then reads it as if it were valid, and several out-of-memory tricks can turn that into remote code execution.
    • CVE-2026-109619: some global state can keep pointing at request memory after it has been freed. A later request on the same PHP worker can read that stale state before it is reset, which can also lead to remote code execution.

    php.net says the risk covers all PHP installations serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed, and is highest for mod_php, where a demonstrated exploit runs before any application code. For a Joomla or WordPress site this means your login page, security extension and file permissions are not in the way: the attack happens one layer below the CMS.

    FactDetailSource
    CVSS v4.0 score9.2 for both CVEs (vector AV:N/AC:H/AT:P/PR:N/UI:N)NVD
    Advance notice20 Oct 2026, release set for 21 Oct 14:00 UTC (7:30 PM IST)php.net
    Fixed releases8.5.12, 8.4.27, 8.3.36, 8.2.35 on 21 Oct 2026php.net
    Changelog entry“Fixed GHSA-w8hw-w9fx-j79w, GHSA-6wmf-4rv5-p3rp (Avoid state corruption via bailout)” in all four branchesPHP changelog
    NVD publication21 Oct 2026, 14:17 UTC (7:47 PM IST), status “Received”NVD
    CISA assessmentOn 21 Oct, CISA’s SSVC entry on NVD rated exploitation as “none” and technical impact as “total”; NVD status is still “Received” (not yet analysed)NVD
    Attack trafficCloudflare says it observed attack traffic after the CVE details leakedCloudflare

    Step 1: How do I check which PHP version my site really runs?

    Check the version the web server uses for your site. The command-line php -v on the same server can be a different build, so do not rely on it alone.

    In Joomla 4, 5 or 6.2

    Log in to the Administrator, open System → System Information, and read PHP Version on the System Information tab. The PHP Information tab shows the full phpinfo output, including the Server API line (for example FPM/FastCGI or Apache 2.0 Handler), which tells you whether you are on the higher-risk mod_php.

    In WordPress

    Go to Tools → Site Health → Info and expand Server. The PHP version and Server API rows are listed there (WordPress Site Health docs).

    With no admin access

    Upload a one-line file, open it in the browser, note the version, and delete it immediately, because phpinfo output helps attackers:

    <?php echo PHP_VERSION, " ", PHP_SAPI;

    Name it something random (not info.php). It prints the exact version and the server API, for example 8.3.36 fpm-fcgi. PHP manual: phpversion()

    Checking many sites

    Repeat the same check per site, because one hosting account can run different PHP branches per domain. Record domain, branch, patch level and Server API in a sheet, and sort by the table above.

    Step 2: How do I update PHP to a fixed version?

    Two different things are called “updating PHP”. A patch update (8.3.35 to 8.3.36) is a drop-in security fix that your host installs on the server. A branch change (8.1 to 8.3) is something you usually select yourself and must test, because extensions and plugins can break. PHP2Shell needs the patch update everywhere, and a branch change if you are on 8.1 or older.

    cPanel (shared hosting)

    1. Open Software → MultiPHP Manager (cPanel docs), or Select PHP Version on CloudLinux servers.
    2. Check which branch your domain uses. The selector picks a branch; the patch level inside it is whatever the host has installed.
    3. If you are on 8.1 or older, take a backup, then pick 8.3 or newer and test the site (see Step 2b).
    4. Run the Step 1 check again. If the patch level is still below the fixed build, open a ticket (template in Step 5).

    Server admins with WHM install the fixed EasyApache 4 packages through the normal system update and manage versions in MultiPHP Manager for WHM.

    Plesk

    In Plesk, open the domain, then PHP (PHP Settings), and choose the PHP version. Plesk’s own advisory (updated 21 Oct 2026, 15:13 UTC / 8:43 PM IST) lists the state of its PHP builds:

    Plesk PHPLinuxWindows
    8.2Fixed in 8.2.35In development
    8.3Fixed in 8.3.36In development
    8.4Fixed in 8.4.27In development
    8.5Fixed in 8.5.12In development
    7.4, 8.0, 8.1In developmentIn development

    To see which builds a Plesk server has, go to Tools & Settings → PHP Settings; the version is part of each handler name. On Linux over SSH, /opt/plesk/php/8.3/bin/php -v shows it (swap 8.3 for your branch).

    Plesk also lists its own panel engine (sw-engine) as affected on all versions, with hotfixes planned as 18.0.80#11 and 18.0.81#4. If you run Plesk on Windows, use the interim hardening in Step 4 until the builds ship, and keep checking Plesk’s advisory.

    CloudLinux, LiteSpeed and other managed hosts

    On CloudLinux, the per-site PHP selector uses CloudLinux’s own alt-php builds, so the patch arrives when CloudLinux ships it and your host installs it. LiteSpeed is named in php.net’s list of affected setups. On managed WordPress and Joomla hosts with no PHP setting, the host alone controls the patch: ask for the exact version and date (Step 5).

    Your own VPS or dedicated server

    • Distribution packages (Ubuntu, Debian, RHEL and clones): install the vendor security update with your normal package manager. Distributions often backport security fixes without changing the upstream version number, so confirm with the vendor’s security notice for these CVE IDs, not by version string alone.
    • Third-party repositories or source builds: upgrade to the fixed upstream release from php.net downloads or your repository once it publishes the build.
    • Docker images: pull an image built on the fixed release, rebuild, and redeploy every container; a running container never patches itself.
    • Then restart PHP (Step 3). Without a restart the old code keeps serving requests.

    Step 2b: Moving off PHP 8.1 or older without breaking the site

    CMS versionPHP minimumPHP recommendedCan it reach a fixed branch?
    Joomla 6.x (incl. 6.2)8.3.08.4Yes, every supported setup is 8.3+ (Joomla docs)
    Joomla 5.x8.1.08.3Yes, move to 8.3 (Joomla docs)
    Joomla 4.x7.2.58.2Yes on 8.2, but upgrade Joomla too (Joomla docs)
    Joomla 3.x5.3.108.0 (highest listed)No; see the Joomla 3 section below (Joomla docs)
    WordPress (current)7.4 (legacy)8.3 or greaterYes (WordPress requirements)
    1. Back up files and database first (how to back up Joomla).
    2. Update the CMS core, then every extension, plugin and theme, on the old PHP version.
    3. For Joomla, scan extensions for compatibility with our free Joomla 6 compatibility check.
    4. Switch the branch on a staging copy if you have one, or during a quiet hour on live.
    5. Test front end, forms, checkout, login and admin. If you get a white page or 500 error, switch back and use this guide to find the failing extension.
    6. Still on Joomla 3? PHP cannot move until Joomla does; see the Joomla 3 section.

    Step 3: How do I confirm the patch is actually live?

    1. Repeat the Step 1 check through the website (Joomla System Information, WordPress Site Health or the one-line file). The version must be 8.2.35, 8.3.36, 8.4.27, 8.5.12 or higher, or a vendor package your vendor confirms fixes both CVEs.
    2. On a server, restart every PHP process: restart PHP-FPM pools, and for mod_php restart Apache fully. php.net’s advisory tells admins to restart every worker for settings to apply; the same applies to new binaries.
    3. Check that no process still uses the old library. On Linux this should print nothing:
    grep -lE ' /(usr|lib|opt).*\(deleted\)$' /proc/[0-9]*/maps 2>/dev/null

    Then check every site on the account, not just the main one; add-on domains can run different branches.

    Step 4: What can I do while I wait for my host?

    php.net lists interim measures that reduce exposure to specific attack paths but, in its words, do not make an installation safe. They must be set in php.ini, the PHP-FPM pool or the web server config, which apply before the request is parsed. php.net says not to rely on ini_set() or FPM .user.ini.

    SettingTargetsNotes from php.net
    session.upload_progress.enabled=0CVE-2026-109619Blocks the confirmed session paths, not other variants. Neither Joomla nor WordPress core needs it.
    fatal_error_backtraces=0 (PHP 8.5 only)CVE-2026-109619Blocks the confirmed fatal backtrace path only.
    memory_limit=-1 set with php_admin_valueCVE-2026-109618Removes the controllable memory-limit failure; use a container or cgroup limit instead, not RLIMIT_AS or RLIMIT_DATA.
    post_max_size = 8M (no uploads) or 32M (uploads), upload_max_filesize lowerCVE-2026-109618Also cap request size, field count, multipart parts, headers and nesting at the web server or proxy.
    Remove invalid or deprecated per-request settings (for example in .htaccess)CVE-2026-109619Hiding errors with display_errors or error_reporting does not help.

    A Joomla site with large media uploads or a WordPress shop importing big CSV files may need the 32M limit. Our Joomla .htaccess guide shows where per-directory PHP settings live, so you can find and remove deprecated php_value lines.

    Does Cloudflare or a WAF protect me?

    Partly. Cloudflare says customers using its free or paid WAF have been protected by default against known PHP2Shell attacks since 21 Oct 2026, 03:02 UTC (8:32 AM IST), and still tells customers to patch PHP (Cloudflare blog). A WAF only helps if attackers cannot reach your server directly by IP, so restrict the origin to Cloudflare’s IP ranges. Treat any WAF rule as a stopgap.

    Step 5: What if my host will not update PHP?

    Send a short ticket that leaves no room for a vague answer:

    Subject: PHP2Shell (CVE-2026-109618 / CVE-2026-109619) patch date
    
    Hi, my site [domain] runs PHP [version]. PHP released 8.2.35, 8.3.36,
    8.4.27 and 8.5.12 on 21 October 2026 to fix two unauthenticated remote
    code execution flaws (https://www.php.net/). Please confirm:
    1. the date the fixed build will be installed for my account, and
    2. if you use vendor-backported packages, the package version that
       includes both fixes.
    If my branch (8.1 or older) will not be patched, which supported
    branch can I switch to today?
    Thanks.

    If the host cannot give a date, or only offers PHP 8.1 or older, that is a reason to move. Until then, put the site behind a WAF with the origin locked down, apply what Step 4 allows on your plan, and keep fresh offsite backups. CERT-FR’s advice for unsupported versions is to isolate affected systems and migrate to a maintained version (CERT-FR), and BleepingComputer reports that the UK NCSC told organisations to update or take systems offline until patched (BleepingComputer).

    Step 6: How do I know if my site was already attacked?

    The flaws allow code execution as the web server user, so look for what an attacker would leave behind:

    • New or changed PHP files in upload, cache, images or tmp folders, especially since 20 Oct 2026.
    • Unknown administrator or Super User accounts.
    • Unusual POST requests, very large multipart uploads, or bursts of 500 errors in the access and error logs around 20 and 21 October.
    • Unexpected cron jobs, outbound connections or spam sent from the server.

    If you find any of these, patching alone is not enough. Follow our hacked Joomla incident-response guide or our WordPress malware removal service, and rotate database, FTP, admin and API passwords afterwards. For ongoing hardening see the Joomla security guide.

    PHP2Shell checklist

    Done?Task
    ☐Recorded PHP version and Server API for every site
    ☐Every site on 8.2.35, 8.3.36, 8.4.27, 8.5.12 or a vendor-confirmed backport
    ☐PHP-FPM / Apache restarted, no deleted libraries in use
    ☐Sites on 8.1 or older scheduled for a branch change
    ☐Interim settings applied where still unpatched
    ☐Logs and files checked for signs of compromise
    ☐Host ticket answered with a patch date

    The short version

    Find the PHP version every site really serves, get it onto 8.2.35, 8.3.36, 8.4.27 or 8.5.12, restart PHP and check again. Use the interim settings only while you wait, and chase your host for a date. If a site is on Joomla 3 or PHP 8.1 and older, the patch you need is a version upgrade, and the sooner it is planned the less any future PHP flaw matters. If you want a second pair of hands, Infyways has worked on Joomla sites since 2010 and replies to enquiries within 12 hours; you can reach us here.

    Frequently asked questions

    What does PHP2Shell mean for a non-technical site owner?

    PHP, the engine that runs Joomla and WordPress, has a fault that lets a stranger run commands on your server without logging in. Ask your host to confirm your site runs PHP 8.2.35, 8.3.36, 8.4.27, 8.5.12 or newer.

    Can I patch PHP2Shell on a Joomla 3 site?

    Not on a supported setup. Every fixed PHP release is 8.2 or newer, and Joomla 3.10 does not run on PHP 8.2+. Vendor backports and php.ini settings reduce risk only partly, so the lasting fix is upgrading to Joomla 6.2 via 4.4 and 5.x.

    What is PHP2Shell?

    PHP2Shell is the name for CVE-2026-109618 and CVE-2026-109619, two critical flaws in the PHP runtime rated CVSS v4.0 9.2. They can allow unauthenticated remote code execution on servers that serve web requests with PHP.

    Which PHP versions fix PHP2Shell?

    PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12, released on 21 October 2026. PHP 8.1 and older get no official release.

    Do I need to update Joomla or WordPress?

    No CMS update fixes PHP2Shell, because the flaw is in PHP. Keep the CMS updated anyway, especially if you need to move to a newer PHP branch.

    Will a security plugin or extension protect my site?

    No. php.net describes a demonstrated exploit that triggers before any application code runs, so CMS security plugins and extensions never see it.

    Is PHP 8.1 safe if my host says it is patched?

    Only if the host uses a vendor package that backports both fixes, and can name it. The PHP project itself published no fixed 8.1 release.

    Which PHP version should a Joomla 6.2 site use?

    Joomla 6 requires PHP 8.3 and recommends 8.4. Use 8.4.27 or 8.3.36 or newer.

    Which PHP version should WordPress use?

    WordPress recommends PHP 8.3 or greater. On 8.3, use 8.3.36 or newer.

    Can I set the PHP2Shell mitigations in .user.ini?

    No. php.net says not to rely on ini_set() or FPM .user.ini; use php.ini, the FPM pool or server configuration, then restart every worker.

    Is Cloudflare enough to protect my site?

    No. Cloudflare deployed WAF rules on all plans but still tells customers to patch, and a WAF does nothing for traffic sent straight to your server IP.

  • How to Find Which Joomla Extension Is Causing a 500 Error

    How to Find Which Joomla Extension Is Causing a 500 Error

    A Joomla 500 error means PHP or the web server aborted the request. The extension name is in the log, not in the generic “Whoops” page. Read error_log (and Joomla’s log folder), turn Debug on from Global Configuration or configuration.php, then isolate the last update. On a staging copy only, you can temporarily rename a plugin folder to prove the group. Never delete production files without a backup, and never “clean up” live plugins to find a 500.

    The browser message is empty on purpose. Production hides fatals. Your job is to make the fatal visible in a log, then disable one extension, not the whole site.

    500 page with no name, error_log line pointing at plugins/system

    The HTML is a dead end. The PHP error log is the map. The path under plugins, modules, or components is the extension.

    What you will learn

    • Where hosts put error_log and where Joomla writes administrator/logs
    • How to enable Debug and Maximum error reporting when the admin still opens
    • How to set $debug and $error_reporting in configuration.php when admin does not
    • Why the last update is the first extension to disable
    • How to rename a plugins folder on staging only as a group test
    • How to disable one row in #__extensions without deleting files
    • What not to do on production

    Official: Fatal error (Joomla User Manual). If the site runs but two add-ons fight, use Joomla extension conflict instead of this 500 path.

    500 vs white screen vs “Whoops”

    Joomla 4 and 5 often show a page titled like Whoops, looks like something went wrong with an HTTP 500 status. That is still a server 500. A white screen is the same class of failure with display_errors off.

    Source What it is good for
    PHP error_log (host panel, or a file in the account) Fatals that happen before Joomla’s pretty error page
    Web server error log (Apache/nginx) .htaccess, PHP-FPM socket, permissions
    administrator/logs/ (or the path in Global Configuration) Joomla Log::add and some extension logs, not every fatal
    Debug System + Error Reporting Maximum Stack trace after Joomla has bootstrapped
    Browser Network tab Confirms 500 vs 403 vs timeout. Does not name the PHP file

    If the log line is .htaccess or mod_security, you may not have an extension problem. Fix the server rule, then come back if PHP still fatals.

    Step 1: Copy the site, then backup production anyway

    Before any rename, disable, or configuration.php edit on a live site:

    1. Snapshot or copy files and the database (host backup, or your own). If you cannot restore, do not experiment on production.
    2. Prefer a staging URL with the same Joomla and PHP versions. Do the hunt there. Deploy the known-good disable back to production.
    3. Tell the team the site may be briefly noisy if you enable Maximum error reporting on production.

    Do not delete the plugins directory on production “to see what happens.” You will take down authentication, two-factor, and SEF. You may not get admin back without a restore.

    If you need someone else to hold the copy and the log hunt: Joomla support and maintenance.

    Step 2: Read error_log before you click around

    Ask the host where PHP logs. Common places:

    • cPanel Errors or Metrics → Errors
    • Plesk PHP log
    • A file named error_log in public_html or in the account home
    • ~/logs/error.log on some VPS stacks

    Open the log at the timestamp of your test request. One line of PHP Fatal error is worth an hour of plugin guessing.

    Copy:

    • The exception class (Error, TypeError, ParseError)
    • The file path and line
    • The first few frames of the stack if present

    Map the path:

    • plugins/system/example/ → System plugin “example”
    • plugins/content/example/ → Content plugin
    • modules/mod_example/ → that module (unpublish it in Site Modules once admin works)
    • components/com_example/ → that component
    • templates/cassiopeia/ or a child → template PHP, often an override. See customize without editing core after the site is up.
    • libraries/ → core or a library package. Do not delete libraries. Restore a backup or revert the last Joomla update.

    Joomla also logs under Global Configuration → System → Path to Log Folder (default administrator/logs). Check everything.php or dated files if the host PHP log is empty. Many fatals never reach Joomla’s logger because PHP died first. That is why error_log is step 2, not step 5.

    Step 3: Debug from Global Configuration, or from configuration.php

    If administrator still loads:

    1. System → Global Configuration.
    2. System tab: Debug System = Yes.
    3. Server tab: Error Reporting = Maximum.
    4. Save. Reload the failing site URL once (and the admin URL if that is what 500s).
    5. Read the on-screen file and line. Then set Debug = No and Error Reporting = System Default. Save.

    The Debug console is configured by System – Debug. Allowed Groups can hide the console from guests. You still want Maximum reporting for the fatal text.

    If administrator is a 500 too, do not keep hitting login. Use FTP or the host file manager:

    1. Download configuration.php. Keep a copy.
    2. If the file is 444, set it to 644 long enough to edit (the manual describes this).
    3. Set public $debug = true;
    4. Set public $error_reporting = 'maximum';
    5. Save. Reload once.
    6. Put $debug back to false and $error_reporting back to 'default' or 'none' (match what you had) as soon as you have the path. Leaving Maximum on production leaks paths to visitors.

    Official steps: Fatal error.

    Optional: rename the template’s error.php on staging if that file is itself fataling and hiding the real message. Do that only on the copy.

    Step 4: Disable the last update first

    System → Update → Extensions (if admin works) or your change log:

    • Last extension update
    • Last Joomla update
    • Last PHP version change on the host (this 500s old extensions without a zip install)

    Disable in this order once you have a path, or if the log is empty but the clock matches an update:

    1. The extension named in the log.
    2. If the log names a plugin, disable that plugin in System → Manage → Plugins (or #__extensions below).
    3. If admin is down, you cannot click Plugins. Use the database: table #__extensions (your prefix), find element matching the plugin name, set enabled to 0. The user manual describes this for a faulty extension. Do not set core rows to 0 unless you know the row.
    4. If the last change was a component update, disable its plugins first (packages register several rows). Then take the component off the default menu item so it is not the Home view.

    Clear cache files on disk if page cache is on (cache/ folder) after a disable. A cached 500 is rare. A cached blank HTML is less rare. Still worth deleting cache/ on staging.

    Step 5: Staging only, rename a plugins folder to test a group

    This is a group proof, not a production technique.

    On staging:

    1. Confirm you can restore (snapshot, or a zip of plugins/ you just made).
    2. Rename one third-party plugin directory, for example plugins/system/suspect → plugins/system/suspect.off. Joomla will skip that folder. Core plugins stay.
    3. Reload. If the 500 is gone, that folder was in the path (or something it triggered was).
    4. Rename it back. Disable the plugin properly in the database or UI so the site does not fatal on the next page that autoloads it in a different way.

    You can rename a group folder on staging in an emergency, for example plugins/system → plugins/system.off, to see whether any system plugin is involved. That will break a lot of features. It is a binary test on a copy, then you put the folder name back immediately and disable one plugin at a time.

    Do not do this on production. Do not delete the folder. Do not rename plugins as a whole on a live shop. You will remove authentication plugins and lock everyone out. If you already did that on production, restore the backup from Step 1. Do not invent a “fix” by uploading empty directories.

    If you need a batch disable with the UI still up, that is the conflict article’s plugin batches, not a filesystem delete.

    Step 6: Database disable when the UI is dead

    phpMyAdmin or an SQL client, on a backup first:

    • Table: {prefix}_extensions
    • Find the row: type = plugin, element = the plugin name, folder = system/content/…
    • Set enabled = 0

    For a module, you can also unpublish in {prefix}_modules (published = 0) if the log named mod_….

    For a component Home page that 500s, change the default menu item in {prefix}_menu to a core featured or article view, or disable the component’s plugins, rather than DROP TABLE. Deleting tables is how you turn a 500 into a restore.

    When admin returns, uninstall or roll back the extension with System → Manage → Extensions if you are done with it. Uninstall is not the same as deleting folders by hand. The installer cleans #__extensions rows.

    Memory, timeouts, and logs that name PHP, not an extension

    Some 500s never mention plugins/. They still belong to an extension.

    • Allowed memory size exhausted at a line in plugins/system/example/ is that plugin (or a loop it triggered). Raise memory_limit only on staging to confirm. On production, fix the plugin or the data set it loads (a module that queries every article is a typical case).
    • Maximum execution time exceeded in a component view is that component, or a plugin that runs on that view. Do not raise max_execution_time as the only fix.
    • PHP Parse error in an override under templates/…/html/ is your copy, not the vendor zip. Restore the core layout on staging, then repair the override in a child.

    .htaccess 500s often follow a security plugin that wrote rewrite rules, or a hand edit after an extension installer. On staging, temporarily rename .htaccess to .htaccess.bak and use Joomla’s default htaccess.txt copied to .htaccess. If the 500 vanishes, the rules were the problem. Put your custom rules back one block at a time. Do that on production only after a backup, and only if you can restore via the host panel when you lock yourself out.

    Gzip in Global Configuration plus Maximum error reporting can produce odd output on some hosts. If Debug shows a fatal and the browser still shows a generic 500, disable Gzip for the test. Turn it back on later.

    After the site loads, close the hole

    1. Set $debug false and error reporting off/default.
    2. Set Preview and Debug plugins back to normal groups.
    3. Update or replace the extension. If it needs old class names on Joomla 5, that is a compatibility check on the installed but not working article, not a reason to leave Debug on.
    4. If a plugin tmpl was the fatal (parse error in an override), fix the override in a child. Plugin override.
    5. Write the extension name and version in your runbook so the next 500 is shorter.

    Checks: backup, error_log path, debug, last update, staging rename only

    Log first. Last update second. Rename plugin folders only on staging. Never delete live files to “test.”

    Key takeaways

    1. A Joomla 500 is a server abort. The extension is named in error_log (or a Debug stack), not in the Whoops HTML.
    2. Copy the site or take a full backup before you change configuration.php or plugin folders on anything you care about.
    3. Enable Debug and Maximum error reporting only for the reproduce, then turn them off.
    4. Disable the last updated extension first when the clock matches and the log agrees.
    5. Rename plugin folders only on staging, as a temporary proof. Put the names back. Disable via Plugins or #__extensions.
    6. Never delete production plugins/, components/, or libraries/ to debug. Restore from backup if you already did.
    7. Database enabled = 0 on one extension row is the safe UI-down move. Dropping tables is not.
    8. When two extensions work alone and 500 together, finish recovery then use the conflict process.

    Frequently asked questions

    How do I find which Joomla extension is causing a 500 error?

    Read the PHP error_log at the request time. The file path under plugins/, modules/, or components/ is the extension. Enable Debug if Joomla still bootstraps. Then disable that extension, starting with the last update if the log is empty.

    Can I rename the plugins folder on the live site?

    No. Use staging. On production, take a backup and disable one #__extensions row, or restore. Renaming plugins on live removes authentication and can lock out admin.

    Admin is a 500. How do I turn on debug?

    Edit configuration.php: $debug = true and $error_reporting = 'maximum'. Reload once, copy the error, then turn both back off. The user manual documents the permission change if the file is read-only.

    The error_log is empty. What next?

    Check the web server log, Joomla’s log path, and whether you are looking at the right vhost. Enable Maximum reporting on staging. If PHP dies before logging, ask the host for the FPM log.

    Should I delete the extension files to stop the 500?

    No. Disable it. Deleting files on production without a backup is how you lose the only copy of a paid extension and still leave broken #__extensions rows. Restore, then uninstall from the administrator when it loads.

    Could PHP be the “extension”?

    A host PHP upgrade can fatal old extensions. The log still names the extension file. The fix is an update of that extension, or rolling PHP back on staging to prove it.

    When is a 500 not an extension?

    Disk full, bad database credentials in configuration.php, a broken .htaccess, or a core update that failed mid-way. The log still decides. If it names libraries/ after a Joomla update, restore the update backup, do not delete libraries.