Your Own Error Page


The ActiveForms platform was designed as a tool that is transparent to the end-user. A person who submits an entry sends data to the form owner, and not to ActiveForms. That is why you can serve forms from your own domain or prepare your own error page.

Your own error page is an HTML page presented to users in the following circumstances:

An incorrect URL (404)—if a customer types https://activeforms.com/yourcompany/account_application and there is no active form at account_application. This could be due to incorrect linking, mistyping or disabling a form that used to be active.

Insufficient permissions to access a form (403)—if a form is accessible in a non-Public mode, and the auth parameter value is incorrect.

ActiveForms application error (500)—if there indeed is a platform error, or when remote services aren’t working.

To edit your error page, select the Setting -> Error page layout menu option. First, select Enable custom error page, and then edit it like a form layout—you can change the HTML, CSS, JS, and binary files.

There are 2 differences between editing an error page and form layouts:

  • Somewhere in the page body, you need to use the $ERRORNO$ variable, which will be replaced with the error number during the presentation. The number helps ActiveForms administrators to track the situation in logs.
  • You can use the $HTTPSTATUS$ variable in the page body. It will be replaced with the HTTP response status during the presentation. The possible values are 404, 403, and 500.

Depending on the $HTTPSTATUS$ value, you can display messages like “Form not found” or “Access to the form denied”. You implement that in JavaScript by hiding fragments of HTML code:

if ("$HTTPSTATUS$" == "404") {
} else {
recent posts
3rd Apr 2014
Faster than ever!
5th Dec 2013
Live validation!
2nd Dec 2013
Features distilled
12th Mar 2012
Flicking Channels
26th Jan 2012
Your Own Error Page
9th May 2011
Box Properties
15th Apr 2011
Grouping Fields
13th Apr 2011
Form Versioning
24th Feb 2011
Form Access Modes
22nd Feb 2011
Required Fields
4th Feb 2011