The Summary Fields extension creates read-only custom data fields that extend Contact and are automatically populated with up-to-date totals such as total lifetime contributions, last contribution amount, last attended event, etc.
Other
8
stars
29
forks
source link
improve feedback to use on whether settings are updated or not #32
Now that we have the ability to update data via a cron job (instead of triggers), we have a
communications problem.
If the status is "scheduled" - it could mean that the settings are not saved. Or, it could mean that the settings are saved, but we are always in a scheduled status since we update on every cron job.
I think the proper solution is to use two different variables - one to keep track of whether the settings are saved and another to keep track of whether the data needs to be updated.
Also, would be helpful to include the fact that we are using the cron method for updating data up top, where we would list that all the sql triggers are not enabled.
Now that we have the ability to update data via a cron job (instead of triggers), we have a communications problem.
If the status is "scheduled" - it could mean that the settings are not saved. Or, it could mean that the settings are saved, but we are always in a scheduled status since we update on every cron job.
I think the proper solution is to use two different variables - one to keep track of whether the settings are saved and another to keep track of whether the data needs to be updated.
Also, would be helpful to include the fact that we are using the cron method for updating data up top, where we would list that all the sql triggers are not enabled.