| 开发者 |
kloos
freemius |
|---|---|
| 更新时间 | 2026年10月2日 18:57 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
kloos-newsroom-sync-publisher folder to /wp-content/plugins/, or install the ZIP from Plugins > Add New > Upload Plugin.On the free plan and on the Receiver-based connection, yes: install the free Kloos Newsroom Sync Receiver plugin there and connect it with the key it generates. Pro's direct REST connection type is the exception — it reaches a destination site with just an editor account and an application password, no Receiver plugin needed.
Nothing is disconnected or deleted, and every site stays connected regardless of plan — the free plan never limits how many sites you can connect via the Receiver plugin. Pro-only connection types and features — the direct REST connection and the PDF distribution report — stop being reachable until the license is active again; sites connected through the Receiver plugin are never affected by license status.
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.
Yes, each site in the network can run Publisher and/or Receiver independently.
wns_rcv_ to knsrcv_, so a site running both plugins still never re-distributes an article it imported. Older Receivers keep working.knspub_/KNSPUB_ prefix instead of wns_pub_/WNS_PUBLISHER_/wns_fs (WordPress.org requires prefixes over 4 characters; "wns" was too short). No user-facing change.wp wns-publisher add-site and edit-site accept --driver, --rest-user, --rest-status, --create-categories and --trash-copy.wp wns-publisher report.