Does not seem to work on WP7 for me

Installed, setup the connection with a local (same network) llama.cpp instance, which I use elsewhere. It does seem the models, so I know it’s talking to the server. Saved that (Seemed to take a couple goes to get it to remember the preferred model!). Enabled all the ai features, but when trying to use any in a post etc., it just says ‘I need to ‘This feature requires an AI Connector to function properly.’, click the link to go to the connectors, and it’s there, ‘connected’, and configured. So, don’t know. Running WP 7.0 This sounds like a conflict with that specific AI Provider plugin. You mention you’re using a llama.cpp instance, can you point me to the actual AI Provider plugin you’re using to access that instance so I can test? Thanks for the quick response. It was the ‘ https://wordpress.org/plugins/ultimate-ai-connector-compatible-endpoints/ ‘ plugin. It does state it’s tested and compatible with WP 7. It does show as connected in the connectors list. Tagging @superdav42 as a heads up from the connector perspective @pjsgsy do you have the Connector Approvals experiment enabled? If so, do you see that the connector plugin is enabled for the AI plugin on the respective screen? In doing some quick testing, I think it’s an issue with that particular plugin. From what I’m seeing, it seems it’s registering a Connector with authentication set to none but the new AI Client in WordPress 7.0 only works with Connectors that have authentication set to API key. So in this case, it shows as connected on the new Connectors screen but isn’t actually available to use with the AI Client (which impacts not only this AI plugin but any plugin that tries to use that Connector). Thanks for reporting this @pjsgsy , and thanks @dkotter for pinpointing the cause. You were correct. Our connector was registering with authentication set to none because many local servers like Ollama and llama.cpp don’t require an API key. However, WordPress 7.0’s connector system and the AI plugin only recognize connectors that declare api_key authentication with a populated setting value, so although the connector appeared as “connected” on the Connectors page, it was invisible to any AI feature that checks for valid credentials. Most of my testing was with the SD AI Agent which does not make this check so I didn’t notice there was a problem. We’ve just released version 2.1.1 which fixes this. Please update and let us know if that resolves it for you. Thank you all for your prompt help, and a resolution! I can confirm after updating, it works. Marvellous. Rarely see such support, so, thanks! Have a great weekend. OK, unsure if this is related to the plugin, or WP, but in testing a few of the features, I do note this error when trying to generate meta descriptions. This also seems to apply to suggesting categories, etc. Just a fyi. Thanks again. Ability "ai/meta-description" callback threw an exception: WordPress\AiClient\Providers\Models\DTO\ModelRequirements::areMetBy(): Argument #1 ($metadata) must be of type WordPress\AiClient\Providers\Models\DTO\ModelMetadata, __PHP_Incomplete_Class given, called in D:\Inetpub\Websites\paul\wp-includes\php-ai-client\src\Providers\ProviderRegistry.php on line 238 This reply was modified 6 days, 5 hours ago by pjsgsy . @pjsgsy It’s hard to say exactly which code is to blame for that error. It’s related to fetching data from the persistent object cache. So if you flush the object cache with wp cache flush it should start working. I just release 2.1.2 which adds protections to avoid this problem. so update or flush the cache or both.