I agree with Stefan, exporting the project as disk files seem to be the best option available, if you ever intended to roll things back project-wise.
One of the first thing I do with a CMS project is define a user job to export the project at regular interval. On Tue, Oct 6, 2009 at 3:27 AM, Stefan Buchali <[email protected]>wrote: > > I would use the RedDot export project function instead of a database > backup. > The project databases are bound to a their RedDot version, so I don't > know what happens if you try to roll back the project database after > having upgraded RedDot to a higher version. > The RedDot project import function, however, is downlevel compatible, > so there will be no problem afaik. > > The built-in versioning is either page level or content class level. > There is no roll back to a certain date. > > Content class versioning can be activated at the "General project > settings" node. > > > Regards, > Stefan > > > -- 646-807-8683 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en -~----------~----~----~----~------~----~------~--~---
