Had to roll back to v.2.44 as v3.x is broken

I have been in contact directly with OS site support but the “help” I got there was useless, as they kept referring me to the troubleshooting documentation, which is out of date. While the prompts were working, no notifications were being sent. In the console I was getting the message “Uncaught ReferenceError: OneSignal is not defined” in reference to a js file I had previously set up with the assistance of one of the OS developers to set the External User IDs – I don’t know if this was connected to the notifications not being sent though; incidentally they were not even appearing on the OneSignal site dashboard.

As soon as I rolled back to 2.44 that error disappeared and notifications were being sent again though, so I suspect it might be the issue. Looking at a lot of the posts in this support forum it seems that many others are experiencing problems, and it seems as though this new version was not tested enough before being made available.

In addition, in my efforts to discover what the problem with the new version might be, I discovered that if the plugin setting “Automatically send notifications when a post is published or updated” is checked, this not only turns it on for posts but pages as well (I reported this to OneSignal support also) – I, for one, do not want notifications sent every time I update a page, and I also wouldn’t want to have to go through every page turning this option off! This should be a separate option. It isn’t this way with the old version I am using now.

As well as hopefully fixing the issues in the new version, I hope you will test any future update much more thoroughly as well as updating the documentation to match before releasing any update.