This (nothing happening when you click on a node) happens a lot with Umbraco 7 (since it uses AngularJS), but usually resolved when you refresh the page. This time the problem is persistent.
Does any of your created document types have the same name? Or does it make use of some 3rd party or custom property edits, which may contain invalid javascript that makes Umbraco choke?
I should have been more specific - It's actually not the name that matters but the alias. If two document types have the same alias then things can act up as well. My bad.
But since the issue seems to have something to do with the compiled dll's then it's not the alias issue either.
But do you make use of some 3rd party .dll's or anything?
Happy to hear that I got you on the right track and you got the issue solved. Remember to mark your last post as the solution so others can go straight to it if the encounter the same issue. That way they get an idea about what to try.
Bug? Nothing in Settings are clickable anymore
I was creating some document types.
All of a sudden I can't click anything in Settings (or Users) anymore.
I can expand the trees, but when I click - say a Document Type or a Stylesheet - nothing happens.
There is a JavaScript error though:
Error evaluating js callback from legacy tree node: ReferenceError: openNodeType is not defined
or openView is not defined
or openUserTypes is not defined
I also noticed another error before that, not sure if it is related:
GET http://localhost/umbraco/LegacyTreeJs?umb__rnd=7.2.1.1195729766 ;
This (nothing happening when you click on a node) happens a lot with Umbraco 7 (since it uses AngularJS), but usually resolved when you refresh the page. This time the problem is persistent.
How can I make Umbraco work again?
Hi Hardi
Does any of your created document types have the same name? Or does it make use of some 3rd party or custom property edits, which may contain invalid javascript that makes Umbraco choke?
/Jan
Thanks Jan for the reply.
No I can't see any Document Types with the same name. No custom property editors either.
I just noticed this has been reported with no solution yet (I couldn't find it before)
Hi Hardi
I should have been more specific - It's actually not the name that matters but the alias. If two document types have the same alias then things can act up as well. My bad.
But since the issue seems to have something to do with the compiled dll's then it's not the alias issue either.
But do you make use of some 3rd party .dll's or anything?
/Jan
Thank you Jan! You were right.
We removed all dlls and references, cleaned them up, re-include what we need and it fixed the problem.
Hi Hardi
Happy to hear that I got you on the right track and you got the issue solved. Remember to mark your last post as the solution so others can go straight to it if the encounter the same issue. That way they get an idea about what to try.
/Jan
I am now getting the same error again after I continued working on the website >.<
Don't worry. I managed to fix it by undoing everything.
is working on a reply...