Contents
Multilingual settings — Plugixa FAQ
The Multilingual tab configures how Plugixa FAQ integrates with translation plugins (Polylang, WPML). It auto-detects whichever plugin is active and exposes a language filter throughout the admin.
Go to Plugixa FAQ → Settings → Multilingual.
Options
| Key | Default | Values |
|---|---|---|
multilingual_enabled |
auto |
auto — detect Polylang/WPML and enable if found. off — disable multilingual features even if a plugin is active. |
multilingual_fallback |
default_language |
When a requested language has no translation: default_language shows the default-language FAQ; hide omits the FAQ entirely. |
What “auto” detects
- Polylang (free and Pro) — uses Polylang’s registered languages and term meta.
- WPML (paid) — uses WPML’s language configuration and string tables.
Only one translation plugin should be active. Running both simultaneously is unsupported.
Fallback behavior
With multilingual_fallback=default_language:
- A French FAQ without an English translation still appears on English pages (in French).
- Useful when your default language is complete and other languages are partial.
With multilingual_fallback=hide:
- Missing translations are silently omitted from the frontend.
- Useful when you’d rather show fewer FAQs than mixed-language content.
Language filter in admin
When multilingual is active, every list page (FAQs, Categories, Custom Fields) gains a language filter:
- ALL — shows every language.
- EN / FR / … — filters to one language.
The filter persists in localStorage per list, so switching between pages keeps your context.
Migration for existing FAQs
Pre-multilingual FAQs have language_code = NULL. On first activation, a background migration backfills these to your default language. If the migration didn’t run:
Settings → Advanced → Re-run multilingual migration. See Troubleshooting.
Related
- Multilingual guide — creating and grouping translations
- FAQs management — language filter in use
- Settings overview