This repository was archived by the owner on May 3, 2022. It is now read-only.
[WIP] EZP-25137: As an editor, I want to be able to create and embed a Content "on the fly" in the RichText editor#674
Open
dpobel wants to merge 11 commits intofeature/content-from-dashboardfrom
Open
Conversation
4e1bff1 to
d47a16d
Compare
Contributor
|
I'll use 9586054 on the PR about https://jira.ez.no/browse/EZP-26315 ( not open yet I'll updtate the link when open) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JIRA: https://jira.ez.no/browse/EZP-25137
Requires: ezsystems/ez-js-rest-client#78
Status: on hold
Description
This should provide a way for the user to create a Content item while using the UDW (so when filling a Relation(s) field, adding an embed element in the RichText editor, ...)
Feature status
This is kind of working but at the moment, it's not possible to choose the parent Location of the future Content item. There are also plenty of positioning bugs.
Remaining tasks:
contentCreatedhandler in the event parameter of the event trigger to run the Content Creator side view