Palasthotel Content Change Observer
| 开发者 |
palasthotel
edwardbock janaeggebrecht |
|---|---|
| 更新时间 | 2026年11月4日 13:33 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-3.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
Content Change Observer tells one WordPress site what changed on another. The observed site records modifications - saved and deleted posts, and anything a theme or plugin reports - and the sites observing it receive them and react in their own code, for example to refresh a cached teaser list or a mirrored menu.
The plugin moves no content by itself. It transports the modification (content id, content type, create/update/delete and time); what happens next is up to the
content_observer_on_modifications action on the observing site.
- Connect sites as observer, observable or both, secured by an API key
- Modifications are pushed hourly (notify) or pulled on demand (fetch)
- Admin pages to manage connections and inspect and apply modifications
- WP-CLI commands for every step, so a system cron can replace WP-Cron
- A portal clears its cached teaser list as soon as an article on the news site changes
- Several sites rebuild a mirrored navigation when the main site's menu changes
- A central search site re-indexes changed posts and drops deleted ones
- An archive site stores a copy of every article, so it survives a later deletion
安装:
- Install the plugin on every site that observes or is observed, from Plugins > Add New or by uploading
palasthotel-content-change-observer.zip - Activate it
- Enter an API key under Content Change Observer → Settings on each site
- Connect the sites under Content Change Observer → Manage
- React to the
content_observer_on_modificationsaction in your theme or plugin
屏幕截图:
常见问题:
Does it copy posts between sites?
No. It reports which content changed. Copying or refreshing content is done by your own code reacting to the modifications.
Can I record changes other than posts?
Yes. content_observer_add_modification( Modification::build( $id, 'my-type' )->update() ) records a modification of any content type.
更新日志:
2.0.0
⚠ BREAKING CHANGES
- the plugin folder is palasthotel-content-change-observer instead of content-observer. WordPress treats it as a new plugin: install it, deactivate and delete the old one, then activate the new one. Settings, connected sites and modifications stay, as options and tables keep their names. Features
- rename the plugin to Palasthotel Content Change Observer (c40e088) Bug Fixes
- show log notices only on the plugin's own admin pages (5acb3b4)
- connection test can no longer make the site request arbitrary URLs (4f494f5)
- escape admin notice logs and keep API keys out of them (08b8c06)
- escape the API key field on the settings page (8fc9ae1)
- modifications page disappears after applying modifications (c3f6bb8)
- protect Fetch, Notify and Apply against cross-site requests (1ae6a34)
- reject requests to other sites' routes when no API key is set (7775e3d)
- Major library updates
- all js(x) files converted to typescript
- fix: use admin_url passed from php for ajax calls
- Feature: Admin notices logger
- New modifications page
- Library update
- all js api calls are cors independent
- First release