codepeople

Hello @pexel

You entered the tags directly in the fields labels.

However, I see you created a custom template and entered the style definitions with !important modifier, and the new CSS rules are being assigned to the fields in light and dark modes.

Best regards.

Hello @pexel

Please enter the CSS rules with the !important modifier. Ex.

<strong><font style="color:RoyalBlue !important;">Gün:</font></strong>

Best regards.

Hello @slimpickins

Thank you very much for the feedback and sharing your solution. I’ll analyze its implications to include in the next plugin update.

Best regards.

Hello @uponity

In the current plugin version, you cannot use variables as fields predefined values directly, but you can assign them at runtime. For example, assuming you have the myvar variable:

[CP_CALCULATED_FIELDS id="1" myvar="4"]

And you want to use it as the default value of the fieldname123 field.

Insert an “HTML Content” field in the form and enter the following piece of code as its content:

<script>
fbuilderjQuery(document).on('formReady', function(){
    getField('fieldname123').setVal(cff_var['myvar']);
});
</script>

Best regards.

Hello @pexel

Thank you very much for using our plugin. The current plugin version estimates the forms’ heights, even rendering them on the client side. You don’t need to enter specific heights anymore. However, if you have forms configured as hidden by default, and you display them at runtime, when the form is shown it moves the rest of the page tags. But this is unavoidable, even when estimating the form height.

Best regards.

Thank you very much for the review!

Best regards

Hello @uponity

Thank you very much for using our plugin.

My apologies for the confusion. We are editing the FAQ entries because we modified the implementation of global variables to avoid plugin conflicts.

In previous plugin versions, the shortcode directly creates the global variables, but this has a problem. If another plugin uses a javascript variable with the same name, the global variable will provoke a conflict. The same would happen with global browser variables like window.

With recent plugin versions, the shortcode generates a cff_var object, where the shortcode variables are cff_var properties.

So, if you insert the shortcode:

[CP_CALCULATED_FIELDS id="1" myvar="4"]

You can use it as follows:

fieldname1*cff_var['myvar']

or

fieldname1*cff_var.myvar

Best regards.

Hello @emolotel

I’m sorry, but I don’t understand your question. You remove the “Single Line Text” field from the form and insert a “Number” field in the same place. Finally, it is necessary to edit the equations and dependencies where you used the “Single Line Text” field to include references to the “Number” field.

Best regards.