We have moved to GitHub Issues
You are viewing the read-only archive of Umbraco's issue tracker. To create new issues, please head over to GitHub Issues.
Make sure to read the blog posts announcing the move for more information.
Created by Richard Thompson 27 Feb 2018, 15:47:43 Updated by Jacob Midtgaard-Olesen 23 Apr 2018, 13:54:05
Tags: Unscheduled RegressionI've updated a 7.8.1 site to 7.9 using Nuget. When I ran the site it takes me to the login screen to authorise the upgrade but there is no login form.
When I check the console in Chrome I see the following error:
Uncaught TypeError: Cannot read property 'cacheBuster' of null
This error comes from the DependencyHandler.axd.
I've tried clearing out /App_Data/TEMP/ClientDependency and bumping the client dependency version. I've also go the Chrome developer tools set to clear the cache and have hard refreshed.
Hmmm, try setting debug="true" in your web.config and see if that helps. I'll dive into the code later to see what is going on.
I had this too on Cloud today, causing a deploy to fail. Simply turning debug mode in Web.config on, reloading, then off again gives ClientDependency the kick it needs.
The problem is that we are now properly cache busting everything and clearing out the angular template cache (which we did before but now it's done in a more robust way). However, during upgrades, the 'cacheBuster' value is not available because we don't output this value when the app is in an upgrade state :(
I'll push a PR for this asap.
PR: https://github.com/umbraco/Umbraco-CMS/pull/2484
Previously (and I'm not entirely sure why), we didn't output the application
part of the Server Variables when in an upgrade mode, however we had specific checks in the BareMinimumServerVariables
(which are the ones output when running the upgrader) to ensure that application.cacheBuster
was in the result but since the application
part was null, this value wasn't output.
The fix is:
_applicationContext.IsConfigured
and output the application
state during upgradesIsConfigured
state - This means that the cache buster value will change before and after the upgrade which is what we wantTo test:
For what it's worth I can confirm that using debug="true" the login screen appears.
Priority: Major
Type: Bug
State: Fixed
Assignee:
Difficulty: Normal
Category:
Backwards Compatible: True
Fix Submitted:
Affected versions: 7.9.0
Due in version: 7.9.1
Sprint: Sprint 79
Story Points: 1
Cycle: 8