Blog Sections Open
Why Newly Created Resources Can Return 404 Until the Environment Catches Up
A practical debugging note for environments where new resources exist in the manager but do not become reachable immediately on the public site.
When a resource is visible in the manager but the frontend still returns 404, the instinct is often to blame the document itself. In practice the problem is frequently the environment around it: cache, routing state, hosting quirks, or delayed filesystem/database consistency.
What to check
- Whether the site cache was actually refreshed.
- Whether the host has rewrite or propagation quirks.
- Whether the resource alias and parent path resolve the way the frontend expects.
- Whether a custom listing or routing layer is still pointing at stale data.
This kind of bug is especially common on low-cost hosting or environments with unusual caching behavior. The manager may be correct immediately while the public layer lags behind.
Fixing getResourcesTag Output After an Update
How to restore tag-based getResourcesTag listings when an update changes placeholder handling or tag output stops rendering.
Fixing ajaxSubmit and eForm 500 Errors in Evolution CMS
How to troubleshoot AJAX form submissions that trigger a 500 error when ajaxSubmit and eForm are combined in an Evolution CMS project.