RTC Updates Requested PR-6.2-dev Pending

User tests: Successful: Unsuccessful:

avatar CSGoat0
CSGoat0
12 Apr 2026

Pull Request resolves #39274

  • I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

Fixed incorrect author visibility on the article detail page when navigating from a Category Blog menu item that has Author set to Use Article Settings, and the article itself has Author set to Use Global, while the Global configuration has Author set to Hide.

The root cause was in ArticleModel.php: the params merge logic was a simple merge() of article attribs on top of the menu/global params. This did not account for the three-tier resolution (Menu → Article → Global) that ArticlesModel.php correctly implements for the Category Blog view.

Specifically, when a menu param is set to use_article:

  • If the article has an explicit value ("0" or "1"), that value should be used.
  • If the article is set to "" (Use Global / empty string), the global component param should be used as the fallback.

The fix aligns ArticleModel::getItem() with the same three-tier resolution logic already present in ArticlesModel::getItems().

File changed: components/com_content/src/Model/ArticleModel.php

Testing Instructions

  1. Go to Content → Articles → Options, set Author to Hide, click Save & Close.
  2. Create Article A (Test Article - Show Author) with Author set to Show.
  3. Set the Category of Article A to be "Uncategorized". Click Save & Close. (Both Articles should have the same Category as well as the Category Blog. So, if you changed this, change the others too).
  4. Create Article B (Test Article - Use Global) with Author set to Use Global.
  5. Set the Category of Article B to be "Uncategorized". Click Save & Close.
  6. Go to Menus → Main Menu → Add New Menu Item, set type to Category Blog (Type -> Article -> Category Blog).
  7. Under the Options tab, set Author to Use Article Settings. Save.
  8. Visit the Category Blog page and verify both articles display correctly.
  9. Click into Article A (Show Author) — verify the author is visible.
  10. Click into Article B (Use Global) — verify the author is hidden.

Actual result BEFORE applying this Pull Request

When navigating to the detail page of Article B (Use Global), the author is incorrectly displayed, even though the Global configuration has Author set to Hide.

Expected result AFTER applying this Pull Request

The detail page of Article B correctly hides the author, respecting the three-tier resolution chain: Menu (Use Article Settings) → Article (Use Global) → Global (Hide).

The detail page of Article A continues to correctly show the author as expected.

Link to documentations

Please select:

  • Documentation link for guide.joomla.org:
  • No documentation changes for guide.joomla.org needed
  • Pull Request link for manual.joomla.org:
  • No documentation changes for manual.joomla.org needed
avatar CSGoat0 CSGoat0 - open - 12 Apr 2026
avatar CSGoat0 CSGoat0 - change - 12 Apr 2026
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 12 Apr 2026
Category Front End com_content
avatar hiteshm0
hiteshm0 - comment - 12 Apr 2026

@CSGoat0
This PR will fail stylings checks, please look into it.

avatar CSGoat0
CSGoat0 - comment - 12 Apr 2026

@CSGoat0 This PR will fail stylings checks, please look into it.

Hello, that's correct.
It happened with me on another pr too.
Could you please help me understand this problem?

avatar CSGoat0 CSGoat0 - change - 12 Apr 2026
Labels Added: PR-6.2-dev
avatar CSGoat0 CSGoat0 - change - 14 Apr 2026
The description was changed
avatar CSGoat0 CSGoat0 - edited - 14 Apr 2026
avatar BeginnerJoomlaCom BeginnerJoomlaCom - test_item - 16 Apr 2026 - Tested successfully
avatar BeginnerJoomlaCom
BeginnerJoomlaCom - comment - 16 Apr 2026

I have tested this item ✅ successfully on 74e705d

I need some Time till i look at the Detail Article Page :-)

Thanks @CSGoat0 for the Pull Request.

@Mike92115 @filipe-torres Can you please also test?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47580.
avatar krishnagandhicode krishnagandhicode - test_item - 24 Apr 2026 - Tested successfully
avatar krishnagandhicode
krishnagandhicode - comment - 24 Apr 2026

I have tested this item ✅ successfully on 74e705d


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47580.

avatar krishnagandhicode
krishnagandhicode - comment - 24 Apr 2026

I have tested this item ✅ successfully on 74e705d


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47580.

avatar richard67 richard67 - change - 24 Apr 2026
Status Pending Ready to Commit
avatar richard67
richard67 - comment - 24 Apr 2026

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47580.

avatar richard67
richard67 - comment - 24 Apr 2026

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47580.

avatar CSGoat0 CSGoat0 - change - 24 Apr 2026
The description was changed
avatar CSGoat0 CSGoat0 - edited - 24 Apr 2026
avatar CSGoat0 CSGoat0 - change - 24 Apr 2026
The description was changed
avatar CSGoat0 CSGoat0 - edited - 24 Apr 2026
avatar CSGoat0 CSGoat0 - change - 24 Apr 2026
The description was changed
avatar CSGoat0 CSGoat0 - edited - 24 Apr 2026
avatar brianteeman
brianteeman - comment - 9 May 2026

If this is fixing a bug shouldn't it be on the 5.4 branch?

avatar richard67
richard67 - comment - 9 May 2026

If this is fixing a bug shouldn't it be on the 5.4 branch?

@brianteeman Correct.

@CSGoat0 Could you rebase to 5.4-dev? Or if that makes problems (which can be the case as the 6.2-dev branch is in advance with commits compared to 5.4-dev) redo it for 5.4-dev? Thanks in advance.

avatar richard67
richard67 - comment - 9 May 2026

If this is fixing a bug shouldn't it be on the 5.4 branch?

@brianteeman Correct.

@CSGoat0 Could you rebase to 5.4-dev? Or if that makes problems (which can be the case as the 6.2-dev branch is in advance with commits compared to 5.4-dev) redo it for 5.4-dev? Thanks in advance.

P.S.: See also https://github.com/joomla/joomla-cms#which-branch-should-my-pull-request-target .

avatar CSGoat0 CSGoat0 - change - 10 May 2026
Labels Added: RTC Updates Requested
avatar CSGoat0
CSGoat0 - comment - 10 May 2026

If this is fixing a bug shouldn't it be on the 5.4 branch?

@brianteeman Correct.

@CSGoat0 Could you rebase to 5.4-dev? Or if that makes problems (which can be the case as the 6.2-dev branch is in advance with commits compared to 5.4-dev) redo it for 5.4-dev? Thanks in advance.

P.S.: See also https://github.com/joomla/joomla-cms#which-branch-should-my-pull-request-target .

You are right, sorry.
I made it early and didn't know if I should rebase or make a new one.
Here is the new PR.

avatar alikon
alikon - comment - 10 May 2026

if you make the same pr to the 5.4 branch ie #47752 then you can close this one
when #47752 will be merged on 5.4.x it will be upmerged to 6.x

avatar richard67
richard67 - comment - 10 May 2026

@BeginnerJoomlaCom @krishnagandhicode Thanks for testing this PR. Could you also test the new PR #47752 for 5.4?

@Mike92115 @filipe-torres As you had issue #39274 , could you also test PR #47752 for 5.4?

Thanks in advance.

avatar richard67 richard67 - change - 10 May 2026
Status Ready to Commit Closed
Closed_Date 0000-00-00 00:00:00 2026-05-10 09:37:31
Closed_By richard67
avatar richard67 richard67 - close - 10 May 2026
avatar richard67
richard67 - comment - 10 May 2026

Closing in favour of PR #47752 .

When that has been merged, the change will be merged all the way up (6.1-dev, 6.2-dev, 7.0-dev) by release managers.

@CSGoat0 Thanks for your contribution so far.

avatar CSGoat0
CSGoat0 - comment - 10 May 2026

Closing in favour of PR #47752 .

When that has been merged, the change will be merged all the way up (6.1-dev, 6.2-dev, 7.0-dev) by release managers.

@CSGoat0 Thanks for your contribution so far.

Thank you!

I was thinking, if it's the same changes across the 2 branches and it was tested on 6.2, isn't the final test before merge enough? Also, I have tested it on 5.4 before making the second PR.

avatar richard67
richard67 - comment - 10 May 2026

Would be good to have at least one human test again, just to play safe.

Add a Comment

Login with GitHub to post a comment