I'm having the same problem. Though only with one of my two Umbraco sites.
I upgraded them using the Nuget Package manager in VS2019 from 8.11 to 8.12.
I too have deleted the Bin, obj, and client Dependency directories but still had the same issue.
I just had this exact issue today. Upgrading from 8.12 > 8.12.2 via nuget in Jetbrains Rider.
Oybek's suggestion solved my issue. Downloading zip and moving the Umbraco-folder into solution got everything up and running.
Looking at the diff comparing the repo post upgrade to after copying the /umbraco-folder from the downloaded zip, I can see there's a lot of changed files. So I'm assuming this has something to do with the upgrade, either malfunctioning in my enviroment or a general issue with the upgrade script.
Isn't the fact that this is erroring out a symptom of not having the correct files? Just removing that one line of code probably removes the error, but what other files are wrong when compared to what they should be?
100% - you should restore the entire /umbraco folder ideally. A nuget reinstall or overwrite from the zip is the way to go. But it sounded like you were having difficulties with this.
We recently encountered this same error on our local development version after running the upgrade -- our fix was to delete the /umbraco folder entirely, and restore it from nuget.
(in theory you could probably also restore the /umbraco folder from a downloaded zip of the appropriate version of umbraco)
If someone encounters this issue again, it would be really cool if you could take a copy of your Umbraco folder before doing as as Chris suggests above. If the issue is resolved then a diff on the folders might identify the cause.
I have also just encountered this. Chris' solution (deleting /umbraco and letting nuget restore it when rebuilding in VS) - fixed it.
I had pulled an updated packages.config from someone else doing the upgrade, this is what caused the problem.
As David suggested I took a backup of my /Umbraco folder before I deleted it and yes, I can see a lot of differences, including the code in /umbraco/views/default.cshtml that was causing the error.
So clearly pulling and updating my working version with the updated packages.config isn't enough to get the changes to the umbraco folder replicated. I had to delete the folder and force VS to restore.
With this line in place a nuget restore will add all missing files to the folder.
Does it overwrite changed files on a restore? If so then that does sound like the way to go.
I had intended to just use git commit messages better. If the commit is prefixed with 'UPGRADE' (or tagged possibly) then a user should reinstall the UmbracoCMS package.
Upgraded to 8.12.1 now get 'Umbraco.Web.Editors.BackOfficeModel' does not contain a definition for 'IconCheckData'
Happens when I try go to the cms.
I've cleared my app_data and dlls and rebuilt my solution. :(
Hello Tim,
Try to clear bin folder except the Roslyn Folder and rebuild the project
Hi,
I've tried that but no joy :(
Hi,
How did you perform the upgrade, through visual studio using nuget. Or manually using the downloadable zip file ?
Dave
I'm having the same problem. Though only with one of my two Umbraco sites. I upgraded them using the Nuget Package manager in VS2019 from 8.11 to 8.12.
I too have deleted the Bin, obj, and client Dependency directories but still had the same issue.
Same here. Are you'll using Unattended Upgrades? I wondered if that was related.
I had the same issue here, after upgrading umbraco i can't access admin.
I tried to clear bin folder and client dependency folders no luck
after i followed tips from here fix
download latest Umbraco in a zip format, copy /umbraco folder from the zip and replace it on your project /umbraco directory
go to Config/ClientDependency.config and change clientDependency version
We found that deleting everything and restoring from git resolved it. Seems like a file issue rather than a database one.
I just had this exact issue today. Upgrading from 8.12 > 8.12.2 via nuget in Jetbrains Rider.
Oybek's suggestion solved my issue. Downloading zip and moving the Umbraco-folder into solution got everything up and running.
Looking at the diff comparing the repo post upgrade to after copying the /umbraco-folder from the downloaded zip, I can see there's a lot of changed files. So I'm assuming this has something to do with the upgrade, either malfunctioning in my enviroment or a general issue with the upgrade script.
Hi
I also got same issue when i upgrade, i downgrade it to 8.12.0 and then upgrade to latest again fixed my problem
Thanks
Had the same issue going directly to 8.11.2 from 8.10.1. I can confirm that upgrading to 8.12.0, then 8.11.2 afterwards via Nuget fixes this.
Have you attempted both the Nuget method and downloading the release zip and copying over the folders?
You can literally delete the
iconHelpercode in the Default.cshtml (see path in YSOD) if you want. It's not supposed to be there in 8.12.2Isn't the fact that this is erroring out a symptom of not having the correct files? Just removing that one line of code probably removes the error, but what other files are wrong when compared to what they should be?
100% - you should restore the entire
/umbracofolder ideally. A nuget reinstall or overwrite from the zip is the way to go. But it sounded like you were having difficulties with this.We recently encountered this same error on our local development version after running the upgrade -- our fix was to delete the /umbraco folder entirely, and restore it from nuget.
(in theory you could probably also restore the /umbraco folder from a downloaded zip of the appropriate version of umbraco)
If someone encounters this issue again, it would be really cool if you could take a copy of your Umbraco folder before doing as as Chris suggests above. If the issue is resolved then a diff on the folders might identify the cause.
I have also just encountered this. Chris' solution (deleting /umbraco and letting nuget restore it when rebuilding in VS) - fixed it.
I had pulled an updated packages.config from someone else doing the upgrade, this is what caused the problem.
As David suggested I took a backup of my /Umbraco folder before I deleted it and yes, I can see a lot of differences, including the code in /umbraco/views/default.cshtml that was causing the error.
So clearly pulling and updating my working version with the updated packages.config isn't enough to get the changes to the umbraco folder replicated. I had to delete the folder and force VS to restore.
I created an issue for this: https://github.com/umbraco/Umbraco-CMS/issues/10133
I wrote a blogpost a issue and some ways to prevent this from happening in the future :
https://dev.to/dawoe/nuget-restore-issues-after-umbraco-upgrade-3n9o
Would love to hear your thoughts.
Dave
Great stuff.
Does it overwrite changed files on a restore? If so then that does sound like the way to go.
I had intended to just use git commit messages better. If the commit is prefixed with 'UPGRADE' (or tagged possibly) then a user should reinstall the UmbracoCMS package.
High five Oybek! Worked and saved a lot of time.
is working on a reply...