We do a lot of work with the DotNetNuke portsl and have been for many years. However, as time goes on the DotNetNuke deliverables have been increasingly more problematic and become quite a burden for any organisation supporting their software.
When DotNetNuke was originally established as a comumity oen source project it was alive with contributors keen to make it great, however since the company has comercialised the management and a paid version they have proved that throwing millions of dollars in areas other than software development does not make a viable product.
While we have sat on the sidelines watching and hoping that lessons would be learnt, we have lost customers and faith in DotNetNuke Corp. and our patience with a string of problematic releases that have destroyed all but the most hardened user.
Today, after another release of DotNetNuke 5.6.2 we are once again disapointed with compatibility with existing installations and fundamental issues being pushed out to the scary c# release some time into the future (6.0)
In addition to core modules either in a constant state of incompleteness, the move to drop fckEditor in favour of the Telerik editor has produced one of the most user visible controls as one of the worst choices by DNN Corp, While the Telerik editor tries to be all things to all people it is difficult to use and pretty much impossible to get the expected results. Based on Teleriks community editor, It is safe to say that we would keep away from their commercial offerings.
So, in an effort to solve our customers pains, we went searching for a way to throw away the Telerik HTML Editor once and for all and as luck would have it we found the CKEditor. CKEditor was a breeze to install and users immediately liked what it delivered.
Subscribe