"Jeff Fongemie" <[EMAIL PROTECTED]> wrote:
>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.
If he's going to preview and edit immediately following the addition of the new text,
you could simply pass the text as form vars to a preview page. If he wants to make
changes, he hits the Back button to return to the form, otherwise he hits a Publish
button to save it to the db...
If he's not necessarily going to add text and preview it in the same session, you
could
save it to the db with a "Status field" in that table. When he's approved it, simply
change the Status (e.g.) from 'Draft' to 'Live'. Set up your live pages to only pick
up
content with a status of Live...This keeps your content in a single table and avoids
the
hassles of two tables for essentially the same content... Only time you might want to
use
a second table is if he needs to be able to take LIVE content and rework it
through multiple work sessions. In that case, you could reference the LIVE record as a
foreign key in your DRAFT table, and when he's done fiddling with the new version,
simply update the LIVE record with the contents of its DRAFT equivalent...
Gene Kraybill
LPW & Associates
Mansfield, PA
------------------------------------------------------------------------------
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.
