Hi Craig,

thanks for the suggestion but that's not the issue - this is a fully working install & the indexes are being built successfully. When I open 'Developer' page in the back office, I can inspect the responses from:

/umbraco/BackOffice/Api/ExamineManagementApi/GetIndexerDetails

and

/umbraco/BackOffice/Api/ExamineManagementApi/GetSearcherDetails

And they look sane, for instance the internal indexer reports:

{
  "$type": "Umbraco.Web.Search.ExamineIndexerModel, umbraco",
  "indexCriteria": {
    ... loads of objects ...
  },
  "documentCount": 346,
  "fieldCount": 131,
  "deletionCount": 36,
  "isOptimized": false,
  "isLuceneIndex": true,
  "name": "InternalIndexer",
  "providerProperties": {
    "$type": "System.Collections.Generic.Dictionary`2[[System.String, mscorlib],[System.String, mscorlib]], mscorlib",
    "AutomaticallyOptimize": "False",
    "CommitCount": "0",
    "DataService": "UmbracoExamine.DataServices.UmbracoDataService",
    "DirectoryFactory": "",
    "DisableXmlDocumentLookup": "False",
    "EnableDefaultEventHandler": "True",
    "IndexingAnalyzer": "Lucene.Net.Analysis.WhitespaceAnalyzer",
    "IndexSetName": "InternalIndexSet",
    "LuceneIndexFolder": "...location on disk...\\App_Data\\TEMP\\ExamineIndexes\\Internal\\Index",
    "Name": "InternalIndexer",
    "OptimizationCommitThreshold": "100",
    "RunAsync": "True",
    "SupportProtectedContent": "True",
    "SupportUnpublishedContent": "True",
    "TempStorageLocation": "",
    "UseTempStorage": "False"
  }
}

... yet nothing is shown in the Examine management page in the back office.

Search works both in the back office, and externally using the ezSearch package, but the index cannot be interrogated or refreshed using the pages in the back office.

I now need to extend Examine (plugging in another document management system), but clearly something is wrong here and I'm not able to start until this is resolved.

Hi Ismail,

I thought so too - it seems like the angular components aren't rendering correctly, but there's nothing showing up in the console whatsoever. I've added an angular inspector to Chrome and nothing jumps out at me (but then I know nothing about angular).

It's as if there's an error being caught somewhere. This is incredibly odd, because there is a second site built from largely the same codebase which is unaffected by this. Craig, you're right - I'm trying to work backwards but Examine hasn't been touched for a long time, so unfortunately I have no idea when this issue first arose. It could be months. There is another, possibly related issue with Redirect URL management, in that the symptom is the same; the json is returned to the front end, but not quite everything is being rendered in the page (the pager is there, but no content). Again, this is a feature that 'just works' and we don't check routinely. It does appear, however, that redirects are no longer being added correctly. I've done a diff on the /umbraco/ directory across a working, and an affected site, and there is nothing to report.

The sites are managed by content editors and published to a live site via Courier.

I'll get down to some more serious debugging, I had hoped this would be an issue someone would have seen before!

Cheers, Ben.

just check if in web.config you have debug = false if so then try setting it to true and see if that gets things working.

Regards

Ismail

Hi Ismail,

was in debug mode throughout. Setting to false, back to true - no change.

I'm going to take a copy of the site & database and cut it right back, it's pretty unwieldy trying to debug something of this scale. I'll update if there's anything new.

Cheers, Ben.

Hi Skippy,

Sorry, I can't be of more assistance.

I was going to suggest doing a full diff on the whole solution folder...

Since you mentioned using Courier, which I haven't used for some time now... but it used to be super buggy and it had a tendency to miss certain files when copying between sites.

I tend to use Beyond Compare for any diffs: https://www.scootersoftware.com/

You can get a 30-day free trial.

Let me know how it goes, good luck!

Craig

Thanks Craig, your help is much appreciated anyway. I have done a full diff between the sites, and again nothing immediately jumped out - so it's time to take it line by line.

I can target the 'known working' database with the 'problematic' web application, and the issue persists; the inverse is also true - so it's clearly an issue in the web app somewhere.

The site which is showing issues has had a lot more use, and there have been a lot more Courier runs, but we'll see.

Cheers, Ben.

Excellent news!

Happy you found it and can now continue coding :-)

Regards

Craig