Using AjaxSnippet with pdoResources in Evolution CMS Workflows

AjaxSnippet is useful when you want to refresh only part of the page, but it becomes fragile if the trigger parameter, snippet call, and frontend request format are not aligned. That becomes even more noticeable when the content block is produced by something heavier like pdoResources.

The underlying lesson is simple: the trigger should be treated as part of the request contract. If the frontend and the snippet disagree about how the AJAX call is identified, the refresh logic fails before the content layer ever gets a chance to render.

When pdoResources is in the chain, the safest approach is to keep the AJAX wrapper minimal and make sure the content query itself can still render correctly outside the AJAX context. That makes the whole setup easier to debug and easier to reuse.