Creating an importer that automatically publishes its imported nodes seems to require that the "Published Status" mapping be set somehow to 1. But there doesn't seem to be a way to actually do that, so the nodes are unpublished.
I'm trying out this module because I'm fed up with the bugs in FeedAPI (specifically regarding its memory of last imported items, which is constantly messed up and losing items), but this doesn't see to be nearly ready for prime time. Hence the alpha condition, I guess. Is there a schedule for more stable releases?
Thanks
Comments
Comment #1
alex_b commentedFeeds respects the default settings of the content type. Does it not?
Not yet.
Comment #2
alex_b commentedClosing after more than 4 weeks of inactivity.
Comment #3
coderintherye commentedYes, feeds respects the content type defaults, but there is still reason to want a feature of being able to map to the target "published" setting. If for instance one is using the workbench module, nodes may be unpublished by default, but if you import them via feeds, you'll want them to be in the published state. There's more use cases as well.
Going to go hack up feeds to do this now, so perhaps a patch could be forthcoming.
Comment #4
kingandy+1 for this feature ... my use case is that some items are being unpublished (either manually or automatically for various reasons), and I want them to be automatically republished whenever Feeds updates them. Since it's not a new node, the "default status" setting does nothing.
I was planning to try Feeds Tamper to rewrite the contents of a blank field to '1', but it seems like something that Feeds should be capable of handling itself.
Comment #5
kingandyIs #1443406: Set default to publish nodes automatically a duplicate of this? It's a support request about the problem this feature is intended to solve...
Comment #6
coderintherye commentedYeah dupe or close with response to #1 and point here if want the feature.
Comment #7
megachrizYou can use the "Set default value" plugin from the Feeds Tamper module.