I am getting a strange error after upgrading to 7.2.2 today in
production. When I try to access /umbraco I get a blank screen with
"UmbClientMgr is not defined" in the JavaScript console as an error.
The site is hosted as a Windows Azure Website and it works fine
when running locally.
I'm not too familiar with Azure hosting but have you tried to go to the /config/ClientDependency.config file and increment the version number and then recycle the app pool to see if that works?
It should bust the backoffice cache, which may be the issue.
What steps did you take in order to do the upgrade? what was the process?
Thanks for the reply, I tried bumping the version number with no love :( Currently I am trying redeploy to a new Azure website to see what the result it.
I performed the upgrade with NuGet locally and committed it back in to my GitHub repo where it was picked up by Azure and deployed. I am guessing that something the NuGet upgrade performed did not make it up into the site.
Yes I do use an ignore file, I basically ignore everything that is not custom code and have NuGet restore it all when the site is deployed. I am thinking that the NuGet restore on the Azure Site is not doing something :S
FYI deploying to a whole new site shows the same symptoms.
Looking into what it could be, will keep this thread updated.
UmbClientMgr is not defined after upgrading to 7.2.2
Hello all,
I am getting a strange error after upgrading to 7.2.2 today in production. When I try to access /umbraco I get a blank screen with "UmbClientMgr is not defined" in the JavaScript console as an error.
The site is hosted as a Windows Azure Website and it works fine when running locally.
Anyone have any idea?
Aaron
Hi Aaron
I'm not too familiar with Azure hosting but have you tried to go to the /config/ClientDependency.config file and increment the version number and then recycle the app pool to see if that works?
It should bust the backoffice cache, which may be the issue.
What steps did you take in order to do the upgrade? what was the process?
/Jan
Hey Jan,
Thanks for the reply, I tried bumping the version number with no love :( Currently I am trying redeploy to a new Azure website to see what the result it.
I performed the upgrade with NuGet locally and committed it back in to my GitHub repo where it was picked up by Azure and deployed. I am guessing that something the NuGet upgrade performed did not make it up into the site.
Aaron
Hi Aaron,
do you use an ignore file? Maybe not all important files are commited to GitHub?
Best,
Sören
Hey Sören,
Yes I do use an ignore file, I basically ignore everything that is not custom code and have NuGet restore it all when the site is deployed. I am thinking that the NuGet restore on the Azure Site is not doing something :S
FYI deploying to a whole new site shows the same symptoms.
Looking into what it could be, will keep this thread updated.
Aaron
Hey all I ended up rolling back to before the upgrade. Will try again tomorrow.
Aaron
Any luck with this. Just experiencing the same issue!
is working on a reply...