Notifications Plugin
Notifications sends supported AVideo events through the in-site notification bell, e-mail, browser/mobile push, or a webhook. Each channel has separate requirements.
| Channel | Requirement | Typical failure |
|---|---|---|
| Notification bell |
bellNotificationEnabled and an eligible signed-in recipient |
User/event is not eligible |
Working site SMTP and emailEnabled
|
Delivery rejected or sent to spam | |
| OneSignal push | Provider application, browser/mobile setup, user permission, and API values | Subscriber/device was never registered |
| Webhook | Reachable HTTPS endpoint that accepts the event | Timeout or non-success HTTP response |
- Open Admin → Plugins → Notifications → parameters.
- Enable one channel at a time.
- Select which events/recipients should be notified, such as a video owner, subscribers, tag subscribers, live followers, or a fixed e-mail address.
- Review the subject/message templates and placeholders shown by the plugin.
- Save and trigger one test event with a normal user.
- Confirm delivery once; prevent duplicate retries before enabling another channel.
For e-mail, first follow Setting up AVideo to send e-mails.
For push, create the application in OneSignal and enter the current application ID/API values required by the installed plugin. Provider onboarding and mobile/browser credentials can change, so follow the current OneSignal documentation. Keep REST API keys private.
For a webhook, enter the HTTPS endpoint in notifyVideoUploadWebhook and log the event ID/time/status on the receiving service.
Why did one user receive nothing? Check the event's recipient rules, subscriptions, verification requirement, user preference, valid e-mail/push subscription, and logs.
Why was the same notification sent twice? Look for duplicate event processing, multiple Scheduler/cron runners, webhook retries, and repeated publishing actions.
Why does the bell work but e-mail does not? The bell is stored in AVideo; e-mail additionally depends on SMTP, address validity, and recipient filtering.
Can I put secrets in a notification template or webhook URL? No. Templates can reach users, and URLs can appear in logs. Use secure server-side authentication.
Related guides: Email and push notifications, UserNotifications, and Scheduler.
