Blog Sections Open
Saving Uploaded Files on the Server While Emailing Only a Link in eForm
How to change an eForm workflow so uploaded files stay on the server and email notifications receive only a clean download link instead of the raw attachment.
Not every file submitted through a form should be mailed as an attachment. For larger files or long-lived documents, it is often cleaner to save the file on the server and send only a link in the notification email.
That changes the workflow from “mail transport” to “file intake plus link notification”, which is usually easier to scale and less fragile.
A safer pattern
- accept the file through the normal eForm upload flow,
- move or save it into the intended folder on the server,
- store the resulting path or URL,
- insert that link into the mail template instead of attaching the file.
This keeps mail size small, avoids attachment-related delivery problems, and leaves the file available for later review by the team.
When file uploads are part of a business process rather than a one-time contact form, link-based delivery is often the more maintainable choice.
Choosing a Gallery and Slideshow Strategy for Evolution CMS
A practical overview of how to think about gallery and slideshow functionality in Evolution CMS instead of looking for one universal module.
Building FAQ-Style Comment Threads in JotX with Moderator-Only Replies
How to shape JotX into an FAQ-like support flow where users ask questions and only moderators or administrators can post the threaded answers.