No post should take 100 seconds to be broadcast to a single blog.
If you disable CloudFlare, does it broadcast correctly?
Thread Starter
DFC005
(@dfc005)
Even with CloudFlare disabled it takes a LONG time.
I do have a lot of categories on the site. Could that be causing issues when broadcasting?
Thread Starter
DFC005
(@dfc005)
With CloudFlare disabled, it takes approx 3 minutes before I get the “Post Updated” status.
Obviously that’s ridiculous but when I don’t broadcast, it’s < 10 seconds.
Any ideas?
Switch on debug mode. When you broadcast you’ll get an enormous amount of debug text.
Since each line is timestamped you can quickly find out what it is that is taking time.
Thread Starter
DFC005
(@dfc005)
Well, this could be the problem…
2014-05-28 13:43:51 ThreeWP_Broadcast: Running save_post hook.
2014-05-28 13:43:51 ThreeWP_Broadcast: We are currently on blog NRL | Zero Tackle (2).
2014-05-28 13:43:51 ThreeWP_Broadcast: Broadcasting the post 13520
2014-05-28 13:43:51 ThreeWP_Broadcast: Linking is enabled.
2014-05-28 13:43:51 ThreeWP_Broadcast: Post type is hierarchical: no
2014-05-28 13:43:51 ThreeWP_Broadcast: Will broadcast taxonomies.
2014-05-28 13:43:51 ThreeWP_Broadcast: Has 1 attachments.
2014-05-28 13:43:51 ThreeWP_Broadcast: Attachment 13521 found.
2014-05-28 13:43:51 ThreeWP_Broadcast: Will not broadcast custom fields.
2014-05-28 13:43:51 ThreeWP_Broadcast: Found 0 gallery shortcodes.
2014-05-28 13:43:51 ThreeWP_Broadcast: Clearing the POST.
2014-05-28 13:43:51 ThreeWP_Broadcast: Beginning child broadcast loop.
2014-05-28 13:43:51 ThreeWP_Broadcast: Switched to blog 1
2014-05-28 13:43:51 ThreeWP_Broadcast: Creating a new post.
And that’s where it stops. Is that a complete output?
Noticed that when debug was on, it created the child post but didn’t link it to the parent.
That is definitely not complete output. You’re missing a ton of taxonomy syncing and the final “stopping WordPress” line.
The question is now: how many plugins do you have that could possibly delay broadcasting? Since broadcasting is completely internal I doubt Cloudflare itself is the problem. Any caching plugins, perhaps?