seanhelmes

As always, thank you Thomas!

I experienced the same issue just a moment ago when I updated. I have reverted back to previous version which temporarily resolved the issue for now.

Hi,

Same thing on my websites with WordPress 5.2.1.

The top bar disappears and the menu is automatically reduced when editing posts or pages with Gutenberg and Classic Editor.

– I am experiencing the same issue.

Amazing! Thank you. Great plugin and support!

Thank you!

@snnake2005 All I did was update the onesignal plugin and I cleared my browser and server caches just to be safe. What theme are you using? Do you have any other plugins installed that output a metabox on the post or page edit screens? The OneSignal plugin could potentially be conflicting with something other than the Yoast plugin that could cause the issue you are experiencing.

@maxwell44 perhaps try clearing your browser and/or server caches and retry?

@maxwell44 yes I am using the classic editor. I do not use gutenberg editor.

version 1.16.16 does appear to have fixed the issues for me/my site. I am running WordPress v5.1 with Yoast 10.0 alongside OneSignal v1.16.16 and it seems to all be working fine for me.

@maxwell44 just simply overwrite the onesignal plugin folder with the older version of the plugin.

@maxwell44 You won’t lose settings by rolling back the plugin/files. It won’t make any changes to the database where your settings are stored for the plugin.

@maxwell44 just re-install and activate the older version of the OneSignal plugin (v1.16.14) which can be downloaded from https://github.com/OneSignal/OneSignal-WordPress-Plugin/archive/88efc88e83f023eb8cb4471f7eb68aeb9d2b61b8.zip and the issue will be resolved.

@rgomezp same issue happens in WordPress v5.1 with classic editor and Yoast SEO v10 running. It breaks the classic editor so I can’t publish or update posts (the button is gone) and Yoast SEO plugin does not work.

I had same issue with using classic editor and Yoast SEO v10 but switching back to OneSignal v1.16.4 made everything work fine again for me for now until a new version of the OneSignal plugin with the bug fixed comes out.

I had same issue with using classic editor and Yoast SEO v10 but switching back to OneSignal v1.16.4 made everything work fine again for me for now until a new version of the OneSignal plugin with the bug fixed comes out.

I too can confirm the combination of having Yoast v10.0 and the latest version of OneSignal v1.16.15 both active creates the issue.