Skip to content

fix: prevent filter from overriding WP_AI_SUPPORT preference#11295

Open
justlevine wants to merge 32 commits intoWordPress:trunkfrom
justlevine:fix/wp_supports_ai-constants-order
Open

fix: prevent filter from overriding WP_AI_SUPPORT preference#11295
justlevine wants to merge 32 commits intoWordPress:trunkfrom
justlevine:fix/wp_supports_ai-constants-order

Conversation

@justlevine
Copy link

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

This PR fixes wp_supports_ai() to early-return if WP_SUPPORTS_AI is false, instead allowing the wp_supports_ai filter to switch the value back on even if the user/host has explicitly disabled it.

Follow up to #11149

Note

This PR is based on #11149.
Relevant diff: f0c1632

Use of AI Tools

Github Copilot Autocomplete on the doc blocks.


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.

justlevine and others added 30 commits March 4, 2026 02:31
Co-authored-by: Weston Ruter <westonruter@gmail.com>
> phpstan: Method WP_AI_Client_Prompt_Builder::get_builder_callable() should return callable(): mixed but returns array{WordPress\AiClient\Builders\PromptBuilder, string}.
@github-actions
Copy link

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 justlevine, westonruter.

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

@github-actions
Copy link

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.

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.

2 participants