[MAGNOLIA-323] Make AccessManager accessible or create methods to create Content with custom nodetype Created: 23/Mar/05 Updated: 23/Mar/05 Resolved: 23/Mar/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 2.1 Final |
| Type: | Task | Priority: | Minor |
| Reporter: | Thomas Bach | Assignee: | Sameer Charles |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
snippet from the userlist: hmm yes its missing, ll add this to current svn trunk. > There are constructor methods from the Content-Class that allow us to use our custom nodetypes, but the last argument AccessManager is created once you log in and yes its only accessible from the session. AccessManager is only used if you retrieve hierarchy manager could you please add this to JIRA? thanks
|
| Comments |