Conversation
|
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @dushakov92. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
@dushakov92 Thank you for opening this PR. Note that a few major changes are being implemented currently as part of the merge of WP AI Client into WordPress Core:
Once you update to the next release of this package, please ensure to require the 3 providers directly in your plugin. At the same time, it's recommended you prepare your plugin for usage of WordPress 7.0 (e.g. use the Given the above, I'm going to close this PR, as the change is not needed according to the plans above. Thanks again! |
|
@felixarntz |
The provider implementations for OpenAI, Google, and Anthropic were moved to their own packages in
php-ai-client v1.0:wordpress/openai-ai-providerwordpress/google-ai-providerwordpress/anthropic-ai-providerIt looks like
wp-ai-clientneeds a couple of updates to work with this new structure:The three provider packages need to be listed in
composer.jsonso they get pulled in automatically.AI_Client::init()needs to register each provider with theProviderRegistryso they're available to the credentials manager.Without these,
API_Credentials_Manager::collect_providers()returns an empty array and the settings page at/wp-admin/options-general.php?page=wp-ai-clientdoesn't show any provider fields.What this PR does:
composer.jsoninit()viaProviderRegistry::registerProvider(), guarded byclass_exists()checksTested locally — settings page renders correctly after these changes.