tvbythenumbers

Thanks very much.

I wasn’t successfully able to complete the transition to https: for the site (unrelated issue), but I thought I’d backed out all the changes.

The fact that only the Twitter & Facebook URLs were https: was driving me crazy!

Adding “_wpas_done_all” to the “Do not copy these fields” line on the Duplicate Post Options page solved the problem of duplications of published posts not being sent to Facebook, Twitter & Tumblr by Publicize.

Your help is most appreciated.

Thanks very much, will give that a try and see how it works.

This is what the Publicize developers wrote to me. It might help.

“[Duplicate Post] copies the Post Meta information to the new post. Publicize saves whether orn ot a post has been Publicized in the post meta, and when a post is published, it verifies the status first in the meta, to make sure that a post doesn’t end up being Publicized twice. You might want to suggest to the Duplicate Posts plugin author that they could include a check for the Publicize post meta data, and then ask the user if they want to re-Publicize that post, or something along those lines.”

Yes, your explanation makes complete sense as to why it needs to index the entire site. Thanks.

I did continue building the cache using the “try to continue” button many times and it did complete, and I only lost a bit of sleep ??