Backend / Frontend
-
I have a problem with the visitor form display. In the administration I can see everything fine.
https://prnt.sc/d65HTuIJRPQZAs a visitor I can’t see the radio button, font, etc.
https://prnt.sc/JWzoPtPy7o1lI have default settings everywhere.
-
I hope you’re well today!
Usually this means that there’s some kind of unexpected conflict (with theme or some other plugin) or some caching/asset optimization issues.
To start with, please:
– if you are using any kind of JS/CSS optimization plugin on site, make sure to use its option to regenerate such assets
– if there’s any caching (on site and/or server) fully flush it
If this doesn’t change anything, please share a link to the page with this form so we could visit it and take a closer look and we’ll suggest further steps.
Best regards,
AdamI tried disabling all plugins and changing the template – the problem is still there.
https://www.rrzdarsko.cz/zazitkove-odpoledne-s-royal-rangers/
Thank you for response and sharing form page URL.
I checked it and it is related to CSS but in this case it’s actually related to a certain glitch in the plugin (it’s only affecting some setups/hosts, not all of them).
Please try following steps:
1. access your site’s WordPress installation files on server (e.g. using FTP or cPanel “File Manager” or similar way)
2. go to the “/wp-content/uploads/forminator/” folder and open .htaccess file for editing
3. see if there’s a line like this in that .htaccess file
Options -ExecCGI
and if yes, remove it, then save the file.
4. then add this code to the site as MU (Must Use plugin):
<?php add_filter( 'forminator_upload_root_htaccess_rules', 'wpmudev_remove_htaccess_rules', 10, 1 ); function wpmudev_remove_htaccess_rules( $rules ) { if ( ! empty( $rules ) ) { $rules = str_replace('Options -ExecCGI', '', $rules); } return $rules; }
– create an empty file with a .php extension (e.g. “forminator-css-error-patch.php”)
– copy and paste that code into it
– save the file and upload it to the “/wp-content/mu-plugins” folder of your site’s WordPress installation5. Finally, clear all caches on site/server and check the form. It should start working then.
Our Forminator Team is aware of the issue and working on a permanent fix to be included in one of upcoming releases but I don’t have ETA yet. Above workaround, however, should work fine for now.
Kind regards,
AdamI tried the instructions, but it doesn’t work.
Hi @honzapecenka,
I hope you are doing well today!
Please check your Site Health info for your uploads folder and check if it is correct on Forminator as well and update if it is not.
To do this, we have implemented a new feature starting from v1.25 to set the custom upload folders. Please go to Forminator->Settings->Data->File Upload Storage->Custom and enter the full path of your upload folder for Forminator and try again.
https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#file-uploads-storage
If both did not help, please wait for the permanent fix from our Forminator team which will be implemented on the upcoming releases.
Kind regards,
ZaferHi.
Upload folder for Forminator is set correctly.
Thank you for confirmation.
This is quite strange, I admit, as with either the suggested fix or with correcting upload paths in Forminator – it should start working.
If you still have this workaround applied (fully – meaning not only the .htaccess edited but also the code added to the site), could you please try one more thing?:
– edit the form to change it’s “Design Style” in form “Appearance” settings; it doesn’t matter which style you select – it just needs to be different than it currently is
– update the form
– then change the “Design Style” back to the one you used originally
– and update the form again
– and then clear all cache on site/server/CDN – whatever cache is active for the site
– and check if the issue is still happening (please check in both regular and incognito browser tab)If it’s still happening, can you tell us please:
1. where are you hosting your site and is it shared hosting, Managed WordPress hosting, VPN or other type of hosting?
2. is it powered by Apache, Nginx or a “hybrid” of both?
3. what’s the PHP version powering the site?Kind regards,
AdamUnfortunately, this didn’t help either. When I changed the design to none, the radio button worked.
This is a shared hosting – wedos.cz, Apache, PHP 8.2.1Hi @honzapecenka,
Just to be sure, could you please go to the “/wp-content/uploads/forminator/” folder once more and open the .htaccess file and double-check whether the following line still shows up or not?
Options -ExecCGI
If the .htaccess was edited before adding the code as mentioned in here:
https://www.ads-software.com/support/topic/backend-frontend-2/#post-16952476Then there are chances for the
Options -ExecCGI
to get re-added to .htacecss file.Could you please double-check and see if there the mentioned line is still present? If yes, please remove it and then check whether it works fine or not.
Also, could you please confirm whether you added the mentioned code as a mu-plugins as requested? There could be chances the code might not work if added via theme files or plugins
Looking forward to your response.
Kind Regards,
Nithin
First I edited .htaccess and deleted Options -ExecCGI.
https://prnt.sc/oljSdEHkul9gThen I added the code to the mu-plugins directory.
https://prnt.sc/LVFQTjmuvcaYNow I have checked everything and it is set as per the instructions.
Thank you for the screenshots,
Indeed the steps are correct, 500 errors will return a log line in Apache error log https://httpd.apache.org/docs/2.4/logs.html https://www.loggly.com/use-cases/how-to-monitor-your-apache-logs/ could you please check the logs, or save them, upload in Google drive and share the link?
Best Regards
Patrick FreitasHello @honzapecenka ,
We didn’t get logs from you so it looks like you don’t require our assistance. If you need please re-open this topic.
kind regards,
Kasia
- The topic ‘Backend / Frontend’ is closed to new replies.