• Resolved Ian Pegg

    (@ianpegg)


    Hello,

    I haven’t deployed Yoast v20+ to any live environment yet as I have been consistently encountering a type error whenever I visit the ‘Site Connections’ setting page.

    The error I’m getting on this page is:

    "Cannot read properties of undefined (reading 'prevOffset')"

    I have cleared my cookies and cache for the site in question and deactivated all other plugins / non-standard themes but the issue persists.

    In the browser console, I have this little beauty:

    react-dom.min.js?ver=17.0.1:9 TypeError: Cannot read properties of undefined (reading 'prevOffset')
    at c (element.min.js?ver=47162ff4492c7ec4956b:2:3020)
    at p (element.min.js?ver=47162ff4492c7ec4956b:2:3675)
    at a (new-settings.js?ver=343dc024f15b584e8bc06a884de539ef:1:5062)
    at Ja (new-settings.js?ver=343dc024f15b584e8bc06a884de539ef:248:553)
    at ct (react-dom.min.js?ver=17.0.1:9:43430)
    at os (react-dom.min.js?ver=17.0.1:9:111136)
    at Ur (react-dom.min.js?ver=17.0.1:9:77643)
    at Ir (react-dom.min.js?ver=17.0.1:9:77571)
    at Dr (react-dom.min.js?ver=17.0.1:9:77434)
    at Pr (react-dom.min.js?ver=17.0.1:9:74429)

    WordPress core is running 6.1.1 and, so far, I have consistently seen this issue exhibited by both Yoast v20.0.x and v20.2.x.

    In my development environment where I am testing these releases, caching is disabled at all levels and I have deleted all transients.

    Please advise.

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

    (@maybellyne)

    Hello @ianpegg

    I’m sorry about that error; it seems to be related to incorrect translations in some locales on translate.www.remarpro.com where placeholders are incorrectly used in their translations. Can you let me know what locale your WordPress is in?

    Thread Starter Ian Pegg

    (@ianpegg)

    Hello @maybellyne

    Thank you for getting back to me. Most of the sites I manage are using UK English translations rather than the stock US English. I’ve seen the error on all UK sites I’ve tested so far.

    As an aside, I had also noticed that one of the headings on the top settings page appears to be in Mandarin. I suspect this is related to the above issue?

    • This reply was modified 2 years ago by Ian Pegg. Reason: Added extra information about incorrectly translated heading
    Jeroen Rotty

    (@jeroenrotty)

    Hey Ian,

    Thank you for your reply and extra info.

    I configured Yoast SEO in en_UK locally and checked the Site connections page. I was not able to replicate the error at this time. Can you please try to see if the issue still persists when you run 20.2.1 and make sure you installed any translation updates?

    For the aside, on what page did you see the mandarin/chinese characters? I know that we fixed an issue on translate.www.remarpro.com for a few English locales that 1 string was indeed translated with such characters, but I thought we had fixed all of those. If you can let me know if you can still see it and where, I’d be happy. Thank you!

    Thread Starter Ian Pegg

    (@ianpegg)

    Hello @jeroenrotty

    Thanks for taking the time to test for this issue. I’ve just tried upgrading to the latest release again – and this time I updated translations before going to the settings page. Doing this fixed both issues!

    I didn’t stop to consider that an outdated translation set could cause a fatal in JS. Perhaps the plugin could be configured to fall back to the stock US English when issues like this arise?

    Jeroen Rotty

    (@jeroenrotty)

    Hey @ianpegg,

    Thank you for your reply and testing. Well, the issue we had recently is that some translations in some locales had some placeholders in an incorrect order – and the placeholders were filled by HTML elements, so that broke the editor. Having that fallback to another locale that might also have that issue, is not really a solution to the issue, unfortunately. But I’m happy to hear it’s sorted!

    I’ll mark the topic as resolved for now. Have a great day!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Admin backend type error in Yoast >= v20’ is closed to new replies.