Hello, I have installed your module 2 days ago and almos finished the front page. I went to fluent forms to edit it a bit but I noticed the fluentforms admin loading forever and I cannot use it at all. I have disabled - enabled the module, purged cache, nothing helps.
The "forever loading" state in the WordPress admin is typically caused by a JavaScript conflict or a server memory exhaustion occurring when the Fluent Forms editor tries to initialize its interface within the Salient theme environment.
Immediate Troubleshooting Steps
Since you have already tried toggling the module and purging the cache, please try these specific steps to pinpoint the conflict:
Check for JavaScript Errors:
Right-click anywhere on that loading screen and select "Inspect."
Click on the "Console" tab. If you see bright red text, it indicates a specific script (likely from another plugin or a theme optimization) is "breaking" the Fluent Forms editor.
Increase PHP Memory Limit:
Complexity in the Salient theme and form builders can occasionally hit the default 128MB or 256MB memory limit.
Reach out to your host or edit your wp-config.php file to increase this to 512M.
Conflict Test:
Temporarily disable any Optimization Plugins (like WP Rocket, Autoptimize, or SiteGround Optimizer).
These plugins often "minify" or defer the exact JavaScript files Fluent Forms needs to load its admin dashboard.
Salient-Specific Compatibility
While Salient is fully compatible with Fluent Forms, certain Theme Options can interfere with third-party admin panels:
Salient CSS/JS Minification: Go to Salient > General Settings > CSS/Script Related and ensure "Minify Generated CSS" is temporarily off while you configure your forms to see if it resolves the loading loop.
Hello Ephraim, I have checkeed the concole, there are continiously recording errors (screenshot) which seems to be not be caused by another module. The php limit is set ot -1, no limit at all. The website is new and there are no optimization plugins yet. It´s fresh WP instalation, I put your theme and started learing out texts and contents. Then reached footer where the form is and I try to edit it. The only module I put is for SVG support of the logo. Thank you Ivaylo
Thank you for that detailed follow-up and the screenshot of your Network tab.
The 403 (Forbidden) errors you see for global-settings are the "smoking gun". A 403 error means the server is receiving the request but explicitly refusing to authorize it. Since this is a fresh installation without optimization plugins, the block is almost certainly happening at the Server/Hosting level, specifically by a security feature called ModSecurity or a Web Application Firewall (WAF).
The Cause: Security Rules
Security filters on some hosts misinterpret the long strings of data (nonces and query parameters) sent by Fluent Forms as a "suspicious" request and kill the connection before it reaches the plugin.
How to Fix the 403 Error:
1. Contact Your Hosting Support (Recommended) Send them the screenshot you shared with me and ask them to:
Check the Server Security Logs for your IP address.
Whitelist the specific rule that is triggering the 403 error on admin-ajax.php and the Fluent Forms REST API endpoints.
2. Check for "SVG Support" Conflict You mentioned an SVG support plugin. While unlikely to cause a 403, some older SVG plugins can interfere with how WordPress handles sanitization and permissions.
Test: Temporarily deactivate the SVG plugin and refresh the Fluent Forms page. If the 403s disappear, you may need to switch to a different SVG plugin like "Safe SVG".
3. Refresh Your Permalinks Sometimes the WordPress REST API (which Fluent Forms uses) gets "confused" on fresh installs.
Go to Settings > Permalinks.
Don't change anything, just scroll to the bottom and click "Save Changes." This flushes the site's internal rewrite rules and can often clear up 403/404 errors on API calls.
After your host makes changes or you refresh permalinks, please follow this guide to clear your browser cache to ensure you aren't seeing a "cached" version of the 403 error.
Hello, I have installed your module 2 days ago and almos finished the front page. I went to fluent forms to edit it a bit but I noticed the fluentforms admin loading forever and I cannot use it at all.
I have disabled - enabled the module, purged cache, nothing helps.
Attached files: Screenshot 2026-01-22 220931.png
Hello ThemeGrapher,
Thanks for writing in!
The "forever loading" state in the WordPress admin is typically caused by a JavaScript conflict or a server memory exhaustion occurring when the Fluent Forms editor tries to initialize its interface within the Salient theme environment.
Immediate Troubleshooting StepsSince you have already tried toggling the module and purging the cache, please try these specific steps to pinpoint the conflict:
-
-
-
-
-
-
-
-
-
Salient-Specific CompatibilityCheck for JavaScript Errors:
Right-click anywhere on that loading screen and select "Inspect."
Click on the "Console" tab. If you see bright red text, it indicates a specific script (likely from another plugin or a theme optimization) is "breaking" the Fluent Forms editor.
Increase PHP Memory Limit:
Complexity in the Salient theme and form builders can occasionally hit the default 128MB or 256MB memory limit.
Reach out to your host or edit your wp-config.php file to increase this to 512M.
Conflict Test:
Temporarily disable any Optimization Plugins (like WP Rocket, Autoptimize, or SiteGround Optimizer).
These plugins often "minify" or defer the exact JavaScript files Fluent Forms needs to load its admin dashboard.
While Salient is fully compatible with Fluent Forms, certain Theme Options can interfere with third-party admin panels:
Salient CSS/JS Minification: Go to Salient > General Settings > CSS/Script Related and ensure "Minify Generated CSS" is temporarily off while you configure your forms to see if it resolves the loading loop.
Hope this helps!
Let us know if you need further assistance!
Regards,
Hello Ephraim,
I have checkeed the concole, there are continiously recording errors (screenshot) which seems to be not be caused by another module.
The php limit is set ot -1, no limit at all.
The website is new and there are no optimization plugins yet.
It´s fresh WP instalation, I put your theme and started learing out texts and contents. Then reached footer where the form is and I try to edit it. The only module I put is for SVG support of the logo. Thank you
Ivaylo
Attached files: Screenshot 2026-01-23 140329.png
Hello Ivaylo,
Thank you for that detailed follow-up and the screenshot of your Network tab.
The 403 (Forbidden) errors you see for global-settings are the "smoking gun". A 403 error means the server is receiving the request but explicitly refusing to authorize it. Since this is a fresh installation without optimization plugins, the block is almost certainly happening at the Server/Hosting level, specifically by a security feature called ModSecurity or a Web Application Firewall (WAF).
The Cause: Security RulesSecurity filters on some hosts misinterpret the long strings of data (nonces and query parameters) sent by Fluent Forms as a "suspicious" request and kill the connection before it reaches the plugin.
How to Fix the 403 Error:1. Contact Your Hosting Support (Recommended) Send them the screenshot you shared with me and ask them to:
Check the Server Security Logs for your IP address.
Whitelist the specific rule that is triggering the 403 error on admin-ajax.php and the Fluent Forms REST API endpoints.
2. Check for "SVG Support" Conflict You mentioned an SVG support plugin. While unlikely to cause a 403, some older SVG plugins can interfere with how WordPress handles sanitization and permissions.
Test: Temporarily deactivate the SVG plugin and refresh the Fluent Forms page. If the 403s disappear, you may need to switch to a different SVG plugin like "Safe SVG".
3. Refresh Your Permalinks Sometimes the WordPress REST API (which Fluent Forms uses) gets "confused" on fresh installs.
Go to Settings > Permalinks.
Don't change anything, just scroll to the bottom and click "Save Changes." This flushes the site's internal rewrite rules and can often clear up 403/404 errors on API calls.
After your host makes changes or you refresh permalinks, please follow this guide to clear your browser cache to ensure you aren't seeing a "cached" version of the 403 error.
Hope this helps!
Regards,