To address the initial question, and to expand on Richards comments, the answer here is that you should not try to have CMS generate pages in such a way that your old URLs are still valid. The old URLs need to still work, but trying to get a new CMS to conform to your old URL rules is going about things the wrong way. Use URL rewriting to capture the old URLs and remap them to your new CMS-generated URLs. Exposing this mapping in the CMS is ideal, but even doing it manually is feasible (at least for small to medium sites).
Best, - Eric On Sep 22, 8:51 am, bobbykjack <[email protected]> wrote: > I was going to add a note about the "bit hard to explain to authors" > aspect myself. Don't underestimate the training cost associated with > the use of target containers. Try explaining Target Containers to an > author who is not technically minded and whose only experience of > producing content is in MS Word. Then try describing what it means to > assign a Target Container to a link. And, for good measure, try > explaining the Target Container's role in your URL format. > > Some of this can be mitigated by preassigning content, but I believe > you will run into these issues eventually. Although I haven't tried > it, having only worked on an existing RedDot project before, rather > than starting one from scratch, I believe that it would be simpler to > create appropriate content classes and have all pages built 'in full', > with common content (e.g. headers / footers) preassigned at the > content class level. > > - Bobby > > On Sep 18, 9:34 am, "Richard Hauer (5 Limes)" > > > > <[email protected]> wrote: > > @Wayne > > > I would certainly not use target containers (TC) over NavMgr in most, > > all or even many cases. In fact we almost always use NavMgr these > > days because it's more intuitive for implementation leading to fewer > > implementation issues, and it's more intuitive to the authors who need > > to see it every day. The best reason to use NavMgr though is that it > > is the primary means of navigation in v10 SmartEdit. > > > Having said that, if you already have a functional TC site I would > > certainly not give it up to arbitrarily use NavMgr. For smaller > > sites, or where the navigation is not particularly complicated, a TC > > model is just as easy to manage and will execute (build/view/publish) > > faster than a NavMgr equivalent. You can't argue that, because NavMgr > > adds dozens of levels of additional processing before, during and > > after the construction (build-phase) of each page, so whatever price > > you pay for TC you pay more for NavMgr. > > > The key is not to wreck yout advantage by using NavMgr anyway to do > > procedural code in the template, cause then you pay for both! > > > The sum up is this, TC is a perfectly valid implementation model with > > 2 drawbacks: it's a bit limited in what you can do and it's a bit hard > > to explain to authors. If you don't need something it can't do and > > you don't have gumby authors you should have a fine time with TC. > > Before NavMgr we had nothing else and the sky didn't fall in. > > > HTH. > > > Regards, > > Richard Hauer > > ==================== > > 5 Limes Pty Limitedwww.5Limes.com.au > > > On Sep 18, 12:39 am, Wayne Bouwmeester <[email protected]> > > wrote: > > > > @Richard > > > I find your perspective intriguing, considering your posts through the > > > years show you really know your stuff an implementer. > > > > Are you saying that you would try to use target containers over > > > NavManager in most if not all cases? Or is that just with more simple > > > projects where you don't get into deep navigation issues? Do you base > > > this decision mainly on efficiency of publishing? > > > > I find that clients have a hard time understanding how target > > > containers and/or nested lists work, so going with NavManager makes > > > the project easier to maintain for them. Plus you get the navigation > > > index that you can do a lot with. > > > > Wayne. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
