User tests: Successful: Unsuccessful:
Pull Request for Issue #45496 .
As title says. As User I expect that After Content means "after the complete content" not "after intro text"
As this change affects all events "afterDisplayContent" not only custom fields, it should go into 6.0.
See issue #45496.
Custom fields are shown after the readmore text, but should be displayed after Content.
Nothing is displayed after intro text.
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | Front End com_content |
Yes. It is a very old bug, from the very first J4 version. We can say it is ok, people are used to it.
I let the decision to maintainers.
It is a opinion that it's a bug. Others will consider it as the intended behaviour. Either way changing it now will break existing sites.
Discussion here is a waste of time. As people seem to be used to the status quo, I close it.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-05-29 12:05:29 |
| Closed_By | ⇒ | chmst | |
| Labels |
Added:
RMDQ
PR-6.0-dev
|
||
I know it's closed (too fast), as I don't think it's a waste.
Rather than removing events, add new events.
This way it has little to no impact on existing sites and adds flexibility for everyone.
Keep afterDisplayContent (on both intro and full).
Add two new events:
@wwwiiimmm thank you - this is a good idea.
But this too would affect all existing sites and overrides.
For me, the behaviour now is a bug,
Users can easily make overrides of the blog layout and use their own events, probably they do it already.
Would you like to make an own PR as an alternative for this one?
Re-opening and set to draft as there are different opinions if this is expected behaviour ora bug.
| Status | Closed | ⇒ | New |
| Closed_Date | 2025-05-29 12:05:29 | ⇒ | |
| Closed_By | chmst | ⇒ |
| Status | New | ⇒ | Pending |
| Title |
|
||||||
| Title |
|
||||||
I rebased this to 7.0 since it would have a bigger impact on all websites using the blog layout, we also added it to the next Wednesday meeting document.
From a purely practical point of view, I feel it’s more efficient to apply an if condition in a plugin or module that uses the event, rather than having to create an override for serveral sites just because it’s missing there.
It might be an alternative option to simply place it additionally in front of the ‘Read more’ button, rather than removing it completely, since we already have a condition here anyway.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-08-06 07:20:17 |
| Closed_By | ⇒ | chmst | |
| Labels |
Added:
bug
PR-6.1-dev
Removed: PR-6.0-dev |
||
Agree with @LadySolveig - a simlpe solution.
Closing this in favour of #48200.
This will have massive impacts on existing sites.