Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
has problem after upgrade to 3.3
See original GitHub issue <li ui-sref-active="active" permission permission-only="['EMPLOYER', 'EMPLOYER_STAFF']" class="ng-hide">
<a ui-sref="sakura.jobs"><i class="fa fa-cube fa-fw"></i> <span>xxx</span></a>
</li>
the code has no change, only automatic update from 3.2.1 to 3.3 with npm
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Problems after upgrading to OJS 3.3.0-6 - Software Support
I've upgraded an OJS 3.1.2-4 to 3.3.0-6. In the process I've searched through this forum as probably there was an unsuccessful upgrade ......
Read more >Common problems while upgrading to 3.3.0 - phpBB
Common problems while upgrading to 3.3.0 · Problem: Unsupported version of PHP · Problem: Incompatible extension · Problem: The installer detected ...
Read more >Unable to update from 3.3.1 to newer version #5677 - GitHub
I have tried with the latest version of Docker Desktop; I have tried disabling enabled experimental features; I have uploaded Diagnostics ...
Read more >After upgrade to 3.3 version, binding is not installing - Migration
Everything stopped working, all the devices are “Unintialized” and I figured out that I needed to reinstall the bindings. It shows that it...
Read more >tedevil - Foreman community
Upgrade from 3.2/4.4 to 3.3/4.5 fails with dependency problem ... Since the Foreman package is filtered out I assume this is not a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@brenolf Thanks for the hint. I was trying to find what was wrong with my code and started reading the documentation again not finding anything. I used to console.log to output the injected
PermissionStoreandRoleStoreservices and they worked in the sense they were injected. Interesting the services constructor functions are namedPermPermissionStoreandPermRoleStore.Whatever the case I appended
Permto the front of the services and it works.As I mentioned on #311, the problem seems to be related to a major change in 9f9fa18. I changed
PermissionStoretoPermPermissionStore- as found in the angular-permission’s codebase - and it started working again.This seems to be related to a misuse of Angular’s Services inside the library.