Yoas SEO stopped working after update?

@szilviad Both the issue you are experiencing with the Yoast metabox and the Configuration Wizard are likely caused by a conflict with another plugin or theme.

If you have already confirmed that both Yoast SEO and WordPress are up to date and the issue is still occurring, we would next recommend performing a conflict check to determine whether another plugin or theme is interfering with the Yoast plugin.

The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?Twenty Nineteen.?Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.As we can imagine that you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process:?How to check for plugin conflicts.

@devnihil, thanks for your response.
I went through the troubleshooting thing and during troubleshooting I need two plugins enabled only to reproduce the problem. These are Astro Framework (which creates the custom post types where I experience the problem) and of course, Yoast SEO itself as I need to see that is working with said custom post types.
The theme is twenty twenty as recommended and unfortunately, the same issue crops up.

The reason I think there was something amiss in the last update is that before the latest version it was working perfectly with all the normal posts and the aforementioned custom post types as well. Now it DOES work with the normal posts, but doesn’t with the custom post types.

Umm any other ideas what might have broken it?

As I see from the changelog this last one was quite a hefty changeset so it might have been something innit that slipped through QAs cracks? ??

Greatly appreciate your kind help in advance,
Best,
Sz

@szilviad Thanks for your reply. If the issue with the Yoast metabox not loading successfully is still occurring with only Yoast SEO, a default theme, and the Astro Framework plugin we would next recommend check on the edit screen for the custom post type for any JavaScript errors. We have a guide on how to check for these using the browser console here: https://yoast.com/help/how-to-find-javascript-errors-with-your-browsers-console/

If you are seeing JavaScript errors can you please reply back and include the errors? These would be helpful in ascertaining whether the issue is due to bug in the Yoast SEO plugin.

@devnihil, yeah sure.
Here’s the output:
post-edit-1470.js:1 Marking links with nofollow/sponsored has been disabled for WordPress installations < 5.4. Please upgrade your WordPress version or install the Gutenberg plugin to get this Yoast SEO feature.

value @ post-edit-1470.js:1
e @ post-edit-1470.js:1
(anonymous) @ post-edit-1470.js:1
i @ load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2
fireWith @ load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2
ready @ load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2
J @ load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2
acf-input.min.js?ver=5.7.12:3 Uncaught (in promise) TypeError: Cannot read property 'getPostEdits' of null
    at acf.Model.onChange (acf-input.min.js?ver=5.7.12:3)
    at d (load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2)
    at data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
    at Array.forEach (<anonymous>)
    at o (data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2)
    at data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
    at p (data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2)
    at data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
    at Object.dispatch (data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2)
    at tN.<anonymous> (post-edit-1470.js:1)
onChange @ acf-input.min.js?ver=5.7.12:3
d @ load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2
(anonymous) @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
o @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
(anonymous) @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
p @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
(anonymous) @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
(anonymous) @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
(anonymous) @ post-edit-1470.js:1
c.fire @ tinymce.min.js?ver=4960-20190918:2
fire @ tinymce.min.js?ver=4960-20190918:2
yw @ tinymce.min.js?ver=4960-20190918:2
f.content_style.a @ tinymce.min.js?ver=4960-20190918:2
(anonymous) @ tinymce.min.js?ver=4960-20190918:2
Promise.then (async)
e @ tinymce.min.js?ver=4960-20190918:2
loadAll @ tinymce.min.js?ver=4960-20190918:2
bw @ tinymce.min.js?ver=4960-20190918:2
ww @ tinymce.min.js?ver=4960-20190918:2
Aw @ tinymce.min.js?ver=4960-20190918:2
(anonymous) @ tinymce.min.js?ver=4960-20190918:2
(anonymous) @ tinymce.min.js?ver=4960-20190918:2
qt @ tinymce.min.js?ver=4960-20190918:2
u @ tinymce.min.js?ver=4960-20190918:2
n @ tinymce.min.js?ver=4960-20190918:2
l.<computed>.l.<computed>.l.<computed>.o.onload @ tinymce.min.js?ver=4960-20190918:2
load (async)
(anonymous) @ tinymce.min.js?ver=4960-20190918:2
qt @ tinymce.min.js?ver=4960-20190918:2
u @ tinymce.min.js?ver=4960-20190918:2
Di.loadScripts @ tinymce.min.js?ver=4960-20190918:2
Di.loadQueue @ tinymce.min.js?ver=4960-20190918:2
(anonymous) @ tinymce.min.js?ver=4960-20190918:2
waitFor @ tinymce.min.js?ver=4960-20190918:2
(anonymous) @ tinymce.min.js?ver=4960-20190918:2
(anonymous) @ tinymce.min.js?ver=4960-20190918:2
qt @ tinymce.min.js?ver=4960-20190918:2
u @ tinymce.min.js?ver=4960-20190918:2
n @ tinymce.min.js?ver=4960-20190918:2
l.<computed>.l.<computed>.l.<computed>.o.onload @ tinymce.min.js?ver=4960-20190918:2
load (async)
(anonymous) @ tinymce.min.js?ver=4960-20190918:2
qt @ tinymce.min.js?ver=4960-20190918:2
u @ tinymce.min.js?ver=4960-20190918:2
Di.loadScripts @ tinymce.min.js?ver=4960-20190918:2
Di.loadQueue @ tinymce.min.js?ver=4960-20190918:2
(anonymous) @ tinymce.min.js?ver=4960-20190918:2
Bw @ tinymce.min.js?ver=4960-20190918:2
Ow @ tinymce.min.js?ver=4960-20190918:2
render @ tinymce.min.js?ver=4960-20190918:2
n @ tinymce.min.js?ver=4960-20190918:2
(anonymous) @ tinymce.min.js?ver=4960-20190918:2
qt @ tinymce.min.js?ver=4960-20190918:2
e @ tinymce.min.js?ver=4960-20190918:2
C @ tinymce.min.js?ver=4960-20190918:2
d @ tinymce.min.js?ver=4960-20190918:2
a @ tinymce.min.js?ver=4960-20190918:2
acf-input.min.js?ver=5.7.12:3 Uncaught (in promise) TypeError: Cannot read property 'getPostEdits' of null
    at acf.Model.onChange (acf-input.min.js?ver=5.7.12:3)
    at d (load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2)
    at data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
    at Array.forEach (<anonymous>)
    at o (data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2)
    at data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
    at p (data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2)
    at data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
    at Object.dispatch (data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2)
    at post-edit-1470.js:1
onChange @ acf-input.min.js?ver=5.7.12:3
d @ load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2
(anonymous) @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
o @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
(anonymous) @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
p @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
(anonymous) @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
(anonymous) @ data.min.js?ver=e80048e7b309581a40e44b8bd8aaba41:2
(anonymous) @ post-edit-1470.js:1
Promise.catch (async)
t.default @ post-edit-1470.js:1
(anonymous) @ post-edit-1470.js:1
i @ load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2
fireWith @ load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2
ready @ load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2
J @ load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4.2:2

The interesting bit is Yoast is saying I have WP < 5.4 and I triple checked that I’m definitely running 5.4.2.

Does that help at all? Do you need me to do anything else?
Thanks again,
SZ

@devnihil since the code formatting in the above comment is quite ugly here’s the bit which tells you something I hope (as seeing the line numbers in minified versions of js files is not useful at all just breaks code formatting I guess):
acf-input.min.js?ver=5.7.12:3 Uncaught (in promise) TypeError: Cannot read property 'getPostEdits' of null

^^ this comes out twice.
and that error message with WP being < 5.4 which is not true.

Hi,

We would like some more information.

1. Are you using the Classic Editor or the Gutenberg block editor?

2. Does it only happen on Custom Post types which have an ACF field as a part of them? If so, what fields are in use?

3. Are all your non-Yoast plugins and themes also updated? For example are you using Advanced Custom Fields (ACF)? If so, is it updated? ACF’s most recent version is v5.8.13 according to the repository here: https://www.ads-software.com/plugins/advanced-custom-fields/

4. Are you using the Yoast pairing plugin with ACF? Is it updated to v2.6 according to the repository here https://www.ads-software.com/plugins/acf-content-analysis-for-yoast-seo/?

@pcosta88 , let me try to come back to all of these:
1., for that custom post type the classic editor is default and I’m using that.
2., These custom post types come with a theme I’m using so I assume they’re using them for all custom post types.
This is the exact theme I’m using:
https://themeforest.net/item/astro-showcasephotography-wordpress-theme/6364365?gclid=CjwKCAjw4MP5BRBtEiwASfwAL-B5kVxmvQtC6aJ8yw4iar0xLUhJJqoi4tWxwfKHmw0jbSeUSpT3URoCxZYQAvD_BwE
and only slightly modified the looks of it without touching the guts of the custom types.
3., Yes, all plugins are updated and the ACF plugin is not installed
4., I didn’t know such thing exists, but now I have installed it just to give it a go, to see if that fixes it and it didn’t. So when the problem became apparent I wasn’t using said plugin.

@pcosta88 it seems like you’ve just saved the day mate.
Based on your points 3 and 4 I’ve installed both plugins you asked about and magically it fixed the problem. So now these custom posts can be SEOd with Yoast.

Not sure if this is part of any documentation anywhere, but it might possibly be a good idea to mention it in some config docs … “if you’re using magical themes which add custom post types, you might as well need ACF + ACF Yoast pairing plugins ”

Where can I buy you a beer? ??
Thank you ever so much.
Cheers,
SZ

Hi,

Hahahah. ?? No, worries! We glad the issue has been resolved. If you experience any other issues feel free to create a new topic!

@szilviad As soon as we’ll have in-person events again, you can keep track of where we’ll be at https://yoast.com/about-us/events/.

Spoiler alert: it’s very likely you can find him at the next WordCamp US ??

The only error message now, is Yoast telling me I’m running < 5.4 and I’m not. ??

@tacoverdo yeah once in-person events are restarted and y’all are near the UK we might catch up alright? ??
Cheers,
SZ

@szilviad

We understand that you are getting a notification from Yoast that you are running <5.4 and that is incorrect. We’d love to take a look at this!

We ask that you please create a separate topic for this issue. This helps to manage the different issues. You may make a new topic here: https://www.ads-software.com/support/plugin/wordpress-seo/#new-post.

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.