Gp here https://energybalanceinitiative.com/go-far-workshops-for-instructors/#register and then you can scroll down the form to the Course Registration section and select a workshop in the “Please select a registration option below:” field to make the number field appear and see that they have no up/down arrows.
I not seeing it in Google Chrome, Brave or Microsoft Edge but I do see it in Firefox.
Here is a video about what I am talking about: https://app.screencastify.com/v3/watch/MTTazKRKe2MMcwt43LLR
]]>Normally, others same type input fields shouldn’t be able to enter number without clicking it, but my currently issue was the opposite where I don’t need to click on the others input fields. Just by pointing my cursor inside the input field and I can type a number inside.
Sorry if this is confusing, I’m not sure how to describe this issue
How do I remove this feature/function?
]]>For example, I want the field to be pre-populated with unique submission number + making the field invisible + so that site visitor does not need to fill it herself.
I am sure this is do-able. Only that I am not techy enough to understand the “query parameter”
Thanks in advance.
]]>I want the field to have no less AND no more than 9 characters AND they have to all be numbers.
Is this possible?
]]>First, let me say that I actively use a certain amount of custom code via Forminator hooks to change the default styling of my email notifications from list form to table form. For example:
Default Email Styling
<ol>
<li>
<strong>Hello</strong>
World</br>
</li>
</ol>
My Email Styling:
<table>
<tr>
<th>Hello&</th>
<td>World</td>
</tr>
<table>
I know this support is not for fixing custom code. However, there is a quirk with number fields and how they translate into emails that I thought I should bring to the forefront. Using my code and {all_fields} or {all_non_empty_fields}, number fields insist on using double decimal places (ex. 2.00) regardless of what decimal place choice I make within the form editor, it always has two decimal places. I removed my code to see how {all_fields} and {all_non_empty_fields} behaved on their own.
{all_fields} behaves as expected. A number with the proper number decimal places(or lack there of) was displayed. {all_non_empty_fields} on the other hand showed always showed two decimal places after the integer.
With or without my custom code, this number quirk does not appear to exist when using the number short code directly (ex. {number-1} displays as “2”). Nor does the number quirk appear in the database. All the numbers appear as anticipated.
I can’t tell where this quirk originates. Both {all_fields} and {all_non_empty_fields} have similar, if not identical, code in “helper-fields.php”. I imagine the issue could be arising in the “forminator_custom_form_after_render_value” filter in “front-user-registration.php”, but I’m not familiar with that area of Forminator’s code. Otherwise, maybe it’s being affected by the jquery code? But I feel like that’s only affecting the front end, not the back end.
I’d love to know if this is functioning as anticipated or if there’s a temporary fix before the next update.
Thanks.
]]>