[CONTEDIT-48] Custom node types in content editor Created: 09/Mar/17 Updated: 04/Apr/23 Resolved: 04/Apr/23 |
|
| Status: | Closed |
| Project: | Content Editor |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Mariusz Chruscielewski | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 1 |
| Labels: | to-verify | ||
| 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)
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Content editor next | ||||||||
| Story Points: | 3 | ||||||||
| Team: | |||||||||
| Description |
|
Currently it's not possible to use any other "root" node type than mgnl:composition, that should be possible in my opinion, let's say that node has to extend mgnl:composition or something like that. |
| Comments |
| Comment by Simon Lutz [ 12/Oct/17 ] |
|
Regarding the first paragraph, node types are listed here: Regarding the second paragraph, the content editor provides three actions: "Close", "Save" and "Save and Publish" so an action to publish directly from the editor is already there. YAML example showing action definitions can be found here: |
| Comment by Mariusz Chruscielewski [ 13/Oct/17 ] |
|
HI Simon, I was thinking about real custom node type, like: I build articlesApp, I make: mgnl:article node type, for audioApp i have mgnl:audio, etc. Just like we have now for standard apps. |
| Comment by Christopher Zimmermann [ 16/Oct/17 ] |
|
I've just confirmed that it is possible to create custom actions in the stories app editor. Therefore I will edit the description and summary. |
| Comment by Christopher Zimmermann [ 16/Oct/17 ] |
|
Agreed that it should be possible to use custom nodetypes as mentioned in Mariusz comment above, adding to backlog. |
| Comment by Antti Hietala [ 27/Oct/17 ] |
|
The second part of the request should already be available. The Stories app has "Close", "Save" and "Save and publish" actions.
|
| Comment by Mariusz Chruscielewski [ 21/Nov/17 ] |
|
Hi Christopher. you wrote: Agreed that it should be possible to use custom nodetypes as mentioned in Mariusz comment above, adding to backlog. What is issue number? would it be part of this issue? Is that maybe fixed already? |
| Comment by Christopher Zimmermann [ 21/Nov/17 ] |
|
Hey there - it is this ticket. To my knowledge the issue has not been resolved. It is on the backlog, but if you have an urgent need I recommend creating a support ticket. |
| Comment by Bhupesh Belchandan [ 23/Jan/20 ] |
|
Is there any update on use of custom node-type in content-editor? This would be really helpful to have this flexibility, to convert existing standard content app to content-editor app. However, it doesn't seems to work with Magnolia6.1 and content-editor-module1.3.3, which is quite odd. Any update on this would be greatly appreciated.
|
| Comment by Laura Delnevo [ 02/Jun/21 ] |
|
Good afternoon, bbelchandan the recent 6.2.9 release comes with Content Editor v2.0 which has been fully migrated to the Magnolia 6 UI framework. You can now switch to the migrated 6 UI module. More details in our latest release notes, here. Nevertheless, please note that this specific improvement ticket has not yet been tackled in the 2.0 version. |
| Comment by Laura Delnevo [ 04/Apr/23 ] |
|
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, |