OneSignal – Web Push Notifications

Descrição

OneSignal is an easy way to increase user engagement. Use OneSignal to send visitors targeted push notifications so they keep coming back. It takes just a few minutes to install.

After setup, your visitors opt-in to receive push notifications when you publish a new post. Visitors receive these notifications even after they’ve left your website, thus driving re-engagement.

You can configure notification delivery at preset intervals, create user segments, and customize the opt-in process for visitors.

OneSignal is free for up to 30,000 subscribers; there are no limits on the number of push notifications you can send. Contact support@onesignal.com if you have any questions. We’d love to hear from you.

Company

OneSignal is trusted by over 600,000 developers and marketing strategists. We power push notifications for everyone from early stage startups to Fortune 500 Companies, sending 4 billion notifications per day. It is the most popular push notification plugin on WordPress with 90,000+ installations.

I'me very disappointed about the NOT assistance and not presence to give help to their users.
There are a loto fo several problems and bug and inusability situations that they have not solved and affronted.
I'll try other services that appear to be more usable asap

Registro de alterações

1.16.13

1.16.12

1.16.11

On WordPress 5.0 “Send notification on post publish” now unchecks after posting.

Added extra checks to ensure double notifications are not sent for the same post.

1.16.10

Updated plugin description and added FAQ section.

1.16.9

Reverting the UI changes for HTTP switch.

1.16.8

This release makes HTTP switch match the dashboard (renamed to “My site is not fully HTTPS”) and removes deprecation warnings for php 7.2.

1.16.7

This release updates the service worker to use a 50% smaller service worker-only file.

1.16.6

This release the issue where even after saving the form, the error about not completing the required fields would appear because the settings for the new page view were loaded before the previous page’s settings were saved. Also a broken doc link was fixed.

1.16.5

This release changes the notification send rate limit from at most one every 10 seconds to at most one every 1 second.

1.16.4

This release removes begining and ending whitespaces from textboxes when saving. This can fix common errors like pasting the App ID, REST API Key, or subdomain (also called label) with an ending whitespace which normally causes errors.

1.16.3

This release greatly simplifies the setup guide to follow our documentation instead of an inline guide.

1.16.2

This release updates the amp-helper-frame.html and amp-permission-dialog.html files used for amp-web-push due to permission changes in Chrome 62.

Update readme to show tested up to 4.9 Release Candidate 2

1.16.1

This release adds an option to disable the “Successfully sent a notification to X recipients” message, and also includes files for AMP web push (to be used with another AMP plugin) in case you decide to add AMP web push for your site.

Add option “Show status message after sending notifications”

Include amp-helper-frame.html and amp-permission-dialog.html for use with AMP web push

1.16.0

This release adds a helpful message describing the notification’s recipient count after sending a notification. After publishing a post, for example, the info box may say “Successfully sent a notification to 100 recipients.”.

Lowered priority of wp_head hook from 5 to 10.

1.15.1

This release fixes a bug with the 1.15.0 release that checks the “Dismiss notifications automatically after ~20 seconds” field. The wrong field was being checked and caused a warning to appear.

1.15.0

This release adds a setting for hiding notifications on Mac OS X platforms.

“Dismiss notifications automatically after ~20 seconds” has been replaced with “Hide notifications after a few seconds” with a couple of
choices “Yes”, “No”, “Yes on Mac OS X. No on other platforms”. Previously, notifications would be persisted on all platforms except Mac OS X.

1.14.4

1.14.3

Use larger sized icons for the featured image

Notification small icons and large images previously used the uploaded image closest to size 80×80. For a large uploaded image with no
resized variants, there would be no issues. But for uploaded images resized to different sizes by WordPress, this caused the smallest image
size to be selected and look blurry. Notification small icons now use the closest available image to 192×192 for a sharper image, whereas
large images use the closest available image to 640×480.

1.14.2

Update Setup tab’s images and text

Clarify some steps that are typically confusing to new users setting up the plugin, like how to get the value in the Subdomain textbox.

1.14.1

Remove .htaccess file

Apache httpd.conf configurations that don’t allow custom .htaccess options will error out with a 500 if we place this file there.

1.14.0

Update semantic versioning; update minor version for new backwards-compatible functionality

Hide Google Project Number from configuration (using one is unnecessary since we provide a default Project Number)

Our plugin is in https://wordpress.org/plugins-wp but not https://wordpress.org/plugins. Hopefully resubmitting the
plugin fixes it

1.13.6

Update style that was being overridden on some sites

1.13.5

Fix undefined index gcm_sender_id error

Do not resend notifications for posts restored from trash

1.13.4

Assign the script initialization variable OneSignal globally so initialization still works if plugins modify our
inline script to be run from an external script file

1.13.3

A user reported the ‘prompt_auto_accept_title’ variable being undefined and causing issues with her site. This issue
is now fixed.

1.13.2

Add proper WordPress action/filter hook for OneSignal init

1.13.1

The web SDK initialization of our plugin can now be fully customized

Removed the Intercom live chat support plugin from our plugin. Users can still email support+wp@onesignal.com.

Click Allow, Site Title, and the auto accept HTTP prompt title can now be customized

Spaces are removed when users save their Subdomain textbox value

The meta box checkbox “Send post on notification publish” now correctly does not send a notification if unchecked.
Previously, there was a logic bug where users could check the box, initially save the post without publishing, and
have a notification sent out when later publishing.

The default plugin tab is now “Setup” if the user is setting up for the first time, and if their App ID or REST API
Key is blank (both values are required)

Correctly call has_post_thumbnail for WordPress versions below 4.4

Check for admin capabilities is done correctly so as to be compatible for users in stateless mode (DISALLOW_FILE_MODS)

Apostrophes and other HTML encoded entities are correctly decoded when using the HTTP prompt

Minor: Remove phantom tooltip linking to GCM page

Minor: site.css now has a source map

1.12.5

Fix broken documentation link

1.12.4

Add option to show GCM Project Number field

1.12.3

Bug fix for manifest.json GCM Sender ID

1.12.2

Remove Google project from the setup flow

1.12.1

Allow HTTP users to select “Automatically prompt…” to use the HTTP prompt