Skip to content
Front User Submit
Menu

Compatibility with themes and plugins

Themes and plugins Front User Submit is tested with, and the settings page caches, optimization and security plugins need.

Front User Submit works with any theme that shows the content of a page. This page lists the popular themes and plugins we tested it with, and the settings that some kinds of plugins need.

How we test

Last test: November 2026, Front User Submit 5.3.3 (free version), WordPress 7.1, PHP 8.3, nginx with PHP-FPM. The same steps also pass on PHP 7.4, 8.0, 8.1, 8.2, 8.4 and 8.5.

We install each theme or plugin on a clean site next to Front User Submit and check these steps:

  1. A guest sends a post with a featured image, a file, a category, a new tag and Cloudflare Turnstile.
  2. The Front Editor block shows the form.
  3. A logged-in author sends a post with the EditorJS editor, opens it from the user dashboard, changes it and saves it. The post content must stay exactly as it was.
  4. A logged-in author sends a post with the TinyMCE editor.
  5. The login and registration forms work.
  6. The form builder, the plugin settings and the block editor open in wp-admin without errors.

We also watch for JavaScript errors in the browser and PHP errors in the log. Cache and optimization plugins are tested with their JavaScript options turned on, because that is where conflicts happen.

Themes

All of these themes work:

Theme Version tested
Twenty Twenty-Five 1.5
Twenty Twenty-Four 1.6
Twenty Twenty-One 2.9
Hello Elementor 3.5.2
Astra 4.14.3
Kadence 1.6.0
GeneratePress 3.6.1
OceanWP 4.2.8
Blocksy 2.1.62
Neve 4.2.19
Storefront 4.6.2

The free Clean form design looks the same in all of them. If you want the form to use your theme’s styles instead, choose Minimum Style in Form designs.

Plugins

All of these plugins work with the default settings. Notes in the table say where you need to change something.

Kind Plugin Version tested Notes
Page builder Elementor, Beaver Builder, SiteOrigin Page Builder 4.4.1, 2.11.2.2, 2.38.0 See Page builders.
Blocks GenerateBlocks, Spectra, Kadence Blocks 2.5.1, 2.20.7, 3.9.1.1 The form also works inside their layout blocks (containers, rows).
Editor Classic Editor, Advanced Editor Tools 1.7.0, 5.10.1
SEO Yoast SEO, Rank Math, All in One SEO 28.9, 1.0.282, 5.0.5.1
Forms Contact Form 7, WPForms Lite, Fluent Forms, Forminator 6.2.5, 2.0.4, 6.2.17, 1.58.6
Shop WooCommerce 11.3.0
Fields and roles Advanced Custom Fields, Custom Post Type UI, User Role Editor, Members, Ultimate Member 6.8.11, 1.19.3, 4.67.1, 3.3.2, 2.14.2 ACF: give a Text field the same Name as an ACF field, and ACF shows the value (get_field() returns it).
Security Wordfence, Kadence Security (Solid Security), Limit Login Attempts Reloaded, WPS Hide Login, Really Simple Security, Loginizer 9.1.1, 10.0.6.1, 3.4.4, 1.9.20, 9.8.4, 2.1.4
Security All-In-One Security (AIOS) 5.5.1 Works by default. If you turn on Disallow unauthorized REST requests, allow the bfe route, see Security plugins.
Cache and speed W3 Total Cache (page cache) 2.11.0 See Page cache.
Cache and speed Autoptimize 3.1.17 Tested with JavaScript optimization on, also with Aggregate JS-files.
Cache and speed LiteSpeed Cache 7.9.3 Tested with JS and CSS minify and combine on. Page caching needs a LiteSpeed server and was not part of the test.
Images Smush, EWWW Image Optimizer 4.3.7, 8.9.2
Translation Loco Translate, Polylang 2.8.10, 3.9.2 With Polylang, new posts get the default language.
Email WP Mail SMTP 4.10.4 Notifications are sent with wp_mail(), so SMTP plugins deliver them.

Page builders

Page builders show the form through its shortcode, for example [fe_form id="123"]. There is no separate builder widget: use the builder’s shortcode element.

Builder How to add the form
Elementor Add a Shortcode widget and paste the shortcode.
Beaver Builder Add an HTML module and paste the shortcode.
SiteOrigin Page Builder Add a Text widget (Visual tab) and paste the shortcode.
Block editor, GenerateBlocks, Spectra, Kadence Blocks Use the Front Editor block, or a Shortcode block, also inside a container or row block.

For each builder we built a page with the builder and checked:

  • A guest sends a post with a featured image and three files uploaded at once. All files are attached to the post.
  • A logged-in author sends a post with EditorJS, then opens Edit in the user dashboard. The edit link opens the same builder page, and the changed post is saved without changes to its content. For this, set Select edit page to Same Form in Edit post settings.
  • The form shows in the builder’s editor: in the Elementor editor preview (the editor finishes loading) and in the Beaver Builder editor.

Elementor was tested with Twenty Twenty-Five and with Hello Elementor.

Divi, WPBakery, Bricks, Oxygen, Elementor Pro: paid, not tested by us. Use their shortcode or code module with the same shortcode.

Page cache

Page cache plugins and host caches serve a saved copy of a page. A saved form page can be hours or days old. Since version 5.3.3 the form notices this and gets a fresh security token before a guest uploads files or sends the form, so you do not need to exclude form pages from the cache.

With older versions, guests on a cached form page older than 12 to 24 hours got “Cookie check failed”, and the login form said “Security error, please refresh page”. If you cannot update, exclude the pages with forms (and the login and registration pages) from the page cache.

The pages of logged-in users are not cached by default in all common cache plugins, so the user dashboard and edit forms are not affected.

Security plugins

The form sends posts and uploads through the WordPress REST API, in the bfe/v1 routes. Guests can only send a form when visitors may use these routes.

Some security plugins can block the REST API for visitors who are not logged in. Then guest forms stop working: uploads and sending fail. Allow the plugin’s routes:

  • All-In-One Security (AIOS): go to AIOS → Firewall → PHP rules → WP REST API. If Disallow unauthorized REST requests is on, tick bfe under Whitelist REST routes and save.
  • Other plugins with a REST API block: allow the bfe namespace (/wp-json/bfe/v1/).

Logged-in users are not affected.

Translation plugins

The plugin is translation ready. Translate it with Loco Translate or on translate.wordpress.org. Labels you type in the form builder are saved in the form: for a site in several languages, create one form per language.

Fixed in version 5.3.3

The test found these problems. They are fixed in 5.3.3:

  • Block themes (Twenty Twenty-Five, Twenty Twenty-Four): editing a post in a form with a TinyMCE, Textarea or Markdown field could change the saved text. Straight quotes became curly quotes, and block markup like <!-- wp:paragraph --> was damaged.
  • TinyMCE field: when the mouse pointer was over the form while the page loaded, the editor could open empty, and saving deleted the post content. This happened most often with Storefront.
  • Twenty Twenty-One: new forms showed “Untitled” in the title field.
  • Page cache and page builders: guests who uploaded several files at once on a cached page or on a page builder page (for example Elementor) could lose some of the files without a message.
  • Autoptimize: with Aggregate JS-files on, the TinyMCE editor did not start. The plugin now keeps the TinyMCE scripts out of the bundle.
  • PHP 8.5: a deprecation notice about finfo_close() was written to the PHP log on every upload.
  • User dashboard: on new sites where the dashboard settings were never saved, the dashboard had no design and showed very large edit and delete icons. It now uses Modern Minimal, the design the settings page shows.

Not tested

We did not test paid themes and plugins: Divi, Avada, WPBakery, Bricks, Elementor Pro, WP Rocket, WPML, Gravity Forms and others. They should work like the free plugins of the same kind above. If something does not work, tell us.

Report a problem with another plugin or theme

  1. Switch to a default theme (Twenty Twenty-Five) for a moment and check the form again.
  2. Deactivate other plugins one by one until the form works. The last plugin you turned off is the one that conflicts.
  3. Tell us the theme or plugin and its version in the community chat or on GitHub.

Last updated 2026-11-19