Title: Calling AI Settings went wrong
Last modified: June 27, 2026

---

# Calling AI Settings went wrong

 *  Resolved [meinService](https://wordpress.org/support/users/meinservice/)
 * (@meinservice)
 * [1 week, 1 day ago](https://wordpress.org/support/topic/calling-ai-settings-went-wrong/)
 * Instead of Displaying page=ai-wp-admin, the page only shows:
   **Something went
   wrong!** Show Error / Hide Error

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Thread Starter [meinService](https://wordpress.org/support/users/meinservice/)
 * (@meinservice)
 * [1 week, 1 day ago](https://wordpress.org/support/topic/calling-ai-settings-went-wrong/#post-18949766)
 * Das Problem lag daran, dass die WordPress REST-API (unter `/wp-json/`) einen **
   404 Not Found**-Fehler zurückgegeben hat. Da das React-Dashboard des Core-AI-
   Plugins diese API benötigt, stürzte die Oberfläche ab, wobei die Fehlermeldung
   leer blieb (weil React ein Rohdaten-Response-Objekt statt eines Text-Fehlers 
   abgefangen hat).
 * Ich habe ein Browser-Subagent gestartet, das:
    1. Den Fehler in der Browser-Konsole diagnostiziert hat (`404` auf `/wp-json/`).
    2. Auf die WordPress-Einstellungen-Seite für **Permalinks** gegangen ist (`/wp-
       admin/options-permalink.php`) und dort auf **„Änderungen speichern“** geklickt
       hat.
    3.  - Dadurch wurden die internen Apache-Rewrite-Regeln und WordPress-Permalinks
          zurückgesetzt/neu generiert.
 * Die REST-API liefert nun wieder korrekte JSON-Daten zurück, und die Core-AI-Einstellungsseite
   unter `http://localhost/wordpress/wp-admin/options-general.php?page=ai-wp-admin`**
   lädt jetzt wieder einwandfrei und ohne Fehler!**
 *  Plugin Author [Jeffrey Paul](https://wordpress.org/support/users/jeffpaul/)
 * (@jeffpaul)
 * [4 days, 14 hours ago](https://wordpress.org/support/topic/calling-ai-settings-went-wrong/#post-18952640)
 * [@meinservice](https://wordpress.org/support/users/meinservice/) I used [Google Translate for your comment and it provided](https://translate.google.com/?sl=auto&tl=en&text=Das%20Problem%20lag%20daran%2C%20dass%20die%20WordPress%20REST-API%20(unter%20%2Fwp-json%2F)%20einen%20404%20Not%20Found-Fehler%20zur%C3%BCckgegeben%20hat.%20Da%20das%20React-Dashboard%20des%20Core-AI-Plugins%20diese%20API%20ben%C3%B6tigt%2C%20st%C3%BCrzte%20die%20Oberfl%C3%A4che%20ab%2C%20wobei%20die%20Fehlermeldung%20leer%20blieb%20(weil%20React%20ein%20Rohdaten-Response-Objekt%20statt%20eines%20Text-Fehlers%20abgefangen%20hat).%0A%0AIch%20habe%20ein%20Browser-Subagent%20gestartet%2C%20das%3A%0A%0A%20%20%20%20Den%20Fehler%20in%20der%20Browser-Konsole%20diagnostiziert%20hat%20(404%20auf%20%2Fwp-json%2F).%0A%20%20%20%20Auf%20die%20WordPress-Einstellungen-Seite%20f%C3%BCr%20Permalinks%20gegangen%20ist%20(%2Fwp-admin%2Foptions-permalink.php)%20und%20dort%20auf%20%E2%80%9E%C3%84nderungen%20speichern%E2%80%9C%20geklickt%20hat.%0A%20%20%20%20%20%20%20%20Dadurch%20wurden%20die%20internen%20Apache-Rewrite-Regeln%20und%20WordPress-Permalinks%20zur%C3%BCckgesetzt%2Fneu%20generiert.%0A%0ADie%20REST-API%20liefert%20nun%20wieder%20korrekte%20JSON-Daten%20zur%C3%BCck%2C%20und%20die%20Core-AI-Einstellungsseite%20unter%20http%3A%2F%2Flocalhost%2Fwordpress%2Fwp-admin%2Foptions-general.php%3Fpage%3Dai-wp-admin%20l%C3%A4dt%20jetzt%20wieder%20einwandfrei%20und%20ohne%20Fehler!&op=translate):
 * > The problem was that the WordPress REST API (at /wp-json/) was returning a 
   > 404 Not Found error. Since the Core AI plugin’s React dashboard relies on this
   > API, the interface crashed, resulting in a blank error message (because React
   > intercepted a raw data response object instead of a text-based error).
   > I launched a browser sub-agent that:
   > Diagnosed the error in the browser console (404 on /wp-json/).
   > Navigated to
   > the WordPress permalinks settings page (/wp-admin/options-permalink.php) and
   > clicked “Save Changes.”This action reset/regenerated the internal Apache rewrite
   > rules and WordPress permalinks.
   > The REST API is now returning valid JSON data again, and the Core AI settings
   > page at [http://localhost/wordpress/wp-admin/options-general.php?page=ai-wp-admin](http://localhost/wordpress/wp-admin/options-general.php?page=ai-wp-admin)
   > is loading perfectly and without errors!
 *  Plugin Author [Jeffrey Paul](https://wordpress.org/support/users/jeffpaul/)
 * (@jeffpaul)
 * [4 days, 14 hours ago](https://wordpress.org/support/topic/calling-ai-settings-went-wrong/#post-18952641)
 * [@meinservice](https://wordpress.org/support/users/meinservice/) based on that
   translation, it sounds like a 404 was resolved and things are working for you
   now?
 *  Thread Starter [meinService](https://wordpress.org/support/users/meinservice/)
 * (@meinservice)
 * [4 days, 4 hours ago](https://wordpress.org/support/topic/calling-ai-settings-went-wrong/#post-18952995)
 * I use Antigravity to develop local. so this tool repaired my local environment.
   why this happens locally, dont know. in live mode, there are no problems now.
 * i want to tell you, there could be an problem with permanent-links 🙂 and a solution
   for that.
    -  This reply was modified 4 days, 4 hours ago by [meinService](https://wordpress.org/support/users/meinservice/).

Viewing 4 replies - 1 through 4 (of 4 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcalling-ai-settings-went-wrong%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/ai/assets/icon.svg?rev=3538009)
 * [AI](https://wordpress.org/plugins/ai/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ai/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ai/)
 * [Active Topics](https://wordpress.org/support/plugin/ai/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ai/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ai/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [meinService](https://wordpress.org/support/users/meinservice/)
 * Last activity: [4 days, 4 hours ago](https://wordpress.org/support/topic/calling-ai-settings-went-wrong/#post-18952995)
 * Status: resolved