FAOU

You do not need a URL. It’s your plugin. I’m not trying to publish broken forms. How many times and ways do I have to reword it? It is the behavior of all Fluent Forms since an update. All you all do is make excuses. You all do not even attempt to address issues. You don’t take any accountability.

For the third time, you have not shared a fix for Fluent Forms Pro’s bad coding that makes the Google reCAPTCHA icon on every page of a website. I have described the issue thoroughly. Go back and read what I have written here or in the support ticket. Do you not understand how CSS works, or do you not understand how your plugin works? Fluent Forms only provides a means to add CSS to individual forms, but you put the bad code on every page of the website whether or not it has a form. This is not typical. Fluent Forms Pro is non-standard. Other form plugins that integrate with Google reCAPTCHA do not do this.

I cannot keep responding if you are determined to not address the issues and say that you already have.

The conditional navigation logic issue is one you can observe if you create any Google Form with multiple sections. I’m not going to waste any more of my time or yours by describing widely known features here. That is something you all should figure out, but it is not the priority because the other issues stated make Fluent Forms Pro completely useless.

It has been well over a month since we tried to get you all to fix the issues with Fluent Forms Pro. It is still essentially unusable, and you have done absolutely nothing to address the issues other than to make excuses. Nothing about the plugin has improved. In fact, as noted earlier, it has gotten even worse.

1. Autofill is not an extension. Autofill is a native feature of every modern browser. You make a form builder and don’t know what autofill is? When a suggestion comes up with info to populate the form and the user clicks it, the form proceeds halfway and is stuck between the steps. Have you even bothered to test it?
2. You never provided a fix for the reCAPTCHA issue. You do not even recognize the issue. Fluent Forms Pro takes no accountability. Even your suggested workaround for me to compensate for your bad implementation is wrong. You changed the entire site and put your redundant code for Google reCAPTCHA on every page, whether or not it has a form. You expect me to go on every single page and add extra CSS styles to make up for your bad code.
3. Conditionality on containers is not a substitute for page conditionality. You’re right that it can be rigged to skip a page, but it is impractical as a method to create advanced navigation. The fact that Fluent Forms Pro doesn’t have the same conditional logic capabilities as free Google Forms is ridiculous.
4. Yes, the pro version has some advanced features, but it doesn’t have basic functionality. We cannot give a good rating for a plugin we paid for that is unusable.

And if you do get a form working, an update will come around that breaks it!

Just found out (only via trial and error, there’s no info about this from Fluent Forms) that subscriptions cannot even be dynamically priced! In fact, it’s not just subscriptions; there is no way to set any of the payment fields’ prices to the value of a numeric field calculation. The calculation features in Fluent Forms are rendered somewhat useless for anything other than a quote calculator because the values cannot be used in the billing or payment features.

Also, there is no official way to hide the calculation fields, so they have to be conditioned to be hidden. Forminator allows you to condition the calculations to be visible or not, but it also has a quick and easy checkbox option to just set it to be a hidden field.

Please do not mark this as resolved. My issue was not addressed, so it was not resolved. I talked about using ACF custom fields early on, but I explained in subsequent messages that after struggling with that, I was trying to get shortcodes to work, which goes well beyond just ACF custom fields in Forminators hidden fields. You all did not address what hook to use or why the code I spent a lot of time writing and testing is not working. Fluent Forms has a specific field for shortcodes and other ways to integrate dynamic content. I don’t want to spend all the time switching our forms over, but I’m wondering if it will save us a lot of time at this point. Are there any plans to add functionality to have shortcodes available in all fields?

Apparently, Wordfence is having an issue with Rank Math.

An error of type E_ERROR was caused in line 52 of the file /home/*****/public_html/wp-content/plugins/wordfence/lib/wfView.php. Error message: Uncaught wfViewNotFoundException: The view /home/*****/public_html/wp-content/plugins/seo-by-rank-math/views/common/modal-prompt.php does not exist or is not readable. in /home/*****/public_html/wp-content/plugins/wordfence/lib/wfView.php:52
Stack trace:
#0 /home/*****/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(6243): wfView->render()
#1 /home/*****/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(6169): wordfence::setupAdminVars()
#2 /home/*****/public_html/wp-includes/class-wp-hook.php(324): wordfence::admin_init()
#3 /home/*****/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#4 /home/*****/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#5 /home/*****/public_html/wp-admin/admin-ajax.php(45): do_action()
#6 {main}
  thrown

Thank you for your quick response! Grateful for your help!

You said that Forminator disables scripts and iframes due to security concerns. What are those concerns? I do not want to compromise our site or any others we work on, but I do not understand how allowing the creator of the form to put in scripts and iframes in the HTML fields (or HTML shown after the form submission) compromises a site’s security. I want to understand before using your code. Also, does Forminator have any plans to enable this in a future update?

Upon further research, I now think the ampersand being replaced with & is not an issue. Somehow, while learning HTML, I never learned ampersands were supposed to be escaped in attributes. I don’t even usually see HTML written like that. Apologies for my mistake.

It seems like your message mostly reworded what I said. I don’t feel like I’ve gotten any help with this yet. I am glad that Forminator is at least considering adding this feature. It seems like less of a need to add a feature as almost a bug. Don’t get me wrong; I still think Forminator is a fantastic plugin, and I am grateful to you all for it. Still, I don’t understand why any of this custom coding is necessary. I understand now (from my own hours researching how to do this, not that you all ever even explained this) that having input in form fields run as PHP would probably be bad from a security standpoint. It does not seem like that point is strong enough to warrant not allowing any shortcodes (including shortcodes like Pods that could print values from custom fields) to work in the fields, especially because the shortcodes could run before the user interacted with the form. I tried the code suggestion in your documentation, but your code there seems to only allow shortcodes to work in HTML fields, not input fields.

add_filter( 'forminator_replace_variables', 'do_shortcode' );

I feel like the responses you all have sent have been to say that I can’t possibly understand and need a developer. Yes, I have a very slim and new understanding of php, but that really is not the issue. Even a developer would have questions here. The official documentation does not include info about Forminator’s hooks, and the closest thing that I could find is a list of Forminator hooks on Github that is not very descriptive.

I have spent hours and hours trying to get this to work. I have tried countless versions of code, but I haven’t had any success. I redirected my efforts to just trying to get shortcodes to prepopulate the data, for example, setting default values to custom field values using shortcodes, as opposed to getting ACF custom field keys to work directly in the form. I wrote the simple code below and put it on the relevant page using a WPCode snippet for PHP. Why is this not working?

<?php
function custom_forminator_replace_form_data($content, $data, $fields) {
    // Process shortcodes in the content
    $content = do_shortcode($content);

    // Process shortcodes in the data
    foreach ($data as &$value) { // Pass by reference to modify the original array
        if (is_string($value)) { // Only process if the value is a string
            $value = do_shortcode($value); // Process the shortcode
        }
    }

    // Process shortcodes in the fields
    foreach ($fields as &$field) { // Pass by reference to modify the original array
        if (isset($field['value']) && is_string($field['value'])) { // Ensure 'value' is set and is a string
            $field['value'] = do_shortcode($field['value']); // Process the shortcode
        }
    }

    // Return all modified parameters
    return [$content, $data, $fields];
}
add_filter('forminator_replace_form_data', 'custom_forminator_replace_form_data', 10, 3);

Thank you for the quick response!

Respectfully, you did not really answer my questions. I tried to be as clear as possible, but I think you have misunderstood. My issue is a very similar to the one in the thread that I linked. Like I said, “I am trying to put some hidden custom field values (corresponding to each individual page) about the project a submission corresponds to in hidden fields of a form.” Whether a user is logged in is irrelevant, so your code does not seem relevant. Correct me if I am wrong though. Maybe you could explain it a bit better. I am no master of PHP, but I should not need a developer. I can put something basic in a code snippet if there’s no way to put it into the form directly. The PHP for this should be relatively simple. The issue is getting the PHP to either work inside Forminator form fields or passing data to some intermediary from which Forminator can obtain the custom field values. How can that be done?

Does Forminator support some kind of “magic” tags (that’s what some programs call the {custom_field_value} type tags)? If Forminator has a format for entering custom field variables (like the {profile_val} entry that you mentioned) without PHP that would be great, but when I tried putting in {profile_val} in the hidden field and submitting the form, it literally just returned “{profile_val}” in the form submission. I also tried this with the custom fields on the page and had similar results. It did not work when I put it in without the brackets either.

If {custom_field_name} worked in the hidden field (with custom value selected), that would make additional PHP unnecessary. Any plans to update Forminator to make that possible? It would be great if Forminator had a dynamic content option that could just pull the info from the post. Just to reiterate, I am trying to pull “dynamic (relative to the form, static relative to the individual post) content” from the post. The same form is on multiple posts.

Are you all working on adding dynamic features to Forminator? It seems like every website today has dynamic content and could benefit from the capability to bring that data into the form.

Thanks!

We absolutely love it and recommend it to others! Thank you, Dave and Forminator team! Hopefully, you don’t mind us pointing out the little things we thought need some improvement. Overall, we know Forminator is exceptional!

It’s not a problem with the site. It’s a problem with Blocksy. You can test it on your own. I even sent you the link to the plugin. It works fine with every other theme tested, and I personally tested several themes including Astra and Kadence. Like I said, I even tested it on a different website. It’s the theme. I sent you screenshots too. Please just test if for yourself. I tested the other themes to consider switching, but I like Blocksy better than Astra and other themes. I’m hoping you all come up with a fix soon.

Hello @cteduard and @creativethemeshq,

Sorry for the delay. There are a ton of unrelated things going on that I have been dealing with.

I have tested this thoroughly on the site and even tested Blocksy on other sites. This is still a problem.

The problem is apparently with how Blocksy works with custom fields plugins. The plugin the website in question is called Advanced Custom Fields. It works on other sites and even works with the site having the issue if we switch to Astra, Kadence, or any other theme that we have tested. When Advanced Custom Fields is activated on a site (I tested it on a separate site too) with Blocksy as its theme or child theme (tried both), the customization pages do not load or function correctly. I like Blocksy best, but we need to be able to use plugins like this. Please fix this.

Thank you!!!

• This reply was modified 1 year, 11 months ago by FAOU. Reason: forgot to include link

It is absolutely 100% certainly the Blocksy theme that is the problem. I have gone through everything and tried everything for hours and hours now. I installed and activated Astra, and that works perfectly fine. I installed and activated Kadence, and that works perfectly fine.

You must have other sites having this issue. It is Blocksy causing this. It’s really unfortunate because I made a lot of progress setting up the site a couple months ago with Blocksy before it stopped working. I considered Kadence. I chose Blocksy instead of Kadence because I heard that Kadence was a rip off of Blocksy. It seems like I made the wrong decision.

This is how the customize pages look with Blocksy. I don’t know when this happened. I have been busy with other things for the past few months.

Hi @cteduard

Thank you for getting back to me!

Everything is fully up to date and set to auto upgrade, including WordPress Core.

There are no new plugins, but I did disable the most recent plugin just to see. It didn’t fix anything. I also tried turning off the redirect mode that the website is currently in while being constructed, although it had been in this mode even when the customize page was working. I have re-enabled the plugin and the redirect mode, since neither were the issue.

I really think it is an issue with the parent or child theme. Everything else seems to be working fine.

Hi @onlykawshar,

I apologize. I’m not sure if maybe this was a caching issue. Thank you for your help! It seems to have resolved itself.