-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot link to another blocks anchors #796
Comments
I suggest to use getUniqueKey() to generate the anchor IDs. |
Nice one @mfendeksilverstripe 👍 will do. |
Hey @StephenMakrogianni how have you been getting on with a solution here? |
@brynwhyman haven't had a chance to get to it yet mate. Hack day is coming up though so might give it a nudge then |
The root problem here is that anchors inside an elemental block are not properly supported. This will be resolved with #186, so I'm closing this issue in favour of that one. |
Issue:
In the WYSIWYG editor, content authors cannot link to another blocks anchors.
Proposed solution
Create a hook or move existing hook on
SiteTree::getAnchorsOnPage()
and update the list with the selected page's anchors categorized by the Elemental block they are in.Change how the list is displayed to something similar to the tree drop down field where the content author could select the Elemental block to anchor to or one of it's "children" (anchors in the WYSIWYG).
Note:
I have started working on the solution and am taking the following into consideration:
EementalArea
on a single pageHTMLText
fields on an ElementAnything else put it in a comment.
Related
#894
PRs
The text was updated successfully, but these errors were encountered: