Or have a 'versions' table attached to the 'page' table. Versions can have
status, with a maximum of 1 'published' for any given pageID, and versions
can have publicationStart and publicationEnd dates. Gives you the
flexibility of rolling back to previous versions as well. Just a thought.
I have done this three ways. I had an edit table (like your temp table) and
that worked fairly well. I did versioning as Jason mentioned, that was a
bit of a PITA. The other way was to use a preview page and I submitted
the form data to the preview page via AJAX and populated it that way. The
My current thought is to use a temp table(s) that:
a. when visiting an edit page - LOADS the live data into the temp table
b. all editing is done in the temp table
c. once he likes it, he can hit the publish button, and the temp data
replaces whatever is currently in the live table.
d.
Most of the case, the user does not want a new item to be published bedore it
is completed.
For existing items, only little adjustements are made and this may be done on
line.
If it is your case, just add some Active logical field in the table and display
the item only if the active flag is
4 matches
Mail list logo
