Google key is set but doesn't show in machine translation options

[xerenahmed]

Describe the issue

I set the Google API Key with the name WEBLATE_MT_GOOGLE_KEY. API Key is valid.

I already tried

• I've read and searched the documentation.
• I've searched for similar issues in this repository.

Steps to reproduce the behavior

1. Set WEBLATE_MT_GOOGLE_KEY
2. Go to 'host/projects/project/component/en/#auto'
3. Click on 'Machine translation'
4. See there is no Google option

Expected behavior

Option as "Google Translate"

Screenshots

No response

Exception traceback

No response

How do you run Weblate?

Docker container

Weblate versions

• Weblate: 4.14.1
• Django: 4.1.1
• siphashc: 2.1
• translate-toolkit: 3.7.3
• lxml: 4.9.1
• Pillow: 9.2.0
• bleach: 5.0.1
• python-dateutil: 2.8.2
• social-auth-core: 4.3.0
• social-auth-app-django: 5.0.0
• django-crispy-forms: 1.14.0
• oauthlib: 3.2.1
• django-compressor: 4.1
• djangorestframework: 3.13.1
• django-filter: 22.1
• django-appconf: 1.0.5
• user-agents: 2.2.0
• filelock: 3.8.0
• rapidfuzz: 2.8.0
• openpyxl: 3.0.10
• celery: 5.2.7
• kombu: 5.2.4
• translation-finder: 2.14
• weblate-language-data: 2022.7
• html2text: 2020.1.16
• pycairo: 1.21.0
• pygobject: 3.42.2
• diff-match-patch: 20200713
• requests: 2.28.1
• django-redis: 5.2.0
• hiredis: 2.0.0
• sentry_sdk: 1.9.8
• Cython: 0.29.32
• misaka: 2.1.1
• GitPython: 3.1.27
• borgbackup: 1.2.2
• pyparsing: 3.0.9
• pyahocorasick: 1.4.4
• python-redis-lock: 3.7.0
• charset-normalizer: 2.1.1
• Python: 3.10.7
• Git: 2.30.2
• psycopg2: 2.9.3
• psycopg2-binary: 2.9.3
• phply: 1.2.5
• ruamel.yaml: 0.17.21
• tesserocr: 2.5.2
• boto3: 1.24.73
• zeep: 4.1.0
• aeidon: 1.11
• iniparse: 0.5
• mysqlclient: 2.1.1
• Mercurial: 6.2.2
• git-svn: 2.30.2
• git-review: 2.3.1
• Redis server: 6.2.7
• PostgreSQL server: 14.5
• Database backends: django.db.backends.postgresql
• Cache backends: default:RedisCache, avatar:FileBasedCache
• Email setup: django.core.mail.backends.smtp.EmailBackend: 127.0.0.1
• OS encoding: filesystem=utf-8, default=utf-8
• Celery: redis://cache:6379/1, redis://cache:6379/1, regular
• Platform: Linux 5.10.124-linuxkit (aarch64)

Weblate deploy checks

SystemCheckError: System check identified some issues:

CRITICALS:
?: (weblate.E003) Cannot send e-mail ([Errno 111] Connection refused), please check EMAIL_* settings.
	HINT: https://docs.weblate.org/en/weblate-4.14.1/admin/install.html#out-mail
?: (weblate.E012) The server e-mail address should be changed from its default value
	HINT: https://docs.weblate.org/en/weblate-4.14.1/admin/install.html#production-email
?: (weblate.E013) The "From" e-mail address should be changed from its default value
	HINT: https://docs.weblate.org/en/weblate-4.14.1/admin/install.html#production-email

ERRORS:
?: (weblate.E011) E-mail addresses for site admins is misconfigured
	HINT: https://docs.weblate.org/en/weblate-4.14.1/admin/install.html#production-admins

WARNINGS:
?: (security.W004) You have not set a value for the SECURE_HSTS_SECONDS setting. If your entire site is served only over SSL, you may want to consider setting a value and enabling HTTP Strict Transport Security. Be sure to read the documentation first; enabling HSTS carelessly can cause serious, irreversible problems.
?: (security.W008) Your SECURE_SSL_REDIRECT setting is not set to True. Unless your site should be available over both SSL and non-SSL connections, you may want to either set this setting True or configure a load balancer or reverse-proxy server to redirect all connections to HTTPS.
?: (security.W012) SESSION_COOKIE_SECURE is not set to True. Using a secure-only session cookie makes it more difficult for network traffic sniffers to hijack user sessions.

INFOS:
?: (weblate.I021) Error collection is not set up, it is highly recommended for production use
	HINT: https://docs.weblate.org/en/weblate-4.14.1/admin/install.html#collecting-errors
?: (weblate.I028) Backups are not configured, it is highly recommended for production use
	HINT: https://docs.weblate.org/en/weblate-4.14.1/admin/backup.html

System check identified 9 issues (1 silenced).

Additional context

No response

[github-actions]

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

[github-actions]

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

[nijel]

These are now managed in the UI, the configuration options are only migrated once during upgrade, see https://docs.weblate.org/en/latest/admin/machine.html. Go to /manage/machinery/ to configure that.

[github-actions]

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!