Blog Sections Open
Fixing HTTPS Captcha and veriword Issues on Hosted Evolution CMS Sites
How to troubleshoot veriword and captcha assets that break only after HTTPS is enabled on a hosted Evolution CMS site.
HTTPS migrations tend to reveal assumptions that stayed hidden on plain HTTP. One common failure mode in older Evolution CMS setups is that captcha or veriword.php assets keep pointing to a non-working or mixed-protocol URL once SSL is enabled.
That can look like a random image failure, but the real problem is usually path or protocol drift. On some hosts, the same manager-side helper behaves differently once the request crosses from HTTP to HTTPS.
The useful lesson is that verification images should be treated like any other asset during an HTTPS transition: check the exact rendered URL, verify whether the host blocks the resource, and confirm that the manager and frontend agree on protocol and path.
Recognizing a Possible PHP Web Shell in an Evolution CMS Project
What to do when you find a suspicious PHP file that may be a web shell or trojan inside an Evolution CMS site.
Fixing DBAPI Connection Failures When localhost and IP Behave Differently
Why DBAPI can fail under FastCGI when localhost and the server IP are resolved differently, and how to reason about that mismatch.