In regards to the angular version - I'm sure it will be upgraded when the time is right but it's not something that you just do. The upgrade could mean breaking changes in the Umbraco core etc. - If I remember correctly it is the intention to upgrade Angular. Just don't know when it will happen. Hopefully in some of the releases we'll see after the summer break.
It's a fairly fresh installation, yes. I've been adding some partials and some static assets, but nothing too notable yet. The fact that this problem is caused by an actual javascript error that's coming from umbraco itself, means that it couldn't possibly have been my fault.
May I ask, why do you need to know if this is a fresh Umbraco installation? Shouldn't this not happen in any scenario?
Well, I need to know since the answer I'm going to provide depends on your scenario.
If you had done an upgrade it could be happening because the client dependency cache needs to be cleared for instance. On a fresh installation...it would be weird if that would do the trick.
I agree it should not happen but it's hard to figure out what's going on in your end when one is not able to see your setup. I have not seen such error on a fresh installation in my end. It's always easier to provide hints and pinpoint where things might go wrong the more one knows about the setup. All I'm trying to do is to see if I can help you out.
Have you tried logging in using Firefox from another machine - Does it act the same? Could it be that perhaps you for whatever reason need to refresh the browser cache?
CMS Login broken
When I go to http://mysite/umbraco, I get this:
So essentially an empty page with a title that says {{menuDialogTitle}}, and literally nothing else. It's all empty otherwise. This is on Firefox 30.
The console spwes out a gigantic error:
Error: too much recursion
.type@http://localhost:52173/umbraco/lib/jquery/jquery-2.0.3.min.js:4:3856
.isPlainObject@http://localhost:52173/umbraco/lib/jquery/jquery-2.0.3.min.js:4:1
x.fn.extend@http://localhost:52173/umbraco/lib/jquery/jquery-2.0.3.min.js:4:2847
[repeated several quadrillion times...]
x.fn.extend@http://localhost:52173/umbraco/lib/jquery/jquery-2.0.3.min.js:4:2847
wrap/<@http://localhost:52173/umbraco#/login?check=false:15:1
y/<@http://localhost:52173/umbraco/lib/angular/1.1.5/angular.min.js:39:120
xb/c/Xc/this.$getXc/this.$getxb/c/<@http://localhost:52173/umbraco/lib/angular/1.1.5/angular.min.js:16:234
d@http://localhost:52173/umbraco/lib/angular/1.1.5/angular.min.js:27:467
xb/c@http://localhost:52173/umbraco/lib/angular/1.1.5/angular.min.js:16:141
xb@http://localhost:52173/umbraco/lib/angular/1.1.5/angular.min.js:16:360
.complete/<.complete/<@http://localhost:52173/umbraco/Application?umb__rnd=ffffffff97656a02:58:21
x.Callbacks/l@http://localhost:52173/umbraco/lib/jquery/jquery-2.0.3.min.js:4:30467
x.Callbacks/c.add@http://localhost:52173/umbraco/lib/jquery/jquery-2.0.3.min.js:4:30673
x.prototype.ready@http://localhost:52173/umbraco/lib/jquery/jquery-2.0.3.min.js:4:1947
.complete/<.complete@http://localhost:52173/umbraco/Application?umb__rnd=ffffffff97656a02:57:17
c/j@http://localhost:52173/umbraco/lib/yepnope/yepnope.min.js:2:2444
g/<@http://localhost:52173/umbraco/lib/yepnope/yepnope.min.js:2:2070
h@http://localhost:52173/umbraco/lib/yepnope/yepnope.min.js:2:222
a.yepnope.injectJs/k.onload@http://localhost:52173/umbraco/lib/yepnope/yepnope.min.js:2:3370
http://localhost:52173/umbraco/lib/angular/1.1.5/angular.min.js
Line 63
The login works fine in IE11, but this is not an acceptable workaround, since our client is not going to be using Windows.
I'm developing against Umbraco version: 7.1.1 assembly: 1.0.5211.22376
/edit
Why such an old version of Angular? Updates are there for a reason.
Hi Martijn
Is this a fresh install of Umbraco?
In regards to the angular version - I'm sure it will be upgraded when the time is right but it's not something that you just do. The upgrade could mean breaking changes in the Umbraco core etc. - If I remember correctly it is the intention to upgrade Angular. Just don't know when it will happen. Hopefully in some of the releases we'll see after the summer break.
/Jan
It's a fairly fresh installation, yes. I've been adding some partials and some static assets, but nothing too notable yet. The fact that this problem is caused by an actual javascript error that's coming from umbraco itself, means that it couldn't possibly have been my fault.
May I ask, why do you need to know if this is a fresh Umbraco installation? Shouldn't this not happen in any scenario?
Hi Martijn
Well, I need to know since the answer I'm going to provide depends on your scenario.
If you had done an upgrade it could be happening because the client dependency cache needs to be cleared for instance. On a fresh installation...it would be weird if that would do the trick.
I agree it should not happen but it's hard to figure out what's going on in your end when one is not able to see your setup. I have not seen such error on a fresh installation in my end. It's always easier to provide hints and pinpoint where things might go wrong the more one knows about the setup. All I'm trying to do is to see if I can help you out.
Have you tried logging in using Firefox from another machine - Does it act the same? Could it be that perhaps you for whatever reason need to refresh the browser cache?
/Jan
is working on a reply...