Congrats too. Many of the 7.5 to 10.1 upgrade blocker still applies:
1. reddot cannot be within rendertag 2. container cannot be used pull in css or js by enabling "Insert placeholder for page in container" in the css/js template property 3. if css/js is managed as content class and referenced via anchor in Management Server, this http://simplyreddot.blogspot.com/2011/12/managing-js-css-xml-as-content-classes.html 4. RQL preexecution within template code To 11 1. If still using ASP RQL, change to new COM object in object connection string. That's it. All of them shouldn't even be a problem if best practices from 7.5 are followed. -Jian On Monday, June 18, 2012 5:11:40 PM UTC-4, b_l wrote: > > Do you have time to outline any gotchas that you came up against while > migrating? > > On Saturday, June 9, 2012 5:08:00 AM UTC-4, Christoph Straßer wrote: >> >> Migrated our old productive WSM 10.1 SP2 / W2K3 - system yesterday to a >> new W2K8 R2 with WSM 11.0 HF3. (Have about 30 projects, some of them are >> pretty large.) Almost everything looks good so far. At least compared to >> the older versions. ;-) >> We are looking forward to next week, when our authors / content editors >> start working with the new 11.0 - system. Personal feeling is good, but you >> never know whether users raise some (error-)conditions no one expected >> before... > > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/niV0juFmo5AJ. 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.
