Title: Data persistence and query strings
Last modified: August 22, 2016

---

# Data persistence and query strings

 *  [psteinweber](https://wordpress.org/support/users/psteinweber/)
 * (@psteinweber)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/data-persistence-and-query-strings/)
 * Hey,
 * I noticed a bit of an unfortunate behaviour when it comes to working with data
   persistence and query strings. If a form has been visited before, a query string
   in the URL doesn’t have any effect when visiting the form again. IMO it would
   be better to give the query string the right of way, i.e. overwriting any previously
   saved data.
 * Any ideas on how to tackle that issue?
 * Philipp
 * [https://wordpress.org/plugins/gravity-forms-data-persistence-add-on-reloaded/](https://wordpress.org/plugins/gravity-forms-data-persistence-add-on-reloaded/)

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Plugin Author [unclhos](https://wordpress.org/support/users/unclhos/)
 * (@unclhos)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/data-persistence-and-query-strings/#post-5408492)
 * Sounds like you should use the option to clear on submit. But I’ll look into 
   changing priorities.
 *  Thread Starter [psteinweber](https://wordpress.org/support/users/psteinweber/)
 * (@psteinweber)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/data-persistence-and-query-strings/#post-5408500)
 * Thanks for the quick reply!
 * I don’t think clearing on submit would do my use case any good.
    It would be 
   great to be able to only clear the one (dynamically populated) field. Just an
   idea…!
 *  [fried_eggz](https://wordpress.org/support/users/fried_eggz/)
 * (@fried_eggz)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/data-persistence-and-query-strings/#post-5408797)
 * This should be possible by comparing the keys in the query string to the keys
   saved in options and let query string take precedence
 *  [aw741e](https://wordpress.org/support/users/aw741e/)
 * (@aw741e)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/data-persistence-and-query-strings/#post-5408816)
 * Any more news on this issue? I’m having the same problem. not sure how to change
   the keys to let the query string take precedence?
 *  [MikevHoenselaar](https://wordpress.org/support/users/mikevhoenselaar/)
 * (@mikevhoenselaar)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/data-persistence-and-query-strings/#post-5408865)
 * Any more news on this issue? I’m having the same problem. This way the dynamic
   populated fields option isn’t working and therefor useless.
    Love to get an update
   on this.
 *  [MikevHoenselaar](https://wordpress.org/support/users/mikevhoenselaar/)
 * (@mikevhoenselaar)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/data-persistence-and-query-strings/#post-5408866)
 * I fixed it myself.
    Hopefully this gets added to the plugin.
 * [http://codeshare.io/TvhoH](http://codeshare.io/TvhoH)
 * The problem was the plugin didn’t do anything with the inputName variable. This
   is the variable GF uses for population.
 * Have fun with it! 🙂
 *  Plugin Author [unclhos](https://wordpress.org/support/users/unclhos/)
 * (@unclhos)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/data-persistence-and-query-strings/#post-5408870)
 * Thanks for the code. Just recently looking back at this plugin after a long programming
   break. The problem with using your code as is the query variable would always
   take precedent. I didn’t want that to happen, as if there was already saved data(
   which I check for), means the user has started to fill the form out before. I
   will need to add in a priority system, or drop down and warning for different
   input values. The thinking is if someone used a link to get to the form, the 
   field might change every time (timestamp or something), and they might try to
   use that same link to find the form again (I know I would).

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Data persistence and query strings’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/gravity-forms-data-persistence-add-
   on-reloaded.svg)
 * [Gravity Forms Data Persistence Add-On Reloaded](https://wordpress.org/plugins/gravity-forms-data-persistence-add-on-reloaded/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/gravity-forms-data-persistence-add-on-reloaded/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/gravity-forms-data-persistence-add-on-reloaded/)
 * [Active Topics](https://wordpress.org/support/plugin/gravity-forms-data-persistence-add-on-reloaded/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/gravity-forms-data-persistence-add-on-reloaded/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/gravity-forms-data-persistence-add-on-reloaded/reviews/)

 * 7 replies
 * 5 participants
 * Last reply from: [unclhos](https://wordpress.org/support/users/unclhos/)
 * Last activity: [10 years, 6 months ago](https://wordpress.org/support/topic/data-persistence-and-query-strings/#post-5408870)
 * Status: not resolved