-
-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRM-20424 remove call to deprecated function. #10259
Conversation
74ab4ef
to
bf94d03
Compare
@eileenmcnaughton This PR gets rid of the warning on most Civi pages. :-) Which link does this code provide?
Which suggests the activity type may not be needed anyway! |
It seems to provide reset=1&action=add&atype={$activityType}&context=standalone which is none of those! |
hmm maybe it is - the activity type is 'Open Case' - does that co-incide with atype=13? Required params |
This is the one covering the UI with errors. The fact it did not cause any test fails means it is not covered by unit tests :-(. As long as the Open Case link is still present for CiviCase users this is working
bf94d03
to
972a604
Compare
& it was wrong! just fixed it - but also fixed one more that filters out 'Closed' cases when looking at 'upcoming' cases on the case dashboard |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks fine to me
This is the one covering the UI with errors. The fact it did not cause any test fails means it is
not covered by unit tests :-(.
As long as the Open Case link is still present for CiviCase users this is working
@davejenx might be worth merging this into the rc? Will clean up the most common source of red ink