topic Processing form data from HTML POST in Alfresco Archive

Processing form data from HTML POST

jcobb — Fri, 14 Aug 2009 09:17:12 GMT

HiI've been getting on well with creating a first surf application - but have a query regarding the best architecture to adopt in processing user data posted to a url from a browser form.I've already created a 'login' component that can appear on any page - it uses an html form to accept username /

Re: Processing form data from HTML POST

schambon — Fri, 14 Aug 2009 14:06:05 GMT

Hi,

1. Using a separate web script for handling POSTs and redirecting is what I'm doing too. Haven't found any other satisfactory way of handling user input, and I'm very happy with the principle anyway.

2. In order to perform redirects, you should just write this in your javascript:


status.code=302;
status.location="your redirection URL";
‍‍‍‍

Cheers,
Sylvain.

Re: Processing form data from HTML POST

jcobb — Fri, 14 Aug 2009 18:48:02 GMT

Thanks Sylvain -

I'll try that redirect code when I get a chance.

Incidentally - I'm working on the principal that I'll keep my components completely independent, and unaware of what else is happening on the page. So they'll want to somehow persist some data across page loads without using posts or variables in the url.

I see something about persisting data in the javascript api -

save()
reload()
remove()

Am i reading that right that you can keep a component's state the same across page reloads by storing model data and reloading it each time the component is called?

Re: Processing form data from HTML POST

jcobb — Sat, 15 Aug 2009 18:56:08 GMT

OK - redirection working well now. In my form I use a hidden field:

<input type="hidden" id="returnUrl" name="returnUrl" value="${page.url.url}"/>

and pick that up in the script I'm posting the form to with something like:

status.code=302;
status.location=page.url.args["returnUrl"];
status.location=page.url.args["reuturnUrl"]+"&registerError="+json.message;

Still getting my head round the best way of passing arguments from page to page for a component, will start a new thread…