Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author stenberg.me

    (@stenbergme)

    Hi phillyj8,

    Modify the page that you deployed and try to deploy it again. My guess is that you will still have two copies of the page (not three), one of them will be the updated version?

    Content Staging is using the guid field in wp_posts to compare posts from your staging environment to posts on your live environment. My guess is that when the database was copied to the staging environment, the domain was replaced with the domain of the staging site.

    Now that’s fine, but for Content Staging to be able to compare posts, the guid field must be left unaltered in the copying process.

    I hope this helps, let me know if you have any questions.

    Thanks!

    I am having the same issue. Not really understanding what you are meaning with the guid field? What I did was installed content staging on my live site, then installed it on my staging site. Did the set up as mentioned and I still get double pages. For instance I am trying to update my homepage, but it creates a separate page.

    I went ahead and made the guid fields match. It’s kind of weird that you have to do that cause isn’t it good practice to switch all the urls to the actual live site when you are copying over?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Page duplicates instead of updating’ is closed to new replies.