With PR #47495 the option is additionally saved as segment in the db article attribs.
With an override in html\com_content\article override like
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<layout title="TPL_CASSIOPEIA_ARTICLE_XYZ_TITLE">
<message>
<![CDATA[TPL_CASSIOPEIA_ARTICLE_XYZ_DESC]]>
</message>
</layout>
</metadata>
Before the PR
{"article_layout":"cassiopeia:xyz", ... }
After the PR
{"article_layout":"cassiopeia:article:xyz"...}
With this change setLayout in our BaseHtmlView can not find the layout anymore, as it only reads segments 0 and 1, and this has now been changed to article instead of using the actual name of the layout file (segment 2).
joomla-cms/libraries/src/MVC/View/HtmlView.php
Lines 280 to 296 in 65e4e29
5.4
Choosen article layout should be rendered
This functionality is broken due to #47495
No response
Changing line 289 in the base HtmlView.php would solve the problem here.
However, I consider this change in behaviour to be inappropriate for what is essentially a patch release.
- $this->_layout = $temp[1];
$this->_layout = end($temp);
| Labels |
Added:
No Code Attached Yet
bug
|
||
| Title |
|
||||||
| Labels |
Added:
Release Blocker
|
||
Thanks @LadySolveig for reporting and details analyst. PR #48450 should fix the issue. Change HtmlView.php as you suggested would solve the layout rendering issue, but the selected option for the parameter will still be lost due to the option value is generated using different format (having view added) in the said PR. Better we keep the old format for value of the option as I do in the PR.
Thanks @joomdonation ❤️ I only had to resolve this issue on a dev site, so I made the quick fix from the comment and wanted to report the regression. I thought of a revert of the inital PR, but if you’ve got a decent fix, so much the better.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-09-12 12:45:24 |
| Closed_By | ⇒ | richard67 |
| Labels |
Removed:
Release Blocker
|
||
Setting the release blocker label as the PR which causes the issue has not been released yet, so the next patch release would introduce a regression.