Creating blocks in blocks not working with latest version
Vote:
Since some time after version 11.10.6 the following features stopped working:
Creating a new block under a newly created block
That is, "For this block" -> "New block"
Creating a new block in a ContentArea inside a block
That is, using the "create a new block" button at the bottom of the ContentArea
How to reproduce for local blocks:
Create two Alloy sites, one with version 11.10.6 and one with latest version (as of this writing 11.11.3)
Create a new editorial block on some page on both Alloy sites
Select the newly created block for editing
Go to "for this block" on the right hand pane
Click "New Block"
At this stage, the 11.10.6 version shows all available block types while the latest version shows an empty list.
How to reproduce for ContentAreas:
Add a ContentArea to the EditorialBlock on both sites
Select an Editorial Block for editing
Click "create a new block" on the ContentArea
At this stage, the 11.10.6 version shows all available block types while the latest version shows an empty list.
In both cases above, the CMS attempts to get all available content types using the following endpoint: /EPiServer/cms/Stores/contenttype/?query=getavailablecontenttypes
The 11.10.6 version includes the parameter &localAsset=true while the latest version does not. Calling the endpoint directly with the missing parameter returns the correct result in the latest version.
Is this a known bug? Is there a fix scheduled? Does anyone know of a workaround?
Since some time after version 11.10.6 the following features stopped working:
How to reproduce for local blocks:
At this stage, the 11.10.6 version shows all available block types while the latest version shows an empty list.
How to reproduce for ContentAreas:
At this stage, the 11.10.6 version shows all available block types while the latest version shows an empty list.
In both cases above, the CMS attempts to get all available content types using the following endpoint: /EPiServer/cms/Stores/contenttype/?query=getavailablecontenttypes
The 11.10.6 version includes the parameter &localAsset=true while the latest version does not. Calling the endpoint directly with the missing parameter returns the correct result in the latest version.
Is this a known bug? Is there a fix scheduled? Does anyone know of a workaround?