> For the complete documentation index, see [llms.txt](https://developers.weglot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.weglot.com/cms/craft-cms/troubleshooting.md).

# 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:

```bash
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:

```bash
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](https://developers.weglot.com/cms/craft-cms/use-cases/exclude-content-and-urls-from-translation.md)).

#### 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](https://developers.weglot.com/cms/craft-cms/use-cases/dynamic-content-translation.md).

#### 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](https://developers.weglot.com/cms/craft-cms/github-repository.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.weglot.com/cms/craft-cms/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
