When using the Exclude Paths configuration field, entered paths are silently ignored during an HTML content search.
Root cause: The exclude-paths check only exists inside fetchFiles(), but the main HTML search flow bypasses fetchFiles() entirely — it uses DA's crawl() function with a processItem callback that has no visibility into the exclude-paths input.
The JSON file search branch calls fetchFilesForJson() directly, so it correctly honors exclusions. Only the HTML crawl is affected.
Steps to reproduce:
- Enter a valid org/site
- Add a folder path to Exclude Paths (e.g.
/drafts)
- Run a search — files under that path still appear in results
Expected: Files under excluded paths are omitted from results
Fix: Apply the same exclude-paths filter inside the processItem callback used by crawl().
When using the Exclude Paths configuration field, entered paths are silently ignored during an HTML content search.
Root cause: The exclude-paths check only exists inside
fetchFiles(), but the main HTML search flow bypassesfetchFiles()entirely — it uses DA'scrawl()function with aprocessItemcallback that has no visibility into the exclude-paths input.The JSON file search branch calls
fetchFilesForJson()directly, so it correctly honors exclusions. Only the HTML crawl is affected.Steps to reproduce:
/drafts)Expected: Files under excluded paths are omitted from results
Fix: Apply the same exclude-paths filter inside the
processItemcallback used bycrawl().