- Issue created by @tlo405
I have a feed that imports once per hour from a URL. My settings are as follows:
We import these into a content type as 'unpublished' by default. Then someone reviews it and publishes it afterwards manually.
If a piece of content is missing from the URL feed, the feed settings are saying it should be unpublished in Drupal. However, the feed settings also say "Do not update existing content items". These almost seem like 2 opposing things...but I have validated via a functional test that these items do not get unpublished if they are missing from the feed. Which is fine...I guess that the "Do not update existing content items" has a higher priority. We have users who manually make edits to the content (which is why we don't want feeds to update existing content items). They also unpublish content when they no longer want it to appear on the site.
So based on that, there should be no way that feeds would edit any existing content on the site. However...that doesn't appear to be the case. I can see scenarios where the latest revision on a node shows over a year ago, yet the node itself shows that it was 'last edited' a day ago. Looking at the logs, this time matches up with when the feeds cron job ran. We aren't creating a new revision for imported items in the feed (that check-box is unchecked in the feeds settings), so the fact that there is no new revision makes sense. I just don't understand how feeds itself can be possibly still be "editing" a node.
Sometimes I will see a log message that a node was "cleaned". Not really sure what causes that to happen...but that's not the case every time.
It's tough to provide actual steps to reproduce this...so I guess this is more of a question than anything else. How could feeds ever edit a piece of content when it's being told not to? What could possibly cause that to happen?
This has been a tough one to debug...any insight would be greatly appreciated!
Active
Miscellaneous