AI OnAI Off
_ContentMixin.getCurrentContext() returns incorrect context on ContentArea->Create a new Block
Already done, but they need a working code sample based on their alloy sample so I have to write such an example to get any further.... Frustrating....
Apr 23, 2018 16:48
Problem can be reproduced by the AlloyDemoKit fork at
https://github.com/meriworks/AlloyDemoKit/commit/29dbb082750562240136e2edb931bf7d5c24cbb8
Edited,
Apr 24, 2018 16:53
<p>Solved the issue with help from episerver support.</p>
<p>The solution was to add information to the metadata for the editor.</p>
<p>See commit below</p>
<p>https://github.com/meriworks/AlloyDemoKit/commit/e1d8e35b906e70680a95bd25f5b50ed3f90de80c</p>
#193697
Jun 04, 2018 8:50
I have a custom component on a block that uses the _ContextMixin as described in the following link
https://world.episerver.com/documentation/developer-guides/CMS/user-interface/Context-sensitive-components/
If I create a new block the context describes the block where the property exists as expected.
If I, on the other hand, have a page with a ContentArea and clicks the "Create a new block" link on that content area, the context returned is not the block context but the page context where the ContentArea is located.