gorish
Forum Replies Created
-
I also deleted the add-on and then reinstalled and reactivated it. That didn’t work either.
So probably an incompatibility error. I have the latest version of PHP, for instance. Or maybe it doesn’t work the latest version of WP (it’s a relatively recent problem, the radio buttons were displaying their status correctly earlier in the year).
I’ve tried other browsers and in private/incognito mode – no change.
What else could the problem be? Is there some way to check that your code (or the CSS directives) meet current standards for the latest versions of PHP, WP, Apache, etc.?
I see now that if I entered the path you suggested then I get /wp/wp-content/wp/wp-content/forminator etc.
I set it back to default.
So now the path (request URL) is correct. But this time I get a 500 error.
Thanks Dmytro.
I changed the data settings as you suggested (before it was the full internal server path /domains……./public_html/wp/wp-content…etc.
But it hasn’t fixed the problem.
As you can see the folder and CSS file exists in the right place.
However, is index.php supposed to be an empty file???
Thanks, but no errors logged.
What do you mean by errors in the console on Forminator’s files? And how can I check if there is a form malfunction? Is it at the code level or maybe incompatibility with the latest version of WP that you need to fix first?
BTW, it works fine when I preview the form, but not when it’s published.
I created a new test page Test Forminator Radio Buttons. The buttons are selected internally and can trigger conditional fields.
But the selected button is not displayed on the published page (but I can see which button is selected in the preview).
Forum: Fixing WordPress
In reply to: Missing Update Profile buttonResolved. It turned out to be an old plugin, Contact Form 7 (which has since been discontinued) and/or addons to this plugin. I uninstalled the plugin (in one case, it had to be done manually by deleting the folder in ../plugins).
And then everything returned to “normal”.
No doubt if you have a similar issue then probably the first thing you should try is to gradually deactivate your plugins.
What helped to identify the culprit was to install the WP Debugging plugin. So it wasn’t a brute force having to go through each plugin in turn… 🙂
(However, in my case this wasn’t sufficient. I had to DELETE the plugin before the error was resolved. It might not be feasible to do this for plugins with saved data or configuration. So perhaps duplicate/backup your wordpress site and then gradually delete plugins until your problem is resolved. Using the debug monitor might prevent you having to follow this more drastic approach.)
- This reply was modified 3 years, 10 months ago by gorish.
I’ve finally found a partial solution to this problem. I’ve looked at hundreds of forum posts where this same problem is discussed and was finally directed to this post this post that suggested a fix.
Firstly, why is this even an issue? Who is responsible for deciding that the (standard?) WP editor(s) strip out important coding features like href, onclick, mouseover, etc.? Nearly all my WP pages include bits of code where icons get clicked or embedded videos are played, etc.
Who can I contact in WordPress to address this issue? At the very least, there should be a configuration setting which lists all the tags that will get stripped / preserved when switching from text mode to visual mode, whether in the text editor or the block editor!
Without realizing it, I’ve more or broken every page on my website by making a small tweak in the text and then only much later being told by a visitor that the functionality has failed. And now I’m having to painfully go through every line and try to figure out what the code should be – and be VERY CAREFUL NOT to enter visual mode to check the layout.
It gets worse: if I subsequently edit some other page visually and then come back and edit a page with interactive elements (e.g. onclick) then the editor starts out in visual mode and instantly wipes out all the code. The only workaround is to keep separate text files for every page and edit them outside WP (without the benefit of checking the layout visually) and copy/paste them into the WP editor. What a palava!
What is it about javascript or javascript:void() that makes this tag different from, say href=”#”? If I use the former syntax, it gets immediately stripped out, but if I use the latter syntax (with the Advanced TinyMCE Configuration plugin) then it’s preserved.
Thanks
Well, maybe so – but they don’t make it clear that you have to continue to renew your “subscription” indefinitely in order to continue using the product(s) you purchased.
A year after buying the “pro” theme, I found that I had to install and reactivate it. (BTW, the license key isn’t emailed to you, you have to log in to your account page and it’s hidden away in the licenses section.)
My subscription had expired and, even though I was still using the version that I had originally purchased, I got a message saying that the license key was invalid.
When I contacted support, I was told that I have to renew my subscription for a further $60 to be able to use the Pro features. I’m happy enough with what I bought. It does the job that I paid for. I don’t need to upgrade to any newer features. I don’t need to pay yet another $60 (and then have the same problem in a year’s time when I want to install the theme on my other websites). I don’t want to fork out $60 indefinitely because I would rather buy some kind of lifetime agency package for $100-$200 that does everything else I want.
Avoid this product and all the other products by Brainstorm Force (ConvertPlug, Ultimate Addons for BB and VC, etc.) unless you’re happy to just use their basic free products.
DO NOT BUY A SUBSCRIPTION because you will be empty-handed after a year, or be locked in to renewing your subscription indefinitely.