Hi,

Feeds node processor currently adheres to the content type setting for revision creation ("Publishing Options") if node updating or replacing are selected in the node processor settings.

I am suggesting to expose it as a setting whether feeds should create a revision or not. Roles with administer content permission have this ability, but I don't see an option in feeds to prevent creation of a revision during import. However, all the other publishing options (publishing status, promoted to front page, sticky) are exposed as field mappings. I think it would be consistent to add "revision creation" as well as an option.

I could see this as a feed importing setting (node processor settings) which would then apply to all items in the feed. Or it could be exposed in the same way as sticky or promoted to front page as a target in the field mappings which would allow item by item configuration (with the feed delivering a 0/1 value per item).

Use case: I import a few hundred nodes from an external database through an XML feed. This feed only includes some basic identifiers and codes, including author information. Users of the site can then update additional text fields (not any of the imported fields) for each imported node. I intend to keep revisions of the changes to these text fields only, not of any changes to the imported fields. I need to run the import daily and some of the codes might change frequently. If I enable revisions in the content type, each import might create a revision. In this scenario it would be extremely helpful to be able to prevent revision creation when feeds saves a node so that only actual updates by users trigger a revision.

Unfortunately, my technical skills in Drupal module development are limited and I cannot provide a patch. But I would gladly test a feature like this if someone else has a similar requirement and is able to provide a patch.

Thanks, J.

Comments

jelo’s picture

I just realized that I can achieve this through RULES as well.

Event: Before saving an item imported via "importer name"
Action: Set a data value (node:revision, value: false)

This action sets revisions to false for all items for this importer. You could set the data value to mapped field if you desire item by item configuration.

However, all the other publishing options could be done with rules as well. Hence, it might still be a valuable feature to add to feeds itself...