Use Smart Forms with Polylang

Smart Form Builder by Dragwyb includes Polylang hooks for its form post type and checks the current language when rendering a form. To display language-specific labels and messages, enable Smart Forms for translation in Polylang, create linked translated forms, and embed the form on the matching language page.

Enable Smart Forms for translation

1. Install and activate Polylang and configure the languages used by your site.
2. Open Polylang’s settings and find the Custom post types and Taxonomies section.
3. Enable the Smart Form Builder form post type (dragwyb-forms) for translation, then save the Polylang settings.
4. Open Smart Forms → Forms and locate the form to translate.
5. Use the language/translation controls to create a form translation for the target language. The plugin includes Polylang hooks that direct translation links to its custom form editor.
6. Translate the field labels, help text, options, and messages in the translated form, then save and publish it.

Use translated forms on language-specific pages

1. Create or translate the page that should contain the form using your usual Polylang workflow.
2. Embed the form with a Smart Form shortcode, the Gutenberg Smart Form block, or the Elementor Smart Form widget.
3. Confirm the translated form is linked to the original in Polylang and has published status.
4. Open each language version of the public page and verify the expected form language.

How language-aware rendering works

The plugin checks the current Polylang language and the language of the form selected in the page content. When a linked translation exists for the current language, it can render that translated form. If the translation lookup returns no form, the handler falls back to the original form ID, so a translated form is not automatically created for you.

Troubleshooting

• If the form stays in the original language, verify that the dragwyb-forms post type is enabled for translation in Polylang.
• Check that the translation relationship is saved and the translated form is published.
• Check the public language page rather than relying only on the editor preview.
• Test form submissions and language-specific email text separately; translation of the page does not automatically translate every form setting.

The plugin source includes Polylang post-type registration and translated-form lookup logic. A live Polylang installation and a linked translation pair were not tested during this documentation update.

Screenshot to add: [Polylang language controls for a Smart Form]