Due to the way Orange Geeks' servers deliver certain types of files, they are incompatible with OneSignals services by default. There is a simple workaround to this:
Setting up OneSignal for the First Time:
- Connect to your site over FTP (contact support if you need your FTP credentials): https://support.orangegeek.com/solution/articles/5000731780-ftp
- Navigate to the directory: /www/wp-content/plugins/onesignal-free-web-push-notifications/sdk_files
- Rename the following files (right click the file and select "rename"):
- rename manifest.json.php to manifest.php
- rename OneSignalSDKUpdaterWorker.js.php to OneSignalSDKUpdaterWorker.php
- rename OneSignalSDKWorker.js.php to OneSignalSDKWorker.php
- Install the OneSignal WordPress plugin and make the following changes to its settings:
- Turn on "use my own manifest.json" and change the "Custom manifest.json URL" to: https://mydomain.com/wp-content/plugins/onesignal-free-web-push-notifications/sdk_files/manifest.php (changing mydomain.com with your domain)
- Turn on "Disable OneSignal Initialization"
- Copy and paste this into your footer, if you use a Genesis theme you can paste it into Genesis > Theme Settings > Footer Scripts
<script>
window.OneSignal = window.OneSignal || [];
window.OneSignal.push(function() {
window.OneSignal.SERVICE_WORKER_PATH = "OneSignalSDKWorker.php";
window.OneSignal.SERVICE_WORKER_UPDATER_PATH = "OneSignalSDKUpdaterWorker.php";
window.OneSignal.init(window._oneSignalInitOptions);
});
</script>OneSignal should now be working on your site
When Updating OneSignal:
Sometimes when updating OneSignal, the filenames that were renamed when setting it up will be set back to their defaults. You just need to follow steps 1-3 above to fix this.