I have a website which worked well under EPiServer 7.5.394. Now I have updated the core and its dependencies to the latest Nuget package (which is at the time of writing 7.8.2). I followed the upgrading instructions, everything works well... except that when I access the CMS Edit functionality, the page displays the top bar, but a blank page where it was supposed to be the edit pages functionality.
Is there anyone aware of a bug like this?
Hi Have you also installed EPiServer.CMS.UI & EPiServer.CMS.UI.Core having version 7.9.1 ?
Do you see CMS and Shell modules under siteroot\modules\_protected ?
Thanks for your answer @Shahid. Yes, I see CMS and Shell folders inside modules/_protected. CMS.UI and CMS.UI.Core are also installed. And both have version 7.9.1.
If you open the episerverframework.config file, do you have any VPP mappings that points to some faulty location for the CMS UI?
I also got this problem after I tried upgrading both the CMS and Commerce (which btw failed with this error: updating 'episerver.commerce 7.5.1002.0' to 'episerver.commerce 7.9.0' failed. unable to find a version of 'episerver.commercemanager' that is compatible with 'episerver.commerce 7.9.0'.)
When I try to view the site in edit mode it doesn't load the page as David says. From the dev console I can see that dojo is trying to load Catalogs.js (http://localhost/epiui/Shell/184.108.40.206/ClientResources/epi-ecf-ui/component/Catalogs.js) but it responds with 404.
@Magnus looking at the console, I see this error when I visit the blank CMS Edit page:
It seems like the installation for the UI packages failed for some reason. Did you see anything in the package manager console when you did the upgrade?
If you go to the "old" location for the package "[appdata]\Modules\.." (not under the site\modules\_protected) do you see any folders named CMS or Shell? If they are still there try to delete them.
When the CMS.UI package are installed using the nuget package manager we are trying to move two modules (CMS and Shell) and tries to delete EPiServer.Suite and CMS.Sources (if they are installed)
I'm quite interested to understand why it failed for you (especially if you did not see any errors in the log). Can you reproduce the problem? Did you have your old modules (app data) on a network share? Was the old modules folder checked in in e.g. TFS (read only)?
Or is there anything else that you can tell me about your setup.
@Magnus your solution worked wonders! There were the folders CMS and Shell under appdata/Modules, and once I removed them, the CMS Edit page worked! The current structure of my Modules folder is the following:
Is there anything else I should consider for removal?
I had a similar issue, except that I was deploying my site to a production environment after installing updates on dev. I was following the instructions given on 'Applying transforms to a production environment'. I published my site from Visual Studio and performed the database transforms resulting from running Export-EPiUpdates on the development machine. I then copied the contents of the publish folder and replaced what was in the site root on the server. I also had to delete EPiServer.Cms.Shell.UI.dll and EPiServer.Shell.UI.dll from modulesbin and bin\modulesbin, but that would have happened automatically if I'd actually replaced the contents of the site instead of just copying over what was there already.
However, the instructions do not mention the required changes to the AppData\Modules folder, which is not exported when I publish the site (should it be?). To get it working I simply deleted the Modules folder on production and replaced it with the folder on dev and after that it worked. Perhaps I should have figured that out for myself, but I'd recommend updating the article for others who follow the same route as me when updating the production environment.