Hi there, Working on a new project, we're struggling with how to best organise things so we can develop new functionality (mainly template updates, but also some content changes) whilst on-going content updates continue to take place. There seem to be a number of options, none of them really solving the problem.
Publication targets might be workable, but they run the risk of content publishing out in the middle of a development phase, with half- finished functionality. I'm also unsure as to whether or not different publishing targets can be access controlled to ensure someone who can publish out to a 'test' site cannot publish out to a 'live' site. Multiple projects (using the master/child mechanism) would seem to solve the above problems, but have the additional problem of keeping everything in sync. Template updates can be synchronised fairly successfully (although the mechanism is hardly sophisticated) but content updates are a whole other ball game. Even if the fairly manual process can be restricted to a reasonable frequency, there appears to be a bug whereby references are not correctly exported/imported. Is anyone aware of that issue? In short, does anyone out there have an approach for having several 'branches' of a project on the go at a given time that actually works for them in practice? Many thanks in advance, - Bobby --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
