Kloos Newsroom Sync Publisher runs on your central WordPress site. Tick the sites you want an article to go to, publish as usual, and the plugin pushes the title, content, excerpt, featured image, category and SEO fields to each one in the background \u2014 with automatic retries, per-site delivery status and a full log.<\/p>\n\n
It's built for anyone running more than one WordPress site from a shared editorial workflow: publisher networks, franchise or multi-location sites, agencies managing several client sites with the same content, or a company blog mirrored to regional sites.<\/p>\n\n
On each destination site, install the free companion plugin, Kloos Newsroom Sync Receiver<\/strong>, and connect it with a signed key \u2014 no destination-site REST credentials to manage, no public write access to guess at. Every request between the two plugins is signed and verified.<\/p>\n\n Upgrading unlocks, on top of everything in the free plan:<\/p>\n\n License activation, billing and upgrades are handled by our payment processor, Freemius \u2014 see \"External Services\" below.<\/p>\n\n This plugin connects to the following external services:<\/p>\n\n Freemius<\/strong> \u2014 used for license activation, plan\/subscription management and plugin update delivery for the Pro plans. The first time you open this plugin's admin page, Freemius shows its own opt-in screen with two explicit choices: \"Allow & Continue\" or \"Skip\". Nothing is sent to Freemius unless you choose \"Allow & Continue\"; choosing \"Skip\" (or simply not opting in) keeps the plugin fully functional on the free plan with no data sent. If you do opt in, what's shared is basic site data (URL, WordPress\/PHP version, plugin version) needed to serve updates and enforce your plan \u2014 never content, post data or destination-site details. See the Freemius Privacy Policy<\/a> and Terms of Service<\/a>.<\/p>\n\n The destination sites you connect<\/strong> \u2014 this is the plugin's core function, not a third-party service: when you add a site under Sites and publish an article, the article's title, content, excerpt, featured image and category are sent directly to that site (over a signed connection to its Receiver plugin, or, on Pro, over its WordPress REST API). These are sites you explicitly configure; nothing is sent anywhere you have not added yourself.<\/p>\n\n\n On the free plan and on the Receiver-based connection, yes: install the free Kloos Newsroom Sync Receiver<\/strong> plugin there and connect it with the key it generates. Pro's direct REST connection type is the exception \u2014 it reaches a destination site with just an editor account and an application password, no Receiver plugin needed.<\/p><\/dd>\n Nothing is disconnected or deleted, and every site stays connected regardless of plan \u2014 the free plan never limits how many sites you can connect via the Receiver plugin. Pro-only connection types and features \u2014 the direct REST connection and the PDF distribution report \u2014 stop being reachable until the license is active again; sites connected through the Receiver plugin are never affected by license status.<\/p><\/dd>\n No. Delivery happens through the REST API of the destination site (or through the Receiver plugin's own signed endpoint); nothing on the central site's own content is modified by installing or using this plugin.<\/p><\/dd>\n Yes, each site in the network can run Publisher and\/or Receiver independently.<\/p><\/dd>\n\n<\/dl>\n\n\nFree plan<\/h4>\n\n
\n
Pro plans<\/h4>\n\n
\n
External Services<\/h3>\n\n
\n
kloos-newsroom-sync-publisher<\/code> folder to \/wp-content\/plugins\/<\/code>, or install the ZIP from Plugins > Add New > Upload Plugin.<\/li>\n\n
Do I need to install anything on the destination sites?<\/h3><\/dt>\n
What happens to my connected sites if I don't upgrade, or my license lapses?<\/h3><\/dt>\n
Does this touch my posts, media or categories directly?<\/h3><\/dt>\n
Does this work on WordPress Multisite?<\/h3><\/dt>\n
1.2.5<\/h4>\n\n
\n
wns_rcv_<\/code> to knsrcv_<\/code>, so a site running both plugins still never re-distributes an article it imported. Older Receivers keep working.<\/li>\n<\/ul>\n\n1.2.4<\/h4>\n\n
\n
knspub_<\/code>\/KNSPUB_<\/code> prefix instead of wns_pub_<\/code>\/WNS_PUBLISHER_<\/code>\/wns_fs<\/code> (WordPress.org requires prefixes over 4 characters; \"wns\" was too short). No user-facing change.<\/li>\n<\/ul>\n\n1.2.3<\/h4>\n\n
\n
1.2.2<\/h4>\n\n
\n
1.2.1<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
wp wns-publisher add-site<\/code> and edit-site<\/code> accept --driver, --rest-user, --rest-status, --create-categories and --trash-copy.<\/li>\n<\/ul>\n\n1.1.0<\/h4>\n\n
\n
wp wns-publisher report<\/code>.<\/li>\n1.0.0<\/h4>\n\n
\n