Keeping eForm Stable When SEO Strict URLs Are Enabled

One of the oldest friction points in Evolution CMS projects is a working eForm setup that suddenly breaks after SEO Strict URLs or stricter URL handling is enabled. The form renders, but submission, validation, or email delivery becomes unreliable.

Typical Legacy Pattern

[!eForm?
 &formid=`contact-form`
 &tpl=`form-tpl`
 &to=`team@example.com`
 &report=`report-tpl`
 &thankyou=`thank-tpl`
 &vericode=`1`
!]

<form method="post" action="[~[*id*]~]">
    ...
</form>

Why Strict URLs Can Interfere

Strict routing can change how the current page URL is resolved during POST requests. If the form posts to a variant of the current resource that the routing layer does not accept cleanly, eForm may validate incorrectly, redirect unexpectedly, or fail before mail transport is reached.

What to Check

• Make sure the form posts to the exact canonical URL of the current resource.
• Keep eForm uncached.
• Avoid mixing multiple URL variants of the same page.
• Review redirects, base href, and rewrite rules together.
• Test the form both with and without strict URL rules enabled.

Good Practice

On older projects, contact forms are often the first place where strict routing issues show up. When that happens, do not start by rewriting the form templates. First normalize the page URL, confirm the POST target, and only then debug the mail layer.

The form code itself is usually fine. The unstable part is the request path.