Logo
Troubleshooting
TroubleshootingTroubleshooting issues

Troubleshooting issues

A translation could fail for several reasons, including:

  • The translation API goes offline
  • The API key for the selected translation provider is missing
  • Automatic translations are not enabled, so the translation post was not created
  • Others

Here is how to find out what's wrong.

Getting notified when a translation fails

By default, whenever an 🔴 Error entry is added to the logs, a notification badge will be displayed in the plugin menu.

Translation to Spanish of the 'Hello World' post failed, and a notification badge is displayed
Translation to Spanish of the 'Hello World' post failed, and a notification badge is displayed

This will inform us that a translation has failed, and prompts us to browse the logs.

Finding the problem

Browse the logs. If you find an 🔴 Error, that's certainly where the problem is.

If you find a 🟡 Warning, then the query found an unexpected condition, which may be the source of the problem.

For instance, if a translated post is not assigned tags, it's because those tags must not have been translated first; the log will then contain an entry with warning Tag has no translation for language '...'.

In this screenshot, a log entry with an 🔴 Error helps us understand why the translation of a media item was not successful:

Viewing single log
Viewing single log

The log entry reads:

🔴 Error [Query "translate-media"] Execution with errors: Provider 'DeepL' doesn't have an API key configured

Then, the issue is that the API key for DeepL is missing in the plugin Settings page.