To maintain the Joomla security and functionality of websites, it’s crucial to regularly update both the site and the third-party extensions used. Regular updates address a variety of issues, including enhancing functionality features, upgrading PHP functions, and ensuring compatibility with the latest Joomla versions.
However, some website owners hesitate to update extensions. This could be due to modifications they’ve made to the extension’s core files, which they fear might be overwritten, or they may be reluctant to purchase the commercial extension after the license expires. As a result, they frequently encounter a red notification upon logging into the Joomla backend.
To disable the update notification for specific extensions in the backend for Joomla 4.x.x, follow these simple steps:
Step 1: Log in to the backend of your Joomla website using the Super admin login details.
Step 2: Navigate to the System Menu > Update > Update Sites.
Step 3: On the Update Sites page, you’ll find a list of Update Sites with an XML link below each. Select the extension for which you want to disable the update notification.
Step 4: Select the extension(s) and click on the disable button. To clear the Joomla cache, go to the System menu > Clear Cache.
By following these steps, you can manage your Joomla upgrade issues more effectively, ensuring a smoother and more secure user experience.
This detailed tutorial will help you handle the upgrade process quickly, whether you’re considering upgrading Joomla 3 to 4, or perhaps looking to improve your older Joomla 1.5 to the latest version.
For those wondering how to upgrade Joomla manually, or wishing to update to the latest Joomla version, this article will provide the necessary steps to make the process as smooth as possible.
Upgrading your Joomla version regularly is essential to maintaining a secure, efficient, and feature-rich website. Let’s delve into the step-by-step process of upgrading Joomla using cPanel.
Backup Your Website
Before any major changes to your Joomla website, it’s always prudent to create a backup. This way, should anything go wrong during the upgrade, you can revert to the previous state. You can do this within cPanel using the Backup Wizard or by using Joomla extensions like Akeeba Backup.
Check Extension Compatibility
Before upgrading, make sure your extensions are compatible with the new Joomla version. You can find this information on the Joomla extensions directory or the extension developer’s website. It’s crucial to ensure smooth operation after the upgrade.
Upgrade Your Joomla Version
Once the backup is complete and the extensions are compatible, you can proceed with the upgrade. If you’re using Joomla 3, you can easily upgrade to Joomla 4 from your Joomla control panel.
If you’re using an older version such as Joomla 1.5, the upgrade process might be a bit more complex. You would need to migrate your site to Joomla 2.5 before proceeding with the upgrade to Joomla 3 or 4. Here, you can follow a detailed guide on how to upgrade Joomla 1.7 to 2.5 and subsequently upgrade from Joomla 3 to Joomla 4.
Test Your Website
Once you’ve completed the upgrade, make sure to thoroughly test your website to ensure everything is functioning correctly. If you run into issues, you might need to refer to this guide on fixing Joomla issues.
Update Your Extensions and Templates
After ensuring your website works well with the new Joomla version, it’s time to update your extensions and templates. Doing this after the Joomla upgrade reduces the chances of encountering compatibility issues.
Now that you know how to upgrade Joomla using cPanel, it’s important to regularly check for new Joomla updates to keep your website secure and running efficiently. Joomla’s latest version, Joomla 4, has introduced several new features to enhance your website’s performance and improve the user experience.
To show a module inside a Joomla article, publish the module to a custom position and type {loadposition your-position} in the article, or load one specific module with {loadmodule mod_name,Module Title}. Both shortcodes come from the core Content – Load Modules plugin in Joomla 4, 5 and 6.
Option 1: {loadposition} (load every module in a position)
Go to Content → Site Modules and click New. Choose a type, for example Custom, Articles – Latest or Menu.
In the Position field type a new name that your template does not use, for example article-promo, and press Enter to create it.
Under Menu Assignment choose “On all pages” (or the pages where the article appears). A module assigned to no pages will not load, even inside an article.
Save and close the module.
Open the article and, where the module should appear, type {loadposition article-promo} on its own line. Save.
Every published module in that position is rendered, in module ordering. Add a style to change the chrome: {loadposition article-promo,card} uses the Cassiopeia “card” style; none outputs the module without a wrapper.
Option 2: {loadmodule} (load one module by type and title)
Use this when you do not want to create a new position:
The first value is the module type (as listed in the Modules list, for example mod_custom), the second is the exact module title. Without a title, Joomla loads the first published module of that type. Joomla 4 and later also accept {loadmoduleid 97} to load a module by its ID, which is the safest choice if titles change.
Make sure the plugin is enabled
Go to System → Manage → Plugins, search for Content – Load Modules and check it is enabled. In its options you can set the default module style. If the shortcode appears as plain text on the page, this plugin is disabled or the text editor has wrapped the code in a link or span.
Why the module is not showing
Symptom
Fix
Shortcode shows as text
Enable Content – Load Modules; retype the shortcode in the editor’s code view
Nothing appears
Module unpublished, assigned to no pages, or access level higher than the visitor’s
Shows in the article but also in a sidebar
The position name is used by the template; pick a unique name
Works in the article view but not in a blog/featured layout
Check “Show Intro Text” and that the shortcode is in the intro, or use the full article view
What is the difference between loadposition and loadmodule?
loadposition renders every published module assigned to a position. loadmodule renders one module chosen by its type and title, and loadmoduleid renders one module by its ID.
Why does {loadposition} show as plain text?
The Content – Load Modules plugin is disabled, or the editor has inserted HTML inside the braces. Enable the plugin and retype the shortcode in code view.
Does loadposition work in Joomla 6?
Yes. The Content – Load Modules plugin is part of Joomla 4, 5 and 6 core.
Uploading an Excel sheet to a Joomla website involves several steps. Here’s a step-by-step procedure to help you achieve this:
Login to Joomla Administrator Panel:
Navigate to your Joomla website’s admin URL (typically yourwebsite.com/administrator).
Enter your username and password to log in.
Media Manager:
From the top menu, select Content and then click on Media.
This will take you to the Media Manager, where you can manage and upload files.
Upload the Excel File:
Click on the Upload button (usually represented by an upward arrow icon).
Browse your computer to select the Excel file you wish to upload.
Once selected, click on the Start Upload button. Your Excel file will be uploaded to the Joomla server.
Linking the Excel File:
Once the file is uploaded, you can link to it from articles or modules.
Edit or create a new article where you want to place the link.
Highlight the text you want to use as a link.
Click on the Insert/Edit Link button in the editor toolbar.
In the URL field, browse or type the path to the uploaded Excel file. It will typically be in the format: /images/yourfilename.xlsx.
Set the target to “_blank” if you want the file to open in a new window/tab.
Click on Insert to add the link.
Extensions for Advanced Functionality:
If you want to display the Excel content directly on your Joomla site or provide advanced download features, you might consider using Joomla extensions. Extensions like “Edocman” or “Dropfiles” can help manage and display documents, including Excel sheets, more effectively.
Ensure File Security:
Make sure that any sensitive information is removed from the Excel sheet before uploading.
Regularly backup your Joomla site, including the Media Manager files.
Consider using security extensions to protect your uploaded files from unauthorized access.
Test the Upload:
After uploading and linking the Excel file, visit the front end of your Joomla site.
Click on the link you created to ensure the Excel file downloads or displays correctly.
Remember, the exact names of buttons and the layout might vary depending on the Joomla version you’re using and any customizations or extensions you have installed. Always ensure that you’re following best practices for website security when uploading and linking to files.
Disabling deprecated Joomla messages means stopping PHP E_DEPRECATED notices (and often Joomla “Log Deprecated API” noise) from flooding the front end, administrator, or log files. On Joomla 4, 5, and 6 the safe first move is Global Configuration → Server → Error Reporting set to None on production (or Simple while you triage), with Debug System off. Hiding messages is not a substitute for updating the extension or template that still calls old APIs.
Thin guides still tell you to paste error_reporting(…) at the bottom of configuration.php. That file is a PHP class of settings, not a free-form bootstrap script, and Joomla already maps Error Reporting into $error_reporting. This guide shows the admin path, the correct DIY edits when the admin is locked, PHP host filters, what Maximum does on PHP 8, and when you should fix the real code instead of silencing it.
What you will learn
What deprecated messages are (PHP vs Joomla API logging)
Production vs staging Error Reporting choices
How to turn off Log Deprecated API and Debug System
DIY: edit $error_reporting in configuration.php when the admin is down
DIY: php.ini / .htaccess filters when System Default inherits a noisy host
Why Maximum + PHP 8 can make a site unusable, and how to recover
When silencing is wrong and you need an upgrade instead
Two different “deprecated” problems
Source
What you see
Control
PHP E_DEPRECATED
Yellow/red notices on the page, or entries in the server error log
Basic errors (roughly errors, warnings, parse). Filters many notices and deprecations
Quick triage without drowning in E_DEPRECATED
Maximum
Forces a very high reporting level (effectively all errors)
Staging only. Can flood PHP 8+ sites with deprecations
Development
Full developer reporting
Local clone only
Security note: production should not display PHP errors to the public. Prefer None for visitors, and read server logs or a staging clone when you need detail.
Step 1: Set Error Reporting in Global Configuration
Log in to Administrator.
System → Global Configuration → Server tab.
Error Reporting: choose None for live sites, or Simple if you still need basic faults visible to admins on staging.
Save & Close.
Reload the front end and administrator. Deprecated banners from PHP display should be gone when None is active.
Step 2: Turn Debug System off on production
System → Global Configuration → System tab.
Debug System: No.
Debug Language: No unless you are translating.
Save.
Debug Mode plus Maximum is how sites become unreadable under PHP 8 when old extensions still emit deprecations.
Step 3: Stop Log Deprecated API filling administrator/logs
System → Global Configuration → Logging tab.
Log Deprecated API: No on production (Yes only while you are intentionally auditing extensions).
Log Almost Everything: No unless you are debugging a specific incident.
Note the Path to Log Folder. If deprecated.php is huge, archive or delete it after you turn logging off (keep a copy if you still need the list of offenders).
Save.
Log Almost Everything does not include the deprecated category. Deprecated API calls use the separate Log Deprecated API switch and write to deprecated.php.
Step 4: DIY when the administrator is locked
If deprecated output or a fatals storm blocks the admin UI, edit configuration.php over SFTP or hosting File Manager. Change permissions temporarily if the file is read-only (often 444 → 644 on Linux hosts), edit, then lock it down again.
Set the property Joomla already understands. Do not append a free-standing error_reporting(…) call at the bottom of the class file:
public $error_reporting = 'none';
public $debug = false;
Useful values for $error_reporting: 'none', 'simple', 'maximum', 'development', or 'default' (system default). Matching debug:
public $debug = false;
Optional logging flags you may also see in the same file:
public $log_everything = 0;
public $log_deprecated = 0;
Save the file, reload the site, then finish the job in Global Configuration once the admin is reachable again.
Some deprecations fire so early that only the PHP process setting fully hides them. Prefer the host panel (MultiPHP INI, PHP-FPM pool, or “Select PHP version → Options”).
Example php.ini / FPM style:
display_errors = Off
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
log_errors = On
On Apache with AllowOverride permitting PHP flags, some hosts accept:
php_value error_reporting 22527
(22527 is a common integer for E_ALL & ~E_DEPRECATED on older PHP lines. Confirm with echo E_ALL ^ E_DEPRECATED; on your PHP version, or use the host UI instead of guessing.)
If Global Configuration is set to Maximum, Joomla overrides the host filter for display. Switch Maximum off first, then tune PHP.
Step 6: Verify and keep staging honest
Production: Error Reporting None, Debug No, Log Deprecated API No.
Staging clone: temporarily use Simple or Development, or enable Log Deprecated API, and capture which extensions appear in the log.
Confirm visitors no longer see notice HTML in View Source.
Confirm the server error log is not still spamming the same deprecations every request (display off does not always stop logging).
Clear Joomla cache after config changes.
What not to do
Do not paste error_reporting(E_ALL & ~E_DEPRECATED); at the bottom of configuration.php. That old Infyways tip (and many Stack Overflow clones) treats a settings class like index.php.
Do not leave Maximum + Debug on a public PHP 8 site “just in case.”
Do not error_reporting(0) in core index.php as your long-term strategy. Updates overwrite it and you lose real fatals you need.
Do not ignore a flood of deprecations forever on an abandoned extension. PHP 8.3 / 8.4 and Joomla 6 will keep raising the cost.
Fix the cause when messages point at your stack
Signal
Likely cause
Next step
Deprecations name a third-party extension path
Extension not ready for your PHP / Joomla line
Update or replace the extension
Deprecations name a template override
Old PHP in the override
Rewrite the override on a child template
Only on Maximum / Development
Expected noise while modernising
Keep production on None; fix on staging
Site unusable after a PHP upgrade
Reporting too high + legacy code
Set None/Simple via configuration.php, then plan an upgrade
If the site is still on Joomla 3 or early 4 with abandoned extensions, silencing notices only buys time. Infyways upgrades start at $149 with a free audit within 12 hours: Joomla Upgrade Services.
What thinner articles leave out
Topic
Typical post
This guide
First step
Hack configuration.php with error_reporting()
Global Configuration Error Reporting
Joomla API log
Ignored
Log Deprecated API and deprecated.php
PHP 8 + Maximum
Missing
Why the site can go blank or unusable
Locked admin
Vague FTP advice
Edit $error_reporting and $debug properties correctly
Host PHP
One .htaccess line
display_errors, logging, and Maximum override behaviour
Root cause
“Messages are annoying”
Update extensions or upgrade the CMS
Key takeaways
Production: Error Reporting None, Debug System No, Log Deprecated API No.
Simple is a useful middle ground for triage without full deprecation spam.
Avoid Maximum on live PHP 8+ sites unless you are ready for noise.
When locked out, set $error_reporting = 'none'; and $debug = false; in configuration.php.
Do not append raw error_reporting() calls to configuration.php.
Host PHP filters help when System Default inherits a noisy ini, but Maximum overrides them for display.
Silencing is temporary. Fix or replace the extension that still uses deprecated APIs.
Frequently asked questions
How do I disable deprecated Joomla messages?
Set Global Configuration → Server → Error Reporting to None on production, turn Debug System off, and set Log Deprecated API to No.
What is the difference between Error Reporting None and Simple?
None hides PHP error display. Simple still shows basic errors and warnings but filters much of the notice and deprecation noise.
Why did Maximum make my PHP 8 site unusable?
Maximum forces very high reporting, so every E_DEPRECATED from legacy extensions can dump onto every page. Switch back to None or Simple.
How do I edit Error Reporting if the administrator will not load?
Edit configuration.php and set public $error_reporting = ‘none’; and public $debug = false; then reload.
Should I add error_reporting() to configuration.php?
No. Use the $error_reporting property or the Global Configuration UI. Appending a free-standing call is an outdated and brittle hack.
What does Log Deprecated API do?
It writes Joomla deprecated API usage to deprecated.php in the log folder. Turn it on only while auditing, then turn it off.
Will hiding deprecated messages fix security issues?
No. It only stops display or API logging. Outdated extensions can still be vulnerable. Plan updates or a migration.
Can I filter E_DEPRECATED in php.ini only?
Yes for System Default, and for some compile-time cases. If Joomla Error Reporting is Maximum, change that setting too.
Where do we start if deprecations come from abandoned extensions?
Updated 15 October 2026 · By Abhilash Sahoo, Founder, Infyways
Quick answer: The fastest way to add custom JavaScript to Joomla 5 or 6 with Cassiopeia is to create media/templates/site/cassiopeia/js/user.js. Joomla loads it on every page with no code changes. For anything more, use the Web Asset Manager:
For a file: $wa->registerAndUseScript('my.site', 'media/templates/site/cassiopeia/js/site.js', [], ['defer' => true]);
For a snippet: $wa->addInlineScript('…');
To keep it to one page, put the code in a template override.
Avoid pasting raw <script> tags into the template or a Custom HTML module. Editors strip them, and a Content Security Policy blocks them. This all applies unchanged to Joomla 6.2, the latest version.
I tested every method below on a real Joomla 5.4.10 site (PHP 8.2, XAMPP) and checked the browser console in Chrome. I also compared the relevant Joomla 6.2.0 source files. Images marked “real output” show what the site actually printed. References: Joomla’s Adding JavaScript and Web Asset Manager documentation.
Site-wide files, CDN URLs or snippets without template edits
No
Yes (Normal, Defer, Async)
Yes (tested)
All front-end pages, minus exclusions
Don’t edit Cassiopeia’s own index.php. Joomla updates overwrite it. My tests changed it only to show the output; for a real site, use a child template.
How do I add JavaScript with user.js in Cassiopeia?
Go to System → Site Templates → Cassiopeia Details and Files.
Open media/templates/site/cassiopeia/js (shown as the js folder). Click New File, name it user, choose type .js, and click Create.
Add your code and save:
document.addEventListener('DOMContentLoaded', () => {
// your code
});
Nothing else is needed. Cassiopeia’s joomla.asset.json already declares a template.user script, and index.php already calls useScript('template.user'). The tag only appears once the file exists:
Two things I found in testing:
No defer.user.js loads as a normal script, so wrap DOM code in DOMContentLoaded.
Caching. The ?970ad6 on the URL is the site’s media version, not a hash of your file. After editing user.js, visitors may still get the cached copy. Hard-reload while testing. For a change visitors must get immediately, rename the file, or load it with the Web Asset Manager and your own version number. See caching in Joomla.
How do I add a script with the Web Asset Manager?
The Web Asset Manager (WAM) is the official API in Joomla 4, 5 and 6. In a template file, $wa = $this->getWebAssetManager();. Elsewhere, use Factory::getApplication()->getDocument()->getWebAssetManager().
The arguments are name, URI, options, HTML attributes and dependencies. Here’s what Joomla actually printed:
When I passed an empty options array, Joomla added the media version (?970ad6) to the CDN URL as well. Pass ['version' => false] to keep third-party URLs clean. This matters for some CDNs and for SRI hashes.
Should I use joomla.asset.json instead?
If you have several scripts, yes. Declare them once in your template’s or extension’s joomla.asset.json, then call $wa->useScript('name'):
Templates and components pick up their file automatically. For a module or plugin, call $wa->getRegistry()->addExtensionRegistryFile('mod_example'); first (official docs).
How do I add inline JavaScript or pass PHP values to JS?
$wa->addInlineScript("document.documentElement.dataset.ready = '1';");
// PHP → JS without building strings
$this->addScriptOptions('custom.cfg', ['siteName' => $sitename]);
// in JS: Joomla.getOptions('custom.cfg').siteName
In my test, Joomla.getOptions('custom.cfg') returned {"siteName":"Demo"}. Your script needs core as a dependency to use Joomla.getOptions.
How do I add JavaScript to one page only?
Create a template override for that view, for example System → Site Templates → Cassiopeia Details and Files → Create Overrides → Components → com_content → article. Then add near the top of templates/cassiopeia/html/com_content/article/default.php:
Overrides live in the html folder, and Joomla updates leave them alone. To target one menu item rather than one view, wrap the call in a check on $app->getMenu()->getActive()->id.
How do I add JavaScript without editing the template?
Use a system plugin that registers your scripts through the Web Asset Manager for you. One example is Easy Includes 2.0 from JoomlaX (our own extension), which supports Joomla 4, 5 and 6. Its documentation lists what it does:
Files tab: add a site-relative path or a full https:// CDN URL for each CSS or JS file. For each script you choose Normal, Defer or Async loading, plus optional type="module", nomodule, crossorigin and an SRI hash.
Inline Code tab: paste short, trusted CSS or JS snippets. Inline JavaScript isn’t HTML-filtered, so only trusted admins should manage the plugin.
Load Priority: rows with higher numbers register first.
Exclusions: skip selected user groups, components (for example com_users) or URL path fragments (for example /checkout). If any exclusion matches, nothing loads on that page. There is no include-only-on-this-menu-item option, so for single-page scripts use an override.
Cache busting: Off, Auto (uses the file’s modification time) or Aggressive (for testing only).
Front end only by default. The admin area loads the assets only if you turn on Enable in Administrator.
Script loading is set per file, and there is no head-or-body choice. Version 2.0 replaced that option with Normal/Defer/Async. I installed the 2.0 package on the same test site, with the CSP nonce turned on:
A deferred file printed as <script src="/j5/images/ei-test.js?1792064452" defer nonce="…">. With Auto cache busting, the number is the file’s modification time.
The inline snippet also got the nonce, and Chrome ran both.
On the login page (com_users, excluded), neither loaded.
Updates install from the Joomla admin with a valid JoomlaX licence.
Can I put a script in a Custom HTML module?
Yes, and the script runs on a site without a CSP. In my test, the module’s <script> ran normally. There are two catches:
Editors strip it. TinyMCE lists script under Prohibited Elements by default. Switch your user’s editor to Editor – None or CodeMirror while pasting. Make sure your group’s Text Filter (Global Configuration → Text Filters) isn’t removing it. Super Users have no filtering by default (Joomla HTML filters guide).
A CSP blocks it. The script has no nonce, as the next test shows.
Will my script work with a Content Security Policy nonce?
Only if it goes through Joomla’s API. I enabled System – HTTP Headers → Content Security Policy with Nonce on and script-src 'self' https://cdn.jsdelivr.net. Joomla prepended a fresh nonce to the header and added nonce="…" to every Web Asset Manager tag, including user.js and the addInlineScript() block. Chrome then ran those and blocked the module’s raw script:
Since Joomla 4.2 you no longer need to type {nonce} in the directive. The plugin removes the old placeholder and adds the nonce itself (from the 5.4 and 6.2 source). Every external host your scripts load from must be listed in script-src. More on headers in our Joomla .htaccess guide and the official HTTP Headers guide.
Should I use defer, async or type=”module”?
Attribute
Runs
Order kept?
Use for
none
Immediately, blocks HTML parsing
Yes
Rarely; tiny scripts that must run first
defer
After HTML is parsed
Yes
Most site scripts that touch the DOM
async
As soon as downloaded
No
Independent third-party scripts (analytics)
type="module"
Deferred by default
Yes
Modern ES modules (Joomla core uses this)
With WAM, pass these as attributes, for example ['defer' => true] or ['type' => 'module']. For tracking scripts, respect consent: see disabling cookies for visitors.
What about Document::addScript()?
It still works, but it’s deprecated. In both the Joomla 5.4.10 and 6.2.0 source, addScript() and addScriptDeclaration() are marked @deprecated 4.3 will be removed in 7.0. When you touch old code, replace them with registerAndUseScript() and addInlineScript(). If an old extension also uses removed classes, see fixing Class JRequest not found.
What changed in Joomla 6.2?
For custom JavaScript, very little. I compared the 6.2.0 package with 5.4.10:
The libraries/src/WebAsset classes are identical.
Cassiopeia’s index.php is identical, so user.js works the same way.
The HTTP Headers plugin adds a Reporting-Endpoints header option.
Code you write for Joomla 5 with the Web Asset Manager carries over to Joomla 6.
Troubleshooting
Symptom
Cause
Fix
user.js not in page source
Wrong folder, or a non-Cassiopeia template
Use media/templates/site/cassiopeia/js/user.js; other templates need WAM
Edits to user.js don’t show
Browser cache; the media version didn’t change
Hard-reload; clear Joomla and CDN cache
<script> vanished after saving
TinyMCE or the Text Filter
Use Editor – None or CodeMirror; check Text Filters
Console: “violates the following Content Security Policy directive”
Raw script without a nonce, or host not in script-src
Load it through WAM; add the host
Joomla is not defined
Script runs before core.js
Add ['core'] as a dependency
null when selecting elements
Ran before the DOM was ready
Use defer or DOMContentLoaded
CDN URL has ?abc123 appended
WAM versioning
['version' => false]
Script gone after a Joomla update
Edited a core template file
Move it to a child template, override or user.js
Script loads twice
Added by both a module and the template
Use one method; WAM de-duplicates by asset name
FAQs
Where is user.js in Joomla 5?
It doesn’t exist until you create it at media/templates/site/cassiopeia/js/user.js. Cassiopeia then loads it automatically.
Does user.js survive Joomla updates?
Yes. Joomla doesn’t ship a user.js, so updates don’t overwrite it. The 6.2.0 package doesn’t include one either.
Is the Web Asset Manager required?
Not strictly, but it’s the supported API. It handles dependencies, load order, versioning and CSP nonces. addScript() is deprecated and due for removal in Joomla 7.
How do I add Google Analytics or Tag Manager?
Register the vendor URL with WAM, using async and 'version' => false. Put the config snippet in addInlineScript(), and add the vendor hosts to your CSP. Load it only after consent if you need consent.
Can I add JavaScript to a single article?
Use a template override of the article view with a menu-item check, or a Custom HTML module assigned to that menu item. Don’t paste scripts into the article text.
Why does my script work for Super Users but not for editors?
Different user groups have different Text Filters. A lower group’s filter can strip <script> when they save the module or article.
What is the difference between addInlineScript and addScriptDeclaration?
addInlineScript() is the Web Asset Manager method, and it gets the CSP nonce. addScriptDeclaration() is the deprecated Document method.
Can I load ES modules?
Yes. Pass ['type' => 'module'] as an attribute. Joomla’s own scripts, such as template.min.js, load this way.
Is there a no-code option with page exclusions?
Yes. A system plugin such as Easy Includes lets you add JS and CSS from plugin settings on Joomla 4, 5 and 6. It can skip pages by user group, component or URL fragment. It doesn’t target single menu items, so use an override for one-page scripts. Setup steps are in the getting-started guide.
Can you add or clean up scripts for me?
Yes. We move hard-coded scripts into the Web Asset Manager, enable CSP and fix load-order bugs. We do this on its own or as part of a Joomla upgrade. Server settings that affect scripts are covered in Joomla php.ini settings.
Short answer: For most Joomla sites, use Conservative caching plus the System – Page Cache plugin for guest pages, with exclusions for carts, forms and logged-in areas, and a fast cache handler (Redis or APCu where available). This guide is the strategy. If you only need the clicks to switch cache on or off or to clear it, see how to enable, disable and clear Joomla cache.
Caching in Joomla means storing rendered HTML, component views, and module output so the next guest request skips most database and PHP work. In Joomla 4, 5, and 6 you control three layers: Global Configuration System Cache (Off, Conservative, or Progressive), the System – Page Cache plugin for whole guest pages, and per-module Advanced caching. Handlers decide where copies live (File, APCu, Redis, or Memcached).
Official docs explain the switches. Deep technical posts explain com_cache internals. LiteSpeed magazine pieces cover one host stack. This guide is the operator map: which mode to pick by site type, what breaks Progressive and Page Cache, Redis and Memcached setup gotchas, how to clear and purge safely, and when caching alone cannot fix a slow EOL site. Infyways upgrades and tunes production Joomla from $149 with a free audit within 12 hours.
What you will learn
The three cache layers and the order they win
Conservative vs Progressive vs Page Cache with a decision table
File, APCu, Redis, and Memcached: when each handler is right
Exclusions for carts, forms, login, and personalised modules
Clear vs purge, CLI clean, and stale-content fixes
How LiteSpeed (or another edge cache) should sit beside Joomla cache
A staging checklist and when to call Infyways
How Joomla caching is layered
Think of three increasing levels of aggressiveness. The first layer that can answer usually wins.
Layer
Where you set it
What it caches
Who it serves
System Cache (Conservative or Progressive)
System → Global Configuration → System → Cache Settings
Component views and modules (rules differ)
Mostly guests for core content views; access levels are part of the cache id
Module Advanced tab
Each module → Advanced
That module only (Use global or No caching)
Respects Conservative; ignored for guests under Progressive
Important: turning System Cache to Conservative does not by itself cache the full page. Full-page guest caching needs the System – Page Cache plugin enabled separately.
Conservative vs Progressive vs Off
Mode
What happens
Use when
Avoid when
Off
No view or module cache from Global Configuration
Debugging, template work, chasing a stale bug
Busy production brochure sites
Conservative (recommended default)
Caches eligible component views and modules that allow caching. Module “No caching” is respected
Almost every site: membership, forms, stores, multilingual
Never the wrong starting point
Progressive
For logged-off users, all modules are cached. Module “No caching” has no effect. Module output often shares a com_modules group file
Static brochure sites after careful staging tests
Menus that change by page, random modules, login-aware chrome, anything that must differ per Itemid
Myth to kill: Progressive is not “caching for logged-in users.” Official docs are explicit that core view cachability rules do not flip that way. Progressive is more aggressive module caching for guests.
Classic Progressive failure: the wrong module appears on the wrong page because one cached module blob was reused across Itemids. If you see that, switch back to Conservative immediately.
System – Page Cache plugin
This is the fastest built-in path. On a hit, Joomla can return stored HTML before most of the site boots. It only serves guests. Logged-in visitors always get a fresh build so names, carts, and private menus stay private.
Enable: System → Manage → Plugins → System – Page Cache
It uses the same handler and Cache Time as Global Configuration
Exclude menu items and URL patterns for anything dynamic
Use Browser Caching sends browser cache headers. Leave it off unless you understand that visitors can keep a page after you clear server cache
Always exclude (or never page-cache): contact and other forms, search results, login and registration, carts and checkout, tokenised or one-time pages, and any URL that must reflect the current session. Editing an article does not always clear every page that embeds it. Clear the page cache group after content launches that must be instant.
Cache handlers: File, APCu, Redis, Memcached
Handler
Stores in
Best for
Watch outs
File
cache/ and administrator/cache/
Default on shared hosting and most single servers
Many tiny files on slow disks; purge expired regularly
APCu
PHP shared memory
Single server speed win for small items
Not shared across nodes; cleared on PHP restart
Redis
Redis server or Unix socket
Clusters, high traffic, LiteSpeed object cache stacks
Wrong host or socket causes 500s; change handler before killing Redis
Memcached
Memcached server or socket
Shared cache across web nodes
Often labelled experimental in host UIs; test persistence settings
Modern Joomla no longer relies on old handlers such as XCache or eAccelerator. If a host guide still lists them, ignore that part.
Redis tip from real support threads: if you disable System Cache while Redis is already unreachable, you can still get connection errors until you switch the handler back to File (or a working Redis), save, then turn caching off. Flush cache after handler changes.
Global Configuration fields that matter
Setting
Meaning
Practical default
System Cache
Off / Conservative / Progressive
Conservative
Cache Handler
Where items are stored
File, then Redis on capable hosts
Platform Specific Caching
Adds device type into the cache id
No, unless desktop and mobile HTML truly differ on the same URL
Cache Time
Lifetime in minutes (default 15)
15 for mixed sites; lower for news; higher for static brochures
Path to Cache Folder
Custom file path
Leave blank unless you know why
Module Cache Time is in seconds. Global Cache Time is in minutes. Mixing those units is a common misconfiguration.
Per-module caching
Open the module → Advanced → Caching: Use global or No caching
Set No caching for login status, live counters, random quotes, carts, and anything personal
Under Progressive for guests, No caching is ignored. That is why Progressive breaks dynamic chrome
Some modules declare a cache mode in code (static, itemid, and similar). A badly coded static mode can freeze wrong content even on Conservative
Breadcrumbs is a safe module to use when testing Conservative caching on staging.
Decision guide by site type
Site type
System Cache
Page Cache plugin
Handler
Notes
Brochure / marketing
Conservative (try Progressive only after tests)
On, with form pages excluded
File or Redis
Biggest easy win
Membership / ACL content
Conservative
On for public pages only; exclude member areas
File or Redis
Access levels belong in cache ids; still exclude personal dashboards
Multilingual
Conservative
On
File or Redis
Language is part of identity; clear cache after language or SEF changes
VirtueMart / Hikashop / carts
Conservative
On only for static CMS pages; exclude cart, checkout, account
File or Redis
Page Cache on cart URLs causes classic “empty cart” bugs
Heavy community / logged-in traffic
Conservative
Limited; focus on guest landing pages
Redis preferred on busy hosts
Page Cache helps guests only
LiteSpeed host
Conservative
Often rely on LiteSpeed full-page; keep Joomla Conservative
Redis as object cache when offered
Magazine guidance: Conservative with LiteSpeed + Redis reduces conflicts
LiteSpeed, CDN, and Redis together
Edge page cache (LiteSpeed Cache for Joomla, Cloudflare, or a reverse proxy) sits in front of Joomla. Redis or Memcached as the Joomla cache handler speeds object and view cache behind that. Do not stack three aggressive full-page systems without a purge story.
Prefer Conservative when an external full-page cache is already on
Let the edge plugin purge on article save when it supports automatic purge
Use Redis for shared or high-traffic object cache, not as a substitute for excluding dynamic URLs
ESI and logged-in edge features vary by LiteSpeed edition. Test on staging
Clear Cache vs Clear Expired Cache
Action
Path
Removes
Use when
Clear Cache
System → Maintenance → Clear Cache
Selected groups or everything
After template, override, or extension updates; stale homepage; debugging
Clear Expired Cache
System → Maintenance → Clear Expired Cache
Only past-lifetime items
Routine housekeeping so File handler folders do not fill forever
CLI clean
php cli/joomla.php cache:clean
All (or expired with the expired argument)
Deploy scripts and cron
With the File handler you can also empty cache/ via SFTP if the admin is down. That is equivalent to a full clear. Joomla cache is not a database table.
Step 1: Set a safe baseline on staging
Clone production to staging.
System → Global Configuration → System → Cache Settings: System Cache = ON – Conservative caching, Handler = File, Platform Specific Caching = No, Cache Time = 15.
Save. Browse as a guest. Confirm pages load and dynamic modules still update.
Only then introduce Redis or Progressive on a second staging pass.
Step 2: Enable Page Cache with exclusions
Enable System – Page Cache.
Exclude contact, search, login, cart, checkout, and account menu items.
Leave Use Browser Caching off for the first week.
As a guest, load a public article twice. Confirm a cache/page entry appears when using the File handler.
Edit that article, clear the page group, and confirm the front end updates.
Step 3: Tune modules and handlers
Set personal or random modules to No caching (Conservative only).
If the host offers Redis, set handler to Redis, enter socket or host, port 0 for Unix sockets when required, save, then Clear Cache.
Retest guest and logged-in paths, forms, and checkout.
Optional: try Progressive only on a static brochure clone. Revert at the first wrong-module symptom.
Step 4: Production cutover and monitoring
Apply the proven staging settings during a low-traffic window
Clear Cache after deploy
Watch Core Web Vitals and server CPU for a week
Schedule Clear Expired Cache or CLI purge if you stay on File
Document exclusions so the next editor does not enable Page Cache on checkout
Troubleshooting stale or broken cache
Symptom
Likely cause
Fix
Old article text on guests
Page Cache still holding URL
Clear page group; shorten Cache Time if launches are frequent
Wrong module on a page
Progressive guest module cache
Switch to Conservative; clear com_modules
Empty cart or stuck form
Page Cache on dynamic URLs
Exclude those menu items and URLs; clear page cache
Redis connection 500 after “turning cache off”
Handler still Redis while server is down
Set handler to File while Redis is up, save, then disable caching
Logged-in users see no speed gain from Page Cache
By design
Rely on Conservative + Redis; Page Cache is guest-only
Mobile gets desktop chrome
Platform Specific Caching off while serving different HTML
Enable only if HTML truly differs; prefer one responsive template
Cache multiplies a healthy stack. It does not replace an unsupported Joomla 3 site, an abandoned template full of blocking scripts, or PHP that the host is about to retire. If Time to First Byte stays poor after Conservative + Page Cache on staging, fix the CMS and template path first.
Infyways runs that path as a service:
Free compatibility and performance audit within 12 hours
Fixed packages from $149 small / $299 medium / custom for stores and clusters
125 Joomla extensions built in-house when a cache-hostile extension needs a rebuild
Staging-first cutover and 30 days of post-launch support on defects we introduce
Start with Conservative caching. Add System – Page Cache for guests with strict exclusions.
Progressive is optional and dangerous for dynamic modules. It is not “logged-in caching.”
Full-page cache is a separate plugin. Global System Cache alone is not full-page cache.
File is fine for most sites. Redis or Memcached help clusters and high traffic.
Global Cache Time is minutes. Module Cache Time is seconds.
Clear the page group after launches that must be instant. Purge expired on File hosts.
Edge cache plus Joomla Conservative plus Redis is a common modern stack. Test purge behaviour.
If the site is EOL or template-bound, upgrade first. Cache cannot patch an unsupported core.
Frequently asked questions
What is caching in Joomla?
It is storing views, modules, or whole guest pages so repeat requests skip most PHP and database work. You control it with System Cache, module Advanced settings, and the System – Page Cache plugin.
Should I use Conservative or Progressive caching?
Use Conservative for almost every site. Use Progressive only on static brochure sites after staging tests, because guest modules are force-cached and “No caching” is ignored.
Does System Cache cache the whole page?
No. Conservative or Progressive cache views and modules. Whole-page guest caching needs the System – Page Cache plugin.
Does Page Cache work for logged-in users?
No. The plugin serves guests only so personalised HTML is never shared between users.
Is Progressive caching for logged-in users?
No. That is a common myth. Progressive changes how guest modules are cached. Core view rules for logged-in users stay separate.
What cache handler should I choose?
File for standard shared hosting. APCu for a fast single server. Redis or Memcached when you need shared memory cache across nodes or your host recommends it with LiteSpeed.
Why is my cart empty after enabling cache?
Page Cache is almost certainly covering cart or checkout URLs. Exclude those menu items and clear the page cache group.
How do I clear Joomla cache from the command line?
Run php cli/joomla.php cache:clean from the site root. Use the expired variant for purge-only cleanup in cron.
Will caching fix a slow Joomla 3 site by itself?
No. It can help guests, but unsupported core, old PHP, and abandoned templates still need an upgrade path. See benefits of Joomla migration.
How much does Infyways charge to tune or upgrade a slow Joomla site?
Packages start at $149 for small sites and $299 for medium sites. Stores and multi-node setups are custom after the free audit.
Joomla 5 and 6 can send users to a different page after login without any extension. Set it on the login menu item or the login module, and use separate menu items or modules when different user groups need different pages.
Method 1: Login form menu item
Go to Menus → Main Menu → New and choose Users → Login Form.
In the Options tab, set Login Redirect to the menu item users should land on, and optionally Logout Redirect.
Save. Everyone who logs in through this page goes to that menu item.
Method 2: Login module
Open Content → Site Modules → your Login module. Under Module → Login Redirection Page pick the menu item. This applies to logins from that module only; if you have both a login page and a module, set both.
Different pages for different user groups
Core Joomla redirects per form, not per group. Two core-only approaches work:
Create one login menu item per audience (for example /customer-login/ and /partner-login/), each with its own Login Redirect, and link users to the right one.
Make the landing page a menu item visible to Registered users, and put group-specific modules on it with Access set to each group or access level. Everyone lands on the same URL but sees their own content.
For a true automatic redirect by group (the same login form sending Managers, Customers and Authors to different URLs), use a JED login redirect extension that lists Joomla 5/6 support.
Why the redirect is ignored
Cause
Fix
A return URL is set
A ?return= parameter (for example from a protected page) takes priority; this is expected
Target menu item is restricted
The user’s access level cannot see the target; choose a page they can access
Caching
Exclude the login page from page caching
Login popup or third-party form
Configure the redirect in that extension; see login popup fix
Most Joomla “hosting problems” come down to five things: the PHP version, PHP limits, file permissions, a slow or overloaded server, and missing backups. Here is how to spot each one and fix it, with the requirements for Joomla 5 and 6.
1. PHP and database version too old
Joomla
PHP
Database
Joomla 5
8.1 or newer (8.2/8.3 recommended)
MySQL 8.0.13+, MariaDB 10.4+, PostgreSQL 12+
Joomla 6
8.3 or newer (8.4 recommended)
MySQL 8.0.13+, MariaDB 10.6+ recommended, PostgreSQL 14+
Symptoms: the update to the next major is never offered, or a white screen after an update. Change PHP in cPanel → Select PHP Version or MultiPHP Manager. Current figures are in the Joomla technical requirements.
2. PHP limits too low
Failed extension installs, stalled updates and “Allowed memory size exhausted” errors usually mean memory_limit, upload_max_filesize or max_execution_time is too low. Recommended values and where to change them: Joomla PHP.ini settings.
3. File permissions and ownership
Folders should be 755 and files 644, owned by the account PHP runs as. “Unable to write” or “could not open archive” errors during install point here. System → System Information → Folder Permissions shows which folders are not writable. Never set 777.
4. Slow server
Check Time To First Byte in PageSpeed Insights. If the server takes more than about 600 ms before sending anything, caching and image fixes will not be enough; enable OPcache, use PHP-FPM and HTTP/2 or HTTP/3, and move off overloaded shared hosting if needed. Site-side fixes are in how to speed up Joomla and caching in Joomla.
Host backups are often kept on the same server and for only a few days. Keep your own copies off the server with Akeeba Backup; see how to back up Joomla.
What to look for in Joomla hosting
PHP 8.3+ available, with OPcache, and an easy PHP version switcher
MySQL 8 or MariaDB 10.6+
SSH or at least SFTP access, and cron jobs
Daily backups you can download
HTTP/2 or HTTP/3 and free SSL
Hosting changes made the site slow, broken or hacked? Our Joomla support and maintenance team can audit the server and the site.
Frequently asked questions
What PHP version does Joomla 6 need?
PHP 8.3 or newer; 8.4 is recommended. Joomla 5 needs PHP 8.1 or newer.
Why does my Joomla extension install fail?
Usually upload_max_filesize, memory_limit or folder permissions. Check System Information → Folder Permissions and raise the PHP limits.
Is shared hosting fine for Joomla?
For small sites, yes, if it offers PHP 8.3+, OPcache, MySQL 8 or MariaDB 10.6+ and downloadable backups.