Pages are being published automatically and with wrong username after replication | Community
Skip to main content
Level 2
October 16, 2015
Solved

Pages are being published automatically and with wrong username after replication

  • October 16, 2015
  • 2 replies
  • 885 views

Hello,

Pages on my author instance are publishing automatically and with the username who last replicated from the replication page.

We started to notice this instantly after we uploaded a package, and replicated it.

Has anyone ever experienced this or have a solution to fix it?

 

Thanks,

Steve

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 Ove_Lindström

Hi,

yep, if the content created in another instance, or as a content package, contains the publish and date information, that seems to be happening. My theory is that it is because the nodes contains the replication information and that somehow gets picked up by the replication mechanism.

If it is a content package that you replicate, then it is natural that the containing pages is replicated to the publish nodes. Right?

 

/Ove

2 replies

Level 2
October 16, 2015

We are experiencing a similar problem where pages under a specific path are automatically published upon creation. We also notice that the newly created pages in this path bears the creation date in the past and modified date reflects the actual creation date. Last we did was to activate content few times using the Activate Tree, after which we started seeing this issue.  

@Steve : Were you able to get your problem resolved?

Appreciate any pointers/guidance for identifying the root cause.

 

Thanks!

Ove_LindströmAccepted solution
Level 6
October 16, 2015

Hi,

yep, if the content created in another instance, or as a content package, contains the publish and date information, that seems to be happening. My theory is that it is because the nodes contains the replication information and that somehow gets picked up by the replication mechanism.

If it is a content package that you replicate, then it is natural that the containing pages is replicated to the publish nodes. Right?

 

/Ove