You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Strings are no longer localized on the connector screen after activating #19
When viewing the connector screen before activating the plugin, the PHP-defined strings are properly translated when available within the language pack for the locale being used.
Steps to Reproduce
Create a fresh install.
Install and select Spanish (es_ES) as the locale (or any other language with language packs available for the 7.0 release and the Text and image generation with Gemini and Imagen. string is translated.
View the connectors screen and observe that the string is translated.
Activate the plugin.
Observe the string is back to en_US despite es_ES being the default locale.
This appears to be caused by the fact that the strings are not translated for the plugin, and the connector is being registered as a provider before WordPress Core adds google as one of the defaults.
Note: This is only for the PHP-defined strings. JavaScript strings are not currently localized due to the lack of method for localizing translation strings for script modules. See Core-65015 for more details on this.
@desrosj Does the plugin have es_ES language packs available? If not, that would explain this, and in that case I don't think it's a bug.
It is intentional that the plugins, once activated, take over the "source of truth" for the provider/connector information. Reason for this is that in the plugins we can keep things up to date, e.g. if the provider changes, whereas for Core, we might need to wait several months.
I reviewed this plugin and could only find PHP-defined translatable strings, but no plugin translation files in this repo (languages/, .po, .mo).
So after activation, when the provider data comes from this plugin, seeing English strings is expected unless language packs exist for this plugin locale.
Given that, this looks more like a translation-pack availability gap than a code bug in the connector registration flow.
If needed, we can track a separate follow-up for adding/releasing translation packs.
Activity
felixarntz commentedon Apr 22, 2026
@desrosj Does the plugin have
es_ESlanguage packs available? If not, that would explain this, and in that case I don't think it's a bug.It is intentional that the plugins, once activated, take over the "source of truth" for the provider/connector information. Reason for this is that in the plugins we can keep things up to date, e.g. if the provider changes, whereas for Core, we might need to wait several months.
dilipom13 commentedon Apr 22, 2026
Hello @desrosj
I reviewed this plugin and could only find PHP-defined translatable strings, but no plugin translation files in this repo (
languages/,.po,.mo).So after activation, when the provider data comes from this plugin, seeing English strings is expected unless language packs exist for this plugin locale.
Given that, this looks more like a translation-pack availability gap than a code bug in the connector registration flow.
If needed, we can track a separate follow-up for adding/releasing translation packs.
superdav42 commentedon Oct 13, 2026
So translations have recently been added for this plugin:
https://translate.wordpress.org/projects/wp-plugins/ai-provider-for-google/stable/es/default/
I just tested and with these in place the description is correctly translated before and after the plugin installation.
So I'm closing this as it's working as intended. The plugin just needed the translation finished.