Troubleshooting

Diagnose and fix common issues with the Weglot plugin for Craft CMS.

If something isn't working as expected, these steps will help you narrow it down before reaching out.

Read the Craft logs

The plugin logs errors (including failed calls to the Weglot API) to Craft's logs. Check them first:

tail -f storage/logs/web.log

Look for entries mentioning Weglot or the API. In the Craft control panel you can also enable Dev Mode to surface errors directly.

Clear the cache

The plugin caches your Weglot options, language list and slug maps (keys prefixed with weglot_). If a change made in your Weglot dashboard or in the plugin settings doesn't show up, clear Craft's caches:

php craft clear-caches/all

You can also clear caches from Utilities → Caches in the control panel.

Common issues

The language switcher doesn't appear

• Make sure your API Key is valid and at least one Destination Language is set.

• Confirm the current URL isn't excluded from translation (see Exclude content and URLs from translation).

Translations are out of date

• Clear Craft's caches (above) so the plugin refetches your options from Weglot.

Dynamically-loaded content isn't translated

• Enable dynamic content and add the relevant selectors — see Dynamic content translation.

A page returns a 404 in a translated language

• Check that the URL isn't excluded with a "not found" behavior in your URL exclusions.

Staging and development

On non-production environments you can point the plugin at Weglot's staging services with environment variables (WEGLOT_ENV, WEGLOT_DEV, and the matching staging URLs). Leave these unset in production.

Still stuck?

Gather your Craft and plugin versions, your PHP version, and the relevant log entries, then open an issue or contact support — see GitHub repository.