I had to recreate my developer index as it was deleted because the test period expired. When I tried to run the content indexing job after updating the episerver.find config with the new serviceUrl and defaultIndex values, i got an exception in a property, and fixed this. Here's the job log:
Indexing job [XX] [content]: Reindexing completed. ExecutionTime: 0minutes 0seconds Number of content indexed: 48 Number of content errors: 0 Number of batch errors: 1An exception occured while indexing (Batch): Error getting value from 'DownloadCenterParams' on 'Castle.Proxies.DownloadCenterShortcutBlockProxy'. (see log for more information)
After fixing this issue, I tried to run the content indexing job again, but every time I do so, here's what it reports:
Indexing job [XX] [content]: Reindexing completed. ExecutionTime: 0minutes 0seconds Number of content indexed: 0
My index is empty and thus all my EpiServer Find queries are returning no hits.
What's the Find version you have installed? Strange that it would just fail to index content if the only change is a new developer index...
The currently installed version is 220.127.116.119
What puzzles me the most is that it seemed to find the content after I changed to the new developer index, but it threw an exception because we had a nullref problem in one of our properties. When added a nullref check to this property and updated the site, all content was suddenly invisible to the job.
A reboot of my development machine fixed the issue though, so it works as it should now.