New Spark Media Platform platform uses a custom template engine to render HTML pages. There is a group of components, that render HTML forms and commonly used form components. Refer to Form component documentation to get details and usage examples. The use of New Spark Media Platform form components is encouraged over the use of regular HTML tags, since it provides better layout control.
Each request to actions must send a form token (unless configured otherwise). This is a security measure that allows New Spark Media Platform to verify that the incoming request is legitimate and actually coming from the application. Form tokens are generated by <fm:Form> component.
Actions are the request processors that enable user interaction with the New Spark Media Platform powered application. Tasks such as registration, login, media uploads, comments, profile updates etc. are handled by actions.
Actions must be configured for every application at the point of app creation. All the actions used by the app must be enabled. Every action has required and optional parameters predetermined, but this can be changed during the application installation.
Parameters are predetermined for actions and can be set as required or optional.
So far the actions rely on following email templates to be present:
All actions support redirectUrl form parameter, that will redirect to the specified url upon the successful action completion. All actions support failRedirectUrl to redirect on the action failure. In addition to that failRedirectUrl_{$error_code} params can be specified to redirect to different urls on different action failures.