It shouldn’t take that long, no, but without looking at the broadcast debug text it’s impossible to say exactly how long it is taking and what it is doing.
You can try several things:
- broadcasting to fewer blogs
- using the queue add-on
- increasing the php timeout
Yeah it seems it shouldn’t take so long. But I tried these methods. I’m only broadcasting to 1 blog. I’ve had the host remove the timeout limitation but still problem persists. I may not be able to use this plugin for this if I can’t resolve it.
Again, I need a broadcast debug text to say what is going on.
Go ahead and send it to [email protected]
I sent you the debug. Additionally it seems that turning on the queue add on solves the time out issue. It takes a while but eventually goes.
I’ve looked through the debug file and while, yes, you’re only “broadcasting to 1 blog”, the post you are broadcasting is referring to other posts via an ACF post field, meaning that the other posts also have to be broadcasted.
So the broadcasting of related posts is the culprit and, as you say, can be helped by enabling the queue add-on and allowing the post and related posts to be broadcasted in the background.
aaahh yes. The ACF links is something I don’t even want to broadcast on these posts either. I didn’t realize it was looking to broadcast those cross links as well. Those are not being displayed on the network site. I may have to live with it as I need some of those custom fields but not all. Thanks.
Put the ACF field name(s) into the Broadcast custom field blacklist and the ACF fields will be ignored, and the related posts won’t be broadcasted.