I have the same problem.
In my case it came with an chrome update (Version 47.0.2526.73 m.) So right now im using Firefox, maybe that would work for you?
yep, I get quite a lot of other dropdowns not working across umbraco too. So some inside a property editor, and nuPickers XML Dropdowns don't seem to be letting me select anything in chrome either - works in firefox :(
Only solutions online seem to be update Angular version - but this will break umbraco in other places - so don't do it?
This looks like it's an angular / chrome issue, were some proper upgrading of Angular and/or a chome fix is going to solve in the long term.
however there is a fix you can apply to an existing umbraco site, but it's not nice - and really I've had reservations about posting this because i am not sure if this will have secondary affects somewhere else down the line.
so with a SEVERE HEALTH WARNING that you shouldn't do this unless you are desperate.
on line 171 of /umbraco/lib/angular/1..1.5/angular.min.js
find C[0].selected!==d.selected and replace c[0] with s to
read s.selected!==d.selected
This is essentially applying this commit to angular directly to the angular.min file. which is not really something you should do.
tested with 7.3.0 - it fixes the above, don't know if it breaks anything else.
please don't do this unless you are really deseprate and don't blame me if something goes wrong. you've voided all your warranties with this one.
Can't select property editor in datatype
Hi all,
I can't select a property editor anymore in a umbraco 7.3.2 installation. I updatet it to 7.3.3 but still no luck.
If I want to add a new datatype the dropdown is empty and stays empty. whatever I do.
If I open a existing datatype the property editor is correctly selected but if I select another one it doesn't change.
Does anybody know how to debug/solve this problem?
Thanks.
I've put back a backup from sourcecontrol but that didn't help... I think the only way is a fresh install.
Edit: Ok, I did a fresh install of 7.3.3. The first thing I tryd is to add a new datatype. The problem is also present in this fresh install.
Edit2: It works in IE. Not in chrome version 47.0.2526.73 m
I have the same problem. In my case it came with an chrome update (Version 47.0.2526.73 m.) So right now im using Firefox, maybe that would work for you?
Update:
It works in chrome. You can't select with the mouse but if you use the arrows (up/down) in the property editor it works.
So its a combination chrome + mouse click.
It also happens in 7.2.2 so it can't be Umbraco related?
I didn't try that, but now i see it works with arrows.
I happent right after i updated Chrome.
On my colleague's pc it worked, right until i made him update his Chrome. So i think that it is a problem with Chrome.
Its a problem with chrome and the current Angular version Umbraco uses.
yep, I get quite a lot of other dropdowns not working across umbraco too. So some inside a property editor, and nuPickers XML Dropdowns don't seem to be letting me select anything in chrome either - works in firefox :(
Only solutions online seem to be update Angular version - but this will break umbraco in other places - so don't do it?
I'm using the arrows and space. That works so form me so no need to update angular.
yeah - it does also break dropdowns for editors :(
so dropdown lists, nuPickers, etc don't let you set anything with the mouse
Issue is logged here : http://issues.umbraco.org/issue/U4-7496
He Kevin,
Thanks for logging it. I cant log in with google credentials for some reason...
Frans
Thanks for logging this.
We are experiencing the same thing.
This looks like it's an angular / chrome issue, were some proper upgrading of Angular and/or a chome fix is going to solve in the long term.
however there is a fix you can apply to an existing umbraco site, but it's not nice - and really I've had reservations about posting this because i am not sure if this will have secondary affects somewhere else down the line.
so with a SEVERE HEALTH WARNING that you shouldn't do this unless you are desperate.
on line 171 of /umbraco/lib/angular/1..1.5/angular.min.js
find
C[0].selected!==d.selected
and replacec[0]
withs
to reads.selected!==d.selected
This is essentially applying this commit to angular directly to the angular.min file. which is not really something you should do.
tested with 7.3.0 - it fixes the above, don't know if it breaks anything else.
please don't do this unless you are really deseprate and don't blame me if something goes wrong. you've voided all your warranties with this one.
Kevin,
Thanks for the info.
I think you made it pretty clear that this can damage my health ;)
Saied
is working on a reply...