CiviCase Breaks (AngularLoader deprecated) with Civi Core 5.39

[pbarmak]

All, just fyi, when upgrading Civi Core to 5.39, the latest version of CiviCase (2.0.0,) completely breaks with the following error message (and nothing else on the Manage Cases screen):
User deprecated function: Deprecated function Civi\Angular\AngularLoader:load, use angularjs.loader service.

I'm guessing this maybe related to issue #752, but in case it isn't, I wanted to note it here as a new issue.

Also, the readme of this extension, under Technical Requirements, states "preferably the latest version" for CiviCRM. You might want to update that to a max version of 5.34 or whatever version is completely working. I know several orgs that want to use this extension with it's excellent design, but they may not know the fact that it's not in sync with Civi Core's changes.

[james-compucorp]

Edited - please see updated response below

[pbarmak]

@james-compucorp, apologies for my ignorance, but just a quick question. For those of us who rely on this extension, what happens when the core Civi team sends out a new Security Release like they did with 5.36.1? We've been trying to keep up with the latest Core releases because of the security issues they resolve. How do you all recommend we handle the reality that some key extensions are out of sync with Core?

I have the same question with other key extensions like Shoreditch (which, I believe, is not yet compatible with Drupal 8, or the companion theme isn't, I forget which). I'm trying to figure out how I should approach the fact that we use these great community extensions, but they are not all aligned with Core. Thanks for any feedback.

[james-compucorp]

@pbarmak

Apologies for the confusion here.

I’ve edited my replies to make this clearer as I agree there could be some confusion.

Points as follows:

• This extension is widely used by both our clients and others and we work very hard to maintain it.
• Due to some of the challenges keeping complex extensions in sync with CiviCRM versions we tie a particular release of the extension to a particular version of CiviCRM.
• We plan to release a new version of the extension with every CiviCRM security release as a minimum (although sometimes it can take a week or two to complete testing and get this released).
• As such thank you for pointing out that the readme is not correct. We will change this to show the stated version that this release should support. Currently this is version 5.35.x for Release v2.1.0.

With respect to Shoreditch a lot of the points above apply also in terms of alignment.

• Unfortunately most of Compucorp’s stack is tied to Drupal 7 and hence we haven't been in a huge rush to migrate, especially given that CiviCRM's support for D8/9 is still somewhat experimental and Backdrop support is already stable, so we would welcome support / funding to work towards Drupal 8/9/(10!) support for all of the above.

Do let me know if you have any further questions.

cc @deb1990

[niels-heinemann]

Dear Authors, we have the same problem, I installed everything until I realized that it won't work with our fresh Civi 5.42.

But we do patch civicrm after every update anyway. So couldn't you publish the patches you apply? Maybe we can make them usable in newer Civi versions ourselves.

[allinappliadmin]

Same problem here on different recent flavors of CiviCRM. Right now on 5.54 the activity tab is completely broken and puts the instance down. Even my computer crashed because of the tow many angular errors. see this behavior for example: https://www.loom.com/share/e64939e649d446578144fd79e3a2c826

[allinappliadmin]

still facing this issue on CiviCRM 5.61.4. How could we help fixing this feature?