Network content syndication made easy! Automatically share content by multiposting between multisite blogs.
Broadcast is sporadically supported in my spare time on the WordPress support forum.
For users of the premium add-on pack, support is available via e-mail.
A debug dump is the long text that is displayed when broadcasting a post with debug mode on. This dump can then be read to see what Broadcast is or isn't doing.
To switch on debug mode, see the admin settings. If your site is live it would be wise to input your IP in the associated textarea, so that only you see the debug dump.
Broadcasting to specific blogs, hiding blogs and forcing blogs can be acheived with the User & Blog Settings plugin in the control add-on pack.
To broadcast many posts at once, see the Send To Many plugin in the efficiency add-on pack.
Attachments are force-broadcasted: the child posts have all their attachments deleted and then copied again.
If you have a gallery shortcode in the post ( [gallery columns="2" ids="427,433,430,429,428"] ) then Broadcast will first check that the image does not already exist on the child blog. It does this by searching for the post name (the filename minus the extension). If no image is found, it is copied.
Users report that image filenames ending in dashes or numbers (example-.jpg, example-1.jpg) confuse both WordPress and Broadcast.
If you have manually modified the thumbnails on the parent blog, you might want to use the Duplicate Attachments plugin in an add-on pack, otherwise WordPress will generate new thumbnails on each child blog.
Do you have a lot of attachments that you don't want duplicated to hundreds of child blogs, in order to save space? You'll have to find a way to refer to the images statically instead of using their media IDs. The reason for this is that when WordPress is referred to an attachment, it can only read the media IDs from the current blog. It cannot switch blogs in order to load the image.
The broadcast meta box, menu and columns in the post view can be hidden from users / roles / blogs using User & Blog Settings plugin in the control add-on pack.
Yes. PHP v5.3 has been officially unsupported since the 14th of August, 2014. In fact, even 5.4 is no longer officially supported since September 2015.
If your web host refuses to upgrade to a supported version, go find a new host.
Below is a list of plugins that just will not work properly with Broadcast and / or it's addons:
If you have already created posts on other blogs that are supposed to be children of a specific post, you can use the "find unlinked" bulk action to find and link them.
To be considered an orphan the orphaned posts must have the exact same title (name) as the soon-to-be parent and be of the same post type.
You can also use the Delete Before Broadcast add-on from the pack to delete any similar posts on the child blog before broadcasting.
If you have many attachments in your post, and are broadcasting the post to many blogs, you might encounter a PHP timeout. This means that broadcasting exceeded the PHP time limit and had to be aborted.
There are several solutions to this problem:
You will not need solution #1 if you use solutions #2 and #3. :)
Make sure that:
Broadcast is capable of handling WooCommerce products.
This will broadcast all normal product settings: SKU, price, etc.
If your products have variations, want to sync stock, want to sync orders, need the attribute taxonomies to be synced, you'll be wanting the WooCommerce add-on.
If you have a product gallery, use the Custom Field Attachments add-on to broadcast the "_product_image_gallery" custom field.
Need your PDF vouchers synced upon each purchase? See the WooCommerce extras in the premium add-on pack.
WPML is supported via the WPML add-on in the 3rd party pack. For more information, see WPML discussion here: http://wordpress.org/support/topic/wmpl-integration-not-working
The author suggests using PolyLang instead due to far superior support.
APC works flawlessly.
Xcache v2 does not support PHP namespaces, which is a PHP 5.3 feature. Trying to enable Broadcast with Xcache v2 enabled will result in a PHP crash.
Xcache v3, which does support namespaces, has not yet been tested. Anyone with Xcache v3 experience is welcome to contact me with info.
Requires: 3.9 or higher
Compatible up to: 4.7
Last Updated: 6 days ago
Active Installs: 400+
1 of 4 support threads in the last two months have been marked resolved.
Got something to say? Need help?