** For those still having problems with latest release **

While 1.16.14 was quite stable, it does not include things like notification notices for WP5 with Gutenberg. Version 1.17.0 will include all the new features and should fix many of the last remaining errors folks may still be seeing. If you would like to test this version prior to its release, click here

Coincides with “Yoast Seo 10.0.1” with the “Onesignal 1.16.16” version.
The “Yoast seo” plug-in causes an error.

Actually, I’d say it’s OneSignal causing the error. Yoast is trying to do its keyword analysis on the fly and OneSignal is getting in the way, which breaks not only Yoast’s focus keyword function (the whole snippet meta box actually), but also switching between the visual and text editor and the edit link modal. The issue exists for those of us not using Gutenberg (official “Classic Editor” plugin).

I disable OneSignal and all problems immediately resolve. Going to try the last version listed in this thread and also the upcoming version to see if either corrects the problems. Will post back whatever results I get.

• This reply was modified 6 years ago by btreece84.

1.17.0 does not fix the issue.

v1.16.14 does correct the issue.

My Site:
php 7.0
WP 5.1.1
Yoast 10.0 & 10.0.1 (tried both Yoast versions with OneSignal versions 1.16.16 and 1.17, issue remained – OneSignal v1.16.14 fixes issues on both)

Linking a screenshot of the console error present during this issue: https://i.imgur.com/SHgQJZd.png

@btreece84 ,
It looks like your site is loading old files from 1.16.15. Please re-download and try 1.17.0 and clear your browser cache (or do a hard-refresh). Thanks

• This reply was modified 6 years ago by OneSignal Push Notifications.

Tried, cleared site cache as well just to be thorough. The hard refresh has been working for days, but that gets incredibly tedious when it’s affecting the edit link modal. Worked this time as well, for one load. Once I save draft it’s broke again with all versions after 1.16.14. Tested this time with 1.17 as you requested. No change, tried twice.

Your suggestion works in theory, except it doesn’t account for the fact that when I upload 1.16.14, the conflict with Yoast disappears entirely and everything works as it should (including OneSignal notifications). I’m also disabling cache through the inspector in Chrome. If it were a caching issue then it wouldn’t work with any version (a changed file is a changed file, regardless if forward or backward changes).

Update: I will give Nginx and Memcached a restart later today when traffic dies down, and see if 1.17 works then. It’s getting a bit specific to my setup, but I’ll reply with my results.

• This reply was modified 6 years ago by btreece84.