Comment 29 for bug 1858448

Thanks, Jason.

Two new branches pushed including my sign-off on the final commit. One for 3.5/master and one for 3.4 (which had a minor seed data merge conflict).

user/berick/lp1858448-aged-money-add-fields-and-settings-1

user/berick/lp1858448-aged-money-add-fields-and-settings-1-3.4

===

The commits from these branches cause the money aging functionality to be disabled, pending administrative action -- applying settings and potentially running an external script. So going forward, the feature will only be active if configured.

For the existing SQL upgrade scripts which contain the original changes, how about we just comment out the few lines of SQL code that perform the auto money aging instead of, say, back porting all of the changes? That will be less disruptive and fixes the core problem of data loss.