AI Engine Broken and Blank on Frontend and Backend (Google Chrome)

  • Resolved mcsteebler

    (@mcsteebler)


    3 months, 3 weeks ago

    Hi, I’ve run into this issues on both WordPress 6.6.2 and 6.7.1. AI Engine no longer works on the front and the backend doesn’t show any settings (white blank screen). This issue only happens in Google Chrome. It’s working fine in Safari and Brave Browser.

    • This topic was modified 3 months, 3 weeks ago by mcsteebler.
    • This topic was modified 3 months, 3 weeks ago by mcsteebler.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter mcsteebler

    (@mcsteebler)

    Here’s the console error logs from the blank backend settings page:

    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

    index.js?ver=1726168565:2 Uncaught TypeError: eh is not a function at HTMLDocument.<anonymous> (index.js?ver=1726168565:2:841280)(anonymous)@index.js?ver=1726168565:2

    Error logs from the frontend form that no longer loads:

    react-dom.min.js?ver=18.3.1:10 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

    forms.js?ver=1726168565:2 Uncaught TypeError: er is not a function
    at forms.js?ver=1726168565:2:54608
    at NodeList.forEach ()
    at e (forms.js?ver=1726168565:2:54342)
    at HTMLDocument. (forms.js?ver=1726168565:2:54673)

    • This reply was modified 3 months, 3 weeks ago by mcsteebler.

    Same problem here.

    Plugin Support Val Meow

    (@valwa)

    Hey @mcsteebler! ??

    This appears to be a browser-specific issue with Chrome version 131.0.6778.86. Unfortunately, there isn’t much we can do on our end about this. Please ensure you are using the latest version of WordPress on your website and that your browser’s local cache is cleared. Thanks!

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