Avoiding Unwanted 404 Responses from `getDocumentObject()` in Evolution CMS

One subtle Evolution CMS trap is that some API calls do more than just “return nothing” when a document is missing. In the case discussed here, getDocumentObject() could trigger the 404 flow directly if the requested document ID did not exist.

That matters in custom snippets and routing logic. You may think you are simply checking whether a document exists, but the parser may already be calling the error-page logic before your code has a chance to decide what to do next.

The practical lesson is to treat this method as part of the request lifecycle, not as a harmless low-level lookup. If your script needs a soft existence check, prefer a safer access pattern or validate the ID first before calling the method in a place where an automatic 404 would be disruptive.

This is especially important in custom routers, AJAX endpoints, import layers, and helper snippets that may receive unpredictable document IDs.