> I have a site where the users can add text to a form that will then
> go to database, and from that a "news page" will get it's
> information. Easy.
>
> But, my client wants a way to add the text, hit enter, then preview
> it with the ability to make changes before it goes live. After the
> preview/change process he can hit another submit button to have the
> info go live.
>
> I'm looking for ideas as to where to start. Is this possible? Do I
> need 2 tables, a beta table that is used before it goes live to the
> final table? I'd need to figure out how to get the record from the
> beta table to the live table.
This is a workflow issue. There are lots of ways you can manage workflow;
your method of using a separate table is one. Typically, I'd use a field to
contain the status of the record, then change that status as needed,
although there are some advantages to doing it your way.
Alternatively, if you don't need to keep the preview data around very long,
you might be better off storing in in memory until the user marks it as
live.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
