The 'feed_item_length' setting ("Feed content: Global setting for the default display of content items in each feed - Titles only, Titles plus teaser, Full text") is currently broken.
The current code in node_feed() grabs the value, but does nothing with it.

With the new 'Body as field', those options are now display settings for the 'body' field in 'rss' build mode : hidden, default, summary.

With no field UI in core for now, we could programmatically update all instances of the body field when the setting is changed, but this doesn't play nicely when you enable the CCK UI and can define different settings for different node types.

So I guess the question is: what do we want to do with this feature ?

Comments

yched’s picture

Priority: Normal » Critical

Critical, not as in 'urgent', but as in 'needs to be solved before a release'.

damien tournoud’s picture

Status: Active » Needs review
StatusFileSize
new3.99 KB

I think it makes sense to move that settings back into the aggregator.

Status: Needs review » Needs work

The last submitted patch failed testing.

yched’s picture

Field UI is now in. Users can choose which display settings they want for the 'RSS build mode' field by field, including body.

So agreed on the approach where the 'length of text to display' variable is limited to aggregator feeds (listing "external" content with no fields on them - although in Feed API, agregated (non-node) items could be fieldable too, I guess).

However :
+++ modules/node/node.module
@@ -2065,9 +2065,7 @@ function node_feed($nids = FALSE, $channel = array()) {
- $item_length = variable_get('feed_item_length', 'fulltext');

$item_length is used below (are we displaying full objects or only titles). It's nothing more than a boolean now.

This review is powered by Dreditor.

sun.core’s picture

Priority: Critical » Normal

Not critical. Please read and understand Priority levels of Issues, thanks.

grendzy’s picture

Got bit by this today. It's quite confusing that the teaser setting at /admin/config/services/rss-publishing has no effect. This also seems to impact views.

jodeygrist’s picture

Yeah confirmed, views can't display just the title plus teaser, you end up with the full body.

sheila8stamp’s picture

subscribing

agileware’s picture

This appears to be causing the complete body text to be displayed in RSS feeds instead of just the teaser, which is not good.

Subscribe.

eporama’s picture

Status: Needs work » Needs review
StatusFileSize
new4.21 KB

Just to sum up yched's point, the setting can be ignored for your own RSS feed as now Field UI will let you set the field formatter for each field per content type.

Visit /admin/structure/types/manage/article/display and click on the "Custom Display Settings" to enable the RSS view mode on the article content type, for example. Then you can set "Trimmed" or "Summary or Trimmed" which will be in effect for the default rss.xml and views based feeds.

Seems slightly more difficult now as you have to change those per field per content type if you want teasers. Might be nice to have this as the "default" setting for RSS instead of using the per content-type "default" formatter. Then you can override individual types and fields against this setting rather than having to change each content type.

I think yched's comment in #4 leads to the fact that that whole section about $item_length could be removed as well, since one of the display formatters you can choose for a field is "<hidden>" which if you set for all fields on a content type has the same effect as "Title only".

thumb’s picture

subscribe

catch’s picture

Version: 7.x-dev » 8.x-dev
Issue tags: +Needs backport to D7
petergw’s picture

Unfortunately the fix using a change to the Custom Display Settings of say an Article does not work in an Omega child theme. It works fine in Bartik. So I for one would still like it to be fixed. Afterall, the original design (of now 3 years ago) was that we could use Teasers in an RSS. No one really wants to use the whole article. And the title alone is pretty base.

ianthomas_uk’s picture

Issue summary: View changes
Status: Needs review » Needs work

Setting needs work because the patch is for D7 and this is targeted at D8 (as per backport policy)

lokapujya’s picture

I think the RSS feed display already works in D8. The body display type is set to default. The Default display seems to also need to be set to "Default". Then, I set the RSS Global Setting to one of: "Titles Only", "Titles plus teaser", or "Full text". Then, the RSS.xml conforms to the Global Settings.

When in a view, RSS display types are adhered to. I can set the RSS display's body to use the summary, trimmed, full text, or invisible.

However, if I have the RSS display's summary set to "default", views seems to just be using the full content. Instead, views should drill down to the defaults set in RSS Global settings (or first drill down to the default display and then -if the default display is set to default- then it should use the Global setting. So, is that the bug?

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

pameeela’s picture

Status: Needs work » Closed (outdated)
Issue tags: +Bug Smash Initiative
StatusFileSize
new31.8 KB

A lot of changes since this issue was created - Field UI in core!!

Anyway it works fine now. You can either use a view mode for RSS, or you can opt to 'Use site default RSS settings'. Tested both and all works as expected.