Sessions don't expire when the browser closes, unless you force them to.
So you could keep this info in session even across browser sessions.
Regards
Dale Fraser
http://dale.fraser.id.au
http://learncf.com
http://flexcf.com
-Original Message-
From: cfaussie@googlegroups.com
Mike Kear wrote:
A question for those who have CMS systems
How do you folks handle previews?The preview function in my CMS is
less than perfect and I'd like to do it better.
...
Another method i've seen is having the CMS working entirely from a
preview table, which is a
I'm using an almost identical method. Something like this (although I've
tried to improve up the column names a bit because on my actual schema they
are not as good as they could be ;-)
--
-- Table structure for table `cms_page`
--
CREATE TABLE `cms_page` (
`PAGE_ID` int(11) NOT NULL
FarCry does this by adding status and versionid fields to a content type.
Status to indicate which data is live / pending / draft, and versionid to
link draft content to live content. This means that any given piece of
content can have two versions in the database (our workflow doesn't allow
both
