search

progressivetech / net.ourpowerbase.sumfields

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

fields not updating, log shows past date #5

Open Stoob opened 8 years ago

Stoob commented 8 years ago

Note the attached log.

Fields haven't updated for us in over a month. We recently updated to 2.0.5 and use CiviCRM 4.6.11 on Wordpress. The attached log file shows a 'success' 2016-01-12, yet a date of 2015-11-30 in the output of the log file. Is that a clue?

I've triggered the job manually, no change. There is nothing in CiviCRM.log related to the extension. I've also cleared CiviCRM's cache: admin/setting/updateConfigBackend

Any other thoughts? Thanks!

last_run_log.txt

Stoob commented 8 years ago

contribs extensions last-con

jmcclelland commented 8 years ago

Hi Stoob,

Running the cron job manually won't help in a situation like this. The only purpose of the cron job is to check if you have requested the data to be regenerated on the next cron job. If you haven't made this request, then the cron job doesn't re-generate the data.

If everything is running correctly, you only regenerate the data the first time you install the extension or if you make a change to the way the extension is configured. Otherwise, the data should be properly populated by SQL triggers.

Unfortunately, the SQL triggers are not quite as reliable as I'd like them to be. And it seems that sometimes they don't get properly setup when CiviCRM regenerates all triggers.

So, I would suggest that you start by going to the Summary Fields configuration page (Administer -> Customize Data and Screens -> Summary Fields.

At the top of the page you should see the extension status, which should tell you which triggers are properly enabled. If the contribution table triggers are not enabled, that is probably the problem. Even if they are enabled, you may try applying the changes by clicking save at the bottom which will trigger a re-generation of the data.

I have experienced this problem and find that on some sites I have to periodically re-generate the data. There is some code to help you identify this problem (see sumfields_test_inconsistent_summaries() in sumfields.php). I typically invoke it via drush - but I think there are comparable wp-cli methods you could use.

Stoob commented 8 years ago

Thanks, I just went to the extension settings page, changed nothing, and clicked Save, for 'next cron run'

This is what I saw:

Status of current settings: Setting changes were successfully applied on 2015-11-30 12:01:18. Contribution Table Triggers: Enabled Participant Table Triggers: Enabled

After the 'cron run' it was this.

Status of current settings: Setting changes were successfully applied on 2016-01-13 11:01:10. Contribution Table Triggers: Enabled Participant Table Triggers: Enabled

And the contributions are apparently updated. Thanks for the tip! I have no idea why it "got stuck" in the first place but if there is debugging I can do please let me know what it is. I never saw anything in the error logs or indications of problems.