3

The developers fixed it in the master branch, if anyone comes across this: https://github.com/progressivetech/net.ourpowerbase.sumfields/issues/63


3

The developer updated the issue. There is a missing line in the code. They say they will release version 4.0.1 overnight. If you want to fix it yourself before that look at issue linked above in the comment.


3

It's hard to tell which version of the summary fields you are having issues with but I'm guessing it's 4.0.1 which was suppose to fix the exact same issue with 4.0.0. It obviously doesn't. I filed another issue on github for the newest problem. https://github.com/progressivetech/net.ourpowerbase.sumfields/issues/45 I think the fix is to change line 4 in ...


3

I'd like to build out more infrastructure for this. I've started an Extension Compatibility List which so far has the ability to blacklist an obsolete extension (my original use-case was for merging an extension into core), but it could be extended to blacklist a version of an extension with known bugs or security flaws.


2

When you go to Administer menu » Customize Data and Screens » Summary Fields, the last option is When should these changes be applied?. Your summary fields will be primed at the time selected. If you want to look at the code, the function is sumfields_gen_data.


2

There was a blog sometime ago by Dalin that had a fairly in depth recipe if you want to take a look and see if that helps you make some progress. There is no option to do this through the UI - though it comes up reasonably often.


2

As @coleman says and as I also mentioned in my comment above, you can create an extension as explained here or you can use an existing one and implement hook_civicrm_contact_get_displayname, somthing like this: function myextension_civicrm_contact_get_displayname(&$display_name, $contactId, $objContact) { $formal_title = civicrm_api3('Contact', '...


2

I had a similar experience when I cleaned out and reverted to a slightly earlier CiviCRM DB because we had made a goof (no need to elaborate on that). When I imported the desired backup, I had neither ANY triggers nor the MySQL routine civicrm_strip_non_numeric. We are running Wordpress 4.7.3 and Civi 4.7.16. I was able to recreate both the routine and the ...


2

As KarinG pointed out, best way is probably to raise the issue in GitHub: https://github.com/progressivetech/net.ourpowerbase.sumfields In general, if someone created and shared an extension it does not automatically mean they will fix all bugs you report. It might mean they come back to you and ask if you would fund the fix. Just to manage your expectations ...


2

Sadly the fix in 4.0.1 didn't fix the issue. See Navigation Menu Lost for more details.


1

Summary fields creates a collection of custom fields that it populates. It populates them when you first set the extension up, and then it also updates them as new contributions are stored. I suspect that it doesn't recalculate all the fields when you update your fiscal year, you probably need to ask it explicitly to do that, eg. by resaving the ...


1

Sorry for the slow response - I am just now seeing this question. The status should be: "Setting changes were saved on 2020-05-04, data calculation will be performed on every cron run." I'm not sure why that confusing message is displayed instead. Do you have the summary fields cron job enabled? If not, that could be the problem. When the summary ...


1

They developer released 4.0.2 which should fix the issue. Sounds like they may have an issue with their test env.


1

I ended up just changing the version number in the info file to 3.1.0. Then on the Manage Extensions page it then said there was an upgrade. Hit upgrade and everything was good.


1

Have you seen the summary fields extension? I don't think it does exactly what you need out of the box but you can define additional fields using your own criteria with a little coding.


1

The Github repo for this extension lives here: https://github.com/progressivetech/net.ourpowerbase.sumfields [and has an Issues tab]


1

If you have two transactions entered that are exactly the same and both pending, but one is cancelled, it may have created a conflict in the system. Try deleting the cancelled transaction and see if that helps.


1

We ended up disabling the extension via phpmyadmin, which enabled the "uninstall" link in the UI. Un-installation went fine, and we did a fresh install and now everything appears to be working fine.


1

Like Jon G suggested a little more information would help a lot, I am now assuming I understand what you mean but I do not really :-) Obviously it is possible to place the address on the activity form (I am assuming you mean the form of the activity when you click 'edit'/'view'? But you can not do this from the UI, you will need to do some customization. ...


1

Pretty sure this is now available either in Summary Fields itself or via https://civicrm.org/extensions/joinerys-more-summary-fields


1

I use Summary Fields on several 4.6 sites with no issues. Also - "Jamie" who left the comment is the author of Summary Fields, I'd follow their suggestion!


Only top voted, non community-wiki answers of a minimum length are eligible