Deactivating a page by replication is not removing the node from publish instance | Community
Skip to main content
adobefor
adobefor
Level 2
October 16, 2015
Solved

Deactivating a page by replication is not removing the node from publish instance

  • October 16, 2015
  • 3 replies
  • 957 views

Hi, 

I am trying to deactivate a page by the code replicator.replicate(currentSession, ReplicationActionType.DEACTIVATE , pathToDeactivate);.

This is deactivating the page in author instance. Also, it invalidates the content in publish but the node doesn't go away from the instance. It is still seen, but, clicking on it takes to 404. I have tried various methods and yet this issue exists. Please let me know if I am missing anything here to delete the node from publ on deactivating. 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by vasimakram

    Can you try using EventHandler. which will trigger upon deactivating page or changing property of node.

    3 replies

    Sham_HC
    Sham_HC
    Level 10
    October 16, 2015

    Verify the publish instance log file.

    vasimakram
    vasimakramAccepted solution
    Level 4
    October 16, 2015

    Can you try using EventHandler. which will trigger upon deactivating page or changing property of node.

      adobefor
      adobeforAuthor
      Level 2
      October 16, 2015

      Thanks for the reply. The property 'cq:lastReplicatedAction','cq:lastModified' etc get changed. The issue is the page is not getting removed from the publish instance.

      I will look into eventhandler as well. 

      Terms & ConditionsAccessibility statement

      Loading footer...