Blog Sections Open
Why an Evolution CMS Site Fails on the First Visit but Loads After Refresh
If a site throws a configuration-style error on the first request and works on the second, the real issue is usually bootstrap timing, include paths, or hosting-level file access behavior.
This old troubleshooting case looked dramatic: on the first visit the site displayed an installation-style error such as “MODX is not currently installed or the configuration file cannot be found,” but after refreshing the same page, everything loaded.
Why the Message Is Misleading
The configuration file is often present. The real issue is that the bootstrap process failed to see it or failed to read critical values at the moment of the first request.
The Clue in the Bootstrap Code
The discussion pointed to the startup section around loading config.inc.php and validating core connection values. If those checks fail even briefly, Evolution falls into the “not installed” error branch.
What to Check
- file include paths and manager directory constants
- filesystem latency or race conditions on hosting
- permissions that allow eventual access but fail inconsistently
- server-side caching or opcode behavior that changes between first and second hit
This is one of those issues where the visible error points at installation, but the real problem is environment stability. When the second hit succeeds immediately, look at hosting, file access, and bootstrap timing rather than reinstalling the CMS.
Fixing AjaxSearch When One-Letter Words Stop Returning Results
Why AjaxSearch can miss short prepositions and other one-letter terms, especially after minChars changes, and how to tune it more carefully.
Shrinking an Oversized `modx_session` Table
What to check when the session table becomes enormous: retention, bot load, session handler choices, and safe cleanup options.