Hello

The case formatting and text replacement are not live but take place on the submission to sanitize so the user does not see the changes. Other things like input copying and disabled fields etc are live on the form.

And yes you can choose the case formatting (upper , lower, first letters upper/title , first letter upper)

Hope this helps

Hello

You can use a couple features in our plugin to either prevent incorrect values or change them.

The “numeric only” option would prevent the user from entering a comma or a period in the first place or the text replacement could just auto remove them if you allowed them still (but text replacement only takes place During submission and I am not sure when your calculations are taking place)

It seems that disallowing the special chars using the numeric only option and clarifying the instructions to input centimeters might be the best. ..perhaps even give an example of 1.87 meters = 187 centimeters ?

Hope this helps

Thanks for your response!

Yes I already give examples about the right format on the field description and placeholder. However some people seem to be a bit dumb and do it wrong anyway :/

So if someone uses a dot instead of a comma for example, the whole calculation doesn’t make any sense…

Isn’t it possible to replace a dot with an comma before form submission with your Plugin?

text replacement only takes place During submission and is not seen by the user.

You could always just use conditional logic to hide the submit or next page button and show an HTML Message field to the user if the height is over or under a normal range or contains a comma. The HTML field could give near instant feedback telling them to lose the comma and use a period, and rexeplain the desired format. This would prevent the use of commas.

Hope this helps

Hello, currently no you cannot specify individual formatting options for each input of a multi part field.

Unfortunately For this particular usage the case formatting happens next to last so that it effects any text replacements so even if you replaced the values they would be auto cased again.

We can potentially look at working on something like this on the future

Hope this helps

UPDATE:

We have updated the case formatting code to support most languages with UTF-8 encoding. This update should be out very shortly

UPDATE: Version 2.4.2 has been released. This version should now support most all alphabet characters with case properties for auto case formatting.

• Auto case formatting now supports most all languages with UTF-8 encoding (Some Turkish may not be supported)
• Tested on WordPress 4.9.8

Happy Auto Formatting

Great, thank you.

My bad, yes validation message. And yes, list field. Ok will try that fix. Also, is there a way to auto format phone numbers on the list field?

Unfortunately there is currently no input masking for list fields but you can use the numeric characters only setting and potentially the min or max character setting to get a numeric phone number the length you would like it to be.

• Fixed and issue with list fields giving an initial minimum character validation error when no minimum character limit is set.

Hello,

Both yes and no.

You can use text replacement to replace any character with any other character if you always wanted those characters to be replaced with capital versions, but you cannot use the auto case formatting to change special characters to different caps formatting.

Hope this helps

UPDATE: Version 2.4.2 has been released. This version should now support most all alphabet characters with case properties for auto case formatting.

• Auto case formatting now supports most all languages with UTF-8 encoding (Some Turkish may not be supported)
• Tested on WordPress 4.9.8

Happy Auto Formatting

Hello

Thank you for letting us know of the issue. We will definitely look into it for correction in the next update likely next week.

To attempt to workaround/clear the issue in the interim if you wanted you could try entering a character minimum for those fields and saving them removing and saving again.

Hello,

1. The plugin will currently update existing entries if the specific field data is updated/changed and saved/updated. So if you are updating data on an existing entry the new data will be auto formatted. The idea to make it able to manually update all fields in entries retroactively is both possible and interesting and we will give it some thought for a possibility in a future update.

2. The plugin should work with almost any characters for certain options like the blacklisting or text replacement and capitalization but other features may not be compatible due to differing keyboard layouts / alphabets etc.

3. Yes

Hope this helps

Perfect! You just got a new client. I’ll try my best not to be a PITA

Hello,

Thank you for the feedback! We will look to consider this for the next update

Hello,

The “Phone” field is currently not supported by auto formatter.

Supported Field Types: single line text, paragraph text, name, email, website, address, number, list, dropdown, multi select, radio buttons, checkbox, quiz, post_title, post_content, post category, post_excerpt, post_tags, post_custom_field. *Not all options are available on all field types. Only options which are useful to particular field types apply to that field type. Some options like requiring matching or blocking entry between fields can be applied to supported fields and checked against unsupported fields

But that said ..it clearly seems like it would be useful to support the phone field for at least the “require/block matching field values” options. We will definitely look to implement that ability in the next update

For a supported field you will just want to set the “Block Matching Values (with these field IDs)” option on each field with the field ID’s of the other fields it cannot match. example if field one three and 5 cannot match you would enter 3,5 in field one 1,5 in field 3 and 1,3 in field 5 for that option.

Hope this helps

shoot! can I refund since the phone field is not supported just yet

We’ve actually already released the new version with support for phone fields.

• Added support for “Phone” as supported field type with the following options: Read Only Field, Disabled Field, Turn Off Autocomplete, Require Matching Values, Block Matching Values.

Hope this helps

Understood,

Currently we do not have any plans to filter data on the pre-render stage for Gravity View cases, although it is likely possible. But for now this would likely be a good topic to request of the Gravity View authors.

Thanks, I have talk to gravity view team and they say there is no solution

One more thing plugin detail says “HTML tag and PHP code removal” How does it work?

Certain text based fields accept html input and could also accept php written within that. That options strip the html tags off all content and leaves the content remaining. Similiar to the link removal option but it keeps content inside of any tags but removes any php

Hello,

There are a few ways to achieve this.

1. use “alpha characters only” ..for letters only in realtime

2. use “numeric characters only” ..for numbers only in realtime

3. use “alpha numeric characters only” for letters and numbers only in realtime

4. use ’ ::>,’ or ’ ::>remove,’ (“remove” should have asterisks around it as in the instructions but the editor here removes them and bolds the inner content) either in the fields “individual text replacement” option or in the central strict text replacement if you turn on central text replacement for the field and want to remove spaces globally with that option (use it as directed in instructions without quotes around it) to auto remove any spaces from the user input as the entry is saved. the user will be able to put spaces in but they will be removed on submission and save to database. The syntax of the text replacement tells it to replace the space with nothing.

hope this helps

Thanks for your quick response. We implemented the real time validation with REAL TIME VALIDATION PLUGIN FOR GRAVITY FORM, but we observed that when turned on, it does not work with maximum-minimum character input of gravity form. If we buy your plugin, can it work along side the real time validation plugin without disabling it or any conflict?

Thanks for anticipated reply.

Our plugin does not directly disable any other plugin or normal gravity forms operations and plugs into the hooks, actions, and filters provided directly by gravity forms to process data within gravity forms standard method of operation.

We can assert compatibility and proper integration with gravity forms itself but generally speaking, unless specifically tested.. most plugins cannot simply state full compatibility with any other since a plugin can do anything and even change the entire way that WordPress itself operates. If the plugin you are using does not override or impede gravity forms standard validation and database writing operations then our plugin should run fine alongside it. However, this does not mean that that two will work together as you expect.. Example: our validation runs with gravity forms validation so unless the plugin you are using runs the standard gravity forms validation in real time, our plugins validation will not run with it but should run when standard gravity forms validation does if the plugin you are using doesn’t interfere with or disable it.

Gravity forms does not have min char standard, our plugin does. The max-char in gravity forms is placed within the input HTML itself to restrict the input to max chars and shouldn’t be impeded by any plugin, so it is interesting that the real time validation is not working with it.

UPDATE:

Version 2.2 adds the ability to select fields for Alpha Only, Numeric Only, Or Alpha-Numeric Only inputs. This feature restricts the ability to only enter characters of certain types into the inputs in real time. This is helpful or may cases but even for “number ” type inputs where you can normally still enter alpha characters and not get any errors until the form is validated. Both Gravity Forms built in ..and our “Maximum Characters” options restrict the max length in real time. Our plugins Min-Char restriction currently checks if conditions are met on normal form validation and not in realtime since all inputs start with zero characters unless intentionally prepopulated.

• Added Numeric Characters Only field setting to only allow input of numeric (number) characters.
• Added Alpha Characters Only field setting to only allow input of alpha (letter) characters.
• Added Alpha-Numeric Characters Only field setting to disallow special characters and only allow input of alpha-numeric (letter and/or number) characters.
• Added support for number fields with options: Numeric Characters Only, Read Only Field, Disabled Field, Turn Off Autocomplete, Require / Block Matching Values
• Added support for List fields with options: Auto Case Settings, Minimum Characters, Maximum Characters, Before text, After Text, Remove Links, Remove HTML/PHP, Read Only Field, Disabled Field, Turn Off Autocomplete, Numeric Characters Only, Alpha Characters Only, Alpha-Numeric characters only, Central Blacklist, Central Text Replacement, Individual Blacklist, Individual Text Replacement.
• Added ability to make Drop Down, Multi Select, Radio Buttons, and Checkboxes readonly and/or disabled.
• Strengthened readonly and disabled attributes by removing ability to click on the fields or labels on form entry.

of course we on the blacklist checking for the field in its advanced settings. Your plugin does not seem to be too complicated. And no we did not solve the issue. do you have proper support?

Yes. The plugin is not complicated to use, but we cannot overlook the simple solutions. The Strict Blacklist works wonderfully for everybody else but for some reason we would like to help determine, it is just not working on your site/form/field.

Does the standard blacklist work specifically on the same field?

If not you should make a clone/copy the form to test out solutions and try just deleting the text field that has issues and create a new text field in its place and set it up the same then preview the form and test the blacklisting. The setting is stored as part of the field object so if the field object got saved oddly for any reason this should clear that up. If successful , implement on your regular form.

If you have a test/clone site I would suggest checking the setting to save plugin settings on uninstall, and disable and remove the plugin then reinstall. This is to try to clear any possible issues on plugin install. I would also clear the cache for the form page or any server PHP caching for the site if possible. Then if still not working , disable any potentially conflicting plugins and testing again then if it works begin to turn plugins back on one by one with tests between.. That way we could narrow down the issue if there’s anything preventing the operation from running. It’s unlikely that it is a plugin conflict .. but possible

If you would just like a support rep to log in a check out the setup to help determine the issue please just use our author contact form to identify yourself and send us a temp login and instructions on the form / field that the issue resides on . They will need access to the auto formatted settings page and as well

..also If you are not running the latest plugin version Version 1.9.7. Please download and install it.

Excellent! Thank you!

Update:

Version 1.9.6 (submitted for release)
* Clarified instructions.
* Fixed issue with “Strict Text Replacement” not replacing values when the search string was entered first.

..Generally speaking the updates are approved for release within a 1-3 days, but the issue is confirmed as being fixed. thanks again for the report, and happy auto-formatting

Update:

1.9.6 has been released.

Please note that as in the samples on the settings page, quotes should not be used around anything within the text replacement structure. The quotes would only be seen as part of the text to either be replaced or replace it with so it would search for ’ ’ . The same would go for %20. It would literally search for %20.

In order to use special characters in your text replacement you have to use the “strict text replacement” option. This is covered in the option guide for the text replacement options on the settings page.

To replace spaces with underscores the following would be entered onto the end of your replacements in the “strict text replacement” option

, ::>_,

Gravity forms trims leading and trailing spaces by default so if the data entered begins or ends with spaces they will simply be removed and not changed to underscores.

Hope this helps

We do not recommend editing the core PHP plugin.

The issue has been resolved and will be submitted for release under a minor version change today, so it should be approved for released within a few days. ver 1.9.2

Thank you again for the report

..just as a note concerning your question on, the form->fields array is ordered by form field order and does represent the form field ID as far as the array numbering. It always starts at 0 and increments from there. The fields id is another array layer under the index for the field object itself.

thank you! Appreciate the promptness.

1.9.2 is now available

Plugin is primarily intended for ASCII character english language and special characters may not be recognized properly for the case functions

UPDATE: Version 2.4.2 has been released. This version should now support most all alphabet characters with case properties for auto case formatting.

• Auto case formatting now supports most all languages with UTF-8 encoding (Some Turkish may not be supported)
• Tested on WordPress 4.9.8

Happy Auto Formatting

Hello Jimmy,

The auto case / capitolization is performed on the data during submission and saved to the database so the submitted entry will have the auto formatting applied but the user does not ever see its effect unless they receive data back through confirmation / notification.

Excellent !!! Exactly what I have been looking for … Sold!

“How to change date format to dd/MMM/YYYY?”

With the date field there is a “date format” setting under the general settings for the field. Although there is no option for a 3 char month.