Wordpress-seo: Getting a Blank Meta Box When Using Classic Editor plugin and OneSignal Push Notifications

[Jerparx]

Please give us a description of what happened.

Getting a blank meta box when both Classic Editor plugin and OneSignal Push Notifications plugins are activated.

Getting the following console errors:

The meta box works fine when using Gutenberg and OneSignal Push notifications. Issue only happens when using the Classic Editor plugin and OneSignal Push notifications.

Please describe what you expected to happen and why.

I expect the meta box to show up.

How can we reproduce this behavior?

1. Install and activate the latest Classic Editor plugin
2. Install and activate the latest OneSignal Push Notifications
3. Create a new post or a page.
4. Meta Box does not load and throws a js error.

Technical info

* If relevant, which editor is affected (or editors):
- [ ] Classic Editor
- [ ] Gutenberg
- [x] Classic Editor plugin

* Which browser is affected (or browsers):
- [x] Chrome
- [x] Firefox
- [ ] Safari
- [ ] Other

Used versions

• WordPress version: 5.1.1
• Yoast SEO version: 9.7 and 10.0
• Classic Editor plugin version: 1.4
• OneSignal Push Notifications: 1.16.15
  
• Tested with theme: Twenty Sixteen

[Jerparx]

Please inform the customer of conversation # 483165 when this conversation has been closed.

[Jerparx]

Please inform the customer of conversation # 483126 when this conversation has been closed.

[maybellyne]

Please inform the customer of conversation # 483210 when this conversation has been closed

[laurasacco]

Please inform the customer of conversation # 483212 when this conversation has been closed.

[laurasacco]

Please inform the customer of conversation # 483166 when this conversation has been closed.

[laurasacco]

Please, inform the customer of conversation # 483231 when this conversation has been closed.

[maybellyne]

Please inform the customer of conversation # 483216 when this conversation has been closed

[jeroenrotty]

Probably a bug with the latest version of OneSignal as seen here:
https://wordpress.org/support/topic/help-with-fatal-error-uncaught-error/
Author has a patch in their repo, but not reachable for me.

Issue on their GH repo: https://github.com/OneSignal/OneSignal-WordPress-Plugin/issues/173

[littleseed]

I confirm that, disabling OneSignal plugin, all is ok again.

[laurasacco]

Please inform the customer of conversation # 483252 when this conversation has been closed.

[maybellyne]

Please inform the customer of conversation # 483300 when this conversation has been closed

[Pcosta88]

Please inform the customer of conversation # 483398 when this conversation has been closed.

[Pcosta88]

Please inform the customer of conversation # 483401 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 483381 when this conversation has been closed.

[mariusghitulescu]

Please inform the customer of conversation # 483469 when this conversation has been closed.

[iamazik]

Please inform the customer of conversation # 483441 when this conversation has been closed.

[mariusghitulescu]

Please inform the customer of conversation # 483465 when this conversation has been closed.

[amboutwe]

Please inform the customer of conversation # 483491 when this conversation has been closed.

[amboutwe]

Please inform the customer of conversation # 483505 when this conversation has been closed.

[rgomezp]

Hello @Jerparx ,
Just wanted to update this issue that we have released a new version of the OneSignal plugin with a fix for this specific bug.

Cheers

[littleseed]

Thks.
Paolo.

------ Messaggio originale ------
Da: "Rodrigo Gomez Palacio" [e-mail]
A: "Yoast/wordpress-seo" [e-mail]
Cc: "littleseed" [e-mail]; "Comment"
[e-mail]
Inviato: 13/03/2019 21:06:07
Oggetto: Re: [Yoast/wordpress-seo] Getting a Blank Meta Box When Using
Classic Editor plugin and OneSignal Push Notifications (#12418)

Hello @Jerparx https://github.com/Jerparx ,
Just wanted to update this issue that we have released a new version of
the OneSignal plugin with a fix for this specific bug.

Cheers

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Yoast/wordpress-seo/issues/12418#issuecomment-472584348,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpoG2yygDqLk4j_zmcT5l2yV1sK4-5Mks5vWVovgaJpZM4bspS_.

[littleseed]

I installed the upgrade, but the problem persists...
Paolo.

------ Messaggio originale ------
Da: "Paolo Semino" [e-mail]
A: "Yoast/wordpress-seo"
[e-mail];
"Yoast/wordpress-seo" [e-mail]
Cc: "Comment" [e-mail]
Inviato: 13/03/2019 21:07:02
Oggetto: Re[2]: [Yoast/wordpress-seo] Getting a Blank Meta Box When
Using Classic Editor plugin and OneSignal Push Notifications (#12418)

Thks.
Paolo.

------ Messaggio originale ------
Da: "Rodrigo Gomez Palacio" [e-mail]
A: "Yoast/wordpress-seo" [e-mail]
Cc: "littleseed" [e-mail]; "Comment"
[e-mail]
Inviato: 13/03/2019 21:06:07
Oggetto: Re: [Yoast/wordpress-seo] Getting a Blank Meta Box When Using
Classic Editor plugin and OneSignal Push Notifications (#12418)

Hello @Jerparx https://github.com/Jerparx ,
Just wanted to update this issue that we have released a new version
of the OneSignal plugin with a fix for this specific bug.

Cheers

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Yoast/wordpress-seo/issues/12418#issuecomment-472584348,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpoG2yygDqLk4j_zmcT5l2yV1sK4-5Mks5vWVovgaJpZM4bspS_.

[rgomezp]

Hello Paolo,
What is the problem you are seeing?

[LockeAG]

Hello @Jerparx ,
Just wanted to update this issue that we have released a new version of the OneSignal plugin with a fix for this specific bug.

Cheers

I just updated , but it didn't work at all , Problem persist

[rgomezp]

Can you please hard-refresh? This clears the cache and reloads the JS file

[littleseed]

Empty Yoast Seo sections if using Classic Editor Plugin

------ Messaggio originale ------
Da: "Rodrigo Gomez Palacio" [e-mail]
A: "Yoast/wordpress-seo" [e-mail]
Cc: "littleseed" [e-mail]; "Comment"
[e-mail]
Inviato: 13/03/2019 21:10:03
Oggetto: Re: [Yoast/wordpress-seo] Getting a Blank Meta Box When Using
Classic Editor plugin and OneSignal Push Notifications (#12418)

Hello Paolo,
What is the problem you are seeing?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Yoast/wordpress-seo/issues/12418#issuecomment-472585734,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpoGxKMycLXVP0JqkE5BdyPad3XzCzLks5vWVsagaJpZM4bspS_.

[LockeAG]

Hello Paolo,
What is the problem you are seeing?

Is the same console error specified in the main post of this thread.

[Pcosta88]

Please inform the customer of conversation # 483487 when this conversation has been closed.

[littleseed]

After hard refresh it seems to work as usual.
Thks.
paolo.

------ Messaggio originale ------
Da: "Rodrigo Gomez Palacio" [e-mail]
A: "Yoast/wordpress-seo" [e-mail]
Cc: "littleseed" [e-mail]; "Comment"
[e-mail]
Inviato: 13/03/2019 21:11:04
Oggetto: Re: [Yoast/wordpress-seo] Getting a Blank Meta Box When Using
Classic Editor plugin and OneSignal Push Notifications (#12418)

Can you please hard-refresh? This clears the cache and reloads the JS
file

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Yoast/wordpress-seo/issues/12418#issuecomment-472586103,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpoG1g8cWq_SKoSimkNKgBlXJoTUdJ5ks5vWVtYgaJpZM4bspS_.

[LockeAG]

After hard refresh it seems to work as usual. Thks. paolo.
…
------ Messaggio originale ------ Da: "Rodrigo Gomez Palacio" [e-mail] A: "Yoast/wordpress-seo" [e-mail] Cc: "littleseed" [e-mail]; "Comment" [e-mail] Inviato: 13/03/2019 21:11:04 Oggetto: Re: [Yoast/wordpress-seo] Getting a Blank Meta Box When Using Classic Editor plugin and OneSignal Push Notifications (#12418)
Can you please hard-refresh? This clears the cache and reloads the JS file — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12418 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/ACpoG1g8cWq_SKoSimkNKgBlXJoTUdJ5ks5vWVtYgaJpZM4bspS_.

For me Hard refresh , Drop Cache from Server , Cloudflare purge, and I keep getting the same error .

😅😅😅😅

[rgomezp]

@LockeAG have the line-numbers changed from OP's original screenshot? In other words, are you still getting the same error even with the reloaded code? If you can include the full stack-trace or screenshot similar to OP's, we would be much better able to know what's going on and assist you. Thanks

[LockeAG]

@LockeAG have the line-numbers changed from OP's original screenshot? In other words, are you still getting the same error even with the reloaded code? If you can include the full stack-trace or screenshot similar to OP's, we would be much better able to know what's going on and assist you. Thanks

Sure :

[rgomezp]

Yeah, it looks like your browser is caching the previous version. Please make sure to do a hard-refresh ("force-reload") or clear your browser's cache. Another way to verify is by opening up a different profile in your browser or trying on another browser altogether (Safari, Chrome, Firefox). You can find more info here: https://wordpress.org/support/topic/version-1-16-16-thread/

[amboutwe]

Please inform the customer of conversation # 483549 when this conversation has been closed.

[LockeAG]

Yeah, it looks like your browser is caching the previous version. Please make sure to do a hard-refresh ("force-reload") or clear your browser's cache. Another way to verify is by opening up a different profile in your browser or trying on another browser altogether (Safari, Chrome, Firefox). You can find more info here: https://wordpress.org/support/topic/version-1-16-16-thread/

I tried in Firefox , Safari , Brave, Chrome , All incognito , the problem persist .

[michaelbriantina]

Please inform the customer of conversation # 483589 when this conversation has been closed.

[jeroenrotty]

This should be closed as the OneSignal 1.16.16 release has fixed it, remind all users to clear local browser cache.

[PatrickYoast]

Closing as this is fixed as mentioned above by Jeroen