Do I need separate templates for each language?
No. Templates keep base slugs like header. You create locale-specific template parts (header-en, footer-de, etc.) or map custom slugs in the admin table.
Used in
6 questions answered
WP Multilingual FSEAnswers pulled from across 4wp.dev — plugins, architectures, development, jobs, and audience guides. Powered by the 4WP FAQ registry.
4WP Multilingual FSE
Does it change the Site Editor or only the front end?
Swapping runs on the front end (and is suspended during admin/REST). Editors still manage all parts in the Site Editor; admin tabs help map, clone, and audit coverage.
Used in
Does it work with block patterns?
Version 0.2 adds pattern language scope and filters the block pattern inserter via REST so editors see patterns relevant to the active language.
Used in
What does 4WP Multilingual FSE do?
It resolves base FSE template part slugs (header, footer, and custom parts) to language-specific versions on the front end, based on the active Polylang or WPML locale.
Used in
What happens if a language-specific part is missing?
The resolver falls back to the base slug so the site keeps working. The Design System tab highlights missing variants so you can clone them in one click.
Used in
Which multilingual plugins are supported?
Polylang and WPML via built-in providers. The plugin auto-detects which one is active and reads the current language slug from that stack.
Used in
Still have questions?
Reach out via contacts or explore the plugin docs if you are building with 4WP FAQ yourself.