Ok...is this a fresh installation or have you been trying to create a property editor yourself, using a 3rd party package? Could there be a missing file or something?
It could be the result of something being ignored in the .ignore file, which should not have been ignored. Does it work on some of your colleagues machines?
Are you using git or mercurial for source control? When did it start to happen?
I'm currently working on a project myself where we have ezSearch and the RJP.MultiUrlPicker packages installed and we don't have any issues accessing the examine dashboard options.
Don't know uLess though - But the other two packages are not the issue :)
I'm having the same issue as well and I tried to fix it, as the error is a simple casing problem located in the ExamineManagement.js in line 130. The problem is that the viewModel returns the IndexCriteria for some reason in lower case so the IncludeNodeTypes is undefined.
As said I tried to fix it but it didn't work. The error just got more worse because after the fix I get a ton of "Unable to parse bindings" errors out of the knockout.js.
Probably we should open a ticket so the developers are aware of it ;)
Maybe I can find the issue and create a working workaround so we can use the Dashboard again.
SO CLOSE :) I now see the Searches (W00T - thnx!) but Indexers now being displayed. Can you attach your .ascx file here - I can't download from the ticket :( Maybe rename to .txt???
OK - found the root cause - the old ExamineManagement.ascx is no longer used. Update the control in /Config/Dashboards.config to point to views/dashboard/developer/examinemanagement.html :)
*FacePalm* :D I already thought - Why is there a "examinemanagement.html" file? LMAO!
Anyway I tried it out and it seems to work as well! But it there are some minor issues with that dashboard! Eg. it is not refreshing after the index rebuild.
Today I found myself experiencing the exact same issue on a 7.5.3 umbraco - the ExamineManagement view was empty, no indexers or searchers listed. No errors in the console, no errors in the log either, so I started digging a bit.
Through debugging in the browser console, I could verify that the data was indeed fetched and set in the scope variables. The problem was the loop variable of the ng-repeat directive.
The html (\Umbraco\Views\dashboard\developer\examinemanagement.html) looks like this:
<li class="provider" ng-repeat="indexer in indexerDetails">
...
...
<li class="provider" ng-repeat="searcher in searcherDetails">
Now inspecting these variables in the console, both variables are not 'loopable', as they are both objects containing two child objects - type and values. Values is 'loopable' so I made a small modification in the html:
<li class="provider" ng-repeat="indexer in indexerDetails.$values">
...
...
<li class="provider" ng-repeat="searcher in searcherDetails.$values">
Now my ExamineManagement view works perfectly.
I have not tried upgrading umbraco to the latest version (7.5.4 atm.), so this error has possibly already been resolved, but for now until I upgrade, this fix will have to do.
Examine management empty
Hi
I have a Umbraco installation where the tab "Examine management" is empty, does anyone have an idea why?
Looks like this - it is Umbraco 7.2.1
Hi Carsten
It's not very obvious but I think you need to click on either "Indexers" or "Searchers" in order to have the options expanded :)
Hope this helps.
/Jan
Hi Jan
If only it was that simple :-( - The headlines is not links and nothing happens when I click.
Any other ideas?
Hi Carsten,
which browser and version do you use? Have you the same issue in another browser? Maybe it's a bug in your browser.
Best,
Sören
Have tried both IE 11 and latest Chrome, same result.
Umbraco 7.2.1
Hi Carsten
Aaah yes, my memory played tricks on me there. Just had to check on a fresh installation of 7.2.2 and there should be some links under each heading.
Do you see any JavaScript error in your browsers console log?
If possible you could try upgrading to 7.2.2 and see if that makes the issue disappear.
/Jan
Hm.. have the following JS errors:
description "Unable to parse bindings.\nMessage: ReferenceError: 'Name' er ikke defineret;\nBindings value: text: Name, click: toggleProperties"
{exception} Egenskaben 'IncludeNodeTypes' kan ikke hentes for reference, der er udefineret eller null
Hi Carsten
Ok...is this a fresh installation or have you been trying to create a property editor yourself, using a 3rd party package? Could there be a missing file or something?
/Jan
No it is not a clean installation and I am not the only developer working on the site. Could this error be related to a property editor?
The following 3.party packages is installed:
ezSearch
RJP.Multiurlpicker
uLess
Any ideas?
Hi Carsten
It could be the result of something being ignored in the .ignore file, which should not have been ignored. Does it work on some of your colleagues machines?
Are you using git or mercurial for source control? When did it start to happen?
/Jan
I'm currently working on a project myself where we have ezSearch and the RJP.MultiUrlPicker packages installed and we don't have any issues accessing the examine dashboard options.
Don't know uLess though - But the other two packages are not the issue :)
/Jan
Hi guys,
I am having the same issue. This is a dev site still, I am the only one workign on it, it was a fresh install of 7.2.1 and I just upgraded to 7.2.2.
Here are the javascript errors:
I have the following packages installed:
CMS Import
Config Tree
FALM Housekeeping
ImageGen
Umbraco Forms
I am using Chrome, and have tested on IE11, FF and Safari.
Any ideas? Suggestions?
I'm having the same problem. Anyone get to the bottom of this???
Cheers!
Hey guys,
I'm having the same issue as well and I tried to fix it, as the error is a simple casing problem located in the ExamineManagement.js in line 130. The problem is that the viewModel returns the IndexCriteria for some reason in lower case so the IncludeNodeTypes is undefined.
The corrected line should look like:
NOT
As said I tried to fix it but it didn't work. The error just got more worse because after the fix I get a ton of "Unable to parse bindings" errors out of the knockout.js.
Probably we should open a ticket so the developers are aware of it ;)
Maybe I can find the issue and create a working workaround so we can use the Dashboard again.
Best regards, Helmuth
Ok, I've created a Ticket which includes the changes I've done to get the Dashboard working.
http://issues.umbraco.org/issue/U4-6369
Hope the fix works for you as well!
Best regards, Helmuth
SO CLOSE :) I now see the Searches (W00T - thnx!) but Indexers now being displayed. Can you attach your .ascx file here - I can't download from the ticket :( Maybe rename to .txt???
Cheers, Karl
OK - found the root cause - the old ExamineManagement.ascx is no longer used. Update the control in /Config/Dashboards.config to point to views/dashboard/developer/examinemanagement.html :)
Hey Karl!
*FacePalm* :D I already thought - Why is there a "examinemanagement.html" file? LMAO!
Anyway I tried it out and it seems to work as well! But it there are some minor issues with that dashboard! Eg. it is not refreshing after the index rebuild.
Thanks for sharing that with us!
Best regards, Helmuth
Hey everyone,
Today I found myself experiencing the exact same issue on a 7.5.3 umbraco - the ExamineManagement view was empty, no indexers or searchers listed. No errors in the console, no errors in the log either, so I started digging a bit.
Through debugging in the browser console, I could verify that the data was indeed fetched and set in the scope variables. The problem was the loop variable of the ng-repeat directive.
The html (\Umbraco\Views\dashboard\developer\examinemanagement.html) looks like this:
Now inspecting these variables in the console, both variables are not 'loopable', as they are both objects containing two child objects - type and values. Values is 'loopable' so I made a small modification in the html:
Now my ExamineManagement view works perfectly. I have not tried upgrading umbraco to the latest version (7.5.4 atm.), so this error has possibly already been resolved, but for now until I upgrade, this fix will have to do.
Hope it helps.
BR Peter
is working on a reply...