Releases: OneSignal/OneSignal-Website-SDK
Releases · OneSignal/OneSignal-Website-SDK
150500 Release
150404 Release
150403 Release
Fix for OneSignal init in Chrome 69 on http
- Fix for Issue #404
150402 Release
Init on HTTP "Secure origins" Error Fix
- Fixes
DOMException: Only secure origins are allowed
error during init on HTTP sites- Issue #391
150401 Release
Compatibility with Safari 11.1 & base tag support
- Fixed pushManager error with Safari 11.1 when using your own service worker.
- Issue #380
- Compatible with sites that use a
<base>
tag with a different domain
150400 Release
150300 Release
150201 Release
showHttpPrompt Not Prompting on HTTP
- Fixed issue where showHttpPrompt was not prompting on HTTP sites
- Issue was introduced in version 150200
150200 Release
GDPR methods & addListenerForNotificationOpened Fix
- Added GDPR privacy consent to postpone initialization of the SDK until the user accepts
- New
requiresUserPrivacyConsent
init flag - New
provideUserConsent(boolean)
function
- New
- Fixed
getListeners
error when opening a notification ifaddListenerForNotificationOpened
was called- Issue #344
- Added Promise of id to setEmail. PR #349
WordPress HTTPS Integration Required Files
Please download OneSignal-WordPress-HTTPS-Integration-Files.zip
and not Source code (zip)
.
Unzip the archived files to any directory of your site:
manifest.json.php
OneSignalSDKWorker.js.php
OneSignalSDKUpdaterWorker.js.php