This add-on for Broadcast enqueues posts and processes them in the background, which circumvents WordPress and PHP time limits.
Automatic processing is done via AJAX when the user is viewing the post in the editor or in the post overview.
The queue can also be processed via a cron job, see the HTTP processing settings tab. It is recommended that you disable AJAX queue processing and just use HTTP processing.
If you are using the Gutenberg Block Editor, either refresh the editor in order to get the queue to process or go back to the post overview. Another alternative is to use HTTP processing.
FAQ
What is the limit?
Queue has been tested with a post broadcast to over 3500 blogs. It took a while (it was left overnight) but it got done.
Also tested with two posts queued to the same amount of blogs: 7000 queued posts.
Why is the queue not being filled?
Perhaps you have selected too many blogs for PHP to handle, together with all of the other post editing data that the server needs to accept. See the PHP max_input_vars setting.
A way to test for this is to use the Send To Many add-on to broadcast the post from the post overview. If the queue fills using Send To Many, then it’s probably the above PHP setting that needs to be modified. Or you can just continue using the Send To Many add-on to broadcast the post.
Unable to save Broadcast queue data item
If you receive an Unable to save Broadcast queue data item error message, try raising your max_allowed_packet Mysql setting.
Queue breaking
Some hosts, HostGator for example, have been known to break the queue.
- Symptom: Queue works, then stops working. Can be made to temporarily work again by uninstalling and then reactivating the add-on.
- Diagnosis: The cleanup command (OPTIMIZE TABLE) is breaking the data or item tables.
- Solution: Prevent database cleanup by adding the following to your functions.php: add_filter( ‘broadcast_queue_clean_queue’, ‘__return_false’ );
Why is the queue not being processed properly?
If you find a post is not disappearing from the queue after being processed, it’s probably due to an error during broadcasting.
In order to find out what the problem is:
- disable automatic processing of the queue in the settings
- enable WP_DEBUG
- enable Broadcast debug to browser mode
- manually process the item in the queue
You should see a long debug text. An error message should appear at the end, telling you what is wrong.
If you need help deciphering the debug dump, contact Plainview Plugins.
Hi There,
Is there any API or option by using we can process particular? post first if it is at end in queue?
No, not currently. If you need something broadcasted immediately, use the Broadcasting API.
Is there a setting somewhere that I’m missing that will allow me to provide access to the Queue for any user role I choose? Trying to allow a custom role to access it but am currently unable to do so.
I’ve added a snippet that shows how to provide access to the queue menu. Does that solve your problem?
I’m trying to publish many posts (up to 1,800) to one blog rather than 1 post to many blogs. Does this plugin help with that?
The add-on you’re looking for is probably Send To Many – but the Queue will also help you avoid timeouts when broadcasting.