Notificator – Alerts & Notifications
| 开发者 | eboxnet |
|---|---|
| 更新时间 | 2026年8月20日 21:33 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-3.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
- Discover actions and filters in WordPress Core and installed plugins.
- Review likely events in a ranked inbox with source, confidence, and noise information.
- Start from ready-made templates or create a notification from scratch.
- Deliver each event to the WordPress dashboard, mobile push, MQTT, or a combination.
- Add conditions so a notification is sent only when its event data matches your rules.
- Add placeholders, priority, and throttling to make alerts more useful and less noisy.
- Export notification configurations as JSON and reuse them across WordPress sites.
- Manage notifications and review delivery status from one activity workspace.
- Register well-described events and templates from another plugin or theme.
- An event is something that can happen in WordPress, such as a user signing in or an order changing status. Discovering or registering an event does not start monitoring it.
- A template is a ready-made starting configuration for an event. Applying a template opens a draft that you can review and change.
- A notification is the saved rule that listens for an event. Only enabled notifications can create alerts.
安装:
- Install and activate Notificator.
- Open Notificator > Overview in wp-admin.
- Select Scan plugins to discover available site events.
- Apply a template or create a notification from a discovered event.
- Keep Dashboard enabled to receive alerts inside WordPress.
- Optional: get the Notificator mobile app, create an account and WordPress Plugin API key, then add and enable that key in Settings.
- Enable Mobile push or MQTT on the notifications that need remote delivery.
- Optional: under Settings > MQTT broker, connect your own HiveMQ Cloud cluster and use the same topic prefix in your device firmware.
屏幕截图:
常见问题:
Do I need a Notificator account or API key?
No. Dashboard delivery and the plugin's setup and management features work without one. An API key is needed only for mobile push or MQTT delivery.
What is the difference between a template and a notification?
A template is an editable starting point. It does not listen for an event by itself. A notification is the saved, enabled rule that listens for an event and delivers an alert through your selected channels.
Does scanning send my plugin code to an external service?
No. Hook discovery runs on your WordPress installation. Optional observation stores metadata such as execution counts and argument types, not argument values.
Are hook arguments sent to Notificator?
The plugin does not send raw hook arguments as a complete payload. It sends the notification content and metadata described under External Services. Rendered placeholder values become part of the notification and may contain personal or sensitive information. Review each remote notification before enabling it.
How do I get a Notificator account?
Download Notificator Project for iPhone or iPad from the Apple App Store. Install the app and select the option to create an account. Registration is completed in the mobile app. Notificator is also coming to Google Play for Android, but that release is not publicly available yet.
How do I receive notifications in the mobile app?
Install and sign in to the Notificator mobile app, create a WordPress Plugin API key, and add that key in the plugin's Settings tab. Enable Mobile push on the notifications you want on your phone and make sure the app has notification permission.
Can I use my own HiveMQ Cloud account?
Yes. HiveMQ Cloud is the only MQTT provider supported by the current release. HiveMQ offers a free Serverless plan with no credit card required, subject to HiveMQ's current limits and terms.
Create an account at https://console.hivemq.cloud/, choose Create Serverless Cluster, and open the cluster overview. Copy the cluster URL and enter only its hostname in Notificator. Under Access Management, create a Publish Only username and password for WordPress and a separate Publish and Subscribe credential for the device.
Enable MQTT delivery under Settings > MQTT broker, then enter the hostname, publisher username, password, and topic prefix. New configurations default to notificator-project. The device must use the same cluster and topic prefix.
The password is encrypted locally using keys derived from this WordPress installation. It is excluded from exports, logs, diagnostics, and saved retry payloads. For an MQTT-enabled delivery, the plugin decrypts it only while preparing the HTTPS request to the Notificator API.
Is there a Pro or paid version?
No. Notificator is free and open source, and we intend to keep its current features free. We may introduce optional new features or hosted services in the future, but they will not remove or place the functionality available today behind a paywall.
Can another plugin register an event or template?
Yes. Integrations can register documented events with notificator_companion_register_event() and provide templates through notificator_companion_register_templates. See the repository README and integration guide for complete examples.
Can I reuse my notification setup on another site?
Yes. Export configured notifications as JSON from Tools and import them on another site. You can merge with the destination setup or replace it. Review plugin availability, hooks, placeholders, API keys, and delivery channels before enabling imported notifications.
What happens to plugin data when I uninstall it?
Deactivation keeps the configuration. Deleting the plugin through WordPress removes all plugin-owned settings, notifications, activity, scan caches, scheduled jobs, user metadata, and transients, including across multisite. The Tools dialog also provides a test reset that keeps saved API keys and the custom MQTT connection.
更新日志:
- Declares compatibility with WordPress 7.1.
- Adds official App Store links and clearer WordPress Plugin API key guidance.
- Adds first-class support for connecting a user-owned HiveMQ Cloud cluster.
- Encrypts the MQTT password locally and excludes it from exports, diagnostics, logs, and saved retry jobs.
- Sends MQTT credentials only in memory for an enabled MQTT delivery or explicit connection test.
- Adds an MQTT connection test and clearer delivery-readiness feedback.
- Reorganizes Settings into consistent, more readable sections and tabs.
- Improves settings typography, contrast, responsive behavior, and in-place controls.
- Removes the implicit default MQTT broker and defaults new topic prefixes to
notificator-project.
- Prevents saved field metadata from selecting or invoking runtime object methods.
- Resolves supported WooCommerce and Contact Form 7 object fields through explicit server-side handlers.
- Removes obsolete getter-method metadata from built-in templates and adds a trusted PHP filter for custom integrations.
- Prompts for a new discovery scan when a plugin is activated after the last successful scan.
- Identifies newly activated plugins directly in the Overview scan step.
- Hides the first-time scan prompt immediately after event discovery completes, without requiring a page reload.
- Marks the Overview discovery step complete and refreshes its scan summary immediately after a successful scan.
- Refreshes the Discovery inbox, event cards, filters, and totals in place when a scan finishes.
- Initial public release of Notificator.
- Includes local dashboard alerts, optional mobile push and MQTT, event discovery, ready-made templates, conditions, activity history, integration APIs, and complete uninstall cleanup.