Linux 软件免费装
Banner图

ViewMend Site Tracker

开发者 phpner
更新时间 2026年9月26日 21:21
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

deployment website monitoring content updates change tracking

下载

1.1.1 1.0.0 1.1.0

详情介绍:

ViewMend Site Tracker connects WordPress to ViewMend website change monitoring. It records content updates, plugin and theme changes, core updates, and supported cache purges, then sends them to ViewMend in the background. ViewMend runs website checks, captures screenshots, compares pages, and stores reports on its own servers. The plugin displays those findings and performance results in WordPress administration. Events include the affected public page URL when WordPress can identify it. ViewMend can match that URL to a tracked page and queue a check, depending on your integration settings, credits, and existing queued checks. Use Timeline events alongside completed checks to investigate changes after a release or content update. A ViewMend account and Site Tracker integration are required. Supported WordPress changes Autosaves, revisions, drafts, trash moves, comments, users, orders, customer records, media churn, and arbitrary option changes do not create events. How WordPress website change monitoring works
  1. WordPress confirms an enabled content, plugin, theme, core, or supported cache action.
  2. The plugin creates one stable event ID and stores the compact event in its local queue.
  3. A background worker delivers the event to ViewMend without delaying the originating WordPress request.
  4. ViewMend records the Timeline context and returns delivery, matched-page, and queue status.
  5. If automatic checks are enabled and the page is eligible, ViewMend queues a check. Results appear in ViewMend and the WordPress Overview.
Native WordPress controls and durable delivery The plugin has four sections: Overview, Connection, Event rules, and Activity. Overview displays findings, content changes, resources, and selected-page performance from completed ViewMend checks. Resource details include the stored request URLs for the selected check. Event rules let you choose which actions to report. For example, you can report plugin updates while leaving activation and deactivation events off. Activity shows delivery status, retries, and the response received from ViewMend. Website checks and page comparisons run in ViewMend.

安装:

  1. Upload and activate the plugin.
  2. Open ViewMend from the main WordPress administration menu.
  3. Follow the setup-guide link on the Connection screen and create WordPress credentials in the target ViewMend Tracker project.
  4. Copy the Integration ID and one-time API token into WordPress > ViewMend > Connection.
  5. Save and test the connection. The test creates a real ViewMend event.
  6. Open Event rules and choose the confirmed WordPress operations that should create events.
  7. Open Activity, confirm the local test row reaches Delivered, and inspect the queue state returned by ViewMend.
WordPress cron must run for background delivery. The plugin schedules near-term work and a recurring five-minute recovery event. Multisite network activation is not supported. Activate and configure the plugin separately for each required site.

屏幕截图:

  • Connection verifies the ViewMend integration and keeps the saved API token hidden while making settings easy to update.
  • Event rules let administrators choose the exact WordPress actions to report, including publication, meaningful updates, and permanent deletion.
  • Activity shows confirmed deliveries with exact affected URLs, matched pages, and the response returned by ViewMend.
  • Page insights combine performance history, Core Web Vitals, transferred resources, resource changes, and local event delivery health.

升级注意事项:

1.1.1 Fixes cache-event privacy, multisite isolation, event delivery and settings validation. Existing settings, tokens and queued events are preserved.

常见问题:

Is this a standalone WordPress website monitoring plugin?

No. It connects WordPress events to ViewMend and displays ViewMend results. A ViewMend account and Site Tracker integration are required.

Can it track WordPress page changes?

Yes, for public posts, pages and products. Events include the affected permalink. ViewMend can check an already tracked page when your integration settings and available credits permit it. Drafts, autosaves, revisions, trash moves and protected content are excluded.

Which site changes can it report?

Public content changes, plugin and theme operations, successful core updates, WP Rocket purges and connection tests. Choose individual actions in Event rules.

Do website checks run on my WordPress server?

No. ViewMend runs checks, captures screenshots, compares pages and stores reports on its own servers. WordPress records and delivers events and caches results. ViewMend checks request your public pages and their resources.

Does the plugin contact an external service?

Yes, after you configure the ViewMend connection. See External service for the request triggers, data fields, terms and privacy policy.

Which cache plugins are supported?

WP Rocket. Domain purges apply site-wide. URL-specific purges include only public posts, pages, products and the home page that WordPress can verify locally. Private, password-protected and unknown routes are excluded.

What happens when ViewMend is unavailable?

Delivery retries network failures, HTTP 429 and server errors up to six times, with increasing delays. Retry-After is respected up to six hours. Manual retries keep the original event ID.

What happens on deactivation or uninstall?

Deactivation removes cron schedules and preserves all data. Uninstall also preserves data by default. You can enable deletion of ViewMend settings, the token, and local delivery history in Connection settings. On multisite, this choice is respected separately for each site.

更新日志:

1.1.1 1.1.0 1.0.0