Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
At the moment a simplefeed item appears to inherit whatever discard time is set for the parent feed. Unfortunately, this setting is not retroactive. (for instance if one sets the discard time to 'never' and then later changes it to '1 week', the previously published nodes will not be updated to be discarded within a week. Depending on the number of nodes - that's a lot of manual and/or sql updating to do, as I've recently found out.
Comments
Comment #1
m3avrck CreditAttribution: m3avrck commentedInteresting idea.
Here's the catch: You set the set the default to 1 week. Bunch of items created. You edit some of these, perhaps change to 4 weeks. Now you update the parent to never.
Which ones are updated? *All* of them? The ones that have the same default?
A bit trickier in that sense, but perhaps the latter, updating all the ones with same default are updated. Maybe that is best?
Comment #2
Caleb G2 CreditAttribution: Caleb G2 commentedCan see how that would be useful for fine-grained control. A system which just globally updated all feed items from a given feed would work for most of my workflows, too.
Also a separate, but related, UI issue - right now there are three places in which a discard date exists, with no explanation give to how they interrelate to each other and/or affect the work flow:
a) on the /admin/settings/simplefeed page
b) on the parent feed page
c) on the individual feed items themselves
This is a bit perplexing to figure out for the uninitiated.
Perhaps a mention on the /admin/settings/simplefeed page discard setting:
And then on the Feed edit page discard setting: