Fixing AjaxSearch Breakage When FileSource Points to a Missing Snippet File

File-based snippet workflows are convenient until the file path drifts. In the reported case, AjaxSearch itself was fine, but the FileSource plugin still tried to load a snippet file that no longer existed. The result was a chain of “headers already sent” warnings and manager-side editing failures.

This is an important maintenance lesson for Evolution CMS teams using file-backed snippets: once the snippet source is externalized, the path becomes part of the application contract. Rename or move the file carelessly, and the manager may break in places that seem unrelated at first.

Whenever a manager edit screen fails around snippet loading, check the file-backed source map before you assume the snippet logic itself is broken.