FSE Multilingual
4WP Multilingual FSE
Locale-aware FSE template parts for Polylang and WPML — keep header and footer in your templates, swap language-specific parts on the front end.
Version 0.2.0 · WordPress 6.4+ · PHP 7.4+ · GPL v2+
4WP Multilingual FSE lets block-theme teams ship one set of FSE templates while serving locale-specific headers, footers, and custom template parts.
Multilingual block themes without template sprawl
Keep base slugs like header in every template. Create header-en, footer-de, or map custom slugs — the plugin resolves the correct part when Polylang or WPML switches the active locale.
How it works
- Install and activate 4WP Multilingual FSE alongside Polylang or WPML.
- Open Settings → 4WP Multilingual FSE and confirm the detected provider.
- Create language-specific template parts — e.g.
header-en,footer-ar— or use Clone from the admin table. - Map each base slug to a locale part per language, or rely on the
{base}-{lang}naming convention. - Templates stay unchanged — the plugin swaps
core/template-partslugs on the front end before WordPress renders them.
Perfect for
- FSE / block themes with Polylang or WPML that need different headers, footers, or CTAs per language
- Agencies building multilingual marketing sites without duplicating every template file
- Teams that want a gap report and clone workflow instead of manual Site Editor copy-paste
- Sites using language-scoped block patterns in the inserter (v0.2+)
Key features
Provider detection, smart slug resolution, and a Design System tab for multilingual FSE coverage
Provider-aware
Built-in Polylang and WPML providers detect the active locale, with sensible fallbacks when a language part is missing.
Smart resolver
Admin mapping → {slug}-{lang} convention → base part fallback. Adds forwp-lang-{code} and RTL body classes.
Design System tab
Gap analysis shows missing locale variants; clone single or bulk parts, then jump straight into the Site Editor.
Requirements
| WordPress | 6.4 or higher (FSE / block theme) |
| PHP | 7.4 or higher |
| Multilingual plugin | Polylang or WPML (one active provider) |
| Current version | 0.2.0 |
| Distribution | GitHub (WordPress.org listing planned) |
Pair with 4WP Polylang API Sync for remote content control, or install the full suite from 4WP Bundle.
FAQ
Common questions about locale-aware FSE template parts — wrapped with 4WP FAQ for Schema JSON-LD
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.
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.
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.
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.
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.
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.
Ready to localize your block theme?
Clone the repository, map your template parts, and ship locale-aware headers and footers without template sprawl.