extensions issueshttps://develop.tadpole.cc/groups/extensions/-/issues2022-06-27T16:41:25Zhttps://develop.tadpole.cc/extensions/cc.tadpole.callnext/-/issues/1CND makes CiviCRM dashboard unusable for non-admins2022-06-27T16:41:25ZAndy BurnsCND makes CiviCRM dashboard unusable for non-adminsFor non-admins, the CiviCRM Dashboard has become unusable. I have tested the cause and it is due to the Call Next Dashlet. I tested dashboard without dashlets (works great) and with a similar activity report dashlet (works great) and it ...For non-admins, the CiviCRM Dashboard has become unusable. I have tested the cause and it is due to the Call Next Dashlet. I tested dashboard without dashlets (works great) and with a similar activity report dashlet (works great) and it loaded in 8s and did not freeze up the dashboard.
![activity_dashlet_test](/uploads/1d80f1077a946173840cba24ce3ab6e0/activity_dashlet_test.png)
But with CND it can take minutes to navigate to somewhere else in Civi if the user goes to CiviCRM dashboard first, which of course they do. Network error appears. It still freezes when the CND stops refreshing. The user session is stuck and it can be several minutes before it works again. The load / refresh takes forever. The county leader test I stopped counting at 100s.
Tested for state admin and county leader (to test any difference in ACL v related permissions methods)
**State Admin**
![CO_state_admin](/uploads/087192d60adcf311944ec513713bb79d/CO_state_admin.png)
**County Leader**
![pa_county_leader](/uploads/df46dc72b0c440cfe3bd3830c2609e1e/pa_county_leader.png)
For an administrator like myself, I can keep CND on dashboard (even though it's not a dashlet I need to use) and it loads in 15s with 1304 records in queue.
Process list has long sleep commands
![image](/uploads/32fc441002d5f79a1633396e51b043e2/image.png)
I had thought our performance tuning had helped with this with my testing on staging2. I guess first thing is we are sure we did not miss any performance.
Do we want to run PHP profiler on it? Get the slow query log? What are the next steps to address this?2020-09-25https://develop.tadpole.cc/extensions/cc.tadpole.logcallblock/-/issues/7Default Call Log to be open2019-08-21T15:36:16ZDana SkallmanDefault Call Log to be openThe call log block should be open right upon landing on contact summary screen.The call log block should be open right upon landing on contact summary screen.Christian WachChristian Wachhttps://develop.tadpole.cc/extensions/cc.tadpole.logcallblock/-/issues/6Set maximum character limit2019-04-03T09:05:40ZAndy BurnsSet maximum character limitFor the subject and details fields, a max character limit should be in place, unless Civi has one already? We want to prevent a bad actor from injecting 'novels' into the db. I am not sure what the exact character limit should be. I'll t...For the subject and details fields, a max character limit should be in place, unless Civi has one already? We want to prevent a bad actor from injecting 'novels' into the db. I am not sure what the exact character limit should be. I'll think about and maybe you have a suggestion.Christian WachChristian Wachhttps://develop.tadpole.cc/extensions/cc.tadpole.logcallblock/-/issues/5Require subject line field2019-04-02T13:23:46ZAndy BurnsRequire subject line fieldShould require the subject lineShould require the subject lineChristian WachChristian Wachhttps://develop.tadpole.cc/extensions/cc.tadpole.logcallblock/-/issues/4User flow from call next dashlet to call log block2019-08-21T15:35:54ZAndy BurnsUser flow from call next dashlet to call log blockThe call log block subject should populate with the subject that was created when they were put into the queue. It should be open right upon landing on contact summary screen. Is there a way to pass a parameter e.g.'&calllogopen' to the ...The call log block subject should populate with the subject that was created when they were put into the queue. It should be open right upon landing on contact summary screen. Is there a way to pass a parameter e.g.'&calllogopen' to the URL to do this only in this circumstance?https://develop.tadpole.cc/extensions/cc.tadpole.logcallblock/-/issues/3Add help text to call log notes2019-04-02T13:24:06ZDana SkallmanAdd help text to call log notes> call details box, have help text, 'type call notes here'> call details box, have help text, 'type call notes here'Christian WachChristian Wachhttps://develop.tadpole.cc/extensions/cc.tadpole.logcallblock/-/issues/2Remove CKeditor from call log details2019-04-02T13:24:46ZDana SkallmanRemove CKeditor from call log details> Ckeditor is not needed. It wasn't in the mockups. It actually is a problem in general as there is no reason for markup. It also allows access to our image files in Civi and ability upload. Just a can of worms. A simple text box instead...> Ckeditor is not needed. It wasn't in the mockups. It actually is a problem in general as there is no reason for markup. It also allows access to our image files in Civi and ability upload. Just a can of worms. A simple text box instead is better.
Should just be notes text area.Dana SkallmanDana Skallmanhttps://develop.tadpole.cc/extensions/cc.tadpole.logcallblock/-/issues/1Add Engagement Index with CiviCampaign enabled2019-04-02T13:25:03ZDana SkallmanAdd Engagement Index with CiviCampaign enabled> Engagement index should be added (key to know the overall temperature' of the contact).
Adding screenshot for reference on where it appears when adding an Activity in CiviCRM once CiviCampaign is enabled.
![cc-ei-select](/uploads/0f...> Engagement index should be added (key to know the overall temperature' of the contact).
Adding screenshot for reference on where it appears when adding an Activity in CiviCRM once CiviCampaign is enabled.
![cc-ei-select](/uploads/0fe98007f30b8ded8798f0ae986bad81/cc-ei-select.png)
Maybe good to add field to add before Completed selection on call log dashlet, thoughts?Dana SkallmanDana Skallman