Quantcast
Viewing all articles
Browse latest Browse all 9076

Unable to create new blocks after upgrade to CMS 11.18, tried another upgrade to 11.19.1 still same issue

Hi there,

Has anyone come across this weird issue which I am facing since upgrade to Episerver cms version 11.18. The issue is that when I try to create a new block in content area or under global blocks folder, I'm unable to create it. The weird part is on integration environment I am able to see the block in the list on clicking add new block button(in global and content area both) but gives below error when I click on create button.

However on preproduction I don't even see the block in anywhere in the list (neither on global blocks folder nor on trying under content area with where it's added to the allowed types list). Stranger is that it did appear once in the list on initial code deployment and web service restart on preprod too. However, it stopped showing after I tried creating it, when it gave me same error as below I got on integration. On cancelling and retrying on some other page content area or under global folder it stopped appearing in the blocks type list :(

P.S.- I also tried upgrading to 11.19.1 still same error when creating any new blocks. I have already used the workaround to insert or delete from tblContentTypeToContentType which only fixes this issue temporarily and have to do it for every new block type hence can't be the solution.

Error -  "EPiServer.Global : Unhandled exception in ASP.NET
EPiServer.Core.EPiServerException: Content type "MyBlock" is not allowed to be created under parent of content type "SysContentAssetFolder""

There also a similar dojo javascript in console - _317 {message: "Unable to load /EPiServer/cms/Stores/contentdata/ status: 500", response: {…}, status: 500, responseText: "<!DOCTYPE html> ↵<html> ↵ <head> ↵ <titl…nStep step, Boolean& completedSynchronously) ↵-->", xhr: XMLHttpRequest, …}

Console Stack - "Error: Unable to load /EPiServer/cms/Stores/contentdata/ status: 500 at new _317 (http://localhost:31337/EPiServer/Shell/11.19.1/ClientResources/dojo/dojo.js:15:78148) at _2f1._4f2 [as handleResponse] (http://localhost:31337/EPiServer/Shell/11.19.1/ClientResources/dojo/dojo.js:15:133806) at XMLHttpRequest._4fe (http://localhost:31337/EPiServer/Shell/11.19.1/ClientResources/dojo/dojo.js:15:134085)"

I don't think it is related but we have also recently installed ContentDeliveryApi, which I tried uninstalling to see if it fixes this issue but it did not. I then tried to downgrade it to previous version of 11.17.1 which fixed this but I want to know is this is a known issue with upgarded version of CMS or something wrong happened with our upgarde causing this issue?

Any help is appreciated, Thanks.


Viewing all articles
Browse latest Browse all 9076

Trending Articles