User tests: Successful: Unsuccessful:
Pull Request resolves #41445
Modified the category feed view to respect the Show Intro Text article parameter when Include in Feed = Full Text is selected.
File changed: components/com_content/views/category/FeedView.php (line 60)
Before:
$item->description .= ($params->get('feed_summary', 0) ? $item->introtext . $item->fulltext : $item->introtext);After:
$item->description .= $item->params->get('show_intro', 1) ? $item->introtext : '';
$item->description .= $params->get('feed_summary', 0) ? $item->fulltext : '';Previously, the feed ignored the Show Intro Text = Hide setting and always included intro text when Full Text was selected. Now the feed checks the article's show_intro parameter and only includes intro text when it is set to Show.
Prerequisites:
Step 1: Configure Article Options
Step 2: Create an article with Read More
Step 3: Access the RSS feed
Use the URL of your category blog menu item with feed parameters, for example:
http://localhost/your-category-alias?format=feed&type=rss
Or use the direct route:
http://localhost/index.php?option=com_content&view=category&id=YOUR_CATEGORY_ID&format=feed&type=rss
Step 4: Observe the feed output
Look at the <description> tag of your article in the feed.
<description><![CDATA[<p>AA</p>
<p>BB</p>]]></description>Both intro text (AA) and full text (BB) appear, even though Show Intro Text = Hide is selected.
<description><![CDATA[<p>BB</p>]]></description>Only the full text (BB) appears. The intro text (AA) is correctly hidden.
Please select:
| Status | New | ⇒ | Pending |
| Category | ⇒ | Front End com_content |
| Title |
|
||||||
| Labels |
Added:
PR-5.4-dev
|
||
Please refactor code as #47758 for consistency.
I have similar section in this PR #47761.
If I refactor it, it will look like this:
$description = ($feedSummary ? ($showIntro ? $item->core_body : '') . $row->fulltext : ($showIntro ? $item->core_body : ''));Which is more complex even when keeping $showIntro.
What do you suggest? I would leave it as it is.
Maybe one of these:
description = ($showIntro ? $item->core_body : '') . ($feedSummary ? $row->fulltext : '');
or
description = $showIntro ? $item->core_body : '';
description .= $feedSummary ? $row->fulltext : '';
@CSGoat0 could you plese rebase your PR to 6.2. We discussed it today in the maintainers meeting and decided that it is more a feature than a bug fix. Thanks.
Hello,
thank you for the feedback, I respect the decision.
I originally targeted 5.4 because this was reported and confirmed as a bug by both a user and a maintainer as the RSS feed output differs from the HTML view. However, I understand that different perspectives exist on whether this is a bug or a feature.
Since rebasing to 6.2 would require some work on my end, would it be acceptable if I close these 2 PRs and create 2 new ones against 6.2 instead? That would be cleaner for me.
Since rebasing to 6.2 would require some work on my end, would it be acceptable if I close these 2 PRs and create 2 new ones against 6.2 instead? That would be cleaner for me.
@CSGoat0 That would also be ok. Ideally you leave a comment in the old PR which refers to the new PR, and in the description of the new PR you mention that is is a redo of the old PR, and then close the old PR.
Thanks for your understanding.
Since rebasing to 6.2 would require some work on my end, would it be acceptable if I close these 2 PRs and create 2 new ones against 6.2 instead? That would be cleaner for me.
@CSGoat0 That would also be ok. Ideally you leave a comment in the old PR which refers to the new PR, and in the description of the new PR you mention that is is a redo of the old PR, and then close the old PR.
Thanks for your understanding.
Regarding my third PR (Tag Feed fix #47761), I believe this one is different from the other two.
The Tag Feed was losing content entirely — only AA appeared (just the intro), and BB (the whole content body) was completely missing from the feed. This is not a display preference issue; the full text was never retrieved from the database. My fix restores this missing data.
Given that this is a data loss bug, would it be acceptable for 5.4? Or should I also move it to 6.2?
I am asking as it's from the same family but with a different output. Also, no body have mentioned if i should keep it at 5.4 or not that's it.
So, i will be waiting for directions.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-05-17 14:55:37 |
| Closed_By | ⇒ | CSGoat0 | |
| Labels |
Added:
Feature
|
||
Please refactor code as #47758 for consistency.