Showing a Reliable Success Message After eForm Submission on Long Pages

A success message is only useful if the user actually sees it, especially on long pages with more than one form.

Success feedback on long pages becomes tricky when multiple forms share the same script logic. A generic popup or hardcoded scroll position may work for one form and fail completely for another.

What works better

anchor the success state to the submitted form container
inject the response close to the form instead of at a global page position
use per-form targets when multiple forms share the same page

The main lesson is simple: success messages should belong to the form that was submitted, not to a global page-level script that guesses where the user is looking.

Newer post

Adjusting TV Field Sizes and the Main Content Area in the Manager

How to think about resizing TV input fields and the main content area when ManagerManager is not enough on its own.

Older post

Creating Resources from eForm Data in Evolution CMS

How to turn an eForm submission into a newly created resource instead of just sending an email.