Blog Sections Open
Fixing index-ajax.php 404 Errors in Evolution CMS AJAX Flows
A practical debugging note for classic Evolution CMS AJAX handlers that assume index-ajax.php exists and is reachable.
A 404 on index-ajax.php usually means one of two things: either the request is pointing to a file that is not present in the current build, or the site’s routing strategy no longer expects AJAX requests to go through that endpoint.
Symptom
POST /index-ajax.php
404 Not Found
NetworkError: 404 Not FoundWhat to check
- Does the project actually include
index-ajax.php? - Was the site moved, rebuilt, or upgraded so that AJAX now posts to the current page instead?
- Are script URLs broken by base href, subfolder installation, or rewritten paths?
Modern safer pattern
On many Evo projects it is cleaner to post back to the current page URL and let the request branch through a snippet, plugin, or dedicated endpoint you control explicitly. That avoids depending on a file name that may not exist in every distribution.
If an old integration still calls index-ajax.php, verify that the file is real and intentionally supported before trying to patch around the 404 on the frontend.
Troubleshooting directResize in Older Evolution CMS Builds
How to reason about directResize failures in older Evolution CMS installations when uploaded image handling no longer produces the expected resized output.
Blocking Direct Access to Selected Resources with a Plugin
How to prevent direct access to chosen Evolution CMS resources unless a required condition or request flag is present.