Category: Joomla

If you’re running a Joomla website, you may come across an error message that reads “Fatal error: Class ‘ContentHelperRoute’ not found.” This error can occur for a variety of reasons, including issues with the Joomla core files, missing or corrupt files, or database problems. In this blog post, we’ll walk you through the steps to troubleshoot this error and get your Joomla website up and running again.

Clear your Joomla website’s cache

The first step to troubleshoot this error is to clear your Joomla website’s cache. To do this, go to the Joomla administrator area and navigate to System -> Clear Cache. Click on all the options to clear the cache.

Check the Joomla version

Next, check that you are running a supported version of Joomla and that the com_content component is installed correctly. ContentHelperRoute is a part of the com_content component, which is a core component of Joomla. Make sure that you are using a version of Joomla that is supported and that the com_content component is installed correctly.

Check for missing or corrupt files

Check that there are no missing or corrupt files in your Joomla installation. You can do this by navigating to Extensions -> Manage -> Discover in the Joomla administrator area and clicking on the “Discover” button. This will help identify any missing or corrupt files that need to be fixed.

Check the database

Ensure that the Joomla database is functioning correctly by navigating to System -> Global Configuration -> Server and checking the database settings. Verify that the database connection is working correctly and that the database server is running.

Reinstall Joomla core files

If none of the above steps work, try reinstalling the Joomla core files. This will help replace any missing or corrupt files that are causing the “Fatal error: Class ‘ContentHelperRoute’ not found” error.

In conclusion, the “Fatal error: Class ‘ContentHelperRoute’ not found” error in Joomla can be frustrating to deal with, but there are several steps you can take to fix the issue. By clearing your Joomla website’s cache, checking the Joomla version and com_content component, checking for missing or corrupt files, and verifying the Joomla database, you can eliminate many of the most common causes of this error. If you are still experiencing issues, consider seeking help from a Joomla developer or support team.

Slideshow templates are great for people who are not creative and don’t know how to design their slideshow video. The template usually comes in a set of scenes so you different design to use for presenting different forms of information in the slideshow. The following are 9 sites where you can download free slideshow templates.

SlidesCarnival

SlidesCarnival offers fully editable Google Slides and PowerPoint templates for business presentation. You must go to the All Templates category to find the slideshow templates. For each template, it provides details such as the number of slides, icons, can be used for what slideshow program, and the supported screen layout. There is the library of slideshow templates.

Envato Elements

Envato Elements has a collection of thousands of slideshow templates under the video templates category. You can find a lot of slideshow templates for Keynote, PowerPoint, Google Slides and After Effects on this site. You can preview it by pressing the thumbnail. On the left, you can filter the slideshow templates you are looking for by categories, applications supported, plugins required and minimum resolution. If you want to download a template, you must first create a free account with them. There is the library of slideshow templates.

Movavi

Movavi also publishes some free slideshow templates that you can download to use for your presentations. You can download the template directly onto your computer and start using it to design your slideshow. The template is compatible with Movavi Slideshow Maker. The template will only work correctly if you upload at least 15 images. There is the library of slideshow templates.

Canva

Canva is one of the best resources for free presentation slideshow templates. You can preview each scene that comes with the template. To use Canva free template, you must first sign up for a free account. There are lots of categories to choose from including creative, simple, education, cool, brand guidelines, product, marketing, and professional. There is the library of slideshow templates.

Slidesgo

Slidesgo offers a wide selection of free Google Slides and PowerPoint templates. You can browse the templates in several categories including business, education, and marketing. The templates are easy to edit by beginners. Along with the template, you also get access to 1000+ icons and editable graphics. There is the library of slideshow templates.

Biteable

Biteable also has a templates section where you can find a lot of slideshow templates. However, you can’t download the templates directly onto your computer. You must edit the video and then upload your photo to make the slideshow. After that, you will be able to download the finished slideshow to your computer. You must sign up for a free account to use the template at Biteable. There is the library of slideshow templates.

Renderforest

Renderforest offers a lot of slideshow templates that include multiple scenes. To use the template, you must first click on the thumbnail and then click the Create Now button. This will take you to the online designer tool where you can customize the template. You will be able to add scenes, video holders and logo animations. When you finish creating the slideshow, you can download it to your computer. You don’t need an account to use the free slideshow templates at Renderforest. There is the library of slideshow templates.

Slides Gala

Slides Gala is another popular resource for downloading Google and Powerpoint slideshow templates. The templates are open source so you can modify the design in any way you want. They do request that you put a link back to them when you download their free template. You can fully customize the template by changing the colour, text and photos. The template can also be exported to other formats like PDF and JPG. There is the library of slideshow templates.

Motion Array

Motion Array provides a lot of slideshow templates you can use in Adobe after Effects. On the left, you must select After Effects Templates and toggle the free switch to filter the results for free After Effects Templates. If you want to download a template, you simply click the download button with the down arrow. It will ask you to create a free account when you click the download button. The free templates do not include plugins. There is the library of slideshow templates.

For a new Joomla 6 store in 2026, choose an actively maintained cart that already supports Joomla 6: HikaShop, J2Commerce 6, EShop or Phoca Cart. VirtueMart 4 does not run on Joomla 6. VirtueMart 5 does, but it is still a beta (released as 4.9.x). Pick the cart that fits your catalogue, your payment gateway and your migration path. Joomla 6.2, released on 13 October 2026, is the current version.

This guide compares the Joomla shopping carts that are still alive, using data we checked on the Joomla Extensions Directory (JED) and vendor sites in October 2026. It explains what is happening with VirtueMart, maps the US payment gateways each cart supports, and shows how to move a store safely. Need a hand? Tell us your cart, Joomla version and payment gateway. A senior engineer replies within 12 hours. Contact Infyways.

What is the best shopping cart for Joomla in 2026?

There is no single winner. Match the cart to the store:

• New Joomla 6 store that needs a wide feature set: HikaShop. It is actively updated, supports J3 to J6, and ships Authorize.net and PayPal Checkout in the core.
• A content-led shop built on Joomla articles: J2Commerce 6. It turns articles into products and is built natively for Joomla 6.
• Many payment gateways off the shelf: EShop. Five gateways are built in, and the vendor sells more than 50 add-ons, including Stripe, Braintree and Square.
• Simple, digital or point-of-sale shops: Phoca Cart. It is free and includes a POS view.
• Running VirtueMart today: no need to panic. Read what’s going on with VirtueMart before you decide to stay, wait for VirtueMart 5, or migrate.

Joomla shopping cart comparison (October 2026)

Reviews, ratings, versions and compatibility come from each cart’s JED listing, checked on 16 October 2026. Ratings are the star rating shown on the JED. Built-in gateways come from vendor documentation.

Not recommended for new stores: Quick2Cart (JED lists J3 to J5 and no Joomla 6, last updated 15 July 2025), and older names such as MijoShop, jMarket and JomDirectory Cart, which have no Joomla 5 or 6 builds on the JED.

J2Commerce vs HikaShop: which should you choose?

What’s going on with VirtueMart (and what should you do)?

Short answer: VirtueMart is still developed, but its JED listing is unpublished, current 4.x downloads need a membership, and the Joomla 6 version is still in beta. Existing stores do not need to panic-migrate. New Joomla 6 stores should pick a cart with stable Joomla 6 support today.

• Verified: the VirtueMart JED listing says it “has been unpublished” with reason code PE1.
• Verified: VirtueMart’s own news of 14 April 2026 offers VirtueMart 4.6.8 as a download that “needs Membership”. It also says “VirtueMart 5 is already running on Joomla 6”, with the VirtueMart 5 beta published as version 4.9 (virtuemart.net).
• Reported, not confirmed by us: a third-party review on FAUN.dev says the listing was pulled in August 2026 after a security audit and that newer 4.8.x fixes go to members only (FAUN.dev review). The JED page itself gives only the reason code.

VirtueMart migration paths

• VirtueMart to HikaShop: HikaShop’s built-in “Import from VirtueMart” moves categories, taxes, products, images, files, customers and orders, and a redirect plugin forwards old VirtueMart URLs. The documentation lists VirtueMart 1.x, 2.x and 3.x, so test a VirtueMart 4 store carefully on staging (HikaShop import docs).
• VirtueMart to J2Commerce: use a CSV bridge such as RO CSVI, which publishes VirtueMart export templates for HikaShop and J2Store (RO CSVI).
• VirtueMart 4 to Solidshop: a free migrator for the catalogue, according to Solidshop. Orders and customers do not move.
• Off Joomla (Shopify, WooCommerce, Magento): possible, but you lose Joomla content integration and need a full URL redirect plan.

We plan and run these moves as a VirtueMart migration service. Ongoing VirtueMart development is available too, if you decide to stay.

What a cart migration must preserve

• Product, category and manufacturer URLs, with a 301 redirect for every URL that changes
• Titles, meta descriptions and structured data
• Customers, addresses and order history
• Taxes, shipping zones and coupons, which are rebuilt and tested
• Saved cards and subscriptions: payment tokens usually cannot be moved between plugins, so plan for customers to re-enter cards or for a gateway-side token migration
• All of it rehearsed on staging before the live switch

Is your Joomla shop ready for Joomla 6?

Joomla 6.2 is the latest version, released on 13 October 2026, and Joomla 6 needs PHP 8.3 or newer. The cart itself is rarely the only blocker. Payment, shipping and template plugins usually are.

Scan your add-ons with the Joomla 6 compatibility check and the Joomla Migration Scanner. See what’s new in Joomla 6.2, or hand the whole move to our Joomla upgrade service.

Which payment gateways work with Joomla shopping carts?

Stripe, PayPal and Authorize.net are available for most major carts. Square and Braintree are where the gaps are. This matrix shows what we found in October 2026. “None found” means we did not find one, not that one cannot exist.

Gaps worth knowing about:

• Square on HikaShop: the marketplace plugin by Tsuki Dev redirects to Square and supports cards only; its page says digital wallets could not be properly tested (HikaShop marketplace, last updated 6 February 2023).
• Recurring Authorize.net on HikaShop: HikaShop’s team said token-based recurring with Authorize.net “would require some development”. Stripe Checkout recurring was added later, and recurring for PayPal Checkout was announced for HikaShop 6.4.1 (HikaShop forum).
• Phoca Cart: the core ships PayPal Standard, Cash on Delivery and POS Cash only (Phoca Cart plugins). We found no native Square, Braintree or PayPal Advanced plugin.
• J2Commerce 6: older J2Store plugins are not compatible with version 6, so less common gateways may not have a version 6 build yet. Check the marketplace before you upgrade.

Custom payment gateway development

When the gateway you need is missing, or exists only as a redirect, we build it. Infyways develops and maintains payment plugins for HikaShop, J2Commerce, Phoca Cart, EShop and VirtueMart. A typical plugin covers:

• On-site card fields or hosted checkout
• Wallets where the gateway supports them
• Webhooks and order-status sync
• Refunds from the Joomla admin
• Saved-card tokens for recurring billing

Each one is tested in the gateway’s sandbox before it goes live. See Joomla payment gateway integration, or Joomla extension development for other custom plugins.

PCI and security basics

• Prefer hosted fields or tokenisation (Stripe Elements, the Square Web Payments SDK, Authorize.net Accept.js), so card numbers never touch your server and your PCI scope stays small.
• Serve the whole store over HTTPS and keep Joomla, the cart and every payment plugin updated.
• Verify webhook signatures and never mark an order paid from the browser redirect alone.
• Remove payment plugins you no longer use.

How Infyways builds and migrates Joomla stores

1. Audit: cart and version, add-ons, payment and shipping plugins, Joomla and PHP versions, URLs.
2. Staging: a full copy of the store. Nothing changes on the live site.
3. Upgrade or migration: core, cart, data, templates and redirects.
4. Gateway integration: existing plugins configured, or custom plugins built, then sandbox and live test orders.
5. SEO-safe cutover: 301 redirects, titles, structured data and sitemap checked after go-live.
6. Support: fixes and updates after launch.

We work with US merchants and agencies with daily overlap with US business hours, and reply within 12 hours. For dedicated or hourly work, hire Joomla developers.

Why Infyways: we have built Joomla sites and extensions since 2010, and have published 125 Joomla extensions.

Setting up a Joomla shop in five steps

1. Install Joomla 6.2 on PHP 8.3+ (8.4+ if you choose Solidshop), with HTTPS and SEF URLs on.
2. Choose a cart from the table above and install it from the vendor or the JED.
3. Configure currency, taxes, shipping zones and one payment gateway in sandbox mode.
4. Add products and categories, and check product pages and checkout on mobile.
5. Place real test orders, check emails and invoices, then switch the gateway to live.

Frequently asked questions

What is the best shopping cart for Joomla 6 in 2026?

For most new stores, HikaShop or J2Commerce 6. Both are actively updated and list Joomla 6 support on the JED. EShop suits stores that need many gateways out of the box, and Phoca Cart suits simple, digital or POS shops.

Does VirtueMart work with Joomla 6?

Not VirtueMart 4. VirtueMart 5 runs on Joomla 6, according to virtuemart.net, but it is still a beta released as version 4.9.x.

Is VirtueMart still on the Joomla Extensions Directory?

No. As of October 2026 its JED listing is unpublished with reason code PE1. Current releases are on virtuemart.net, and 4.6.8 needs a membership.

How do I migrate from VirtueMart to HikaShop?

On staging, use HikaShop’s built-in Import from VirtueMart, which moves products, categories, taxes, customers and orders, then publish its redirect plugin. The docs list VirtueMart 1.x to 3.x, so test a VirtueMart 4 store carefully.

J2Commerce vs HikaShop: which should I choose?

J2Commerce turns Joomla articles into products, and version 6 is native to Joomla 6. HikaShop has a separate catalogue and more built-in gateways. Choose based on your content model and the gateway you need.

Which Joomla carts support Square?

EShop (paid Squareup add-on), J2Commerce (marketplace) and HikaShop (third-party plugin, redirect and cards only). We found no native Phoca Cart plugin in October 2026. You would need the PaymentHood aggregator or custom development.

Can I take recurring payments with Authorize.net on Joomla?

Not with HikaShop’s current plugins; HikaShop has said it would need development. Stripe recurring is available for HikaShop (HikaSubscription) and DJ-Catalog2, and custom development can add Authorize.net recurring.

Can you build a custom payment gateway for my Joomla store?

Yes. We build payment plugins with on-site fields, webhooks, refunds and recurring tokens for HikaShop, J2Commerce, Phoca Cart, EShop and VirtueMart. Send us your cart and gateway, and a senior engineer replies within 12 hours.

Tell us about your store

Tell us your cart, Joomla version and payment gateway. A senior engineer replies within 12 hours. Contact us, or see our VirtueMart migration service.

There are two things people mean by “uninstall Joomla”: removing one extension from a Joomla site, or deleting the whole Joomla installation from hosting. Both are covered here for Joomla 4, 5 and 6.

Uninstall an extension

1. Go to System → Manage → Extensions.
2. Search for the extension and tick it. Packages (type “Package”) remove all their parts at once, so uninstall the package rather than each plugin or module.
3. Click Uninstall and confirm.
4. Clear the cache (System → Clear Cache) and check the front end.

Core extensions are protected and cannot be uninstalled; disable them instead. If an uninstall fails with an SQL error, check System → Maintenance → Database.

Delete a whole Joomla site with Softaculous or an installer

If Joomla was installed with Softaculous, Installatron or a similar tool in cPanel or Plesk, remove it there: open the installer, go to All Installations, click the delete (X) icon next to the site and tick “remove database” and “remove directory”. This deletes files, the database and the database user in one go.

Delete a Joomla site manually

1. Back up first (see how to back up Joomla); deleted files cannot be recovered from Joomla.
2. Open configuration.php and note the values of $db, $user and $dbprefix.
3. In the file manager or over SFTP, delete the Joomla folder (or its contents if it is the site root, keeping anything that is not Joomla).
4. In cPanel → MySQL Databases (or phpMyAdmin), delete that database and its user. If the database is shared with another app, drop only the tables that start with your prefix.
5. Remove any cron jobs, email forwarders or subdomains you created for the site.

Moving instead of deleting?

If you want to move the site to new hosting or a new domain, do not delete it until the copy works. See how to transfer Joomla to a new host. Switching platform? See Joomla to WordPress migration.

Related Joomla guides

• how to back up Joomla
• transfer Joomla to a new host

Need hands-on help? See our Joomla support and maintenance.

Frequently asked questions

How do I completely remove Joomla from cPanel?

If Softaculous installed it, delete it from All Installations with “remove database” ticked. Otherwise delete the Joomla folder and then the database and its user in MySQL Databases.

Why can’t I uninstall some Joomla extensions?

Core extensions are protected. Disable them instead of uninstalling.

Does uninstalling an extension delete its data?

Usually yes; most extensions drop their tables on uninstall. Export anything you need first.

Short answer: you can’t, and shouldn’t, switch off every cookie on a Joomla site. Joomla core sets a session cookie for every visitor. Forms, logins and CSRF protection need it, and it counts as strictly necessary. What the law asks you to stop is non-essential cookies and scripts, such as analytics, advertising pixels and many video or map embeds. Under EU and UK rules they can’t run until the visitor opts in. Under most US state privacy laws, visitors must be able to opt out of the sale or sharing of their data. Joomla 5, 6 and 6.2 have no built-in cookie banner, so you need a consent extension that blocks scripts before the visitor chooses, not just a notice bar.

In this guide: what Joomla core actually sets (checked against the 6.2.0 code), what GDPR, ePrivacy and US state laws require, a step-by-step setup, a comparison of consent extensions from their Joomla Extensions Directory listings, how to test the result, and an FAQ. This article is general information, not legal advice. See the note at the end.

What cookies does Joomla core set?

We went through the Joomla 6.2.0 source code for every place core sets a cookie on the public site. A default install sets very few, and none of them track visitors across sites:

Everything else comes from what you add: Google Analytics or Tag Manager, Meta or LinkedIn pixels, chat widgets, reCAPTCHA, YouTube and Vimeo embeds, Google Maps and Google Fonts loaded from Google’s servers. That’s where nearly all of your consent work sits.

Where are the cookie settings in Joomla?

• System → Global Configuration → System → Session: Session Lifetime, Session Handler, Shared Sessions and the Track Session Metadata and Track Guest Session Metadata options. These change how sessions are stored. None of them removes the session cookie.
• System → Global Configuration → Site → Cookie: Cookie Domain and Cookie Path. Leave them empty unless you share cookies across subdomains.
• System → Global Configuration → Server → Force HTTPS: set it to Entire Site so the session cookie is marked Secure.
• Users → Privacy → Capabilities: a report of what installed extensions say they store. Use it as a starting point, but Joomla itself warns it isn’t a complete list.
• Plugins: Authentication – Cookie and System – Remember Me control the remember-me cookie. System – Language Filter controls the language cookie.

Did Joomla 6.2 change anything about cookies?

No. The Joomla 6.2 release notes list editor, module, admin, security-update and email changes, with nothing new on cookies or consent. Core still has no cookie banner or consent manager. That’s why the advice in this guide applies the same to Joomla 4, 5, 6.0, 6.1 and 6.2.

Why not just disable the session cookie for guests?

Old forum posts suggest hacking index.php or the session handler so guests get no session. Don’t. Joomla’s form tokens depend on the session, so contact forms, login and registration break or lose CSRF protection. Strictly necessary cookies don’t need consent anyway, so removing this one gains you nothing legally. Just list it in your cookie policy.

What do GDPR and the ePrivacy Directive require?

In the EU, the rule on cookies comes from Article 5(3) of the ePrivacy Directive: storing or reading information on a visitor’s device needs their consent, unless it’s strictly necessary for a service they asked for. The meaning of consent comes from the GDPR. Article 4(11) says it must be freely given, specific, informed and unambiguous. Article 7(3) says withdrawing it must be as easy as giving it. Article 7(1) says you must be able to show it was given. In practice this means:

The UK applies similar rules through PECR and the UK GDPR. The ICO’s cookie guidance is the place to check for UK-specific detail.

The EU is also negotiating changes to the cookie rules as part of the Commission’s “Digital Omnibus” proposal. Nothing has been adopted yet, so the current rules above still apply. We’ll update this guide if that changes.

What do US state privacy laws require?

Most US state laws use an opt-out model rather than opt-in. You can usually run analytics with a clear notice, but visitors must be able to opt out of the “sale” or “sharing” of personal data, including cross-context behavioural advertising and, in many states, targeted advertising. Each law has its own thresholds, so many small sites aren’t covered at all. Check each law’s applicability section.

If you serve visitors in both Europe and the US, the simplest setup is opt-in for everyone, plus a “Do Not Sell or Share” link and GPC support. Some consent tools can instead show different rules by region.

How do you set up cookie consent on Joomla, step by step?

1. List what you load. Open the site in a private window, then check DevTools → Application → Cookies and the Network tab. Write down every third-party host and cookie, and which extension or template adds it.
2. Group them by purpose: Necessary, Preferences (functional), Analytics and Marketing. Purpose decides the category, not the cookie name.
3. Pick a consent extension that does prior blocking (see the comparison below), and install it.
4. Move tags out of the template. Remove hard-coded analytics and pixel snippets from the template, “custom code” plugins and modules. Add them through the consent tool’s category slots or blocking rules instead.
5. Turn on Google Consent Mode v2 if you use Google tags. The defaults should be denied before any tag runs, then updated after the visitor’s choice (Google guide).
6. Gate embeds. Replace YouTube, Vimeo and Maps iframes with a placeholder until the right category is allowed, or use privacy-enhanced embed modes.
7. Write the banner text. Say plainly what each category does, and link to your privacy and cookie policy. Give equal weight to Accept all and Reject all.
8. Add a persistent “Cookie settings” link in the footer so visitors can change their mind.
9. For US traffic, add a “Do Not Sell or Share” link if you sell or share data, and check the tool honours GPC.
10. Test, then retest after every change of template, tag or extension (see below).

Which Joomla cookie consent extension should you use?

We compared consent extensions for Joomla 5 and 6 using their own Joomla Extensions Directory (JED) listings in October 2026. Features are as the developers describe them. We haven’t audited each one.

Disclosure: Easy Cookie Alert is our own extension, so weigh our view of it accordingly. In short:

• Want free with the least manual work? Look at NexusConsent’s presets and scanner, or ConsentX if you need GPC and region rules.
• Want a simple free banner with a consent log? ConsentLab covers the basics.
• Still on Joomla 3 or 4? Only the Web357 extension lists J3, and only it and our module list J4. Plan an upgrade either way.
• Want a module you place like any other, with themes and a US opt-out link? That’s the gap our own module was built for.

Whatever you choose, check three things before you buy or install: it blocks scripts before consent, Reject all is on the first layer, and it’s listed as compatible with your Joomla version.

How do you check that your banner actually works?

1. Open a private window with no consent cookie, then load the home page and a page with embeds.
2. Before you click anything, DevTools → Application → Cookies should show only necessary cookies, and the Network tab should show no requests to analytics or ad hosts.
3. Click Reject all and reload. Still no tracking cookies or requests.
4. Clear cookies, click Accept all (or allow only Analytics) and reload. Only the allowed tags should now load.
5. Submit a contact form after rejecting. It should still work, because the session cookie is necessary.
6. Reopen Cookie settings from the footer, withdraw consent and check the tags stop.
7. For US traffic, turn on GPC in a browser that supports it and check your tool treats it as an opt-out.

If tracking still fires before consent, a tag is hard-coded somewhere: in the template, a module, a “custom code” plugin or an extension’s own settings. Remove it there.

What mistakes do Joomla sites make most often?

When should you get help?

Get help if your site runs many extensions, a page builder or a shop, serves both EU and US visitors, or still runs Joomla 3. Infyways has built Joomla sites since 2010 and makes 125 Joomla extensions, so we know where scripts hide in templates and extensions. We can audit what your site loads, set up consent with prior blocking, clean up hard-coded tags, and upgrade older sites so a current consent tool will run. We don’t give legal advice; your lawyer or DPO decides the policy, and we make the site do what it says. Send us your site URL. We reply within 12 hours.

Sources we checked (October 2026)

• ePrivacy Directive 2002/58/EC (consolidated), Article 5(3)
• GDPR (Regulation (EU) 2016/679), Articles 4(11) and 7
• EDPB Guidelines 05/2020 on consent
• EDPB report of the cookie banner taskforce (January 2023)
• CJEU, Case C-673/17 Planet49 (1 October 2019)
• UK ICO: cookies and similar technologies
• California Attorney General: CCPA
• California Privacy Protection Agency: CCPA regulations
• Colorado Attorney General: Colorado Privacy Act
• Connecticut Attorney General: Connecticut Data Privacy Act
• Texas Attorney General: Texas Data Privacy and Security Act
• Indiana Attorney General: Consumer Data Protection Act
• Kentucky Attorney General: Office of Data Privacy (KCDPA)
• Rhode Island General Laws § 6-48.1
• Google: Consent Mode
• Joomla 6.2.0 source code
• Joomla 6.2 release announcement

Frequently Asked Questions

Does Joomla have a built-in cookie consent banner?

No. Joomla 4, 5, 6 and 6.2 have no cookie banner or consent manager in core. You need a consent extension, ideally one that blocks optional scripts until the visitor chooses.

What cookies does Joomla set by default?

A session cookie with a random hashed name for every visitor. Optional core features add a remember-me cookie when users tick “Remember Me”, a user-state cookie for logged-in users, and a language cookie on multilingual sites. None of these track visitors across sites.

Does the Joomla session cookie need consent?

Generally no. It’s needed for forms, logins and security, which falls under the strictly necessary exemption in the ePrivacy Directive. List it in your cookie policy all the same.

Can I disable cookies completely in Joomla?

Not without breaking forms and login security. What you should disable is non-essential cookies, such as analytics, ads and some embeds, until the visitor consents.

Is a cookie notice bar enough for GDPR?

No. EU rules need prior consent for non-essential cookies. That means no tracking before a choice, a real Reject option and a way to withdraw later. A bar that only says “OK” doesn’t do that.

Do US websites need a cookie banner?

Most US state laws don’t require opt-in consent for cookies. They do require an opt-out from sale, sharing or targeted advertising where the law applies, and several states require you to honour the Global Privacy Control signal.

Does Google Analytics on Joomla need consent?

For EU and UK visitors, analytics cookies generally need consent first. Load GA4 through your consent tool and set Google Consent Mode defaults to denied until the visitor allows analytics.

Did Joomla 6.2 change how cookies work?

No. The 6.2 release added editor, module, admin and email features, but nothing on cookies or consent. The session and plugin cookies work as they did in 6.1.

Legal note: This article is general information about cookie and privacy rules as of October 2026. It isn’t legal advice, and following it doesn’t guarantee compliance with GDPR, ePrivacy, PECR, the CCPA or any other law. Laws and guidance change, and which ones apply depends on your organisation and visitors. Check your obligations with a qualified lawyer or your data protection officer.

A Joomla browser compatibility issue is a page that works in one current browser and fails in another. Joomla 4, 5, and 6 support the current major version and the one before it of Chrome, Edge, Firefox, and Safari (the n-2 policy the project adopted in 2019). Internet Explorer is not supported. Most reports are not browser bugs at all: they are a cached stylesheet, a browser extension, a Joomla 3 template, a cookie scoped to the wrong host, or one of three documented core bugs (Safari 15 and Joomla’s ranged media queries, Firefox 148 and TinyMCE in Joomla 5.4.3 / 6.0.3, and Conservative caching breaking the Web Asset Manager). This guide separates them in order and gives the fix for each.

Generic cross-browser posts tell you to “test on real devices” and “check Can I Use.” That does not help when the administrator dashboard renders as a single column on a client’s Mac or the article editor flickers forever in Firefox. Those are known Joomla issues with issue-tracker numbers, version ranges, and specific fixes. You will find them here, together with a triage that stops you rewriting CSS for a problem the private window would have solved.

What you will learn

• Which browsers Joomla 4, 5, and 6 actually support and where that policy is written
• How to tell a browser bug from cache, an extension, a responsive bug, or a PHP error
• The three documented Joomla core bugs that only show in one browser, with fixes
• Which modern CSS features are safe for Joomla templates in 2026 and which still need fallbacks
• Safari-specific quirks (100vh, hover, date inputs, backdrop-filter, autoplay) and how to code around them
• The Safari login failure that is really the site URL
• A tested one-command fix that makes Cassiopeia render on Safari 15 from a child template
• Which testing tools are worth using and in what order

Supported browsers by Joomla version

Bootstrap’s rule, which Joomla’s UI follows, is the latest stable browsers, not Internet Explorer: Bootstrap browsers and devices. The IE11 bundle removal is recorded in the Joomla 4.4 to 5 removal list. The wiki page Joomla Browser Support is a Joomla 3 document. Do not use it as the matrix for Joomla 5 or 6.

What n-2 means in practice: Safari ships one major per year, so a Mac that cannot go past Safari 15 (macOS Monterey and older) is outside support for every Joomla 4.4.1 or newer release. Chrome, Edge, and Firefox update monthly and auto-update, so “old Chrome” is almost never the cause. Firefox ESR is supported because it tracks a recent major.

Documented one-browser bugs in Joomla core

Check this table before you touch any CSS. If the symptom, browser, and Joomla version match, the fix is known.

Name the failure before you edit CSS

Step 1: Write down the browser, the version, and the URL

1. Note the browser name and a major version (Chrome 14x, Safari 18, Firefox ESR). “Doesn’t work on Mac” is not a report. On a Mac, Safari → About Safari shows the version; the macOS version tells you the maximum Safari it can run.
2. Note the exact URL. Site homepage, one article, and /administrator/ are three different products.
3. If the browser is Internet Explorer, stop. On Joomla 4, 5, or 6 that is expected. Send the user to current Edge, Chrome, Firefox, or Safari.
4. If the browser is Safari 15 or older and the layout is the complaint, go to the core bugs table. You are done diagnosing.
5. If every current browser fails the same way, you are not debugging compatibility. Fix the error, the missing file, or the template, then come back.

Step 2: Rule out cache and extensions

1. Open a private window with extensions disabled. Retest the same URL.
2. If the private window is fine, the cause is a cached file or an extension (ad blockers block scripts and fonts, Firefox Enhanced Tracking Protection and Brave Shields block third-party hosts). Clear that browser’s cache for the site. Then clear Joomla’s cache (System → Maintenance → Clear Cache) and any CDN.
3. If the private window is still broken, the site is serving the failure. Continue.

Joomla appends its media version to core asset URLs, and that version changes when you update Joomla or an extension. A hand-edited user.css does not change it, so browsers can keep the old file for days. Clear Joomla cache after CSS edits, and on a CDN purge the CSS path.

Step 3: Read the console, not the homepage

1. Open developer tools in the broken browser. Console and Network.
2. Reload. Copy the first red error. The file name is the extension or the template.
3. On Network, filter CSS and JS. A red row is a 404 or a blocked request. An unstyled page with a 404 on template.css is a path problem, not a rendering engine.
4. Mixed content (HTTPS page calling http:// assets) is blocked hardest by Chrome and Safari. Fix the URLs in the template and in article HTML. Do not tell users to allow insecure content.
5. “Refused to load” or “violates the following Content Security Policy” means the System – HTTP Headers plugin (or the host) set a CSP that the extension does not satisfy. Browsers enforce CSP slightly differently, which is why it can look like a one-browser bug. Fix the policy or the inline script, do not disable CSP site-wide.

Step 4: See if the template is the only broken piece

1. On a staging copy, set the site template to Cassiopeia (System → Site Templates).
2. Retest the broken browser.
3. If Cassiopeia is fine, your template or one of its overrides is the bug. Update it to a build for this Joomla major, or replace it. Joomla 3 templates (Bootstrap 2, IE conditional comments, MooTools menus) will not become compatible by adding a script.
4. If Cassiopeia fails too, the template is not the cause. Look at modules on that page, then at the core bugs table.

Confirm the template prints a viewport tag. Cassiopeia does. A custom index.php that omits it makes phones look “broken in Safari” while the desktop looks fine:

<meta name="viewport" content="width=device-width, initial-scale=1">

Step 5: Disable the extension named in the console

The first console line usually names a file under /media/, /templates/, /modules/, or /plugins/. Disable that extension on staging and reload.

• A menu or slider that calls MooTools or an ancient jQuery will fail in current browsers even when the rest of the page is fine. Background: remove MooTools from Joomla.
• Do not “fix” it by loading jQuery again. Joomla 4, 5, and 6 core UI does not need jQuery. A second copy fights over $ and creates a new one-browser failure.
• HTML5 Shiv and Respond.js were IE8 hacks. They do nothing on Joomla 4+ and add a script current browsers do not need. Remove them if a ten-year-old tutorial put them in the template.
• Page builders and Helix-style frameworks that still ship -moz-, -ms-, and -webkit- prefixed rules from 2015 produce console warnings but rarely break layout. Update the template; do not hand-edit its compiled CSS.
• Custom scripts you added yourself belong in a child template or a proper include, not pasted into index.php: add or remove custom JavaScript in Joomla.

Step 6: Audit modern CSS the template uses

When the template is yours or a child template, check the newer CSS features it relies on. This is the 2026 state of the features that most often produce “works in Chrome, broken in Safari or Firefox” on Joomla sites. Verify current numbers on Can I Use.

Pattern for anything not yet universal:

.hero { min-height: 100vh; }
@supports (height: 100dvh) {
  .hero { min-height: 100dvh; }
}

Step 7: Safari and iOS quirks that are not bugs

Step 8: Fix Safari login separately from CSS

If the page looks right in Safari but login or the administrator session dies, stop comparing stylesheets.

1. Global Configuration → Site → Site URL, and the live host, must be the same scheme and host. https://example.com and https://www.example.com are different cookie hosts. Chrome is more forgiving of the redirect. Safari drops the session.
2. Force one host in the server redirect, then clear cookies and test again.
3. Global Configuration → System → Cookie Domain and Cookie Path: leave blank unless you run subdomains that must share the session.
4. If the Joomla page is inside an iframe on another site, Safari blocks that third-party cookie. Do not embed the login.
5. Session and consent cookies are covered in disable cookies for Joomla visitors.

Step 9: Fix it in a child template, not in core

Joomla 4.1 and newer support child templates. Every browser fix you write belongs there so updates do not erase it.

1. System → Site Templates → Cassiopeia (or your template) → Create Child Template.
2. Add rules to media/templates/site/{child}/css/user.css. Cassiopeia loads user.css automatically after its own CSS.
3. Need to override a core stylesheet? Joomla resolves a relative asset such as template.min.css by looking in media/templates/site/{child}/css/ first and only then in the parent’s folder (HTMLHelper::includeRelativeFiles). A file with the same name in the child wins. No joomla.asset.json edit is needed.
4. Never edit media/vendor/bootstrap, media/templates/site/cassiopeia, or media/system. The next Joomla update replaces them and the “fix” disappears in one browser first, which restarts the whole hunt.

Tested: make Cassiopeia render on Safari 15 from a child template

We inspected the files Joomla 6.0.0 and 6.1.0 ship. Cassiopeia’s template.min.css contains 111 media queries, all in range syntax and none in min-width form. Atum has 118, and media/vendor/bootstrap/css/bootstrap.min.css (Bootstrap 5.3.8) has 81. Cassiopeia does not load the vendor Bootstrap file at all; Bootstrap is compiled into template.min.css, so swapping the vendor file does nothing for Cassiopeia. The fix is to transpile the template CSS.

1. Create the child template (step 1 above). Note its folder name, for example cassiopeia_legacy.
2. On any machine with Node.js, run Lightning CSS against the shipped file with a Safari 15 target:

   npx lightningcss-cli --targets "safari >= 15" --minify 
     media/templates/site/cassiopeia/css/template.min.css 
     -o media/templates/site/cassiopeia_legacy/css/template.min.css

3. Result on Joomla 6.1.0: 111 ranged queries became 111 min-width / max-width queries, file size 247 KB to 251 KB, everything else unchanged. Repeat for template-rtl.min.css if you serve RTL.
4. Clear Joomla cache. Load the site in Safari 15 (BrowserStack macOS Monterey works) and the grid returns.
5. After every Joomla update that changes Cassiopeia, rerun the command. Your child file is never touched by the updater, but it also does not receive core CSS fixes until you regenerate it.

For the administrator, the same approach works with an Atum child template and media/templates/administrator/{child}/css/template.min.css. In practice, updating Safari on the one editor’s Mac is the cheaper fix. For third-party templates that load media/vendor/bootstrap/css/bootstrap.min.css, transpile that file into the child’s css/ folder and change the template’s asset URI to point at it.

Step 10: Retest the supported browsers, in this order

1. Chrome or Edge on desktop (same engine, still check Edge once if the client uses it).
2. Safari on a real Mac or iPhone. Desktop Chrome does not stand in for iOS Safari; on iOS, Chrome and Firefox are WebKit under the hood, so “works in Chrome on iPhone” tells you nothing about Chrome on desktop.
3. Firefox, including ESR if the client is a locked office build.
4. The administrator on each, not only the homepage. Article edit screen included (that is where the Firefox 148 bug shows).

Tools, in order of cost: your own devices and a colleague’s Mac; Safari Technology Preview and Firefox Developer Edition for what is coming next; Playwright (free, runs Chromium, WebKit, and Firefox from one script) for regression screenshots; BrowserStack or LambdaTest when you need a specific old macOS and Safari 15 to confirm the ranged media query case. A paid lab is not the first step, and it will not make Internet Explorer run Joomla 6.

Do not sniff the browser

Joomla’s old browser class, and any template switch based on the user-agent string, will mislabel current Edge, Brave, and in-app webviews. Safari on iPad reports itself as macOS Safari. Serve one template. Fix the CSS with @supports and media features like (hover: none). User-agent hacks are how a site ends up with a broken stylesheet that only one browser ever loads, which then looks exactly like a compatibility bug.

When the honest fix is an upgrade

If the site is Joomla 3 and the goal is “works in current Safari and Chrome”, Protostar and a pile of IE scripts are the wrong project. Move to a Joomla 5 or 6 template built on Bootstrap 5, on staging, then retest. Path notes: Joomla upgrade issues and benefits of Joomla migration. Infyways runs those jumps from $149, with a compatibility audit within 12 hours: Joomla Upgrade Services.

What thinner articles leave out

Key takeaways

1. Joomla 4, 5, and 6 support the current and previous major of Chrome, Edge, Firefox, and Safari. Not Internet Explorer, not Safari 15.
2. A wide screen showing the mobile layout in Safari 15 or older is the ranged media query bug. Update Safari, or transpile template.min.css into a child template. Do not edit core CSS.
3. Firefox 148 and a flickering TinyMCE on Joomla 5.4.3 or 6.0.3 means install the hotfix or update.
4. Same failure in every browser is not a browser bug.
5. Private window first, then the console, then Cassiopeia, then the extension named in the error.
6. Safari login failures are usually the site URL and cookie host.
7. Use @supports, 100dvh, and (hover: none) instead of user-agent sniffing.
8. Put every fix in a child template. Do not add HTML5 Shiv, Respond.js, or a second jQuery.

Frequently asked questions

Which browsers does Joomla support?

For Joomla 4, 5, and 6: the current major version and the one before it of Chrome, Edge, Firefox, and Safari. Internet Explorer is not supported. The old Joomla 3 browser list is not the matrix for current releases.

Why does the Joomla administrator show one column on a Mac in Safari?

Safari 15 and older do not understand the ranged media queries in Joomla 4.4.1 and newer core CSS, so the responsive grid collapses. Update to Safari 16.4 or newer, or use Chrome or Firefox on that Mac.

Why does the article editor keep reloading in Firefox?

Firefox 148 broke TinyMCE in Joomla 5.4.3 and 6.0.3. Install the Firefox 148 TinyMCE hotfix from the Joomla download page or update to 5.4.4 / 6.0.4 or newer.

Why does the site look fine in Chrome and broken in Safari?

Check a private window, then the console. If the layout is the mobile layout on a wide screen, check the Safari version. If only login fails, compare the Global Configuration site URL with the host Safari is using, including www and HTTPS.

Why is the administrator broken in Internet Explorer?

Joomla 4 and newer use Bootstrap 5 and modern JavaScript. IE11 is outside that support. Use Edge or another current browser.

Will HTML5 Shiv or Respond.js fix it?

No. Those scripts patched Internet Explorer 8. They do not fix Joomla 4, 5, or 6, and they should come out of the template.

The layout breaks on phones but not on desktop. Is that a browser bug?

No. If every browser breaks at the same width, it is responsive CSS or a missing viewport tag. If only iOS overflows at the bottom, replace 100vh with 100dvh.

One browser still shows the old design after I changed the template. Why?

That browser cached the CSS. Test in a private window, then clear Joomla cache and the CDN. Editing user.css does not change Joomla’s media version.

Should I load jQuery so older browsers work?

No. Extra jQuery copies cause $ conflicts. Current Joomla does not need jQuery for the core layout.

Can I make Cassiopeia work on Safari 15 without editing core files?

Yes. Transpile media/templates/site/cassiopeia/css/template.min.css with Lightning CSS targeting Safari 15 and save the output as template.min.css inside your child template’s css folder. Joomla loads the child’s copy first. Replacing media/vendor/bootstrap does nothing for Cassiopeia because Bootstrap is compiled into template.min.css.

Does Cassiopeia work in all browsers?

It works in the browsers Joomla supports. Use it as the control. If Cassiopeia is fine and your template is not, fix or replace the template.

Who can fix a template that only fails in one browser?

Infyways traces the console error and upgrades templates that cannot be patched. Request a Joomla upgrade audit.