Been trialling this new plugin which is really useful, but it does seem to be causing some saving issues on resources. The saving is looping and just hanging. The changes are saved if you refresh the page but not ideal.
If I disable the plugin saving works as expected.
This is on MODX 3.0.2 and 3.1.2 with PHP 8.3.
I really love the idea of having AI to assist so would be good to get this resolved.
I haven’t had the pleasure to play with it, yet.
But I can try to assist you with debugging/hunting the issue.
Normally when such issues happen, you get some information in the developer-tools.
Go edit a page in your setup. Before you press save, open the dev-tools (F12, or CTRL+SHIFT+I). Now press save.
You either can see a Javascript-Error in the tab “Console”, or you see a red line request in the network-tab. If there is a red request, click on it (a side panel opens), and now press on the sub-tab “answer” (or response), and copy the body of the response.
I’ve done as suggested and these are the errors I have received:
typRequest URL:
https://www.website.com/connectors/index.php
Request Method:
POST
Status Code:
500 Internal Server Error
Remote Address:
213.129.84.97:443
Referrer Policy:
strict-origin-when-cross-origine or paste code here
And also:
{message: 'JsonReader.read: Json object not found'}
message
:
"JsonReader.read: Json object not found"
[[Prototype]]
:
Object
read @ ext-all.js:21
handleResponse @ utilities.js?mv=312pl:409
processResponse @ ext-all.js:21
success @ ext-all.js:21
n @ ext-all.js:21
t @ ext-all.js:21
A @ ext-all.js:21
It could be a conflict with another plugin / extra too. Does the above help?
so the first message is from the network-tab, and the second from the console-tab. We are getting closer. And yes, I’m assuming from the beginning, that it has to do with another extra, or something else.
Now do that process again, and then after saving, click on the red request (/connectors/index.php) again. You have shown me the information from the first sub-tab (“Headers”):
Indeed looking at the response there might give us a helpful error message.
The only thing that AIKit currently does on save is index resources into the Pinecone vector database if that’s configured, so I’m guessing it’s going to be tied in with that. Are you using that?
(If you’re not, it’s totally possible that not having it set up causes it to break… this is a very early proof of concept project.)
aikit.vector_database and aikit.pinecone_ system settings would be relevant as well.