Tutorials - Basic Tutorials
- Details
- Written by: Bjørn Ove Bremnes
- Parent Category: Tutorials
- Category: Tutorials - Basic Tutorials
When every Joomla article appears to open the same page, the documented behavior points first to menu-item routing and, on sites using SP Page Builder, to the global article-details layout setting. The records here do not confirm a core Joomla defect on the affected site; they only show that a Single Article menu item shows one article in the frontend and that a Menu Item Alias links one menu item to another, which can affect which page visitors reach. [R1][R2] [R1] [R2]
The guidance below stays within the preserved research limits: no live-site testing was performed, the exact site version was not provided, and any update advice is maintenance-oriented rather than a guaranteed fix. Where a third-party builder is involved, treat its behavior as conditional and verify the actual routing effect before making wider changes. [R3][R4][R5] [R3] [R4] [R5]
Check for a Single Article or alias menu item that is taking precedence over article URLs
Use when every article opens the same page or layout, especially on Joomla 5.4.x / 6.2.x sites using core article menu items alongside a page builder.
Inspect menu structure first if every article opens the same destination. The documented Joomla menu item types include Single Article, which is used to show one article in the frontend, and Menu Item Alias, which creates a link from one menu item to another. In the reported symptom, either a Single Article item or an alias chain could make several article URLs appear to converge on one page, so the most source-supported diagnosis is to check for menu precedence and unintended aliasing before changing content. [R1][R2] [R1] [R2]
Editorial risk-reduction advice: back up or work on staging, note the current menu structure, and prefer repointing or disabling a conflicting menu item rather than deleting it immediately. That is a safeguard for reversibility, not a documented Joomla requirement. After saving any menu changes, retest multiple article URLs from the frontend and confirm that different articles now resolve to different pages. [R1][R2] [R1] [R2]
Before you begin
- Administrator access to Joomla backend.
- A staging copy or backup before changing menu structure.
- Ability to inspect the main menu and any hidden/article menus.
Steps
- Back up the site first, or work on staging and keep a rollback point.
- In Menus, inspect all menu items for any Single Article or Menu Item Alias entries that could resolve article links to one page.
- Open suspicious items and confirm which article they point to; remove or repoint the conflicting item if it is unintended.
- If the site uses multiple menus, check whether an alias menu item is forwarding visitors to another article menu or a different article view.
- Retest several different article URLs from the frontend after saving changes.
Precautions and editorial safeguards
- Do not delete menu items blindly; export or note the current menu structure first.
- If this is a production site, schedule the change during low traffic and keep a rollback backup.
- Keep the fix reversible: prefer disabling or repointing a menu item before deleting it.
Verify the result
- Open at least three different article URLs in a private browser window.
- Confirm they now resolve to different article pages instead of one repeated destination.
- Check the Joomla menu item being used for each article and verify it matches the intended article or layout.
This addresses Joomla routing precedence and menu structure. If a third-party extension is rewriting article links after page load, more investigation is needed.
Review SP Page Builder’s global Article Details Page Layout setting
Use when Joomla articles are being rendered through SP Page Builder and the site behavior changes depending on whether the builder or core article layout is active.
If the site uses SP Page Builder for article rendering, review the global Article Details Page Layout setting in SP Page Builder Dashboard > Settings. The documented option controls how single article or article details pages are displayed, and the settings reference explicitly includes a separate dynamic article detail page choice. That makes the builder-wide layout a plausible conditional factor when Joomla articles all land on one repeated page in a site that relies on SP Page Builder integration. [R3][R4] [R3] [R4]
Editorial recommendation: verify whether the site should use the existing SP Page Builder layout or a separately created dynamic article detail page, then retest several article URLs after saving the setting. This is a configuration review, not proof that the setting alone caused the issue, and changing it globally may affect multiple pages on a site that depends on SP Page Builder. [R3][R4] [R3] [R4]
Before you begin
- Administrator access to the SP Page Builder dashboard.
- Knowledge of whether the site should use an SP Page Builder layout or a separate dynamic article details page.
- A backup or staging environment before changing builder-wide settings.
Steps
- Back up first, or change the setting only on staging before production.
- Open SP Page Builder Dashboard > Settings and inspect the article-details layout option.
- If the site should use a separate dynamic article details page, select the dynamic article details layout option and ensure that page exists and is the intended one.
- If the site should instead use existing SP Page Builder layouts, confirm that the existing layouts are not all mapped to the same details page by mistake.
- Save, clear caches if applicable, and retest multiple article URLs.
Precautions and editorial safeguards
- This is a reversible configuration change, not a core file edit.
- Do not treat an issue report or video claim as proof that a specific page should be unpublished; verify the actual routing effect first.
- If the site depends on SP Page Builder for article rendering, changing this globally may affect multiple pages.
Verify the result
- Open different Joomla article URLs and confirm they no longer all resolve to the same SP Page Builder page.
- Check the frontend title/body content to make sure the correct article is displayed for each URL.
- If available, compare results before and after the setting change in staging.
Official docs confirm the setting exists, but they do not prove that this setting alone caused the reported symptom on the user’s site.
If the site is on a supported Joomla branch, update within that branch after testing on staging
Use when the site is running an older supported build and the routing issue may be compounded by already-fixed core or integration bugs; this is an ancillary stability step, not the primary fix.
If the site is on a supported Joomla branch, a version update within that branch can be a supporting maintenance step after staging validation. The roadmap identifies Joomla 5.x as the currently supported major release series, so keeping the site current within its branch may reduce exposure to already-fixed core or integration issues, but this is not a confirmed root-cause fix for the symptom. [R5] [R5]
Editorial risk-reduction advice: confirm the exact Joomla version, test any update on staging first, and keep a rollback backup. Updating Joomla will not automatically correct a third-party routing misconfiguration, and the preserved research specifically limits this to supportive maintenance rather than a guaranteed solution. [R5] [R5]
Before you begin
- A known current release path for the site’s branch.
- Backup and rollback plan.
- Staging environment to validate extension compatibility.
Steps
- Confirm the site’s Joomla branch and current version.
- If it is on Joomla 5.x or 6.x, compare it with the current official release for that branch and test the update on staging first.
- After updating, recheck article routing and SP Page Builder behavior.
- Keep the change reversible with a full backup and rollback procedure.
Precautions and editorial safeguards
- Do not upgrade blindly on production.
- Updating Joomla will not automatically fix a third-party routing misconfiguration.
- Avoid treating unreleased branches as production targets.
Verify the result
- Confirm the exact Joomla version before and after the update.
- Retest multiple article URLs and compare behavior with the staging baseline.
- Confirm extensions, template, and menu items still resolve correctly after the update.
This is supportive maintenance, not a confirmed root-cause fix for the symptom. It should not be sold as a guaranteed solution.
The documented path to diagnosing this symptom is to check Joomla menu precedence and aliases first, then review SP Page Builder’s global article-details layout if the site uses that integration, and only then consider branch maintenance as a supporting step. The evidence here supports routing and layout selection as the main areas to inspect, but it does not prove a core Joomla defect or a single universal cause. [R1][R2][R3][R4][R5] [R1] [R2] [R3] [R4] [R5]
Scope and limitations
CURRENT guidance. No installation testing was performed. Review version applicability and rehearse on a staging copy before applying changes.
Sources
- R1: The Single Article menu item type is used to show one article in the Frontend of the site.
- R2: The Menu Item Alias menu type is used to create a link from one Menu Item to another Menu Item.
- R3: Choose Article Details Page Layout: Using this dropdown menu, set how single article or article details pages are displayed.
- R4: Use default Dynamic Article Details layout: Select this option if you want to use a separately created dynamic article detail page.
- R5: Joomla! 5.x is the currently supported major release series of the CMS.
- Details
- Written by: Bjørn Ove Bremnes
- Parent Category: Tutorials
- Category: Tutorials - Basic Tutorials
Joomla’s documented article removal process is a two-stage workflow: first, articles are sent to Trash, and then they can be permanently removed from Trash. This tutorial explains that bulk deletion path for a filtered set of articles in the Articles list, using the administrator interface and the built-in toolbar actions. [R1] [R1]
Use Joomla core article Trash/Delete workflow for the filtered set
Supported Joomla branches where the article list and Trash workflow are available; appropriate when you can delete in batches using the built-in toolbar and filters.
Use the core Articles list workflow when you need to remove a group of articles that you can target with filters or current status. Open Content > Articles in the administrator, then use Filter Options to narrow the list to the articles you want to remove. Select the article checkboxes, choose Trash from Actions to move them to Trash, switch the status filter to Trashed, then select the trashed articles and choose Delete to permanently remove them. Joomla’s own guidance describes this as a two-stage process: the first stage sends the article to Trash, and the second stage removes it from Trash. [R1] [R1]
This workflow is appropriate when you want to work with Joomla’s built-in article management tools rather than a separate process. The Trash status acts like a holding area, which means the items are no longer shown in the active Articles list until you filter for Trashed. From there, Delete is the final action that removes the selected articles permanently. [R1] [R1]
Use caution before the final Delete step. Once items are deleted from Trash, they are gone permanently. The source guidance also notes that if you are deciding whether to remove an article entirely, it may be worth considering whether it should instead be kept for future reuse. In this article’s scope, however, the documented bulk-removal path is limited to the Trash/Delete procedure itself. [R1] [R1]
For practical checks, confirm that the selected articles disappear from the active list after Trash, then confirm they appear under the Trashed status filter before you delete them. After you select Delete, verify that the items no longer appear in either the active list or the Trashed view. These checks follow the same documented list and filter flow described in the Joomla tutorial. [R1] [R1]
Editorial caution: because bulk deletion is destructive, it is sensible to use a backup, a rollback plan, and a staging rehearsal before making changes in production. Treat those as precautionary recommendations rather than Joomla requirements, and rely on the administrator’s Trash/Delete workflow as the documented method for the removal itself. [R1] [R1]
Before you begin
- Administrator access.
- A recent backup and a rollback plan.
- A staging rehearsal if deleting many articles.
- The articles can be targeted by current filters or status.
Steps
- Open Content > Articles in the administrator.
- Use Filter Options to narrow to the articles you want to remove.
- Select the article checkboxes.
- Choose Actions > Trash to move them to Trash.
- Switch the status filter to Trashed.
- Select the trashed articles and choose Delete to permanently remove them.
Precautions and editorial safeguards
- This is destructive after the Trash step is emptied; confirm the target set before deleting.
- Verify any article aliases or references that may still matter before permanent deletion.
- Prefer staging first if you are deleting thousands of records.
Verify the result
- Confirm the selected articles disappear from the active list after Trash.
- Confirm the same items appear under the Trashed status filter.
- After Delete, confirm they no longer appear in Trashed or the active list.
This is a manual bulk process, so it may still take several rounds for very large datasets.
In short, Joomla’s article deletion process for a bulk set is to filter the Articles list, send the selected items to Trash, change the status filter to Trashed, and then use Delete to permanently remove the trashed items. The key limitation is that this is a manual, two-stage process, and once deleted from Trash the articles cannot be recovered through that workflow. [R1] [R1]
Scope and limitations
CURRENT guidance. No installation testing was performed. Review version applicability and rehearse on a staging copy before applying changes.
Sources
- Details
- Written by: Bjørn Ove Bremnes
- Parent Category: Tutorials
- Category: Tutorials - Basic Tutorials
A Joomla core update can fix bugs and important security problems, but updating safely involves more than clicking a button. For example, the Joomla 5.4.7 and 6.1.2 releases of 7 July 2026 included access-control and cross-site-scripting fixes, showing why timely maintenance matters.
Read more: Joomla Update Checklist Before Clicking the Update Button
- Details
- Written by: Bjørn Ove Bremnes
- Parent Category: Tutorials
- Category: Tutorials - Basic Tutorials
Joomla user registration deserves a deliberate security review before you invite visitors to create accounts. The most important question is not which CAPTCHA to select or how long a password should be. It is whether your site needs public, self-service registration at all. A school, club, or association with a small known membership may be able to create accounts through an internal process, while a public community may genuinely need visitors to register themselves.
This tutorial covers Joomla 6.1 and Joomla 5.4. It explains how registration, account activation, email delivery, user groups, password email, domain rules, and anti-automation controls work together. You will also learn why email confirmation establishes mailbox access rather than identity, why CAPTCHA cannot stop every spam registration, and why Joomla 6.1 administrators must be especially careful about patch levels when using Administrator activation.
The goal is a registration workflow that matches your membership requirements without granting unnecessary access or depending on a single security control.
Read more: Joomla User Registration Settings You Should Review
