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.
Currently, I'm storing all the changes users make in the session scope, then when they click 'preview' they get a combination of the live page data and the changes that are in session. This has a couple of problems - actually assembling the preview page requires quite a few steps because the data is coming from the database and the session scope, and the other problem is that if the user closes his browser or the session times out, all the updates are lost. Another method i've seen is having the CMS working entirely from a preview table, which is a duplicate of the 'live' table. Changes are written into the preview table and previews are assembled from that. When changes are committed to the live site, they are copied across from the preview table. I'm looking for some advice about how the rest of you handle preview functions in applications like CMS systems. How do you handle this? -- Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
