• Resolved bobsled

    (@bobsled)


    Yoast in not loading now. All I get is a blank screen, and the Yoast panel in edit mode is blank. I have the lastest version of Yoast and WordPress.

    The debug log shows: Function _load_textdomain_just_in_time was called incorrectly. This is usually an indicator for some code in the plugin or theme running too early.

    When I disable all plugins, and only enable Yoast, the probems persisits.

    I’ve seen other users noting this issue, so hopefully you can release an update.

Viewing 15 replies - 1 through 15 (of 17 total)
  • Same problem

    Same issue here too.

    Plugin panel will not display/reveal on pages where it is installed.

    Have tried plugin conflict tests: no conflicts found.

    Seems to be combination of WP 6.7.1 and Yoast 23.9

    Same issue. I have seen the error resolve temporarily by clearing my history/cache, but it returns.

    I’m experiencing this issue too. I removed all the plugins, kept only Yoast, and it still doesn’t work.

    I contacted their support, but unfortunately, their assistance is only available for premium users.

    Does anyone have any tips?

    I have the same problem and it’s been more than 2 days and they haven’t given me a solution. Please write to the official website via chat to see if they will fix it, because they blame the browser and WordPress.

    I would add that I see various errors in the console for the yoast settings screen

    Uncaught TypeError: Cannot read properties of undefined (reading ‘unstable_scheduleCallback’)
    at n (react-dom.min.js?ver=18.3.1:10:105894)
    at react-dom.min.js?ver=18.3.1:10:129073
    at react-dom.min.js?ver=18.3.1:10:129108

    Uncaught TypeError: (0 , n.render) is not a function
    at l (help-scout-beacon.js?ver=4cff4f48af6493046757:7:113)
    at window.wpseoHelpScoutBeaconConsent (help-scout-beacon.js?ver=4cff4f48af6493046757:69:4)
    at admin.php?page=wpseo_dashboard:1303:236

    Uncaught TypeError: (0 , l.render) is not a function
    at HTMLDocument. (general-page.js?ver=ef70b0b4ec9f15f1bf21:46:4428)

    Same here!!
    YOAST please provide a solution, urgently!!

    Let’s give them one more business day to respond with something other than their standard “go disable all other plug-ins”(which has been tried). After that we can all start leaving bad reviews and taking them off our Christmas lists.

    yes, the most mediocre developers only say to deactivate all the plugins and reactivate them, and look in other browsers, and delete the browser and web cache, when evidence has been sent to them that the problem is with the plugins.

    Hey everyone, just to share…

    I use WP-Rocket and also Cloudflare.

    However, even after disabling WP-Rocket, adding bypass cache rules in Cloudflare, pausing it entirely, and clearing browser cookies and cache, it still didn’t work!

    I also use wp-rocket and cloudflare. Clearing my caches did not work for me, either. I’d like atleast an acknowledgement of the issue. It’s confounding. I manage multiple websites, and this issue only presents on one of them, with the same versions of wordpress and Yoast. On our dev site, which is pretty much a copy of the one with the issue, it also does not present. I have uninstalled and re-installed the plugin. Cleared the cache, reinstalled wordpress. No luck. I posted my console errors. Are other people seeing these same errors?

    Thread Starter bobsled

    (@bobsled)

    With a bit of further investigation, this issue isn’t soley a Yoast problem, hence probably the lack of answers from Yoast support.

    The issue is affecting a number of plugins on one of my sites. These include Astra Pro plugin, Jetpack (which is ironic as it is an Automattic plugin), and WP Rollback.

    It seems to be a widespred WordPress core issue since the release of 6.7. Take a look at this WordPress core ticket with comments from developers.

    When you read it, you can see that there is a lot of discussion about how to solve the issue. But sadly, there seems to be no aggreement yet. Hopefully, they can come to a resolution to either rollback the change, or modify the code to solve the issue in 6.7.2.

    Fingers crossed.

    Huh. I just checked and everything is back to normal. I didn’t make any changes but now I can see Yoast settings, etc.

    Hi everyone,

    First of all, thank you all for sharing your experiences and insights regarding this issue. It seems like many of us have been scratching our heads over this one.

    I also spent an entire afternoon running small tests and even went as far as creating a staging site to troubleshoot. Strangely, my freshly cloned staging site had no issues at all—no blank Yoast screens or errors. I was baffled!

    What really threw me off was when I realized that simply opening my live site in an incognito browser tab “fixed” the problem. That ruled out any plugin or server-specific issues. Perhaps this is tied to the latest WordPress version? I’m not entirely sure.

    I tried clearing the cache on WP Rocket, purging Cloudflare, and even revisiting my browser cookies—none of it worked. In the end, the solution turned out to be the simplest one. Here’s what worked for me:

    1. Inspect the page in your browser (right-click anywhere and click Inspect).
    2. Right-click the refresh icon in your browser tab.
    3. Select “Empty Cache and Hard Reload” from the dropdown menu.

    After doing this, everything went back to normal, and Yoast started loading perfectly again!

    I hope this helps someone else save time and frustration. If this works for you, please share your experience—it might help identify a broader pattern!

    Cheers,
    Ricardo

    Same. I didn’t do anything, and it resolved. Would love to know what happened here.

Viewing 15 replies - 1 through 15 (of 17 total)
  • You must be logged in to reply to this topic.