Null in window.wp.data.select(‘core/editor’)

  • Resolved codexhemes

    (@codexhemes)


    4 years, 2 months ago

    Hi guys,

    we are developers of the theme TheGem. We are facing the following issue:
    in blog post page options (classic editor mode) when your plugin is active window.wp.data.select(‘core/editor’) always returns null. We use window.wp.data.select(‘core/editor’) in order to read/write the format and the excerpt of the blog post in this way:

    window.wp.data.select(‘core/editor’).getEditedPostAttribute(‘excerpt’);
    window.wp.data.dispatch( ‘core/editor’ ).editPost( { excerpt: value } );
    window.wp.data.select(‘core/editor’).getEditedPostAttribute(‘format’);
    window.wp.data.dispatch( ‘core/editor’).editPost({format: value });

    We can provide a link so you can check this. The question is: why window.wp.data.select(‘core/editor’) is returning null when your plugin is active? Would you be so kind to look into this issue?

    Thank you!
    Regards,
    Gregor

Viewing 6 replies - 1 through 6 (of 6 total)

  • @codexhemes

    We’re sorry you’re having trouble with our plugin when activated it together with your theme. I imagine this can be frustrating for you.

    Unfortunately, we are not familiar with the above error, mentioned theme, and its coding structure so to pinpoint possible conflicts in JavaScript errors as stated above. However, we would like to investigate this issue and therefore, we expect a little more information about your setup. This might help us replicate the issue on our end:

    1. Can you confirm you are using the most recent Yoast SEO v15.6.2? If you update, does the issue resolve?

    2. Are all your non-Yoast plugins and themes also updated?

    3. Can you confirm you are using WordPress 5.6?

    4. Does the error above occurs on the admin side or frontend? In addition, could you please show us some example URLs where the issue occurs so that we can take a look at them?

    5. Does the above errors still occur when you deactivate all non-Yoast plugins and activate the current theme?

    5. If possible, please provide us as much information as possible in order to replicate the error on our end.

    We look forward to hearing from you.

    Thread Starter codexhemes

    (@codexhemes)

    @suascat_wp

    Hi Suwash,
    thank you for your reply.

    1. yes
    2. yes
    3. yes
    4. in wp-admin. I can provide you login details as well so you can check it, however please provide an info how to do it in a secure way
    5. yes, the problem is with Yoast activated, no matter, which theme is in use: window.wp.data.select(‘core/editor’) returns null

    Thanx again.

    Hi Gregor,

    There is an adjacent issue with Gutenberg editor in regards to the wp.data.select as described here https://github.com/WordPress/gutenberg/issues/28032. We know you are not using Guteneberg but you have it on your WordPress version even though it has been disabled. We are also not sure if that issue is close to the issue you are having. If it is, a user described a workaround here (not sure it will work with your set-up).

    If that issue doesn’t adequately describe the issue you are having, we ask that you please do the following:

    1. Are all your non-Yoast plugins and themes also updated?

    2. Can you confirm you are using WordPress 5.6? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider.?Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast.?This guide explains more:?https://yoast.com/why-we-dont-support-old-wordpress-versions/.

    3 We had another recent release. Can you confirm you are using the most recent Yoast SEO, v15.6.2? If you update, does the issue resolve?

    4. If all are updated, please Check for conflicts. Install the Healthcheck plugin and enable troubleshooting. Then switch to a standard theme like 2020. Does the issue resolve? NOTE: This will not affect how users see your site.

    We ask as we are not sure if you did a full conflict check.

    If the issue happens with Yoast as the only plugin active (or if there is a conflict between Yoast and some other theme or plugin) we ask that you please create a new GitHub issue?for our developers. Please report the issue to a third party developer as well.

    Thread Starter codexhemes

    (@codexhemes)

    @pcosta88

    Hi, thank you for your reply and for sharing the link. However it is not quite what we have and what we are experiencing and this workaround doesn’t help to resolve. The problem appears only if there is Yoast SEO in classic editor and the theme (all other plugins are inactive).

    1. yes, everything is udpated
    2. yes, 5.6
    3. yes, the latest release
    4. we have checked, as said above, the problem appears only if Yoast SEO is active.

    Hi Gregor,

    Ok! Based on the information you provided, we expect this to be an issue. We’re actively using the issue tracking on our GitHub repository so your best next step would be to create a new issue for our developers at https://github.com/Yoast/wordpress-seo/issues/new. You will need an account to create a new issue. If this is your first bug report, please check out: https://kb.yoast.com/kb/how-to-write-a-good-bug-report/.

    Issue reports are monitored so you can expect a reply.

    Hi @codexhemes

    We’re closing this thread as there seem no further questions from you. Feel free to open a bug report in Github so your issue can be further investigated. Please feel free to open a new thread should you have further concerns.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Null in window.wp.data.select(‘core/editor’)’ is closed to new replies.