![]() Again, the developer tools in your browser can come to the rescue, I have the most experience with Chrome so again, hit the F12 button and go to the resources tab to find and delete all cookies.Ĭheck your log files, in ~/App_Data/Logs/ - whenever there's any kind of error that we can log, it will be in here. We recently had a problem where an old cookie would throw a spanner in the works. It does what it says on the tin and requests all assets completely freshly and should load whatever is updated in Umbraco. You now have options! The best one of which is: Empty Cache and Hard Reload. So, for another hot tip in this post: if you use Chrome, hit the F12 button and the reload button next to the address bar is a little bit magical now. Chrome in particular is super aggressive in caching so it might not make a difference. This should clear client side cache for most browsers. Change the version number in that file (just make it 1 higher or lower) and try again. Umbraco uses a lot javascript/angular/html that changes for most releases. No? Okay then, try clearing your browser cache. ![]() Note: Yes, I know this is possible with WinMerge and other compare tools as well, but BeyondCompare is so much better than all of the others. Again, BeyondCompare only shows you the differences between the two folders so it should be easy to spot if anything is amiss. ![]() A special section to pay attention to is the runtime/assemblyBinding one that really needs the bindingRedirect versions to be correct.Īfter you've updated config files: try again, your site probably works just fine now.Įxtra tip: while you're comparing it's also a great moment to check that all the required files are in your bin folder, we ship with what's needed in the zip file so make sure that all the files on the left side are also on the right side and that the versions are the same. The first thing I usually check is the root web.config to make sure that everything that might be new in the Umbraco default web.config file is in the web.config file in my site. You'll get a nice overview of folders and some will disappear as they're the same on both sides, leaving you with just the differences. Right click the zip file and choose "Select left folder for compare", then find the folder where your Umbraco install lives, right click it and choose "Compare to UmbracoCms.x.y.z.zip". Right, with a beautiful BeyondCompare install in place, download the zip file corresponding to the Umbraco version you're trying to upgrade to. Finally, make sure to click the "Ignore unimportant differences" button, which hides unimportant whitespace differences. How? Aha! Here is the best tip I will give you in this blog post: download a copy of BeyondCompare and import these settings. Time to debug! Let's start with the 3 C's: configs, cache and cookies.Ĭheck that your config files in the ~/Config folder have been updated, and especially check if both your web.config files (the one in the root of your site and the on in the ~/Views folder) have been updated. NuGet can have a temperament where it "forgets" to do config transforms, runs into problems while doing the upgrade or "forgets" to copy certain files. ![]() Most people these days use NuGet for installing and upgrading Umbraco, that's also where most people have problems as it LOOKS like everything is done automatically for you, but sometimes it hasn't worked. I like to think of the Umbraco ZIP downloads as the "known good" state when you have "problem x" after upgrading and installing a clean Umbraco install does not have "problem x" then something most likely went wrong with your upgrade. With that out of the way: shit happens! So let's try to figure it out. Needless to say: you have your code checked into source control (or at the very least backed up before you upgrade) and you've made a full database backup before upgrading your site, right? We also document how to upgrade your site as comprehensively as possible, so make sure to read the documentation, loads of hints and tips that we keep up to date: We miss stuff sometimes though, and that sucks, in which case we either try to correct that quickly or at least document it. I'm not blaming the "victim" here, but just want to make you aware that we do all we can to make your upgrades succeed the first time. So when it doesn't work for you, it's most likely that something went wrong on your computer, not in our upgrader. We upgrade the solution we use for masterclasses, we upgrade Our Umbraco and when there's big changes we upgrade a bunch of other random sites too. First of all: we test upgrading for every Umbraco version we release.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |