[MAGNOLIA-2375] Impossible to correctly determine system level access in cases where HM is not set. Created: 18/Sep/08 Updated: 22/Dec/08 Resolved: 19/Sep/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 4.0 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Jan Haderka | Assignee: | Teresa Miyar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
With the latest changes to DefaultContent, it is not possible to determine when system level access should be granted, the same way as it was before. This needs to be reviewed. |
| Comments |
| Comment by Jan Haderka [ 18/Sep/08 ] |
|
Just committed fix for the issue, but it needs to be reviewed and we need some more robust way of determining when system level access should be granted. |
| Comment by Teresa Miyar [ 18/Sep/08 ] |
|
Its fixed now, the access level must never be null, error was in ContentVersion , you could close this issue. |