[MAGNOLIA-6151] BootstrapUtil / DataTransporter creates hierarchy using mgnl:content which might not always be the correct nodeType Created: 31/Mar/15 Updated: 19/May/22 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.3.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Philip Mundt | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
When bootstrapping content, where (some) parent folders do not exist (hierarchy is determined from bootstrap filename), info.magnolia.importexport.BootstrapUtil will always use NodeTypes.Content.NAME as node type which might not always be the correct type and also lead to problems when activating content (when the resulting hierarchy is of mgnl:content > mgnl:contentNode > mgnl:content). This is especially a problem for repositories with custom node types such as dam, where folders will be create with the default node type mgnl:content but should rather be mgnl:folder. As a result those nodes/assets will not appear in the DAM App. |
| Comments |
| Comment by Roman Kovařík [ 19/May/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, |