unclhos

This plugin has NEVER supported files. And you are correct, I don’t make money on this plugin so with being disabled and bills to pay, I don’t have time currently to update it. With the “Save and continue” feature in Gravity Forms, I really don’t see the need to continue support on the plugin either. Unless someone can make a very compelling argument or donates for the time required to update. I don’t see an update coming. Sorry for the loss.

wp_get_attachment_url(get_term_meta( $term_id, 'pix_term_icon', true ));

wp_get_attachment_url(get_term_meta( $term_id, 'pix_term_image', true ));

• This reply was modified 8 years ago by unclhos.

Hmmm, weird. It didn’t work on my install. I will look into why more.

https://www.itnota.com/fixing-php7-compatibility-issue-w3-total-cache/

I’m looking for same information. In compatibilty I see

Mime type detection: Not installed (required for CDN support)

But can’t find any information about it for PHP 7

It is an older version that uses the standard “option” system vs the “transient” system. The option key is a little different. The structure is “{USERNAME}_GF_{FORM_ID}”. You can pull it with a standard get_option() call.

Try version 3.2.3 It doesn’t have the latest features, but should work better for you as it doesn’t use transients. But there is no way to get rid of data via the backend with it.

https://downloads.www.ads-software.com/plugin/gravity-forms-data-persistence-add-on-reloaded.3.2.3.zip

Also it looks like you are running “save and continue” by gravity forms. I have not tested this plugin with that, as it basically does the same thing. But people still wanted me to update this, is the only reason I have continued this plugin.

That is how it was suppose to work. But what that article explains (that i didn’t know at the time) was that transients are MAX time, there are other things (like cacheing plugins) that could wipe out the data before you expect it to. So I might have to create my own “transient” system.

I don’t remember why i added support for the query strings. Maybe in preparation for a priority system. I looked at adding support for the filter method you are using and its going to take a lot of rework to get it done. The $_POST seems to be short circuiting Gravity Forms to even going to that part of the code.

In your case it may be “incorrect”. I have thought about this before, about putting a priority system in place. The purpose of the plugin has always been to bring the user back to the same place they were when the left. Why you would want to change that I don’t understand. But I’ll look into it.

https://journal.rmccue.io/296/youre-using-transients-wrong/

Does this sound like something either of you have setup? Looks like transients might not be the way to go. :'(

https://www.ads-software.com/plugins/gravity-forms-data-persistence-add-on-reloaded/screenshots/

First image, 3rd setting “Clear persistence on submit”. On the newest version, it’s just above the “purge” button.

What setting are you referring to? All settings are per form and on the form settings page.