[MGNLUI-2861] Make CreateItemAction ContentConnector-aware Created: 05/May/14 Updated: 22/May/14 Resolved: 05/May/14 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | content app |
| Affects Version/s: | 5.3 |
| Fix Version/s: | 5.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | jcr-agnostic | ||
| 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
|
||||||||
| Epic Link: | JCR-agnostic content apps migration | ||||||||
| Sprint: | 5.3 Sprint 4, 5.3 Sprint 5, 5.3 Sprint 6 | ||||||||
| Description |
|
CreateItemAction hasn't been liberated from JCR just yet, so it is not aware of ContentConnector and therefore appends a JCR absolute path to the DetailLocation. This was causing troubles to the data module where rootPath of both browser and detail subApps is not the absolute root of the 'data' workspace (e.g. /companies, see cloned issue). Using ContentConnector#getItemUrlFragment should account for that just fine. |