No Code Attached Yet bug
avatar Reda-Muhamed
Reda-Muhamed
24 Aug 2026

What happened?

Banners do not respect the published state or access level of their primary category.

A banner is still displayed by the Banners module when its primary category is unpublished or inaccessible to the current user. Its direct click URL can also still be used: it redirects to the banner destination and increments the click count.

Version

5.4 / 6.2

Expected result

The banner must not be displayed when its primary category is unpublished or the current user does not have access to that category.

The direct click URL must not redirect or increment the banner click count in either case. It should return a 404 Not Found response.

Steps to reproduce

  1. Create and publish a banner with a valid click URL.
  2. Assign it to a published banner category.
  3. Display the banner using the Banners module.
  4. Use the banner direct click URL, for example:
    http://joomla.test/index.php/component/banners/click/1

Scenario 1: Category access

  1. Set the banner’s primary category access level to Registered.
  2. Visit the page and the direct click URL as a guest.

Scenario 2: Unpublished category

  1. Unpublish the banner’s primary category.
  2. Visit the page and open the same direct click URL.

Actual result

In both scenarios, the banner is still displayed by the Banners module.

The direct click URL redirects to the banner destination and increments the banner click count.

avatar Reda-Muhamed Reda-Muhamed - open - 24 Aug 2026
avatar joomla-cms-bot joomla-cms-bot - change - 24 Aug 2026
Labels Added: No Code Attached Yet bug
avatar joomla-cms-bot joomla-cms-bot - labeled - 24 Aug 2026
avatar Reda-Muhamed Reda-Muhamed - change - 24 Aug 2026
The description was changed
avatar Reda-Muhamed Reda-Muhamed - edited - 24 Aug 2026
avatar Reda-Muhamed Reda-Muhamed - change - 24 Aug 2026
The description was changed
avatar Reda-Muhamed Reda-Muhamed - edited - 24 Aug 2026
avatar richard67
richard67 - comment - 24 Aug 2026

@Reda-Muhamed Does this bug really happen on 5.4 and 6.2 but not on 6.1 like you stated in the Version section?

I would assume that if it happens on 5.4 and 6.2, it happens also in 6.1.

avatar richard67 richard67 - change - 24 Aug 2026
Status New Closed
Closed_Date 0000-00-00 00:00:00 2026-08-24 14:23:00
Closed_By richard67
avatar richard67 richard67 - close - 24 Aug 2026
avatar richard67
richard67 - comment - 24 Aug 2026

There is already an issue for this, see #46351.

Closing this here as duplicate.

Add a Comment

Login with GitHub to post a comment