We will have to look into the add-on to check what it does and how it currently works. Have you tried this yet?

Edit:

After quickly looking into the functionality of the plugin it seems almost unnecessary. Granted that is just my opinion, but Gravity Forms already has built in Save and Continue functionality offered that allows users to save their own progress and return to it later to complete filling it out.

Given the nature of how both the options work, Currently Gravity Forms Auto Formatter would not be able to pre-populate with the saved data because its not actually saved to the entry in the database yet which is when the auto formatting takes place. However, this is only for the users entry experience and when they actually submit the entry using either method, all of the data would be auto formatted as expected for the administrative side of things.

Yes and there’s bug maybe linked with my previous question : when I try to save a page with incomplete data and a field changing from “essai d’espace” to “ESSAI D ESPACE” it will only keep “ESSAI”.

Interesting. Can you explain the process that you are using.

Uch, difficult in few words..

Are you speaking of only using the auto caps without the additional “Gravity Forms Data Persistence Add-On Reloaded” plugin? ..Or are you saving the data through that plugin?

Gravity Forms Auto formatter always returns the full user value input unless you are removing, replacing, appending, or otherwise manipulating input text with it as well. It can capitalize the value, but could not truncate it given the functionality of the auto caps feature alone.

If we have a better understanding of the process being used we may be able to offer some insight.

I’m using both auto caps and strict text replacing functionality é::>e,è::>e,ë::>e,’::> ,à::>a,â::>a,ä::>a,æ::>ae,ç::>c,ê::>e,ï::>i,î::>i,ô::>o,ö::>o,œ::>oe,—::> ,–::> ,»::>,«::>,”::>,”::>,’::> ,€::>e,ÿ::>y,ü::>u,û::>u,ù::>u, ... and “Gravity Forms Data Persistence Add-On Reloaded” plugin When saving an incomplete page (returning errors so), it’s reloading persistent data but truncated.

Hmm. Well, I’m not seeing anything obvious there that would cause that to happen. Although if its returning the capitalized version already then the “Gravity Forms Data Persistence Add-On Reloaded” plugin must be doing some temporary saving to the database on some level.

Testing without “Gravity Forms Data Persistence Add-On Reloaded” and submitting an entry with the same replacements with auto caps on the same given input text “essai d’espace” saves “ESSAI D ESPACE” as expected.

Have you tried disabling Gravity Forms Auto formatter altogether and checking if its still being truncated? Gravity Forms Auto formatter uses the official Gravity Forms API to properly modify field data at the time it is saved to the database on submission, and works as expected. The data is just modified as desired and then saved to the database. It does nothing to the data past the initial save, so as the data is pulled it should be pulled normally if it being accessed normally.

..I am currently reviewing their code to see if anything stands out.

..things seem to be in order based on a surface scan of the code. However one possible thing could be that if you are using an autofill and only actually typing the first word in, their plugin relies on a “key up” event to get the current field data, so it may not be actually reading the data if it is autofilled. We have not tested this out in the least as we do not really dive into diagnosing others plugins.

Hopefully they can help you resolve the issue though.

When disabling Persistence Plugin, my field isn’t modified on reloading the page after error on submit. I guess your plugin modify the data after the form final step?

Happy to help! The format is the same. Please remember to NOT use spaces anywhere unless you want the space to be a part of what to search for or what to replace it with ..including after the commas that separate the format otherwise your text to replace will have to begin with a space. Examples of what you are looking to do are below.

by itself: ’::> ,

after another replacement: yes::>nope!,’::> ,

And what about replacing commas ?

Well, currently you can not replace commas. It seems like it would be a rare use case, but there’s no reason why it cannot be added.

Well take a look at adding that ability in there as well for the next update possibly.

Update:

• Added field “Minimum Character” requirement option for field types: text, text area, website, email, post title, post content/body, post excerpt.
• Added field “Maximum Character” restriction option for field types: website, email, post title.
• Added support for blacklisting of terms/phrases with commas using strict blacklist setting.
• Added support for replacement or insertion of commas using strict text replacement setting.
• Improved formatting of plugin validation messages.
• Clarified instructions
• Code improvements.

<3

I still have commas even with text replacement on Note that I updated the plugin and added comma::>remove,

‘comma::>remove’ works wonderfully here. NOTE:there are asterisks arround both terms that do not show here. You should also be able to use ‘comma::>,’ which just contains nothing between the separator sequence and the closing comma

A few things for you to check if this isn’t working on your install/setup. 1. look for spaces around or in your settings entry 2. check the version # of the plugin on top of settings page.. should be 1.7 3. clear any wordpress/server cache for the quiz/form page. you may have PHP caching on your server which is hanging onto old code..

..also remember to turn text replacement on for the field

Yeah everything is checked up and turned on.. Some of commas are replaced but not all of them. Maybe the same difference in “quotes” formatting?

Im not familiar with what you mean by “quotes” formatting. no quotes should be used in the terms or replacements unless you want the quote to be part of what’s searched for or replaced.

Lets try to narrow down what exactly you have set up.

When you say “Some of commas are replaced but not all of them”, are you referring to commas in the same field or different fields?

Is text replacement turned on for all of the fields if this is more than one field?

what is your wordpress/PHP versions?

when using *comma*::>*remove* in our replacement sequences we cannot replicate it not removing all commas from a field. It removes all commas in all of our testing.

If you would like us to review your config you can send us a temp login to a testing site with the setup you have configured so we can try to determine what might be happening.