Dan Tappin wrote:
> To be honest the real answer will be unpopular but since the old system
> is unusable, not maintainable it should be replaced. I think if you
> estimated the time / cost to rebuild the system from scratch it would
> still be the better than trying to continue with this PITA sy
On Tue, 1 Mar 2005 14:56:57 -0800 (PST), Richard Lynch <[EMAIL PROTECTED]>
wrote:
> Anybody got a better idea for handling this sort of design in any
> reasonable fashion?
how about storing all the form info using sessions/session-style
steps. for stability/security, u can store all variables ass
That sounds ugly.
To be honest the real answer will be unpopular but since the old system
is unusable, not maintainable it should be replaced. I think if you
estimated the time / cost to rebuild the system from scratch it would
still be the better than trying to continue with this PITA system.
My current employer has designed a sort of CMS (except it has so many
site-specific hard-coded features that it's not a CMS at all) where things
happen such as:
If you are in the middle of adding a new user, their name appears with a
yellow background, and only after you fill out the other pages a
4 matches
Mail list logo
