Plugin Author
MxChat
(@mxchat)
Hi @nikkers,
Thank you for bringing this up. To confirm, this only happens for you on the Loops API field and not any of the other API fields such as the chat or embedding model APIs? I heard from one other user as well about having issues with the Loops API input, but I couldn’t replicate. I think now this may be what was occurring to them as well.
The API input fields are password input type elements for privacy and it sounds like these fields are triggering maybe your browsers autofill password option and saving with you being able to stop it. I’m going to review and let you know what I find.
yes – on “Loops API field and not any of the other API fields such as the chat or embedding model APIs” AND “Additional Quick Questions field”
It does look like auto filling from the browser.
Thanks
Plugin Author
MxChat
(@mxchat)
Thanks for confirming. I have a fix in place. Goal is to have this update live tomorrow. I’ll comment here when it’s ready.
Plugin Author
MxChat
(@mxchat)
Hi @nikkers,
In the new release 2.1.4 this issue should have been fixed. Let me know if your browser is still automatically filling the Loops API field. I added autocomplete = off to API elements. Browsers may still suggest or offer auto complete, but it shouldn’t fill the input with it unless you click for it to do so.
Once you confirm it’s working I will close out. If it’s still giving you issues, I may have to make this even more robust.
Thanks again.
Fixed thank you – browser is NOT filling the Loops API field or the added questions.
-
This reply was modified 2 months, 1 week ago by
nikkers.
Update – I replied too soon…. In 2.1.4 it does not populate the API or add question field, however if the browser and/or server cache is cleared it still populates both fields.
Also – the page often sends the message “Error saving: Update failed or no changes”
Plugin Author
MxChat
(@mxchat)
Hi @nikkers,
Version 2.1.5 was just released and should fix the “Error saving: Update failed or no changes” message. Please let me know if you still experience this after updating!