Sign in Register

Push Notifications

Push Notifications Setup Guide

This guide covers push notification setup for your site.

It does not cover general PWA setup, app store export, or unrelated notification preferences.

Configure the Push Provider

Go to VH360 PWA & App → Push Notifications → Setup.

For website push notifications, set Push Mode to Provider (Web Push).

Set Provider to OneSignal.

Enter your OneSignal credentials:

  • OneSignal App ID
  • OneSignal REST API Key

You can find these values in your OneSignal dashboard under Settings → Keys & IDs.

You may also configure:

  • Default Click URL: the default page opened when a notification is clicked.
  • Default Icon URL: the default icon used for notifications.
  • Auto-prompt on page load: automatically asks visitors for notification permission.
  • Auto-prompt delay: waits a set number of seconds before showing the auto-prompt.

Save the settings when finished.

The plugin manages the OneSignal service worker delivery for you. You do not need to manually upload OneSignal worker files.

Configure Who Can Send Push Notifications

Go to VH360 PWA & App → General.

Find Push Notification Sender Roles.

Select the WordPress roles that should be able to send push notifications from the frontend dashboard.

Administrators are always included.

Save the settings.

Users with an allowed sender role can see the Push Notifications tab in the frontend dashboard. Users without permission will not be able to send push notifications.

Add a User Subscribe Button

To let users subscribe to push notifications from a page, add this shortcode:

[vh360_push_subscribe]

The subscribe button only displays when the push provider setup is valid.

When users click the button, their browser will ask for notification permission. If they block notifications, they must reset notification permissions in their browser settings before subscribing again.

Send a Test Push Notification

Go to VH360 PWA & App → Push Notifications → Diagnostics.

Use Send Test Push to send a test notification to all subscribers.

Complete the test fields:

  • Test notification title
  • Test notification body

Click Send Test Push.

A subscriber must already have allowed notifications before they can receive the test push.

Send a Manual Push Notification

Go to VH360 PWA & App → Push Notifications → Send.

Enter:

  • Title
  • Body
  • Click URL

Click Send Notification.

Manual sends go to all subscribers.

Send Push Notifications from the Frontend Dashboard

Users with permission can go to the frontend dashboard and open the Push Notifications tab.

The frontend form includes:

  • Title
  • Message
  • Click URL
  • Icon URL

Click Send Notification to send the notification.

The frontend dashboard form sends to subscribed users through the configured push provider.

Configure Automatic Push Notifications

Go to VH360 PWA & App → Push Notifications → Events.

You can enable automatic push notifications for:

  • New Post Published
  • Livestream Started
  • New Comment

For each enabled event, configure the title and body template.

The Events screen shows the available template variables for each event. Use only the variables shown on that screen.

You can also choose which public post types should trigger automatic notifications.

Save the event settings when finished.

Control Push Notifications Per Post

When editing an enabled post type, use the Push Notification box in the editor sidebar.

Enable Send push notification when published if that post should send a push notification when it is published.

If the box is unchecked, that individual post will not send a push notification when published.

Review Diagnostics

Go to VH360 PWA & App → Push Notifications → Diagnostics.

The diagnostics screen shows:

  • Configuration status
  • Service worker status
  • SDK status
  • Subscriber count
  • Validation checklist
  • Recent activity

Use Run Full Validation to check the production setup.

Some checklist items are manual test states. A manual checklist item may still show as not tested until you complete a real subscription or delivery test.

Manage Device Tokens

Go to VH360 PWA & App → Push Tokens.

Use this screen to review stored device tokens.

You can filter and manage tokens by platform, user, activity, and status. Available bulk actions include activating, deactivating, and permanently deleting tokens.

Troubleshooting

Push notification settings are locked

Activate your product license from VideoHub360 → License, then return to the push notification settings.

The subscribe button does not appear

Confirm that Push Mode is set to Provider (Web Push) or Hybrid, that OneSignal is selected, and that the OneSignal App ID and REST API Key are valid.

Subscribers are not receiving notifications

Confirm that the user allowed browser notifications and is not using a private/incognito browser session.

Also confirm your site uses HTTPS. Push notifications require a secure connection.

Service worker files show 403 or 404 errors

Check whether your CDN, security plugin, or caching plugin is blocking the push worker files.

Whitelist these URLs if needed:

/OneSignalSDKWorker.js
/OneSignalSDKUpdaterWorker.js

After changing CDN or cache rules, clear the site cache and run diagnostics again.

A sender cannot see the frontend Push Notifications tab

Go to VH360 PWA & App → General and confirm that the user’s WordPress role is selected under Push Notification Sender Roles.

Save the settings, then have the user reload the dashboard.