Archive Custom Field Data

[Bruce - PhosphorMedia]

Because some of us are neat tidy (at least when coding--ok, I mean OCDish) can we get a feature to 'archive' custom field data no longer used but may not want to loose the data for historical purposes. Perhaps a simple "Display" checkbox which would, if unchecked, not display the custom field on the Product/Category template page. I suppose one could simply use a "group" to stuff them into, but that would still leave them listed everywhere else such as in the Custom Fields listing for the Product Display template as an example.

[lesliekirk]

I'd like to second this for reasons slightly different. Over the past month, I have had something very wonky going on with a site. It looks like data has reverted itself to an older version - if these fields have some sort of "dating" method it might have helped me figure out what's going on or if someone might have been tampering with the data.

[Bruce - PhosphorMedia]

We've experiance 'inadvertent data revision' as well. According to Miva support, it was an issue with caching directives in the htaccess file which they say is no longer needed as its done on the server site...or should be implemented that way.

Another potential cause is browser caching especially in Chrome. Even with no-cache plugins, or having inspector open, we still see this on a daily basis (at least on the front side of the site). Its gotten so bad I've actually switched to Firefox for dev work :) ...was also suggested to use Brave (Chrome based without the evil).

[lesliekirk]

We've experiance 'inadvertent data revision' as well. According to Miva support, it was an issue with caching directives in the htaccess file which they say is no longer needed as its done on the server site...or should be implemented that way.

Another potential cause is browser caching especially in Chrome. Even with no-cache plugins, or having inspector open, we still see this on a daily basis (at least on the front side of the site). Its gotten so bad I've actually switched to Firefox for dev work :) ...was also suggested to use Brave (Chrome based without the evil).

I seem to have issues with Firefox and then there is that Redis Caching module that I hate...