• Resolved mumbomedia

    (@mumbomedia)


    I got this error shown on different tab of the new settings layout on different customer systems with different themes.
    Therefore I disbelieve that the issue isn’t related to a specific wordpress theme.

    Beside the display of this error message on the settings page I got some javascript error in the developer console.

    The first ones are two times the message “e is undefined new-settings.js:5:6588 followed by even two times “TypeError t.split is not a function” in react-dom.min.js:9:64017
    Last but not least I got a localize message stating that an empty string was passed to getElementById() in new-settings.js:245:365.

    Would be great if you could fix it asap because due to this issue adjusting the settings isn’t possible.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @mumbomedia

    I’m sorry about your experience with the plugin. Often, we see problems occur in combination with another plugin or theme. The fastest way to rule out any conflict is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Twenty.

    Please test this on your development or staging site if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin has a troubleshooting mode, which does not affect normal visitors to your site.

    If 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

    If you feel uncomfortable doing this yourself or if this does not solve your issue, our Yoast SEO Premium plugin comes with one year of (technical) support.

    @maybellyne I also have this issue – only other plugin is ACF.

    The error is coming from the draftJs.js external javscript file, enqueued by yoast directly.

    It completely kills the ability to edit content types/taxonomies with the new Yoast UI.

    Thread Starter mumbomedia

    (@mumbomedia)

    @twentyzerotwo Glad to hear that it is indeed a common issue.

    Thread Starter mumbomedia

    (@mumbomedia)

    @maybellyne
    I’m aware how to do a debugging.
    I’m a professional webmaster.
    But as I mentioned already this problem occurs on different customer system with different themes and different plugins.
    Also as @twentyzerotwo mentioned it also occurs if only acf is installed alongside the yoast seo plugin.
    The plugin works well since ui was changed.
    Now the plugin isn’t usable anymore and if the issue isn’t fixed asap I have to replace it with another plugin causing a lot of work since I had to do it on ~ 80 installations.

    Thread Starter mumbomedia

    (@mumbomedia)

    I installed one of the affected system on my test server and disabled plugins and also changed the theme both once to twentytwentytwo and twentytwentythree. Still I get the error when I try to call /wp-admin/admin.php?page=wpseo_page_settings#/format-archives.

    So now I can say with 100% certainty that something about the new UI is not working as expected. However, since the JS files are all minified, it is impossible for me to debug even further. Also, I lack the necessary knowledge of which JS functions should be called and how they in turn interact with other JS functions. Therefore, I would like to kindly ask you again to check and fix the bug as soon as possible. Otherwise I have no choice to replace your great plugin with a different working plugin which would caused a lot of extra work for me and this would be the last I want.

    Thread Starter mumbomedia

    (@mumbomedia)

    @twentyzerotwo That is exactly the issue I’m facing.
    Great to read that it is fix with the next version dated for Feb. 7th which is next week.

    Plugin Support Maybellyne

    (@maybellyne)

    Hello @mumbomedia

    Thanks for your patience while we investigate the issue. Can you check what disable-post_format?is in Yoast SEO > Tools > Export Settings? If it’s disable-post_format = 1?then format archives are disabled but if disable-post_format = ?then they are enabled.

    Does changing this to the opposite and importing the new settings help?

    We look forward to hearing from you.

    Thread Starter mumbomedia

    (@mumbomedia)

    Indeed after exporting, changing disable-post_format from 1 to nothing and reimporting the settings the tab is showned as expected.
    Even after disabling this archive via its tab it is shown as expected.

    Plugin Support devnihil

    (@devnihil)

    @mumbomedia Thanks for confirming that corrected the issue.

    Also, whereas the release containing the fix for this bug will be available on Feb 7, in the meantime you can use the release candidate available here to immediately correct the issue.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘t.split is not a function’ is closed to new replies.