4 Replies Latest reply on Dec 10, 2012 12:23 PM by joel_triemstra

    Not packaging de-activated pages

    joel_triemstra Level 1

      When creating a package from a development author server and deploying to publish servers in staging/production, we've noticed that if content paths are packaged up, and they include de-activated pages, those de-activated pages are (effectively) activated, because the page node now exists on the publish server. Is there a way around this?