Skip to content

Fix: Connectors: AI provider API keys are re-validated on every settings update (/wp/v2/settings), causing needless provider calls and key resets - #13031

Open
hbhalodia wants to merge 2 commits into
WordPress:trunkfrom
hbhalodia:fix/issue-65867
Open

Fix: Connectors: AI provider API keys are re-validated on every settings update (/wp/v2/settings), causing needless provider calls and key resets#13031
hbhalodia wants to merge 2 commits into
WordPress:trunkfrom
hbhalodia:fix/issue-65867

Conversation

@hbhalodia

@hbhalodia hbhalodia commented Aug 13, 2026

Copy link
Copy Markdown

Trac ticket: https://core.trac.wordpress.org/ticket/65867

Description

  • Fixed the issue related to settings check for API key for all connectors, even if the request does not changes or have connector key.
  • This leads to unnecessary calls to provider to check for API key on every settings save via wp/v2/settings.

Use of AI Tools

  • Yes, Claude Code, Opus 5.
  • Used for drafting the ticket mentioned.
  • Used for adding the unit test for the changes mentioned. Tested locally and reviewed tests by me.

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@hbhalodia
hbhalodia marked this pull request as ready for review August 13, 2026 06:56
@github-actions

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props hbhalodia.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant