On Thursday, 21 June 2012 14:50:47 UTC+10, Morgan Ritchings wrote: > > We had a similar experience with a v9 to v11 hf3 upgrade for a client. > With a mix of publication setting amendments and the upgrade we were able > to cut publication time from 12hours down to about 6 for a fullsite > publication of approx 8gb of html and assets. SmartEdit responsiveness also > "feels" better though this could be purely psychological. I have to credit > OT for a solid release. > > - Morgan > > On Wednesday, 20 June 2012 22:24:22 UTC+10, Christoph Straßer wrote: >> >> In terms of how you build the project there are no changes between 10.x >> and 11.0 aside from RQL-COM-object that does not exist any more. (We did >> not used this in the past.) Our first projects startet with Version 5.6. We >> had to change some details when we migrated vom 9.0 to 10.0 about two and a >> half years ago. >> Between 10.1 und 11.0 there was only one project (out of about 30) where >> we had to do a template-modification. (We used the old MSSOAP-COM object to >> call a webservice and replaced this with a custom rendertag which calls the >> webservice via C#/WCF-Code.) >> We had a problem with large RQL-statements we send to the (new) >> RQL-webservice. .NET / WCF limits the messagesize per default to 8kb. We >> had the modify the web.config. This will be added to future revisions of >> the MS-documentation. >> At the moment there is left one unresolved problem, that affects the >> publication via webservice from MS to DS. It seems like MS "forgets" to >> publish some content´s to the DS. The publishing-report and the MS-Logs say >> all contents have been published. When you look to the DS some of them are >> not there. We try to figur this out since last friday together with the >> OT-support. >> Performance is - compared to the older versions - much improved. (The >> nightly publications of our large projects takes somewhere between 1/2 and >> 1/3 time compared to before. In most (but not all!) usecases a author runs >> through in his daily work the MS responses faster than before.) >> We used a W2K3 Server before and stepped to a W2K8 R2 Server. Some >> changes within the Windows Server may affect you. (eg you have to configure >> your windows firewall to allow FTP-Transfer) It´s not a real problem. With >> some W2K8 Server - KnowHow you should be able to solve them. >> I realy hope OT continues to improve the MS within the next months and >> years. They did much important work at the backend with 11.0 and should >> have paved the way for future versions. There is still much work to do. As >> an example the asset managers did not changed much since 2005 or 2006. >> (inconvenient UI, missing features like multi-upload for authors, only one >> subfolder-level, ....) >> Just ask your questions to specific topics. I´ll try to answer them. > > On Thursday, 21 June 2012 14:50:47 UTC+10, Morgan Ritchings wrote: > > We had a similar experience with a v9 to v11 hf3 upgrade for a client. > With a mix of publication setting amendments and the upgrade we were able > to cut publication time from 12hours down to about 6 for a fullsite > publication of approx 8gb of html and assets. SmartEdit responsiveness also > "feels" better though this could be purely psychological. I have to credit > OT for a solid release. > > - Morgan > > On Wednesday, 20 June 2012 22:24:22 UTC+10, Christoph Straßer wrote: >> >> In terms of how you build the project there are no changes between 10.x >> and 11.0 aside from RQL-COM-object that does not exist any more. (We did >> not used this in the past.) Our first projects startet with Version 5.6. We >> had to change some details when we migrated vom 9.0 to 10.0 about two and a >> half years ago. >> Between 10.1 und 11.0 there was only one project (out of about 30) where >> we had to do a template-modification. (We used the old MSSOAP-COM object to >> call a webservice and replaced this with a custom rendertag which calls the >> webservice via C#/WCF-Code.) >> We had a problem with large RQL-statements we send to the (new) >> RQL-webservice. .NET / WCF limits the messagesize per default to 8kb. We >> had the modify the web.config. This will be added to future revisions of >> the MS-documentation. >> At the moment there is left one unresolved problem, that affects the >> publication via webservice from MS to DS. It seems like MS "forgets" to >> publish some content´s to the DS. The publishing-report and the MS-Logs say >> all contents have been published. When you look to the DS some of them are >> not there. We try to figur this out since last friday together with the >> OT-support. >> Performance is - compared to the older versions - much improved. (The >> nightly publications of our large projects takes somewhere between 1/2 and >> 1/3 time compared to before. In most (but not all!) usecases a author runs >> through in his daily work the MS responses faster than before.) >> We used a W2K3 Server before and stepped to a W2K8 R2 Server. Some >> changes within the Windows Server may affect you. (eg you have to configure >> your windows firewall to allow FTP-Transfer) It´s not a real problem. With >> some W2K8 Server - KnowHow you should be able to solve them. >> I realy hope OT continues to improve the MS within the next months and >> years. They did much important work at the backend with 11.0 and should >> have paved the way for future versions. There is still much work to do. As >> an example the asset managers did not changed much since 2005 or 2006. >> (inconvenient UI, missing features like multi-upload for authors, only one >> subfolder-level, ....) >> Just ask your questions to specific topics. I´ll try to answer them. > >
-- 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/-/fP8zCjzbKZ4J. 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.
