| 开发者 | rafael145a |
|---|---|
| 更新时间 | 2026年5月26日 03:17 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
subscribeToTopic() for each topic it wants to receive. No device tokens are stored, no PII is collected, no extra database tables are created..htaccess deny + chmod 600openssl extension (bundled with most hosts)subscribeToTopic() for each topicrafaelmarreca-push-dispatch folder to wp-content/plugins/.No. The plugin uses topic subscriptions exclusively. Your app subscribes on the device; the plugin only sends to topic names.
The plugin enforces 65 characters for the title and 140 characters for the body. The notification composer shows a live character counter and a phone preview as you type.
Yes. Use the Notifications menu item to open the notification composer, write your title and body, choose a topic, and publish.
Enter a custom URL in the Deep link field of the notification composer, e.g. myapp://section/123. Any RFC 3986 compliant custom scheme is accepted.
No. This is an independent, third-party integration that uses Google's publicly documented Firebase Cloud Messaging HTTP v1 API. "Firebase" and "Firebase Cloud Messaging" are trademarks of Google LLC.
openssl_free_key() call (PHP 8+ no longer requires it; PHP 7.4 garbage-collects the key at scope exit).