[eluser]Colin Williams[/eluser]
I think the issue is being way over-complicated. Your view is responsible for spitting out the form and its controls. The controller is going to prep the data. So, like I showed above, you can set the initial values to whatever is available in the session. If nothing is available in the session, you get blank form controls. If there is $_POST data available, the set_value() function uses it instead of the session data, which may or may not be available.
Quote:If I’m not mistaken then it’s 4K Per session, right?
What if I set a session for EACH field? I doubt it will pass the 4K limit
There is not a session per field. Sessions refer to periods of use by one user/client. You use a session id to append data to particular sessions. Like I said earlier, use database session storage and you don't have to worry about the limit because only the ID is stored.
Quote:What I’m looking for is how to save the data entered and have a back (or previous) button that the user can click and he goes back to the previous step and still have all the data he entered earlier saved in the fields
Maybe you haven't read the Session class documentation in the user guide? You will use the session class to store the data collected along the way. Then, on a successful completion, you can unset the session data. Sketch out a diagram to help yourself along.