I am starting out my journey into EpiServer and trying to spin up the AlloyDemo application. I am playing around with Users and associated permissions (more specifically Publishing a page). I ran into an issue where the Publish "popup" is not showing up. When I see the console I get the following error. This error goes away and the Publish popup comes up correctly when I uninstall the EPiServer.Marketing.Testing (I am not sure about the dependency between the Marketing.Testing and popups)
Uncaught TypeError: Cannot read property 'contentData' of nullat Object._isOpenSetter (widgets.js:2)at Object.set (epi.js:2)at Object.onOpen (widgets.js:2)at Object.open (widgets.js:2)at Object.advice (dojo.js:15)at Object._264 [as open] (dojo.js:15)at Object.openDropDown (widgets.js:2)at Object.<anonymous> (widgets.js:2)at dojo.js:15at Object.loadAndOpenDropDown (widgets.js:2)
Would really appreciate any pointers.
I just started getting this myself today. I don't think it has to do with the Episerver.Marketing.Testing as much as it has something to do with the new version EPiServer.CMS.UI. I went back down the 11.13.2 on EPiServer.CMS.UI & dependencies, and it worked for me. I then grabbed the new version of this (11.14.0) and I got the same error.
Try taking EPiServer.CMS.UI back and see if it works for you. In the meantime, I'll report this as a bug.
Could you detail the reproduction steps? I am running a 11.14.0 site without issue.
I've just tried updating to EPiServer.CMS.UI 11.14.0 and also EPiServer.Forms 4.22.0 and we're seeing the same issue.
Can you enable debug scripts by adding the <clientResources debug="true" /> to the episerver.framework section of the web.config. This will produce a more traceable strack trace. Also reproduction steps would help a lot.
Here's the stack trace:
TypeError: Cannot read property 'contentData' of null
at Object._isOpenSetter (http://localhost:49945/EPiServer/CMS/11.14.0/ClientResources/epi-cms/contentediting/viewmodel/PublishMenuViewModel.js:164:50)
at Object.set (http://localhost:49945/EPiServer/Shell/11.14.0/ClientResources/epi/epi.js:4088:33)
at Object.onOpen (http://localhost:49945/EPiServer/CMS/11.14.0/ClientResources/epi-cms/contentediting/PublishMenu.js:252:24)
at Object.open (http://localhost:49945/EPiServer/Shell/11.14.0/ClientResources/dijit/popup.js:272:12)
at Object.advice (http://localhost:49945/EPiServer/Shell/11.14.0/ClientResources/dojo/dojo.js:6158:45)
at Object.dispatcher [as open] (http://localhost:49945/EPiServer/Shell/11.14.0/ClientResources/dojo/dojo.js:6139:57)
at Object.openDropDown (http://localhost:49945/EPiServer/Shell/11.14.0/ClientResources/dijit/_HasDropDown.js:474:23)
at Object.<anonymous> (http://localhost:49945/EPiServer/Shell/11.14.0/ClientResources/dijit/_HasDropDown.js:353:11)
at Object.loadAndOpenDropDown (http://localhost:49945/EPiServer/Shell/11.14.0/ClientResources/dijit/_HasDropDown.js:359:5)
for reproducable steps, just make any change to any block and the error is thrown.
Hopefully that's helpful a little bit
EDIT: And this is a pastebin dump of the log file Chrome spits out.
Thanks, for the update. We are looking into the issue, you can track the bug here: https://world.episerver.com/support/Bug-list/bug/CMS-12825
A workaround is to go back to version: https://nuget.episerver.com/package?id=EPiServer.CMS.UI&v=11.13.2
Upgraded to latest and we are seeing the same issue.
@Ben: Is it a way to disable AB testing on the site (like this app setting for projects episerver:ui:IsProjectModeEnabled = false)? Then we do not have to downgrade or uninstall the Marketing nuget packages?
I'm not sure. I'm not very familiar with the add-on. Uninstalling is probably your best bet if you don't want to downgrade CMS UI while they fix the issue. I have submitted a PR with a fix to the team responsible for the add-on so it should hopefully be available next week.