-
Notifications
You must be signed in to change notification settings - Fork 16
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
Angular error breaks activity tab page #879
Comments
I did a bit of digging on this issue, and it seems to be specific to WordPress. I tested on CiviCRM 5.55 with Drupal7, both the original Compucorp version and our fork, and that worked fine. One potential lead: if we patch
then the problem seems to go away.
|
it seems that it solved on WP (exact path is |
A very weird discovery (without the
And everything works fine ... edit: except the activities tab. Other random findings: loading the Membership tab initializes CiviCase because of this, I think: |
:-| strange indeed |
same issue and fix on 5.56beta1 |
@allinappliadmin It's unlikely to be fixed by core. I had to stop debugging because I was turning in circles. For now we are applying the TabHeader.js fix on our builds. |
With the patch, i am not able to open the activity from the list of activities. @mlutfy |
An interesting workaround is a search kit / form on activities, as a tab in the contact summary. It is possible to expose filters and I think it could be a very good option. |
We ran the fork from @bgm for WP on different recent versions of CiviCRM (now on 5.54) with the necessary plugins and configuration and trying to access the activity tab breaks the tab and blocks the instance.
https://www.loom.com/share/e64939e649d446578144fd79e3a2c826
We've already spent hours trying to debug: deactivate all extensions, activate them one by one, change php version, upgrade and downgrade versions of CiviCRM, update extension, ask @bgm to investigate, migrate to a new website... It crashes the instance, blocks the browser and even froze the computer.
All errors are related to angular.js file:
and especially this line: return Function.prototype.apply.call(logFn, console, args);
I can provide credentials to see the issue live.
I read that the extension is supposed to work only with 5.39 but on versions such as the 5.49 it was working.
Have you noticed such an issue
The text was updated successfully, but these errors were encountered: