Instant Language SwitcherDocumentation
⌕
v0.20.0

Troubleshooting

Common problems and the fastest diagnostic path.

A page remains partly English

  1. Confirm Translate Entire Site has completed.
  2. Check rendered-site discovery progress.
  3. Open Logs and search translation_coverage_gap.
  4. If necessary open Visual Editor for that page and inspect red / red-dotted content.
  5. If the content is JavaScript/AJAX-only, use Visual Editor after it loads.

Shortcode page is not scanned

Search Logs for shortcode scan events. Possibilities include:

  • shortcode returned no HTML in scan context
  • shortcode is JavaScript/AJAX-only
  • plugin requires request/query state not present during scan
  • shortcode was excluded through ist_scan_shortcode

Use Visual Editor for browser-rendered content and consider a site-specific integration for complex plugin routes.

Visual Editor shows a 404

Modern Visual Editor versions launch the original permalink with a secured content ID rather than relying on the translated route. If a 404 persists:

  • clear cache
  • confirm the site is actually running the current plugin JavaScript/PHP version
  • inspect language_content_unresolved / routing logs
  • save WordPress Permalinks

/zu/ opens the Blog page

Confirm WordPress has a static front page configured and save Permalinks. The language root is designed to map to that static front page.

Queue is not moving

  • keep an Instant Languages admin page open
  • use Process next batch
  • inspect WP-Cron / Action Scheduler health
  • search Logs for queue errors
  • verify the provider diagnostic test

DeepL/Google succeeds but content stays English

This is usually a binding/rendering issue rather than a provider issue. Search Logs for translation_coverage_gap and check whether the relevant translation is public (Translated or Approved).

Critical WordPress error

Open Instant Languages → Logs, filter CRITICAL, and export JSON/CSV. A PHP fatal should include file/line/stack information when the plugin logger captures it.

Changes do not appear after upgrade

Purge WordPress/cache-plugin/host/CDN caches and confirm the browser is loading assets with the new plugin version query string.