• Resolved tf5_bassist

    (@tf5_bassist)


    Hi there, I just started experimenting with this plugin and bought the Pro license. Whenever you enter an OpenAI API key, that value does seem to be saved, however, the settings page reverts to whatever the default API value was with the fresh install.

    This means that if you change any settings on the Images tab without also re-entering your own API key, it resets to the non-functioning default API key.

    Seeing as OpenAI doesn’t make your key visible after initial creation, it means you have to save this key somewhere else safe to keep reusing it, and is really a problem for testing out settings and whatnot.

    Edit: The Sources API for Pexels does the same thing. There also doesn’t seem to be any logging or error-handling for Pexels API failures, so jobs just sit there processing indefinitely.

    Can this be addressed? Thanks.

    • This topic was modified 1 year, 9 months ago by tf5_bassist.
    • This topic was modified 1 year, 9 months ago by tf5_bassist.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter tf5_bassist

    (@tf5_bassist)

    Nevermind, I figured it out. I’m in transition between password managers and didn’t notice it was auto-filling despite not having a username field. Guess I need to find out how to stop these fields from autofilling passwords.

    Thread Starter tf5_bassist

    (@tf5_bassist)

    Ahh, it’s a 1Password issue where it’s autofilling where it thinks is a password. There’s now an attribute data-1p-ignore that 1Password can recognize to tell it to not auto-fill. Could this be applied to the API fields in the plugin? Thanks!

    Plugin Author Alexandre Gaboriau

    (@mcurly)

    Hi Tf5 !

    Glad you found the source of the problem.

    As for the 1Password issue, I’ll look into implementing it in the next update if it’s possible.

    Did you only have this issue with the OpenAI API key input ?

    Thread Starter tf5_bassist

    (@tf5_bassist)

    Thanks for the response, no, it doesn’t seem to only be the OpenAI API key input, it also affects the Pexels API key input and the Google Images (API) API key input.

    But I think I figured out that it’s actually Chrome’s autofill that was dropping in the password based on the domain of the site. After I deleted the saved password from Chrome’s manager, it’s no longer overriding the previously stored password. Not sure how to really go about addressing that, but at least I’m fairly sure it’s not the plugin or 1Password.

    Sorry for the shitty troubleshooting and rushing to submit a ticket lmao.

    Plugin Author Alexandre Gaboriau

    (@mcurly)

    No problem.

    I’ll try to see if there’s a problem with the autofill browser feature (chrome) for the next update.

    Thread Starter tf5_bassist

    (@tf5_bassist)

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘OpenAI API resets to default value’ is closed to new replies.