Problem with disable persistence on a per field bases

I installed an older version (3.2.3) and it looks that everything is working great, I think it affects only the latest update.

Best

Giorgio

There has been no change in how that works (after looking at both versions). But I have having some mixed results on when it is working and when it is not. I will try to fix and update soon.

Hi – I’m having the same issue, although there are some issues with going back to 3.2.3

– on version 3.3.0, when a user is signed in, the ability to switch data persistence off for individual fields does not appear to be working. I have 4 regular input text fields where data persists.

– going back to version 3.2.3 switching data persistence off for individual fields is okay – but they no longer are able to be dynamically populated.

– I’m using Gravity Forms 1.9.16

Thanks – good luck debugging and if I can be of any help let me know. It’s a great plugin – so do let me know if you need any more info from me.

Found the problem. Update pushed.

That’s great news – and thank you for your swift response.

I’m still having difficulty however – and it seems to be particularly with fields that are dynamically populated. The fields are all set to have data persistence switched off, but they are all either populated with old data or, if I complete the form again, not populated at all.

Again, thanks for your efforts. If you’d like me to send screenshots or a short video, I’d be happy to do so.

In the meantime I think I’ll populate those fields via jQuery. Thanks.

How are you doing the population? I have it currently setup so $_GET variables overwrite the persistence data. Or it should be. Also any old data that was saved with 3.3.0 will have the fields that you had persistence turned off on as it handles that on the saving side not the display side of the code.

Hi – that could be the issue then. It’s not via $_GET I’m using variables from the URL string / query_vars. For instance, this URL:

https://cloquethospital.com/employment/apply/1167/

I break down the URL and the 1167 is applied to a gravity form shortcode that looks like this:

echo do_shortcode('[gravityform id=1 ajax=true field_values=\'job_id='.$job_id.'\']');

where $job_id is the 1167 variable. Are you saying that if my URL was this instead:

https://cloquethospital.com/employment/apply?job_id=1167

I’d be okay?

re: old data, that’s fine – I created a new user entirely, with no saved data, when I updated the plugin.

Re: old data, there is a purge button now on form settings to delete persistent data on a per form basis

Re: url, the second one would work, but if gravity forms support the way you are doing it, i will try to as well

Brilliant – I really appreciate the swift responses during this exchange.

Right – it’d be awesome if it supported query_vars out of the box, but in the mean time I could replace all my dynamically populated variables like so:

$_GET[‘variable’] = $variable;

having previously set $variable from a query_vars. That’s done the job for me without any jQuery, and maintaining persistence etc.

Thanks again.