[Question] Status field excluded to export/import

Created on 8 August 2022, over 2 years ago
Updated 30 June 2023, over 1 year ago

Hello, my team uses this module to transfer content from the development server to the production server (simplified workflow).
And the team does not want to update the status field (Published) on every server manually. So we decided to exclude it from the ignored list, but before we do it we want to understand why it is in the list in the first place.

Can you share your vision of why you excluded this field?
What challenges did you try to complete/avoid?
Maybe show some practical examples when this is useful

Thank you

💬 Support request
Status

Active

Version

3.1

Component

Miscellaneous

Created by

🇧🇾Belarus sanfair

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇫🇷France tsecher

    I understand what you mean.

    Initially, this module has been made in the same goal of yours : put some content from development or staging environments to production.
    We decided to exclude the publication status from the import in order to be able to upload content without automatically set them visible. In this way, the contributor can check if the content has been imported correctly before publishing it.

    That's the reason why we add the ability in the import interface to force publish or not the elements. Maybe it's not efficient or useful enough and this feature should be reviewed.

    Considering your usage, would importing the publish status be appropriate? We would no longer have the possibility of not publishing new content, and therefore it would potentially be immediately visible, without manual verification (But maybe it is not a usual need).

Production build 0.71.5 2024