Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Joep 96 posts 698 karma points
    Jan 10, 2020 @ 13:07

    Migration 7 to 8 "unpublishes" nodes


    So after migrating multiple environments I have found the following. If the last action of a node was a "Save" and if it was published before. Then after migrating from 7 to 8 the node gets the "draft" status.

    I guess this is because during migration it doesn't look at the history of a node.

    So the question is if this by design or is this a bug?

    Kind regards,


  • Steve Megson 151 posts 1000 karma points MVP c-trib
    Jan 10, 2020 @ 14:56
    Steve Megson

    It's a bug. In v7 the same version ID can be both the published and "newest" version. The migration to v8 creates new version IDs to separate the two but it misses out nodes in the state you describe, leaving them with no published version.

    I thought that had been fixed, but I may have come across the bug as part of a larger change that hasn't been merged yet. If so, I can separate it into its own PR.

Please Sign in or register to post replies

Write your reply to: