"AI" plugin 1.0.1 – Connectors and AI settings pages load blank (JavaScript error) on WordPress 7.0

[polipsicomorfico]

Hello,

I'd like to report a compatibility issue with the "AI" plugin (by WordPress.org Contributors, version 1.0.1).

Problem

After installing and activating the plugin, its configuration pages load completely blank — the content area stays empty and the interface never renders, so it's impossible to configure a provider or enter an API key:

• Settings → Connectors (options-connectors.php)
• Settings → AI (options-general.php?page=ai-wp-admin)

The React app container (#options-connectors-wp-admin-app) stays empty, so the UI is never mounted.

Console errors

Two JavaScript errors appear on every load of those pages:

1. Error: You tried to opt-in to unstable APIs as module "@wordpress/route". This feature is only for JavaScript modules shipped with WordPress core.
   — from wp-includes/js/dist/private-apis.min.js and wp-includes/js/dist/script-modules/route/index.min.js

2. TypeError: Cannot read properties of undefined (reading 'privateApis')
   — from wp-includes/js/dist/block-library.min.js

Environment

• WordPress version: 7.0
• "AI" plugin: 1.0.1
• "AI Provider for Anthropic" plugin: 1.0.3 (active)

Steps already taken

I ran a conflict test by temporarily deactivating the other AI-related plugins on the site (Easy MCP AI, Extendify, Site Assistant) and reloading the pages. The error and the blank screen remained identical, so it does not appear to be a conflict with those plugins.

Could you let me know whether this is a known issue, and whether a fix or workaround is available? Happy to provide further logs or details.

Thank you.

[polipsicomorfico]

Update — additional diagnosis:

I tried the "AI Services" plugin by Felix Arntz (version 0.7.4) as an alternative on the same site, and its settings page (options-general.php?page=ais_services) loads completely blank as well.

Since two different React-based admin UIs, from different authors, fail in the same way, the root cause appears to be at the WordPress core JavaScript level rather than in this plugin specifically. The common error is still TypeError: Cannot read properties of undefined (reading 'privateApis') coming from wp-includes/js/dist/block-library.min.js (a core file). With "AI Services" there is additionally a Minified React error #130 from wp-includes/js/dist/vendor/react-dom.min.js.

This suggests the shared @wordpress/* script-module dependencies in wp-includes/js/dist/ are in an inconsistent state on this environment (possibly an incomplete WordPress 7.0 update, mismatched/corrupted core JS files, or a plugin/theme that dequeues or overrides those scripts), which breaks any modern React-based admin interface that depends on them.

I'm planning to verify whether the standard block editor is affected too, and to try reinstalling/repairing the WordPress core files. Sharing this here in case it helps others seeing the same blank-screen symptom. Happy to provide more details.

[polipsicomorfico]

Further confirmation that this is an environment/core-level issue, not specific to this plugin:

On the same site, the standard WordPress block editor (post-new.php) also loads completely blank — a fully white page with no editor and no content rendered. The block editor is core functionality unrelated to any AI plugin, so this strongly indicates the problem is at the WordPress core / environment level.

A relevant console message captured during the editor load:
jQuery.Deferred exception: Cannot read properties of undefined (reading 'getEditedPostAttribute') — a script trying to access the editor data store (wp.data) finds it undefined, i.e. the core editor/script-module dependencies never initialize.

Environment note: WordPress reports it is already on the latest version (7.0, it_IT), and all plugins, themes and translations are up to date. As a next step I'm going to try reinstalling/repairing the core files via Dashboard → Updates → "Reinstall version 7.0".

In short: the blank-screen symptom affects both the "AI" plugin, the "AI Services" plugin, and the native block editor, pointing to inconsistent/broken shared @wordpress/* core JavaScript on this specific environment rather than a bug in this plugin.