Blog Sections Open
Why eForm Works on Some Pages but Not Others
When eForm sends mail only from selected resources, look beyond SMTP and inspect template structure, parser errors, and page-specific markup differences.
An eForm installation that works on some resources but fails on others usually points to page-level differences, not to the mail transport itself. If SMTP settings are correct, the next suspects are template structure, duplicated IDs, parser issues, or broken chunks.
What to compare
- the working and failing templates
- the form chunk and email chunk used on each page
- whether a container page or homepage uses different wrapper markup
- JavaScript collisions if AjaxSubmit is involved
Why this happens
Teams often assume eForm is broken globally, but the real issue is that one template omits a required placeholder, loads conflicting JavaScript, or changes the parser order enough to break the form block.
Recommendation
Debug one working page against one failing page side by side. In most cases the answer is in the template or chunk composition, not in eForm itself.
Detecting and Removing Quick ManagerManager Malware in Evolution CMS
A practical incident note on hidden-link infections, fake manager plugins, and emergency cleanup steps for compromised Evolution CMS sites.
When Easy2 Gallery Queries Overload the Database
How to interpret repeated Easy2 gallery queries that copy to temporary tables and push a hosting database into critical load.