Completed

"Do not publish" flag feature on content imported from Field59

8 years ago in BLOX CMS • updated by 8 years ago • 5

We really need the "Do not publish" flag feature on content imported from Field59.

Our workflow is most efficient when we can work in advance on processing content for publication. There are times we have content that imports that should be imported as "Do not publish" because it is purposefully set to publish in the future. Think of it as embargoed content.

Having the ability to import content set to "Do not publish" would allow our staff to properly pass content through our editing workflow without prematurely publishing it.

Thank you,

Jacki Gray

Vote

Answer

8 years ago

Thanks for your request! This is scheduled to be released next week.

- Is it?
- Inappropriate
- Spam
- Duplicate
|

Replies 5
Oldest first
- Newest first
- Oldest first

Under review

8 years ago

Hi Jacki!

We have something on our roadmap like this... essentially you would be able to set on the channel or the importer a specific workflow that you wanted to assign to stories by default as they come in. So if you assign it to a workflow that doesn't allow publishing, this would work.

To make sure this would fit your use case, though, can you tell me more specifically what you're doing? Why not just bring in the ones you want to publish at the point of publish time? If there are some assets you leave, and some you take, then we would want to look at how the importer is set up to make sure it is most efficient.

Thanks!