Unfortunately there is no other way, which would be recommended by RedDot. Richard was working or talking about such a solution earlier. The problem here is that you can't easily use a versioning system like SVN. It would work with updated for the HTML in a content class. But when it comes to renaming elements or updating their attributes you still require to interact manually with RedDot.
On 19 Aug., 05:12, Nick Galotti <[email protected]> wrote: > Over the years we have learned the hard way that developing RQL on the > production RedDot server isn't a good idea because it could > potentially require a reboot. We are thinking of developing templates > in a development RedDot server but we don't know the best way to bring > the developed code/content classes over to production, especially for > upgrading existing content classes. > > We are aware of exporting/importing content classes, but is this the > best way? What about when developing large amounts of code? > > Does anyone have experience in this? > > -Nick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
