Everything that's at the content class level will be pushed to the child projects. Therefore if you need other elements to be pushed on a new child project i.e : Keyword list, authorization packages, publishing target and structure, workflow, etc. It's better to create a child project we everything in it and copy that project to create new child projects. Then you just have to share all folders from the master project to the new child project. It saves a lot of time.
SR Web Media Inc. Stéphane Ritchot Conseiller Web [email protected] www.srwebmedia.com -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of UberGeekGirl Sent: December-18-08 8:36 AM To: RedDot CMS Users Subject: Re: How do you use master projects and child projects Thanks for all the info!! What about other settings like pre-references, keyword assigments, and list sorts? Do those come with, or do we need to manually do that? Other then having the handy "connection", is this any different then exporting a tempalte and importing it into the second project? Thanks, Ashley On Dec 17, 12:01 am, "Stephane Ritchot (SR Web Media)" <[email protected]> wrote: > Hello Ashley, > We are currently working with a master project and child project since > version 5.5. > > In our master project, we reproduce a mock site to allow us to test the > changes made in our content classes. Then, when satisfied with the result we > push the changes to all child projects. That way we can achieve major > modifications to all our sites by a click of button and then republish them. > > On crucial element that you need to understand is that when doing the update > of the content classes, it does it to the whole folder of that content > class. In other words, if you have content class A and B in the same content > classes folder, when you'll want to push the changes of content class B, > content class A will be pushed too because they both reside in the same > content classes folder. (Hope this make sense the ways I explained it) > > Another thing that works for us is that we are using a file system to store > our media assets. That way we get the versioning option and the size of the > database project is not too high. The draw back, though, is that when you > export your projects, you need to bring the file system with it. > > Hope this help but if you need more information, let me know! > > SR Web Media Inc. > > Stéphane Ritchot > Conseiller Web > [email protected] > > > > -----Original Message----- > From: [email protected] > > [mailto:[email protected]] On Behalf Of UberGeekGirl > Sent: December-16-08 8:50 AM > To: RedDot CMS Users > Subject: How do you use master projects and child projects > > Hi All, > > I know some of you RedDot veterans and power developers have a concept > of Master Project and Child Projects in RedDot CMS. I assume this uses > content class and asset sharing. > > I was wondering if you would be willing to give us bit more > information on how you use these multiple projects together. I am > interested especially in any information you have about how we can > develop/test things out in a master project and only push the changes > to the child project when they are ready... We are currently trying to > figure out the best method of developing while editors are > contributing content (development and migration in parallel). This > method looks much more promising then our current, mistake prone, > solution (just importing the template and re-working everything again) > > Thanks so much for any information! > Ashley- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
