Category: Joomla

  • UniLogin Joomla Plugin: Email as Username

    UniLogin Joomla Plugin: Email as Username

    Meet Chris, a dedicated Joomla website owner. Chris loves the flexibility and robustness of Joomla for managing his site. However, he noticed a recurring issue: his users struggled to log in because Joomla’s default option required a username.

    Imagine being a regular visitor to a site, eager to log in and access your account, only to realize you’ve forgotten your username.

    Frustrating, right?
    Chris’s users felt the same way. Many times, they would end up resetting their usernames, wasting valuable time and feeling annoyed.

    Chris knew he needed a better solution, one that would allow users to log in with their email addresses, just like most modern platforms.

    The Search for a Solution

    Chris started his search for a plugin that would enable email logins on Joomla. He combed through the Joomla Extensions Directory (JED), hoping to find a perfect match.

    He posted questions on forums, seeking advice from the Joomla community. Unfortunately, his efforts were in vain. None of the available solutions met his requirements or supported the latest Joomla versions.

    Feeling a bit frustrated but not ready to give up, Chris decided to reach out to us for help. He pinged us on Skype, detailing his problem and asking if we could create a custom solution.

    The Birth of UniLogin

    We understood Chris’s predicament immediately. Changing core Joomla files wasn’t an option, as it could lead to issues during updates.

    Instead, we proposed developing a custom authentication plugin that would allow users to log in using either their email address or username. Chris was thrilled with this idea, and thus, the UniLogin plugin was born.

    The development process was smooth. We worked closely with Chris, ensuring every detail was perfect. Once the plugin was ready, we named it UniLogin, symbolizing a unified login experience.

    Implementation and User Experience

    Excited about the new solution, Chris installed the UniLogin plugin on his Joomla website. The installation process was straightforward:

    1. Download and Install: Chris purchased the plugin from the JoomlaX Store for just $20. He then installed it on his Joomla website.
    2. Enable the Plugin: After installation, he enabled the plugin from the Joomla Extensions Manager.
    3. Update Login Text: To ensure clarity for his users, Chris updated the login form text from “Username” to “Email or Username”.

    Here’s how he did it:

    Updating the Login Form Text

    For the Login Form:

    1. Navigate to Extensions > Language(s) > Overrides.
    2. Select your language.
    3. Create a new override.
    4. Search for COM_USERS_LOGIN_USERNAME_LABEL.
    5. Set the override text to “Email or Username”.

    For the Login Module:

    Language override
    1. Go to Extensions > Language(s) > Overrides.
    2. Select your language.
    3. Create a new override.
    4. Search for MOD_LOGIN_VALUE_USERNAME.
    5. Set the override text to “Email or Username”.

    A Happier User Base

    After implementing UniLogin, Chris noticed a significant change. His users no longer struggled with forgotten usernames. The login process became seamless, and user satisfaction soared. Returning customers were particularly happy, as they could now log in with ease, using their email addresses.

    Benefits of UniLogin

    1. Enhanced User Experience: The plugin eliminated the hassle of username resets, making users happier and more satisfied.
    2. Increased Efficiency: The dual login option saved time for users and site administrators alike.
    3. Simple and Effective: UniLogin was easy to install and use, requiring minimal configuration.

    Conclusion

    Chris’s journey from frustration to satisfaction with his Joomla website login process highlights the importance of user-friendly solutions. UniLogin transformed the login experience for his users, ensuring they could access their accounts effortlessly. This plugin is compatible with both Joomla 4 and Joomla 5, making it a versatile solution for various Joomla versions.

    If you’re facing similar login issues on your Joomla site, UniLogin is the perfect solution. It’s time to enhance your user experience and simplify your login process.

    Ready to simplify your login process? Download UniLogin now and give your users the seamless experience they deserve.


    If you’re facing any issues with Joomla and can’t find a solution, don’t hesitate to reach out to us via Skype or our contact form. We are Joomla experts with over 15 years of experience, providing solutions to over 1,000 clients worldwide. Whether it’s troubleshooting, customization, or any other Joomla-related problem, you can be assured that we will find a solution to your problem.

  • How to Create a Link to a Document in Joomla?

    How to Create a Link to a Document in Joomla?

    Creating links to documents in Joomla is a straightforward process. In this guide, we’ll walk you through the steps to link documents using different methods available in Joomla.

    Step 1: Prepare Your Document

    Before you can link a document, you need to ensure it’s uploaded to your Joomla site. You can do this via the Joomla Media Manager or by directly uploading it to your server via FTP.

    Media document upload joomla

    Using Joomla Media Manager:

    1. Navigate to Media Manager:
      • Go to Content > Media.
    2. Create a New Folder (Optional):
      • If desired, create a new folder named docs to organize your documents.
    3. Upload Your Document:
      • Click on Upload.
      • Select your document file (e.g., PDF, DOCX) and upload it.
    4. Get the Document Link:
      • Once the file is uploaded, click the three dots in the top corner of the file.
      • Select the Get Link option. A popup will appear with a Get Link button.
      • Click this button to copy the link to your clipboard for later use.

    Troubleshooting Upload Issues

    If you encounter the error “Unable to upload file or This file type is not supported.,” you can address this issue by adjusting the Media Manager options. Here’s how to do it:

    • Go to the options of the Media Manager and check the configurations as described in the troubleshooting section of this guide.
    Media options joomla
    1. Maximum Size (in MB):
      • Description: This setting specifies the maximum size of a file that can be uploaded via the Media Manager.
      • Current Setting: 10 MB.
      • Usage: Files larger than this size will be rejected during upload. Adjust this value based on your needs and server limitations.
    2. Path to Files Folder:
      • Description: This sets the directory path where non-image files (like documents, audio, video) are stored.
      • Current Setting: images.
      • Usage: You can change this path if you prefer to organize your files in a different directory within your Joomla installation.
    3. Path to Images Folder:
      • Description: This sets the directory path where image files are stored.
      • Current Setting: images.
      • Usage: Similar to the files folder, you can change this to organize your images in a different directory.
    4. Allowed Extensions:
      • Description: This is a comma-separated list of file extensions that are allowed to be uploaded via the Media Manager.
      • Current Setting: bmp,gif,jpg,jpeg,png,webp,ico,mp3,m4a,mp4a
      • ogg,mp4,mp4v,mpeg,mov,odg,odp,ods,odt,pdf,png,ppt,txt,xcf,xls,csv.
      • Usage: Ensure that all required file types for your website are included in this list to prevent upload issues.
    5. Check MIME Types:
      • Description: This toggle ensures that the file’s MIME type is checked against the allowed MIME types list.
      • Current Setting: Enabled (Yes).
      • Usage: This adds an extra layer of security to verify the file type being uploaded matches its MIME type.
    6. Legal Image Extensions (File Types):
      • Description: This is a list of image file extensions that are legally allowed to be uploaded.
      • Current Setting: bmp,gif,jpg,png,jpeg,webp.
      • Usage: Defines which image formats are permissible for upload.
    7. Legal Audio Extensions (File Types):
      • Description: This is a list of audio file extensions that are legally allowed to be uploaded.
      • Current Setting: mp3,m4a,mp4a,ogg.
      • Usage: Defines which audio formats are permissible for upload.
    8. Legal Video Extensions (File Types):
      • Description: This is a list of video file extensions that are legally allowed to be uploaded.
      • Current Setting: mp4,mp4v,mpeg,mov,webm.
      • Usage: Defines which video formats are permissible for upload.
    9. Legal Document Extensions (File Types):
      • Description: This is a list of document file extensions that are legally allowed to be uploaded.
      • Current Setting: odg,odp,ods,odt,pdf,ppt,txt,xcf,xls,csv.
      • Usage: Defines which document formats are permissible for upload.
    10. Ignored Extensions:
      • Description: This is a list of file extensions that should be ignored during the upload process.
      • Current Setting: Empty.
      • Usage: Use this to specify any file types that should be excluded from upload considerations.
    11. Legal MIME Types:
      • Description: This is a list of MIME types that are legally allowed to be uploaded.
      • Current Setting: A comprehensive list of MIME types including image/jpeg, image/gif, image/png, image/bmp, image/webp, audio/ogg, audio/mpeg, video/mp4, application/msword, application/excel, etc.
      • Usage: This ensures that only files with these MIME types can be uploaded, adding a layer of security to prevent malicious uploads.

    These settings collectively manage the types of files that can be uploaded to your Joomla site, their sizes, and their storage locations. Adjusting these configurations can help resolve common upload issues and ensure your site operates smoothly.

    Alternately you can upload file through FTP if you have FTP access.

    Using FTP:

    • Connect to your website’s server using an FTP client.
    • Upload your document to a directory within your Joomla installation (e.g., images/docs).

    Step 2: Create a Menu Item or Article

    To create a link to your document, you can either insert it into an article or create a direct menu link.

    Inserting a Link in an Article

    1. Create or Edit an Article:
      • Go to Content > Articles > Add New Article (or open an existing article).
      • In the editor, type the text you want to link (e.g., “Download PDF”).
    2. Link the Text to Your Document:
      • Highlight the text you want to link.
      • Click on the Insert/Edit Link icon (usually represented by a chain link).
      • In the URL field, enter the path to your document (e.g., images/docs/yourfile.pdf).
      • Set the Target to _blank if you want the document to open in a new tab.
      • Click Insert.

    Creating a Direct Menu Link

    1. Create a New Menu Item:
      • Navigate to Menus > [Your Menu] > Add New Menu Item.
      • In the Menu Item Type field, click on External URL.
    2. Link to Your Document:
      • In the Link field, enter the full URL of your document (e.g., http://yourwebsite.com/images/docs/yourfile.pdf).
      • Set other parameters like Menu Title and Target Window.
      • Click Save & Close.

    Best Practices for Linking Documents

    • Keep URLs Short and Descriptive: Ensure your document URLs are concise and meaningful to improve readability and SEO.
    • Use Clear Link Text: The text for your links should clearly describe the document. For example, use “Download Annual Report” instead of “Click Here”.
    • Organize Your Documents: Use folders and subfolders to keep your documents organized, making them easier to manage.

    Conclusion

    Linking documents in Joomla is a simple yet powerful way to provide resources to your site visitors. Whether you’re inserting links into articles or creating direct menu links, Joomla offers flexible options to meet your needs. By following the steps outlined above, you can enhance your site’s functionality and provide valuable content to your audience.

    Related Joomla guides

    Need hands-on help? See our Joomla development services.

  • Joomla CAPTCHA in Joomla 5 and 6.2: Built-in Proof of Work, reCAPTCHA v3 and More (Tested)

    Joomla CAPTCHA in Joomla 5 and 6.2: Built-in Proof of Work, reCAPTCHA v3 and More (Tested)

    Updated 15 October 2026 · By Abhilash Sahoo, Founder, Infyways

    Quick answer:

    • Joomla 6.1 and later (including Joomla 6.2, the latest version) include a built-in CAPTCHA – Proof of Work plugin. It needs no API keys. Go to System → Global Configuration → Site → Default Captcha, choose it, and save.
    • Joomla 5 has no CAPTCHA plugin in core. Install one from the JED that uses Joomla’s Captcha API (reCAPTCHA v3, Turnstile, Friendly Captcha and others), enter its keys, and select it as the Default Captcha.

    Either way, the CAPTCHA then protects registration, password reset, contact and front-end article forms. Login forms have no core CAPTCHA field.

    I installed a fresh Joomla 6.2.0 site (PHP 8.4) and a Joomla 5.4.10 site to check every step below. I filled in the forms in Chrome and sent bot-style requests with curl. Images marked “real output” show what happened. Background: Joomla’s announcement Built-in Captcha coming to Joomla core.

    Does Joomla have a built-in CAPTCHA?

    Version Core CAPTCHA What I found
    Joomla 4 reCAPTCHA v2 and Invisible reCAPTCHA plugins Need Google keys
    Joomla 5.4.10 None plugins/captcha/ contains only index.html; Default Captcha shows “None Selected”
    Joomla 6.1 / 6.2 CAPTCHA – Proof of Work (ALTCHA library) Enabled on a fresh install, but Default Captcha is still “None”, so you must select it

    The reCAPTCHA plugins were removed during the Joomla 5 series. Joomla’s team gave two reasons: they were outdated, and they depended on Google. On a site upgraded from Joomla 4, a leftover reCAPTCHA plugin can still appear in the list without working. Replace it rather than trust it.

    Joomla 5 has no core CAPTCHA plugin and needs an extension

    Which CAPTCHA should I use for Joomla?

    Comparison of Joomla CAPTCHA options in 2026
    Option Joomla Account / keys Visitor experience Good for
    CAPTCHA – Proof of Work (core) 6.1+ None; no external service Checkbox that solves itself Most sites on Joomla 6; privacy-sensitive sites
    reCAPTCHA v3 plugin (e.g. Sharky’s, free on the JED) 4 / 5 / 6 Google keys Invisible, score-based Joomla 5 sites already using Google
    Invisible reCAPTCHA plugin (e.g. Nicholas Dionysopoulos’s) 4 / 5 / 6 Google keys Badge, occasional challenge Replacing Joomla 4’s old core plugin
    Turnstile, Friendly Captcha, hCaptcha plugins Check each listing Vendor keys Widget, usually no puzzle Sites that avoid Google

    Choose a plugin built on Joomla’s Captcha API. It then appears in the Default Captcha list and works with every core form. Before you rely on Google: the invisible plugin’s documentation says keys must now live in a Google Cloud project, with a limited free tier. Joomla’s announcement says reCAPTCHA now asks for a payment method. Check Google’s current terms.

    How do I enable the Proof of Work CAPTCHA in Joomla 6.2?

    Setting up the built-in Proof of Work CAPTCHA in Joomla 6.2
    1. Go to System → Global Configuration → Site → Default Captcha, choose CAPTCHA – Proof of Work, and save. On my fresh 6.2 install, the only options were “- None Selected -” and this plugin.
    2. Optionally, adjust it under System → Plugins → CAPTCHA – Proof of Work:
      • Difficulty: Easy, Moderate (the default), Hard, or Custom with a Maximum Number.
      • Automatic Solution: off, when the field gets focus (the default), on page load, or on submit.
      • Expiration: 1 minute, 5 minutes (the default), 10 minutes or 1 hour.
    3. Log out and test the registration or contact form.
    Joomla 6.2 CAPTCHA - Proof of Work plugin settings screen

    Does the Proof of Work CAPTCHA actually stop bots?

    It doesn’t try to prove the visitor is human. The browser has to spend computing time on a hashing task (SHA-512 in the 6.2 source) before the form is accepted. That cost adds up for spam sent in bulk. Here’s what I measured:

    Tested Joomla 6.2 Proof of Work CAPTCHA solve times and bot submission rejected
    • Real browser: solved in 0.04–0.09 s on Easy, 0.14–0.25 s on Moderate and about 0.43 s on Hard (3 runs each, headless Chrome on a server CPU). Each registration went through. Phones will be slower.
    • Bot without a solution: a direct POST to task=registration.register returned “Invalid field: Captcha”, and no user was created.
    • Replays: each challenge key is stored in the session and cleared once it’s used, so a solution can’t be reused (from the 6.2 source).

    To be honest about the limits: a determined bot running a real browser can solve the task too, just more slowly. Joomla’s announcement mentions plans to raise the difficulty for repeat requests from the same IP address. The 6.2.0 source doesn’t include that yet. For heavy spam, combine it with the steps in the next section.

    Which Joomla forms use the CAPTCHA?

    Joomla core forms that support a CAPTCHA field
    Form Where to turn it on
    User registration, forgot username, password reset Users → Options → User Options → Captcha (or leave “Use Default”)
    Contact form Contacts → Options → Form tab → Allow Captcha on Contact
    Front-end article submission Articles → Options → Editing Layout → Allow Captcha on submit
    Login No core CAPTCHA field. Use strong passwords, MFA and rate limiting instead
    Third-party forms (RSForm, Convert Forms and so on) That extension’s own settings, if it supports Joomla’s Captcha API

    I checked this list against the type="captcha" fields in the Joomla 5.4.10 and 6.2.0 form files. Both versions have the same five forms.

    How else can I stop Joomla form spam?

    • Turn off what you don’t use. If visitors don’t need accounts, set Allow User Registration to No (Users → Options).
    • Require activation (Self or Administrator) so bot accounts never become active.
    • Block repeat offenders at the server with .htaccess or your firewall (see our Joomla .htaccess guide).
    • Keep Joomla and form extensions updated. Spam often arrives through an old form extension. See the Joomla security guide.

    Is the CAPTCHA GDPR-friendly and accessible?

    The core Proof of Work plugin runs entirely on your server and the visitor’s browser. There are no API keys and no external service. Joomla’s announcement highlights this, and it also calls the method accessible, because there’s no image or audio puzzle. With Google or other hosted CAPTCHAs, the visitor’s browser contacts the vendor, so your cookie and privacy notices may need to mention it. See disabling cookies for visitors and our European Accessibility Act guide.

    Troubleshooting

    Symptom Cause Fix
    Default Captcha only shows “None Selected” No CAPTCHA plugin installed or enabled Joomla 6: enable CAPTCHA – Proof of Work. Joomla 5: install a plugin
    CAPTCHA enabled but not on the form Component set to “None”, or the form isn’t a core form Check each component’s Options; check the third-party form’s settings
    Widget area is blank The plugin’s JS didn’t load (blocked by CSP, wrong live_site, or a JS optimiser) Check the browser console; exclude the CAPTCHA script from minify/defer tools
    “Invalid field: Captcha” for real users Solution expired, or the session was lost (cache, cookies) Raise Expiration; exclude form pages from page caching
    Old reCAPTCHA plugin listed but broken after an upgrade Leftover Joomla 4 plugin Install a maintained plugin, select it, and disable the old one
    reCAPTCHA “Invalid domain for site key” Domain missing in Google’s console Add the domain, including staging
    Spam still arrives The spam comes through a form without a CAPTCHA, or from human spammers Find which form it comes from; add moderation, activation or rate limits
    Form slow on phones Difficulty set too high Go back to Moderate or Easy

    FAQs

    Does Joomla 5 have a built-in CAPTCHA?

    No. Joomla 5.4.10 ships no CAPTCHA plugin. Install a plugin that uses Joomla’s Captcha API, or upgrade to Joomla 6.1 or later.

    Is the Joomla 6 CAPTCHA turned on automatically?

    The plugin is enabled on a fresh install, but the Default Captcha is “None”. You have to select it in Global Configuration.

    Do I need Google keys for the Joomla 6 CAPTCHA?

    No. The Proof of Work plugin uses the ALTCHA library and runs without any external service.

    Can I still use reCAPTCHA on Joomla 5 or 6?

    Yes, with a third-party plugin and Google keys. Check Google’s current pricing and project requirements first.

    Which difficulty should I choose?

    Start with Moderate, the default. It took about 0.15 s in my tests. Use Hard only if spam keeps getting through, and test on a phone.

    Why doesn’t my login form show a CAPTCHA?

    Joomla’s core login form has no CAPTCHA field. Protect logins with strong passwords, multi-factor authentication and server-level rate limiting.

    Can I use a different CAPTCHA for the contact form?

    Yes. Each component’s Options can override the global Default Captcha.

    Will page caching break the CAPTCHA?

    It can. The challenge is tied to the visitor’s session, so a cached copy of the page may serve an old challenge. Exclude registration and contact pages from page caching.

    Is a CAPTCHA enough to stop spam?

    It stops most bulk bots. Combine it with account activation, turning off unused forms and keeping your extensions updated.

    Can you set this up for me?

    Yes. We set up CAPTCHAs and clean up spam as part of Joomla support and maintenance, and we move Joomla 5 sites to 6 with our Joomla upgrade service. Read more about Joomla 6.

  • Basic Search to Smart Search in Joomla 5

    Basic Search to Smart Search in Joomla 5

    Do you know that the com_search is not available in Joomla 5?

    If you’re planning to upgrade from Joomla 4.4 to Joomla 5.0, there’s an important step you shouldn’t overlook. The com_search component is no longer supported in Joomla 5. To ensure a hassle-free upgrade, it’s recommended to uninstall com_search beforehand. In this post, we’ll guide you through this process and introduce you to the enhanced features of com_finder (Smart Search) in Joomla 5.

    Goodbye, Search (com_search)

    For years, Joomla users have relied on the com_search component to power their website’s search capabilities. It was straightforward and got the job done. But as with all technology, change is inevitable. With the release of Joomla 5, com_search has been phased out, signaling the end of its journey.

    Hello, Smart Search (com_finder)

    Joomla 5 introduces us to com_finder, better known as Smart Search. It’s not entirely new; Joomla veterans might remember it co-existing with com_search in earlier versions. But now, it stands alone as the default search solution in Joomla 5. Smart Search boasts a range of improvements:

    • Advanced Indexing: Smart Search creates a detailed index of all content, making search results more accurate.
    • Filtering Options: Users can narrow down their search results using various filters, enhancing user experience.
    • Extensible Plugins: With a rich array of plugins, you can customize Smart Search to cater specifically to your site’s needs.

    Search vs Smart Search

    Functionality and Complexity

    • com_search: Provides a straightforward search function. It allows users to query for content but may not offer refined results.
    • com_finder (Smart Search): Offers an advanced and flexible search system that enables users to filter their search results and allows for indexing, making search results more relevant and accurate.

    Integration with Extensions

    • com_search: Uses plugins that directly query the database for results. This might cause more database load, especially for large sites.
    • com_finder: Uses an indexer that pre-gathers content from the site. This reduces the direct database load during a search, providing quicker search results.

    Search Flexibility

    • com_search: Offers basic search capabilities with limited options for refining or filtering search results.
    • com_finder: Allows users to apply various filters and facets to narrow down their search, making it easier to find precise content.

    System Existence

    • com_search and com_finder coexisted in Joomla versions since 2.5. However, as Joomla evolves, there is a push towards adopting the more advanced Smart Search (com_finder), suggesting it might be the future direction of search in Joomla.

    Search Indexing

    • com_search: Doesn’t have its own indexing system; it pulls content directly from the database during each search query.
    • com_finder: Utilizes an indexing system where content is indexed beforehand. This not only speeds up search results but also ensures that the search is comprehensive, including all aspects of the site’s content.

    Both systems have their merits, but for a more advanced, efficient, and comprehensive search experience on a Joomla website, com_finder (Smart Search) is the recommended choice.

    Smart Search & Third Party Components

    Smart search

    Joomla’s Smart Search (com_finder) is designed to be extensible and can work with third-party components. This is achieved through Smart Search plugins. Here’s how it functions:

    1. Plugins for Indexing: For Smart Search to index and search content from third-party components, there needs to be a specific Smart Search plugin for that component. Joomla core comes with several Smart Search plugins for its core components.
    2. Third-Party Extensions: Many third-party Joomla extension developers provide their own Smart Search plugins to ensure their components’ content can be indexed and searched using Smart Search. When you install such a third-party component, it’s common for it to come with its Smart Search plugin which you can enable to integrate the component’s content into Smart Search.
    3. Custom Plugins: If a third-party component doesn’t come with a Smart Search plugin, it’s possible for developers to create a custom Smart Search plugin for that component. This involves coding a plugin that tells Smart Search how to index the component’s content.
    4. Filters and Advanced Search: Apart from basic content indexing, Smart Search plugins can also provide advanced functionality, such as custom filters. This allows users to refine their search results based on specific criteria related to the third-party component.

    Conclusion

    Joomla’s transition from com_search to Smart Search (com_finder) in Joomla 5 represents its dedication to enhancing user experience with improved search capabilities. Smart Search offers not only faster and more precise results but also integrates effortlessly with third-party components. As com_search fades, Smart Search emerges as the future of Joomla’s search functionality, promising users a more efficient and enriched web experience.

    Related Joomla guides

    Need hands-on help? See our Joomla development services.

  • Schema in Joomla 5 & 6: Core Schema.org Plugins Guide (2026)

    Schema in Joomla 5 & 6: Core Schema.org Plugins Guide (2026)

    Short answer: Joomla 5 and 6 include Schema.org structured data in core. Enable the System – Schema.org plugin plus the type plugins you need (BlogPosting, Book, Event, JobPosting, Organization, Person, Recipe), set your site’s Organization or Person details in the system plugin, then pick a schema type on the Schema tab of each article. Check the result with Google’s Rich Results Test. No extension is needed for the basics.

    Do you know that Joomla 5 just took a massive leap in the SEO game? With its launch on 17th October 2023 , they’ve integrated Schema directly into their core plugins. This isn’t just a minor tweak—it’s a full-blown strategy to supercharge your site’s visibility and SEO prowess.

    Website’s search rankings are not just about keywords anymore. Let me show you how Joomla 5 is making structured data simpler and more impactful than ever.

    Ready to dominate those search results? Let’s go!

    What is Schema Markup?

    Schema markup, a form of microdata, is added to the HTML of a webpage to define exactly what it contains. Search engines then use this data to display enhanced snippets in search results. The end result? Improved visibility and a higher click-through rate.

    How to Integrate Schema in Joomla 5?

    If you have upgraded your website from Joomla 4.4 to Joomla 5 or installed a new version of Joomla 5, in the plugin section of the website you will find the list of plugin available for use by default. You will find 7 different type of Schema plugins and a System Schema plugin.

    Schema.org plugins

    So, to use the plugins into your Joomla article or other components that support Schema the plugin must be enabled.

    • System – Schema.org
    • Schema.org – BlogPosting
    • Schema.org – Book
    • Schema.org – Event
    • Schema.org – JobPosting
    • Schema.org – Organization
    • Schema.org – Person
    • Schema.org – Recipe

    These plugins excluding the System – Schema.org have the same configuration as shown in the screenshot.

    Schema plugin options

    The plugins have two options.

    • Allowed Extensions: If you specify certain extensions (components) here, then the schema integration will only be applied to those selected extensions. For instance, if you only want the “BlogPosting” schema to be applied to articles from the “Content” component and not to other components like “Events” or “Products”, you can select the “Content” extension in the “Allowed Extensions” dropdown.
    • Forbidden Extensions: This is the opposite of “Allowed Extensions”. Any extension you select here will be excluded from schema integration, regardless of what’s chosen in the “Allowed Extensions”. For example, even if you’ve allowed the “Content” extension in the previous setting, but then you add it to the “Forbidden Extensions”, the schema will not be applied to the “Content” component.

    If you’re not in the mood to dive deep into configurations, just let it be.

    Now, lets start setting up the schema for a Joomla article. To do that open a existing Joomla article or create a new article. You will now find a new tab called “Schema” in the edit article page.

    Joomla article schema

    Click on the Schema Tab to start setting up the Schema for the particular article. You will find the Schema Type Set to None. Lets understand the different type of schema and start configuring.

    Schema type joomla article

    Types of Schema Supported in Joomla 5

    As I have mentioned that Joomla 5 supports 7 different type of Schemas. Lets discuss all the schema and its attributes one by one.

    BlogPosting

    Blog posting schema joomla5

    When you select “BlogPosting” for the Schema Type in Joomla 5, it provides a series of fields tailored to the attributes commonly associated with blog posts. Here’s a breakdown of what each section represents:

    1. Image: This allows you to select an image that represents the blog post. This image will be used in structured data, which can be displayed in rich results on search engines.
    2. Headline: This should be the main title or headline of your blog post.
    3. Description: A brief summary or overview of what the blog post is about.
    4. Author: This section provides fields related to the author of the blog post:
      • Type: The type of entity the author is, commonly set to “Person”. There might be other options like “Organization” depending on your Joomla setup.
      • Name: The name of the author.
      • Url: A link to the author’s personal website or profile page.
      • Email: The author’s email address.
      • Address: If necessary, you can provide location details of the author, including:
        • Locality: City or region.
        • Postal Code: Postal or ZIP code.
        • Street Address: Exact street address.
    5. Date Published: The date when the blog post was first published.
    6. Date Modified: The date when the blog post was last updated or modified.
    7. Generic Field: This could be a customizable field where you can add additional structured data attributes that might not be covered by the default options.

    Book

    Book schema joomla5

    Upon Selecting “Book” for the Schema Type in Joomla 5, it provides the following set of fields tailored to the attributes commonly associated with books. The details are as follows.

    1. Title: The title of the book.
    2. Author: The name of the book’s author. You can provide additional details like URL, email, and address for the author as well, similar to the “BlogPosting” schema.
    3. Date Published: The date the book was published.
    4. Abridged: An option to specify whether the book is an abridged version or not. Abridged books are shortened versions, often cutting out non-essential parts to make the content more concise.
    5. Book Edition: Details about the specific edition of the book, if applicable. For example, “2nd Edition” or “Revised Edition”.
    6. Book Format: The format in which the book is available. This could be options like “Hardcover”, “Paperback”, “eBook”, etc.
    7. Illustrator: If the book contains illustrations, this section allows you to provide details about the illustrator, similar to the author details. This includes:
      • Name: The illustrator’s name.
      • Url: A link to the illustrator’s website or profile.
      • Email: The illustrator’s email address.
      • Address: Location details of the illustrator:
        • Locality: City or region.
        • Postal Code: Postal or ZIP code.
        • Street Address: Exact street address.
    8. ISBN: The International Standard Book Number, a unique identifier for books.
    9. Number of Pages: The total number of pages in the book.
    10. Generic Field: Like in the “BlogPosting” schema, this is a customizable field where you can add any additional structured data attributes related to the book that might not be covered by the default options.

    Event

    Event schema joomla5

    Event” for the Schema Type in Joomla 5 provides a set of fields designed to capture information related to events. Here’s a breakdown of the fields provided:

    1. Image: A field where you can upload or select an image that represents the event.
    2. Name: The official name or title of the event.
    3. Description: A brief overview or summary of the event.
    4. Aggregate Rating: This section is for the overall rating or feedback given to the event, if applicable.
      • Rating Value: The average rating value.
      • Review Count: The number of reviews or ratings the event has received.
    5. Start Date: The commencement date and time of the event.
    6. Location: The venue or place where the event is scheduled to take place.
      • Name: The name of the location or venue.
      • Address: The address details of the location, which include:
        • Locality: City or region.
        • Postal Code: Postal or ZIP code.
        • Street Address: Exact street address.
    7. Organizer: Information about the individual or organization responsible for organizing the event.
      • Type: Whether the organizer is a person, organization, or another entity type.
      • Name: The name of the organizer.
      • Url: A link to the organizer’s website or profile.
      • Email: Contact email for the organizer.
      • Address: Location details of the organizer, similar to the location address fields.
    8. Generic Field: A customizable field where you can add any additional structured data attributes related to the event that might not be included in the default options. This section consists of a “Title” and “Value” pair.

    Organization

    Organization schema joomla5

    Organization” for the Schema Type in Joomla 5, it provides a set of fields tailored to capture information related to organizations. Here’s a detailed description of the fields you see:

    1. Name: The official name of the organization.
    2. Logo: A field to upload or select the organization’s logo, providing a visual representation of the entity.
    3. URL: The official website URL or main online presence of the organization.
    4. Email: The primary contact email for the organization.
    5. Address: The physical address of the organization, broken down into:
      • Locality: The city or locality where the organization is situated.
      • Postal Code: The postal or ZIP code for the location.
      • Street Address: The detailed street address of the organization.
    6. Generic Field: A customizable section to accommodate any additional structured data attributes related to the organization that might not fit into the predefined categories. This section provides a “Title” and “Value” pair for custom entries.

    Person

    Person schema joomla5
    1. Name: The full name of the person.
    2. URL: The personal website or main online presence of the individual, such as a blog or portfolio.
    3. Email: The primary contact email for the person.
    4. Address: The physical residence or contact address of the person, further broken down into:
      • Locality: The city or locality where the person resides.
      • Postal Code: The postal or ZIP code for the location.
      • Street Address: The detailed street address.
    5. Generic Field: This is a flexible section that allows you to include any additional structured data attributes related to the person that might not fit into the predefined categories. You can enter a custom “Title” and its corresponding “Value” in this section.

    Recipe

    Recipe schema joomla5

    Recipe Schema Type within Joomla 5 allows you to input structured data specifically tailored for recipes. Here’s an overview of the fields provided:

    1. Image: This is where you can upload or link to an image representing the recipe.
    2. Title: The name of the recipe.
    3. Author: The individual or entity that created or is credited with the recipe.
    4. Cook Time: The time it takes to cook the dish. You can specify the duration in hours and minutes.
    5. Date Published: The date on which this recipe was originally published.
    6. Description: A brief overview or summary of the recipe.
    7. Cooking Method: The technique used for cooking the dish (e.g., baking, frying, steaming).
    8. Preparation Time: The amount of time it takes to prepare the ingredients and the dish before cooking. Again, you can specify the duration in hours and minutes.
    9. Category: The type or classification of the dish (e.g., dessert, main course, appetizer).
    10. Cuisine: The culinary style or tradition the recipe belongs to (e.g., Italian, Chinese, American).
    11. Instructions: Step-by-step directions on how to prepare and cook the dish.
    12. Yield: The quantity or servings the recipe produces.
    13. Suitable for Diet: Any specific dietary considerations the recipe adheres to (e.g., vegan, gluten-free).
    14. Ingredients: A list of all the ingredients required for the recipe.
    15. Nutrition: Detailed nutritional information about the dish, including:
      • Calories
      • Carbohydrate
      • Cholesterol
      • Fat
      • Fibre
      • Protein
      • Saturated Fat
      • Sodium
      • Sugar
      • Trans Fat
      • Unsaturated Fat
      • Serving Size
    16. Generic Field: Similar to the person schema, this flexible section lets you include any additional structured data attributes related to the recipe not covered by the predefined categories.

    JobPosting

    Jobposting schema joomla5

    The “JobPosting” Schema Type within Joomla 5 allows you to input structured data tailored for job listings. This helps search engines to better interpret and display content related to job postings. Here’s an overview of the fields provided:

    1. Title: The title or name of the job position being advertised.
    2. Description: A brief overview or summary of the job position, its responsibilities, and other key details.
    3. Identifier: This section allows you to input a unique identifier for the job posting, with both a “Name” for the type of identifier and a “Value” for the actual identifying information.
    4. Date Posted: The date the job listing was originally published.
    5. Valid Through: The expiration date of the job listing after which it may no longer be valid.
    6. Description of the Job Location: Additional details about the job location.
    7. Employment Type: The nature of the job in terms of its duration or commitment (e.g., Full-Time, Part-Time, Contract).
    8. Date to Start: The date on which the selected candidate is expected to commence their duties.
    9. Hiring Organization: Information about the organization hiring for the position:
      • Type: Specifies that it’s an organization.
      • Title: The name of the organization.
      • URL: A link to the organization’s website.
      • Logo: A link or upload area for the organization’s logo.
    10. Email: The contact email address related to the job listing.
    11. Address: This section captures detailed address information for the hiring organization, including:
      • Locality: City or town.
      • Postal Code: ZIP or postal code.
      • Street Address: The exact street address of the organization.
    12. Job Location: Information about where the job will be based, similar to the address fields mentioned above but specific to the job’s location.
    13. Base Salary: Details about the salary offered for the position:
      • Currency: The currency in which the salary is offered.
      • Amount: Specific details about the salary amount, with fields for the maximum, minimum, and a specific value. There’s also an option to specify the unit of the salary, such as per hour, per month, etc.
    14. Generic Field: This flexible section lets you include any additional structured data attributes related to the job posting not covered by the predefined categories.

    Now that you have learnt integrating the schema plugin, time to test it.

    Testing the schema Markup

    Rich results test

    Follow these steps, and you’ll be good to go:

    1. Grab Your URL: First things first, copy the URL of the page you want to test.
    2. Head to the Testing Tool: Visit Google’s Rich Results Test or Schema Markup Validator
    3. Paste & Run: Drop your URL into the search bar and hit ‘Test URL’.
    4. Review the Results: Once the test runs, you’ll see if your markup is valid or if there are any issues you need to tackle.
    Schema markup validator

    Absolutely! Let’s break it down in a style reminiscent of Neil Patel:


    Schema.org vs. Rich Snippets: What’s the difference?

    Alright, here’s the thing. When you’re diving deep into the SEO world, you’ll come across terms like Schema.org and Rich Snippets. At first glance, they might seem like the same thing, but they play distinct roles in the SEO game. Let’s demystify this:

    Schema.org:

    • What Is It? Think of Schema.org as a library. It’s a standardized collection of schemas, or, in simpler terms, a set of codes you can add to your website. This code helps search engines understand your content better. It’s like giving them a guidebook to your site.
    • Why Use It? By implementing Schema.org markup, you’re giving search engines a clearer picture of what’s on your page. Whether it’s a recipe, product, or event, you’re spelling it out.

    Rich Snippets:

    • What Is It? Rich Snippets are the visual result of using that Schema.org markup. When you search something on Google, sometimes you see results with star ratings, images, or product prices. Those are Rich Snippets in action!
    • Why Use Them? They make your search result stand out! It’s like putting on a fancy outfit for a party. You get more clicks, better engagement, and, ultimately, higher traffic.

    In a Nutshell: Schema.org is the behind-the-scenes code, while Rich Snippets are the front-and-center stars of the show in search results.

    Wrapping It Up

    Joomla 5’s Rich Snippets isn’t just an update; it’s a revolution. It streamlines structured data optimization, paving the way for a stellar search experience. Expect a surge in your site’s traffic and engagement. So, if you’re all about amplifying your online clout, it’s time to harness the might of Rich Snippets in Joomla 5. Let’s elevate your website game!

    Related guides and services

    Frequently asked questions

    Does Joomla 5 have built-in schema markup?

    Yes. Joomla 5 added a System – Schema.org plugin and type plugins (BlogPosting, Book, Event, JobPosting, Organization, Person, Recipe) to core. Joomla 6 continues to include them.

    How do I add schema to a Joomla article?

    Enable the System – Schema.org plugin and the type plugin you need, then open the article, go to the Schema tab, choose the type and fill in the fields.

    Do I still need a schema extension?

    Not for the core types. An extension can help if you need types core does not cover, such as FAQPage or Product, or bulk settings.

    Does schema improve Google rankings?

    Schema helps search engines understand a page and can make it eligible for rich results, but it is not a direct ranking factor. Content and links matter more.

    How do I test Joomla schema markup?

    Use Google’s Rich Results Test for rich-result eligibility and the Schema Markup Validator (validator.schema.org) for general validity.

  • Upgrading from Joomla 4.4.x to Joomla 5: A Comprehensive Guide

    Upgrading from Joomla 4.4.x to Joomla 5: A Comprehensive Guide

    Joomla, a renowned open-source content management system (CMS), has consistently been the preferred choice for numerous web developers and site owners. With the much-anticipated release of Joomla 5 on 17th October 2023, the community is abuzz with excitement. This guide delves deep into the reasons, benefits, and the step-by-step process of upgrading from Joomla 4.4.x to Joomla 5.

    Joomla 5 Release Date

    Joomla 5 was officially released on 17th October 2023. This release marked a significant milestone in Joomla’s journey, introducing a host of new features, improvements, and security enhancements. The release was eagerly awaited by the Joomla community, and since its launch, it has been widely adopted by web developers and site owners worldwide.

    Few Important Things to Know

    The 5.0.0 update notification will only show up if you have upgraded your Joomla to 4.4.0
    The 5.0.0 update notification will only show up if you have upgraded your Joomla to 4.4.0

    The transition from Joomla 4.4.x to 5.x is an upgrade, not a migration. This is great news for two primary reasons:

    1. Joomla 4 (J4) extensions that have removed all deprecated code and use up-to-date Joomla code will function in Joomla 5 (J5).
    2. Most other extensions will operate with the new Behaviour – Backward Compatibility Plugin enabled.
    Behaviour backward compatibility joomla

    What to Do If You Don’t See the Joomla 5 Upgrade Notification?

    There might be instances where the Joomla 5.0.0 upgrade notification doesn’t appear in the System or Home Dashboard of your administrator panel. Don’t worry; a minor adjustment can help you view the notification and proceed with the upgrade. Here’s how:

    Global configuration joomla update
    1. Navigate to the Global Configuration in your Joomla administrator panel.
    2. On the left side, click on the Joomla Update menu.
    3. In the ensuing screen, locate the Update Source tab.
    4. Change the Update Channel from its default setting to Joomla Next.
    5. Save your changes.

    Upon saving, you’ll be redirected to https://YOUR_DOMAIN/administrator/index.php?option=com_joomlaupdate.

    Why should I Upgrade Joomla 4.4 to Joomla 5?

    With the introduction of Joomla 5, the question arises: should you upgrade from Joomla 4.4 to Joomla 5? Here’s a comprehensive look at the reasons to consider this upgrade.

    1. Advanced Features and Functionalities

    Joomla 5 brings a plethora of advanced features that make content management even more efficient. Whether you’re looking to build a personal blog, an e-commerce site, or a community portal, Joomla 5 offers unlimited possibilities to cater to your specific needs.

    2. Ease of Use

    One of the primary reasons Joomla has been chosen by many is its ease of use. The CMS is designed to be user-friendly, even for those without extensive technical knowledge. With Joomla 5, this user experience is further enhanced, allowing you to manage your site’s content with minimal effort.

    3. Award-Winning CMS

    Joomla’s reputation as an award-winning CMS is well-deserved. Over the years, it has bagged numerous accolades, including the “Best Free CMS” and “Best Open Source CMS” by the 2021 CMS Critic Awards. Such recognition is a testament to Joomla’s commitment to excellence and innovation.

    4. Robust Community Support

    Joomla boasts a vibrant community of volunteers, developers, and enthusiasts. This community-driven approach ensures that you have access to extensive support, be it in the form of tutorials, forums, or plugins. With over 109,088 members and growing, the Joomla forum is a treasure trove of knowledge and expertise.

    5. Enhanced Security

    Joomla 5 places a strong emphasis on security. With regular updates and quick responses to potential security breaches, you can be assured that your website is in safe hands. Moreover, Joomla ensures valid HTML and CSS, further enhancing the security and integrity of your site.

    6. Flexibility with Extensions

    Joomla 5 offers a wide range of extensions, including components, modules, plugins, and templates. These tools provide added functionality to your website, allowing you to customize it according to your preferences. Whether you’re looking for specific content management solutions or design templates, Joomla 5 has got you covered.

    7. Future-Proofing Your Website

    Upgrading to Joomla 5 ensures that your website is equipped with the latest technologies and features. As the digital landscape evolves, it’s crucial to have a CMS that can adapt and grow with the times. Joomla 5 offers just that, ensuring your website remains relevant and competitive.

    8. Seamless Upgrade Process

    Unlike previous versions, upgrading from Joomla 4.4.x to 5.x is straightforward. Joomla has made significant strides in ensuring that the upgrade process is as seamless as possible. With detailed guides and documentation available, even those new to Joomla can navigate the upgrade with ease.

    9. Enhanced Extension Management

    Joomla 5 offers improved management of third-party extensions. While the core Joomla upgrade is relatively simple, managing third-party extensions can sometimes be challenging. Joomla 5 has streamlined this process, ensuring that extensions are more compatible and easier to manage.

    10. Improved Documentation and Support

    Joomla’s commitment to its community is evident in its extensive documentation and support. With the release of Joomla 5, there’s an abundance of resources available to guide users through every step of their Joomla journey, from installation to advanced customization.

    11. Optimized for Modern Web Standards

    Joomla 5 is designed with modern web standards in mind. Whether it’s ensuring valid HTML and CSS or optimizing for mobile responsiveness, Joomla 5 ensures that your website is ready for the modern web.

    12. Cost-Efficient

    Being an open-source platform, Joomla offers a cost-efficient solution for website management. With Joomla 5, users can access advanced features and functionalities without incurring additional costs.

    13. Community-Driven Innovations

    Joomla’s vibrant community is its backbone. With continuous feedback and contributions from its community members, Joomla 5 is packed with features that cater to real-world needs. This community-driven approach ensures that the CMS remains relevant and user-centric.

    How to Check if an Extension is Compatible with Joomla 5

    1. Visit the Joomla Extension Directory (JED)

    The Joomla Extension Directory (JED) is the official repository for Joomla extensions. Start by searching for the extension you want to check.

    2. Check the Extension’s Details Page

    Once you’ve found the extension in JED, click on its title to view its details page. Here, you’ll find information about the extension, including its compatibility.

    3. Look for Joomla 5 Compatibility

    On the extension’s details page, there should be a section or badge indicating which Joomla versions the extension supports. Ensure that Joomla 5.x is listed.

    4. Visit the Developer’s Website

    If the JED doesn’t provide clear information, visit the extension developer’s official website. Most developers will have a dedicated page or section for each extension, detailing its features, requirements, and compatibility.

    5. Check for Updates in Your Joomla Backend

    If you already have the extension installed on your Joomla 4.4.x site:

    • Go to Extensions > Manage > Update.
    • If there’s an update available for your extension, it might be for compatibility with Joomla 5. However, always verify this by checking the release notes or the developer’s website.

    6. Contact the Developer Directly

    If you’re still unsure about an extension’s compatibility, consider reaching out to the developer directly. They can provide the most accurate and up-to-date information. Most extension developers are responsive to user queries, especially concerning compatibility issues.

    7. Check User Reviews and Forums

    Sometimes, other users’ experiences can provide insights into compatibility issues. Check the reviews on the JED or Joomla-related forums to see if other users have successfully used the extension with Joomla 5.

    8. Test in a Staging Environment

    If you’re still uncertain, the best approach is to test the extension in a staging or local environment. Clone your live site and upgrade the clone to Joomla 5. Then, test the extension thoroughly to ensure it works as expected.

    Planning Your Upgrade

    Hosting and Technical Specifications

    Hosting and technical specifications joomla

    Before initiating the upgrade, ensure your hosting environment meets the following requirements:

    • PHP 8.1
    • MySQL 8.0.13
    • MariaDB 10.4.x
    • PostgreSQL 12.0

    You can verify your system information in Joomla 4 by navigating to System -> System Information. If your server doesn’t meet these requirements, contact your hosting provider.

    Php information joomla

    Checking Extensions for Compatibility

    Extensions play a crucial role in your Joomla website. Before upgrading, it’s essential to:

    1. Ensure all extensions are compatible with Joomla 5.
    2. Determine if extensions require the backward compatibility plugin.
    3. Identify any extensions that might break your site.

    The Behaviour – Backward Compatibility Plugin allows third-party extensions to use classes no longer included in Joomla 5. This plugin will be enabled by default during the upgrade from J4.4.x to J5.

    Key Components to Consider

    • Cassiopeia: This will remain the frontend template for Joomla 5. Ensure your customizations are compatible.
    • Google reCAPTCHA: Replace Google reCAPTCHA
    • with Invisible reCAPTCHA before upgrading to Joomla 5, as Joomla 5 will no longer support the former. Alternatively, consider using a third-party solution.
    • com_weblinks: As of September 2023, the Weblinks extension functions in J5 with the backward compatibility plugin enabled. However, its future compatibility beyond J5 remains uncertain.
    • Schema.org Plugin: Joomla 5 introduces a dynamic way of handling rich snippets based on schema.org. To customize the output, navigate to System => Manage => Plugins and search for the system plugin “Schema.org – System”. Edit the plugin to add your site information.
    • com_search: This component is not available in Joomla 5. Before upgrading, uninstall it and switch to Smart Search (com_finder).

    Trial Run

    Before executing the upgrade on your main site, conduct a trial run on a subdomain or local environment. This step ensures that the upgrade process works flawlessly and allows you to identify potential issues.

    Step-by-Step Upgrade Process

    Now lets go through the step by step process to upgrade Joomla 4.4 to Joomla 5.0

    1. Ensure your site is running Joomla 4.4.x.
    2. Follow the planning instructions mentioned above.
    3. Backup your website.
    4. Update any extensions that require updating.
    5. Disable or uninstall incompatible extensions.
    6. If using Google reCAPTCHA, switch to Invisible reCAPTCHA.
    7. Enable Debug mode (Global Configuration -> System tab -> Debug System setting to Yes).
    8. Backup your website again and test the backup restoration.
    9. Navigate to System -> Update -> Joomla.
    10. Click on Options in the Top Toolbar on the right-hand side and change the Update Channel to “Joomla Next”.
    11. Follow the on-screen instructions to complete the upgrade.
    12. After the upgrade, test both the frontend and backend of your site.
    13. Disable Debug mode.
    14. Set up Smart Search and the schema plugin as needed.
    15. Celebrate your successful upgrade!

    Troubleshooting and Support

    If issues arise during the upgrade, utilize the Debug mode to identify problematic extensions. Consider restoring from a backup and addressing the issues in a test environment. Use the Database Fix option in the System Dashboard to resolve database structure issues. For further assistance, consider reaching out to the Joomla Forum: Migration & Upgrade Board 5.x.

    Conclusion

    The transition from Joomla 4.4.x to Joomla 5 is a significant leap forward, offering a myriad of benefits from enhanced features to robust community support. This guide provides a holistic view of the upgrade process, ensuring a smooth transition. Embrace the future with Joomla 5!

    In case you are facing issues in upgrade, you can contact us. Our team of experienced Joomla Developers will help you with the process.

  • Joomla php.ini Settings: Recommended Values for Joomla 6.2, 5 & 4 (Tested)

    Joomla php.ini Settings: Recommended Values for Joomla 6.2, 5 & 4 (Tested)

    Updated 15 October 2026 · By Abhilash Sahoo, Founder, Infyways

    Quick answer: as of Joomla 6.2, the latest version (released 13 October 2026), a good starting point for Joomla 6 and 5 is:

    memory_limit        = 256M
    upload_max_filesize = 64M
    post_max_size       = 64M
    max_execution_time  = 120
    max_input_time      = 120
    max_input_vars      = 5000
    output_buffering    = Off
    display_errors      = Off

    Joomla 6.2 needs PHP 8.3.0 or newer (8.4 recommended), and Joomla 5.4 needs PHP 8.1.0 or newer. Check what is actually applied in System → System Information → PHP Settings. Then edit the file your server really reads:

    • .htaccess php_value lines for Apache mod_php
    • .user.ini for CGI, FastCGI or PHP-FPM
    • cPanel’s MultiPHP INI Editor
    • Plesk’s PHP Settings
    • the PHP-FPM pool file on a VPS
    • the main php.ini on XAMPP

    I tested this on a real Joomla 5.4.10 install on XAMPP 8.2.12 (Apache with mod_php, PHP 8.2.12). I changed values with each method and read the results back. The images marked “real output” are screenshots and output from that site. The requirements come from the official Joomla technical requirements, and the directive behaviour comes from the php.net ini reference.

    What PHP version and settings do Joomla 6.2, 5 and 4 need?

    Recommended PHP settings for Joomla 6.2, 5.4 and 4.4
    Requirement Joomla 4.x Joomla 5.x Joomla 6.2 (latest) Source
    PHP minimum 7.2.5 8.1.0 8.3.0 Joomla manual
    PHP recommended 8.2 8.3 8.4 Joomla manual
    Memory limit not stated “at least 256MB” “at least 256MB” Joomla manual
    Required PHP modules json, simplexml, dom, zlib, gd, mysqlnd or pdo_mysql or pdo_pgsql (mbstring recommended) Joomla manual
    output_buffering, display_errors Off (recommended) Joomla installer and update checks
    file_uploads, session.auto_start On, Off Joomla installer and update checks

    Joomla 6.2 (Mwezi) is the current release; its own code enforces JOOMLA_MINIMUM_PHP 8.3.0, and 5.4.10, released the same day, is the last Joomla 5 bugfix release. Joomla 4 reached end of life, so plan your Joomla 6 compatibility check and upgrade. My test site showed this live warning on the dashboard: “Your PHP version, 8.2.12, is only receiving security fixes … Joomla 5 has entered security only mode. Support ends 12 October 2027.”

    Which php.ini values should I set for Joomla?

    Directive PHP default Joomla value Why
    memory_limit 128M 256M (512M for big shops or migrations) Joomla’s documented minimum for 5 and 6. Too low gives “Allowed memory size … exhausted”.
    upload_max_filesize 2M 64M Extension, template and media uploads
    post_max_size 8M 64M (≥ upload_max_filesize) php.net: it “must be larger than upload_max_filesize”, and memory_limit “should be larger than post_max_size”
    max_execution_time 30 120–300 Core updates, backups, imports
    max_input_time -1 120 or -1 Slow uploads
    max_input_vars 1000 3000–5000 Large forms, such as permissions, menus and big article forms, are cut off at 1000
    output_buffering Off (php.ini-production sets 4096) Off Joomla’s installer and updater recommend Off
    display_errors On (php.ini-production sets Off) Off on live sites Don’t show paths to visitors. Use Joomla’s Error Reporting setting for debugging.
    session.auto_start 0 0 Joomla manages its own sessions
    opcache.enable 1 1 Speeds up PHP. If code changes don’t show, check opcache.validate_timestamps.

    The max_input_vars limit is easy to miss. I posted 1,500 form fields to the test site with the default limit. PHP kept the first 1,000, dropped the rest without any visible error, and only logged a warning:

    PHP max_input_vars 1000 limit dropping form fields with Input variables exceeded warning

    If a large Joomla form “saves” but some changes disappear, raise max_input_vars first.

    How do I check my current PHP settings in Joomla?

    In the Administrator, go to System → System Information. The PHP Settings tab shows the values Joomla actually gets, and PHP Information shows the full phpinfo output.

    Joomla 5 System Information PHP Settings tab showing upload size, memory limit and output buffering

    Note what the PHP Settings tab doesn’t list: max_execution_time and max_input_time. Search the PHP Information tab for those. In my test, Output Buffering showed On, because XAMPP ships output_buffering=4096, while Joomla recommends Off.

    In PHP Information, look for three lines:

    • Server API tells you which edit method works.
    • Loaded Configuration File is the main php.ini.
    • Additional .ini files parsed lists extra ini files that can override it.
    Checking the loaded php.ini file and effective PHP values for Joomla

    Don’t trust php -i on the command line. CLI PHP can load a different php.ini from the web server. Check from the browser, or with a temporary file containing <?php echo php_ini_loaded_file(), ' ', php_sapi_name();, and delete it afterwards.

    Where do I change PHP settings for Joomla?

    Where to edit PHP settings for Joomla on cPanel, Plesk, php-fpm and XAMPP

    The right method depends on the Server API line. I tested both per-folder methods on the same mod_php server. The .user.ini file was ignored, and the .htaccess lines applied straight away:

    .user.ini ignored under Apache mod_php while .htaccess php_value applies

    That matches php.net, which says .user.ini files “are processed only by the CGI/FastCGI SAPI. If you are running PHP as Apache module, use .htaccess files for the same effect.”

    Apache mod_php (“Apache 2.0 Handler”): .htaccess

    # In Joomla's root .htaccess
    php_value memory_limit 256M
    php_value upload_max_filesize 64M
    php_value post_max_size 64M
    php_value max_execution_time 120
    php_value max_input_vars 5000
    php_flag  output_buffering Off

    Apache must allow overrides (AllowOverride Options or All). On any other Server API, php_value causes a 500 Internal Server Error, so remove the lines if the site goes down. Our Joomla .htaccess guide covers the rest of that file.

    CGI, FastCGI or PHP-FPM: .user.ini

    ; .user.ini in the Joomla root (and in /administrator if needed)
    memory_limit = 256M
    upload_max_filesize = 64M
    post_max_size = 64M
    max_execution_time = 120
    max_input_vars = 5000
    output_buffering = Off

    PHP reads it from the script’s folder upwards to the document root. Changes can take up to user_ini.cache_ttl to apply (300 seconds by default). Only directives that can be set per directory work here.

    cPanel: MultiPHP INI Editor

    1. Go to cPanel → Software → MultiPHP INI Editor.
    2. In Basic Mode, select the domain, then set memory_limit, upload_max_filesize, post_max_size, max_execution_time, max_input_time and max_input_vars.
    3. Click Apply. cPanel writes the right file for your PHP handler. Check the PHP version in MultiPHP Manager too.

    Plesk: PHP Settings

    Go to Websites & Domains → your domain → PHP (PHP Settings). Choose the PHP version and handler, set the performance and common settings (memory_limit, max_execution_time, post_max_size, upload_max_filesize), and add max_input_vars = 5000 under additional directives. Then click OK or Apply.

    VPS with PHP-FPM (Nginx or Apache)

    ; /etc/php/8.3/fpm/pool.d/www.conf  (Debian/Ubuntu path; varies by distro)
    php_admin_value[memory_limit] = 256M
    php_admin_value[upload_max_filesize] = 64M
    php_admin_value[post_max_size] = 64M
    php_admin_value[max_execution_time] = 120
    php_admin_value[max_input_vars] = 5000
    
    sudo systemctl reload php8.3-fpm

    On Nginx, also raise client_max_body_size, which defaults to 1m. Otherwise uploads fail with 413 before PHP sees them. If PHP’s time limit is higher than the web server’s, increase fastcgi_read_timeout or proxy_read_timeout as well.

    XAMPP and local development

    Edit /opt/lampp/etc/php.ini on Linux, C:\xampp\php\php.ini on Windows (Apache → Config → PHP (php.ini) in the Control Panel), or /Applications/XAMPP/xamppfiles/etc/php.ini on macOS. Then restart Apache. XAMPP runs Apache with mod_php, so .htaccess also works and .user.ini doesn’t. If MySQL won’t start on XAMPP, see our XAMPP MySQL fix guide.

    How do I verify the change worked?

    1. Reload System → System Information → PHP Settings. Don’t rely on the panel showing your edit as saved.
    2. If the value didn’t change, check Server API and Loaded Configuration File in PHP Information.
    3. Test the real task: upload a 50 MB extension, or save the Global Configuration permissions.
    4. On PHP-FPM, reload the service. With .user.ini, wait up to 5 minutes.

    Why are my php.ini changes not applying?

    Symptom Cause Fix
    .user.ini has no effect Server API is Apache 2.0 Handler Use .htaccess php_value instead
    500 error after editing .htaccess php_value on FastCGI or FPM Remove the lines and use .user.ini or the host panel
    Edited php.ini but nothing changed Wrong file, or no restart Match “Loaded Configuration File”, then restart Apache or reload FPM
    Value reverts or is capped php_admin_value in the pool, or host limits Ask the host. A pool admin value can’t be overridden.
    Upload still fails at 64M post_max_size smaller, or Nginx client_max_body_size Make post ≥ upload and raise the Nginx limit
    Form saves but changes are lost max_input_vars at 1000 Set 3000–5000
    Admin settings only fail .user.ini only in the root Usually inherited, but some hosts need a copy in /administrator

    Which Joomla settings sit on top of PHP?

    • Global Configuration → Server → Error Reporting controls what Joomla shows. Keep it at “System Default” or “None” on live sites.
    • Global Configuration → System → Debug System is for development only.
    • Media → Options → Maximum Size (in MB) is Joomla’s own upload cap. It can’t exceed PHP’s limits.
    • Global Configuration → Server → Gzip Page Compression overlaps with server compression, so use one or the other.

    Locking PHP down also matters for security. See our Joomla security guide, which covers display_errors, disable_functions and open_basedir.

    Frequently asked questions

    Where is the php.ini file for Joomla?

    Joomla doesn’t have its own php.ini. Go to System → System Information → PHP Information and read “Loaded Configuration File”. On shared hosting, use your host’s panel or a .user.ini in the Joomla root instead.

    What PHP settings does Joomla 6.2 need?

    Joomla 6.2 is the latest version (13 October 2026). It needs PHP 8.3.0 or newer (8.4 recommended) and memory_limit of at least 256M. In practice, use upload_max_filesize and post_max_size of 64M, max_execution_time of 120, max_input_vars of 5000, and turn output_buffering and display_errors Off.

    What PHP version does Joomla 6 need?

    PHP 8.3.0 at minimum, with 8.4 recommended, according to the Joomla technical requirements. Joomla 5 needs 8.1.0 or newer, with 8.3 recommended.

    What memory_limit should I set for Joomla?

    At least 256M, which is the official recommendation for Joomla 5 and 6. Use 512M for large e-commerce sites, big imports or migrations.

    What max_input_vars does Joomla need?

    Use 3000–5000. The PHP default of 1000 silently drops fields on large forms such as permissions and menus. The old Joomla 3 help screens suggested 2500.

    Should output_buffering be on or off for Joomla?

    Off. Joomla’s installer and pre-update checks list output_buffering as a recommended “Off” setting. XAMPP and many php.ini-production files set it to 4096, which Joomla shows as “On”.

    Why does php_value in .htaccess give a 500 error?

    php_value only works when PHP runs as an Apache module. On FastCGI or PHP-FPM, Apache doesn’t recognise the directive and returns a 500 error. Use .user.ini instead.

    What is the difference between php.ini and .user.ini?

    php.ini is the main server file. .user.ini is a per-folder override that only CGI, FastCGI and PHP-FPM read, it’s cached for up to 5 minutes, and it only accepts per-directory directives.

    Why can’t I upload a 50 MB extension after raising upload_max_filesize?

    The smallest limit wins. post_max_size must be at least as large, and so must Nginx’s client_max_body_size and Joomla’s Media “Maximum Size”.

    Do I need to restart anything after editing php.ini?

    Yes. Restart Apache for mod_php, or reload PHP-FPM. .htaccess changes apply straight away, and .user.ini changes apply within user_ini.cache_ttl (300 seconds by default).

    Can I change PHP settings from inside Joomla?

    No. Joomla only shows them. Change them in the host panel or the server files, then check them in System Information.

  • Benefits of Joomla Migration

    Benefits of Joomla Migration

    The benefits of Joomla migration are concrete: you leave an unsupported major (especially Joomla 3 after August 2023), land on a release that still receives security fixes, run on PHP 8.x hosting hosts still sell, and unlock core features that used to need third-party extensions. In project language, a migration is a major structural hop (typically 3.10 to 4.4). A upgrade is the smoother path the project documents for 4.4 to 5 and 5.4 to 6. Both are what buyers mean when they search for Joomla migration benefits.

    Most articles on this topic stop at “security and speed,” or they stop at Joomla 5. Official docs explain why to migrate. Agency posts list three to ten reasons. Almost none combine official terminology, the full 3 through 6 hop map, Joomla 6 auto-updates, support end dates, when you should wait, the Behaviour – Backward Compatibility 6 rules, cleanup ROI, and a staging plan in one place. That is what this guide does, plus how Infyways runs the work from $149 with a free audit within 12 hours.

    What you will learn

    • Migration versus upgrade versus patch update (with the hop order that actually works)
    • Every major benefit: security, PHP and hosting, performance, admin UX, SEO, accessibility, multilingual, core features, Joomla 6 auto-updates
    • Official support windows so you know when urgency is real versus marketing panic
    • Why migration is also a cleanup project (the angle official docs emphasize)
    • What you lose by waiting on Joomla 3 or early 4, and when Joomla 5 owners can wait
    • How to start with Infyways without treating “click Update” as a plan

    Migration, upgrade, or patch: use the right word

    Confusion here is why thin competitor posts mislead people into a one-click 3 to 6 fantasy.

    Change Official framing Example What you should expect
    Patch Update 5.4.2 to 5.4.3 Same major. Use System → Update → Joomla. See update errors
    4.4 to 5.x Upgrade (not a full migration) 4.4.x to 5.4.x Many extensions work; Behaviour – Backward Compatibility helps. Plan on staging
    5.4 to 6.x Upgrade 5.4 to 6.0+ Disable Behaviour – Backward Compatibility (no number). Keep Behaviour – Backward Compatibility 6 enabled. See compat plugin guide
    3.10 to 4.4 Mini-migration / migration 3.10 to 4.4 Template and extension triage. Protostar does not survive
    3.x toward 5 or 6 Multi-hop migration 3.10 → 4.4 → 5.4 → 6 Never a single updater click. Path: 3 to 4, 5, and 6

    Primary sources: Why Migrate, 4.4 to 5 planning, 5 to 6 planning, and the Joomla 6.0 / 5.4 announcement.

    Support windows that decide urgency

    Scare posts skip dates. The Joomla roadmap and project announcements make urgency measurable:

    Line Bugfix / regular support Security-only support What that means for migration
    Joomla 3.10 Ended August 2023 Ended August 2023 Migrate now. There is no official patch line left
    Joomla 4.x Ended (security ended 14 October 2025) Ended Treat as EOL. Move to 5.4 then plan 6
    Joomla 5.4.x Through 13 October 2026 Through 12 October 2027 Safe to stay while extensions catch up for J6, if you are already on 5.4
    Joomla 6.x Through 17 October 2028 Through 16 October 2029 Active feature line. Finish here when staging is green

    So: Joomla 3 and 4 owners have a real security deadline. Joomla 5.4 owners have a planning window, not a midnight panic, unless the host or an abandoned extension forces the move sooner.

    Benefit 1: Security support that still exists

    Joomla 3.10 reached end of life in August 2023. The site does not magically shut off. Official security patches stop. That is the first benefit of migrating: you are on a maintained line again.

    • Core CVEs ship on current 5.x and 6.x.
    • Abandoned Joomla 3 extensions stop being a permanent attack surface once you replace or rebuild them.
    • Hosts and insurers increasingly treat EOL CMS stacks as unacceptable risk.

    Thin “3 reasons” posts mention security once. The operational point is this: every month on EOL core is a month where your risk grows and your vendor options shrink.

    Benefit 2: PHP and database versions you can still buy

    Hosts retire PHP 7 and old MySQL. Joomla 5 needs PHP 8.1 or newer. Joomla 6 needs PHP 8.3 or newer (8.4 recommended), with MySQL 8.0.13+ / MariaDB in the supported range or PostgreSQL 14+ class. Requirements: Joomla technical requirements.

    Target PHP Why migration unlocks hosting
    Joomla 5 8.1+ Matches mainstream shared hosting in 2026
    Joomla 6 8.3+ (8.4 recommended) Keeps the next renewal cycle viable

    Official docs also warn that hosts will not keep ancient stacks forever. Migration is often forced by the server long before the marketing team asks for new features.

    Benefit 3: Performance without the legacy JS tax

    Current Joomla uses modern PHP, a cleaned codebase, and the Web Asset Manager so templates load scripts only when needed. Core no longer ships MooTools. Default templates are built for current Core Web Vitals expectations.

    The caveat competitors skip: speed appears when the template and bloated extensions move with the core. Migrating the CMS and keeping a Joomla 3 club template untouched does not deliver the performance benefit. Related: remove MooTools from Joomla.

    Benefit 4: An administrator people will actually use

    From Joomla 4 onward the back end is a different product: clearer navigation, Guided Tours, a usable media manager (including AVIF on modern releases), and Dark Mode that editors notice. Magazine writers call out the adjustment period from Joomla 3, then the productivity gain. That matches what we see on client handovers.

    Modern Joomla media manager after migration with drag and drop uploads

    Benefit 5: Core features that replace paid extensions

    This is the benefit Why Migrate stresses and most agency blogs underwrite. Current Joomla can cover work that used to need a stack of third-party tools:

    • Custom fields for structured content
    • Workflows for editorial approval
    • Tags and Smart Search instead of legacy Search
    • Media manager improvements instead of a separate DAM for small sites
    • Cassiopeia child-style customization on recent releases without forking the whole template

    Migration is the moment to uninstall unused modules, kill “great ideas” that never launched, and reduce license sprawl. That lowers cost after go-live, not only risk.

    Benefit 6: SEO you can defend

    Joomla does not rank higher because the version number changed. You benefit because:

    • Modern routing and SEF stay maintainable
    • You can keep aliases and ship a 301 map when something must change
    • Schema and accessibility improvements support how Google evaluates pages
    • The site stays fast enough and online during crawl windows

    Rankings die on broken SEF, 500s after a botched live update, or months of downtime. Staging protects that. Troubleshooting: Joomla upgrade issues and Joomla SEO.

    Benefit 7: Accessibility, multilingual, and compliance

    • Accessibility: current admin and Cassiopeia-oriented front ends take WCAG-oriented patterns seriously. Public sector and education RFPs increasingly require that.
    • Multilingual: language handling and related tooling are stronger than on Joomla 3-era stacks, which matters for EU and multi-region sites.
    • Support window: majors follow a planned lifecycle (on the order of multi-year support per major). You get time to plan the next hop instead of living in permanent panic.

    Benefit 8: Joomla 6 features worth finishing the path for

    Posts that stop at “move to Joomla 5” are already dated. From 5.4 into 6 you also gain reasons to complete the journey:

    • Automatic core updates with the secure update framework introduced across 5.4 and 6.0
    • Behaviour – Backward Compatibility 6 so more extensions survive the hop while vendors catch up
    • Extended versioning that reaches further into custom fields and related content structures
    • Language file caching and media manager improvements
    • Editor updates (TinyMCE on the current 6.x line) for day-to-day publishing
    • Child templates and richer content tools that reduce forking Cassiopeia for small design changes

    Before the hop: prove every third-party extension runs on Joomla 5.4 with the older Behaviour – Backward Compatibility plugin disabled. Then upgrade with Behaviour – Backward Compatibility 6 enabled. After vendors ship native J6 builds, disable BC6 to drop the compatibility overhead. Full rules: 5 to 6 planning.

    Product overview: Joomla 6. Community write-up: What is new in Joomla 6.0.

    Benefit 9: The cost of not migrating

    If you stay on What usually happens next
    Joomla 3 No official security line, vendors gone, PHP upgrades break the site
    Early Joomla 4 on PHP 8.0 hosts Host forces PHP up; site fatals; emergency weekend work
    Joomla 5 without a 6 plan You miss auto-update and lifecycle planning; the next hop becomes a fire drill
    Heavy abandoned extensions Every delay makes rebuild cost higher, not lower

    Waiting rarely saves money. It concentrates risk into a single emergency project.

    Who benefits most (urgency map)

    Situation Main benefit Urgency
    Still on Joomla 3 Security + PHP + vendors High
    Joomla 4, host retiring PHP Stay online High
    VirtueMart / custom components Commerce on supported builds High if vendors dropped your major
    Government / education Supported CMS for audits High
    Joomla 5.4, PHP 8.3+, extensions J6-ready Joomla 6 features + lifecycle Upgrade on staging now
    Joomla 5.4, critical extensions not J6-ready Stay secure on 5.4 while vendors catch up Medium: schedule, do not freeze forever
    Agencies with many client sites One standard stack, fewer snowflake servers High for white-label ops

    What thinner articles leave out

    Topic Typical competitor post This guide
    Versions covered Joomla 3 to 5, or 5 to 6 only 3 through 6 with hop order
    Migration vs upgrade Mixed or wrong Official project language in a table
    Support end dates Vague “EOL soon” Roadmap dates for 3, 4, 5.4, and 6
    Joomla 6 auto-updates Often missing Called out as a finish-line benefit
    BC6 plugin rules Skipped or one line Disable old BC, keep BC6, retire later
    When waiting is OK Rarely said J5.4 security window through October 2027
    Cleanup / core replacements Mentioned lightly Tied to Why Migrate and cost reduction
    Staging + SEO cutover Generic “take a backup” Steps, Pre-Update Check, 301 map, Search Console
    Commercial next step Vague contact form Audit in 12 hours, packages from $149

    Step 1: Inventory version, PHP, and extensions

    1. System → System Information: Joomla, PHP, database.
    2. Export or screenshot Manage → Extensions.
    3. Mark each extension: has a current build, needs rebuild, or can be replaced by core.
    4. Pick only the next hop from the table above.

    Step 2: Back up with a restore test

    A migration benefit is worthless without rollback. Take files + database, store a copy off-server, and confirm restore once. Method: how to backup a Joomla website.

    Step 3: Prove it on staging

    Joomla Pre-Update Check used when planning a migration on staging
    1. Clone production to staging.
    2. Run Pre-Update Check. Fix or replace blockers.
    3. Complete the hop. Run Database Fix. Clear caches.
    4. Click through login, forms, multilingual switchers, and checkout if you have a store.
    5. Only then book the production window.

    When something breaks, use the issue map: common Joomla upgrade issues.

    Step 4: Cut over with SEO and support intact

    • 301 map ready for any alias that must change
    • Search Console checked in week one
    • CDN and page cache purged
    • 30 days of watch for extension edge cases

    How Infyways delivers those benefits

    We are not a generic “we love Joomla 5” essay. We migrate production sites:

    • Free compatibility audit within 12 hours (credentials optional for the first pass)
    • Fixed packages from $149 small / $299 medium / custom enterprise and stores
    • 125 Joomla extensions built in-house, so rebuilds are normal work, not a surprise
    • Staging-first cutover and 30 days of post-launch support on migration defects

    Start: Joomla Upgrade Services.

    Key takeaways

    1. Migration benefits are security, hosting, performance, admin UX, fewer extensions, SEO resilience, accessibility, and Joomla 6 lifecycle features.
    2. Use official words: 3 to 4 is a migration; 4.4 to 5 and 5.4 to 6 are upgrades.
    3. Hop order is 3.10 → 4.4 → 5.4 → 6. No shortcuts.
    4. Urgency follows support windows: EOL on 3/4 is immediate; 5.4 still has a security lane into late 2027.
    5. Cleanup is part of the ROI: drop unused extensions and replace them with core where you can.
    6. Speed and SEO appear only when template and extensions move with the CMS.
    7. Waiting on EOL core increases cost. Fixed-price staging work is cheaper than an emergency rebuild.

    Frequently asked questions

    What are the benefits of Joomla migration?

    You regain security updates, PHP 8 hosting, a modern administrator, vendor-supported extensions, better performance potential, stronger accessibility and multilingual options, and a path into Joomla 5 and 6 features such as automatic core updates.

    Is Joomla 4 to 5 a migration or an upgrade?

    The Joomla project treats 4.4.x to 5.x as an upgrade, not a full migration. Extension checks and staging are still required.

    Is Joomla 5 to 6 a migration?

    No. From 5.4.x it is an upgrade, with Behaviour – Backward Compatibility 6 involved. From Joomla 3 it is still a multi-hop migration.

    Do I need to upgrade from Joomla 5 to Joomla 6 immediately?

    No. Joomla 5.4 remains on a security path through 12 October 2027. Upgrade when templates and extensions are J6-ready and staging is green, not because a headline says “now or never.”

    What is the Behaviour – Backward Compatibility 6 rule before upgrading?

    On Joomla 5.4, disable the older Behaviour – Backward Compatibility plugin (no number in the name) only after extensions run without it. Keep Behaviour – Backward Compatibility 6 enabled for the move into Joomla 6. Disable BC6 later when every extension is native.

    Does my Joomla 3 site stop working after end of life?

    No. It keeps running without official security fixes while hosts and vendors move on.

    Will migration improve Google rankings by itself?

    No. It protects the technical baseline (uptime, SEF, modern HTML performance). Content and links still decide rankings.

    Can core Joomla replace some of my extensions after migration?

    Often yes. Custom fields, workflows, tags, and Smart Search cover many older third-party use cases. That is a deliberate benefit of migrating now.

    How much does Joomla migration cost with Infyways?

    Packages start at $149 for small sites and $299 for medium sites. Enterprise and stores are custom after the free audit.

    How long does it take?

    Small brochure sites can finish in days after staging is ready. Stores and custom components take longer. The audit sets the timeline.

    Where do we start?

    Request a Joomla upgrade audit or contact Infyways.

  • How to Change the Template in Joomla 5 & 6: Step-by-Step Guide

    How to Change the Template in Joomla 5 & 6: Step-by-Step Guide

    To change the template in Joomla 5 or 6, go to System → Site Template Styles, click the star in the Default column next to the style you want, and check the front end. The same steps work in Joomla 4.

    Step 1: Back up first

    A new template can move modules and hide content. Take a full backup with Akeeba Backup (see how to back up Joomla) or test on a staging copy.

    Step 2: Install the new template

    Go to System → Install → Extensions and upload the template ZIP from the vendor. Make sure the vendor lists Joomla 5 or 6 compatibility; templates made for Joomla 3 will not work and may break the site.

    Step 3: Make it the default

    1. Go to System → Templates → Site Template Styles.
    2. Find the new style and click the grey star in the Default column. It turns gold.
    3. To keep the old template for some pages instead, open the new style, go to the Menu Assignment tab and tick only those menu items.

    Step 4: Map module positions

    Each template has its own position names. Go to Content → Site Modules, filter by template, and move modules that disappeared to the new positions. Append ?tp=1 to a page URL to preview positions (enable “Preview Module Positions” in System → Templates → Options first; switch it off again afterwards).

    Step 5: Check overrides and child templates

    Layout overrides live inside the old template folder, so they do not carry over. Recreate the ones you need in the new template, ideally in a Joomla child template so vendor updates do not overwrite them. If changes do not appear, see Joomla CSS changes not showing and template override not working.

    Changing the administrator template

    System → Administrator Template Styles works the same way. Joomla 4, 5 and 6 ship Atum; change it only if an extension needs it.

    Want a custom design instead of a stock template? See Joomla design services or start from the free Joomla template generator.

    Frequently asked questions

    Where are templates in Joomla 5?

    System → Templates → Site Template Styles for the front end, and Site Templates to edit the files.

    Can I use different templates on different pages?

    Yes. Open a template style, go to Menu Assignment and choose the menu items that should use it.

    Why did my modules disappear after changing template?

    The new template uses different position names. Move the modules to the new positions in Content → Site Modules.