<form name="weekview_form" enctype="multipart/form-data"
action="/091/dispatch.php?" method="post">
Ok. You must add session information, that ATK uses to determine what to do
after the redirect.
This can be done like this:
$g_layout->output('<FORM ..... (your form stuff)
$g_layout->output(session_form(SESSION_NESTED));
$g_layout->output('<INPUT .. (the rest of your form stuff.
Quick explanation:
The application execution can be considered as a stack:
Suppose the user starts in the timeregistration menu. This is considered
'level 0'.
If he goes somewhere from there, with SESSION_NESTED (either via a form
(session_form) or link (session_url or href), the action is performed at
'level 1'.
The redirect function will normally move back one level, so it will go back
to level 0, which was the time registration screen.
If you don't do the SESSION_NESTED thingee, the action will be performed at
'level 0', overwriting the timeregistration screen which was also at 'level
0'.
By using this stack mechanism, the user can move infinitely deep into
screens (from customer to project, from project to phase, etc.), and always
come back without losing data (even data you didn't save is still there).
Quite powerful, and not many webbased applications do it like this. (Yes,
I'm proud of it :)
Greetings,
Ivo
--
Ivo Jansch <ivo dot
ibuildings.nl BV - information technology
http://www.ibuildings.nl
[ Achievo mailing list - http://www.achievo.org/ ]
[ to unsubscribe send an e-mail to achievo-unsubscribe dot