Its logged at the debug level. Since drone factory executes so frequently (by default) it doesn’t show messaging at a higher level as it just fills up the logs.
Keeping track of whether or not there was something to import requires some changes to how its handled and for something that is phased out for usenet and will be phased out for torrents when support is added doesn’t make a lot of sense to do.
Completely removed, no, but the number of reasons to use it will be decreased to one or two reasons, external drive import or manually importing for some other reason are two I can think of.
Manually downloaded via sab/get can be handled via the completed download handling import process (assuming drone can properly figure out which series + episode it is).
CDH support was added in master 2.0.0.1617 (June 22nd). It uses the Sabnzbd/nzbget api to determine which downloads are ready for import, previously we only used the api to check for failed downloads.
The biggest advantage, by far, is that CDH waits for (potentially long-running) post-processing scripts and thus doesn’t import until the download client is truely finished.
Anyway, CDH makes the Drone Factory obsolete except for a couple of special cases.
Sorry, I misinterpreted what “completed download handling” was.
I am using CDH, but when NzbDrone can’t find a TV episode, either been taken down, or too old, I revert to that other method, and point the output destination folder to the Drone Factory folder and NzbDrone processes it.
If that other method is going to be incorporated soon, and NzbDrone can monitor the queue, then that’s great, as long as manually added items to the queue are also recognised.
@CBers what exactly are you looking for? There are logging messages, just not at the info level, they are at debug (visible in log files, when debug logging is enabled).
What do you plan to do with the message? or you just want to see it?