Well, in the absence of any interest whatsoever from the forum I solved the problem myself by getting the source of the Text/HTML module and removing the DNNLabelEdit control and replacing it with a simple place holder.  This meant that I had to remove the Update event handler and so lost the 'Click here to edit content' functionality, which was fine - I didn't want it anyway.

There are two points that I think are important here:

I couldn't find the source for the DNNLabelEdit control despite searching the entire source solution.  Does this exist anywhere?

It's very sad to see the such a fundamental part of the CMS becoming less not more standards compliant.  I feel that for such and advanced system (and I think the core and project teams have done a great job) this is one area where DNN is trailing way behind PHP based systems in particular, most of which are fully XHTML/CSS compliant.  Frankly, if I can't make DNN XHTML compliant it is entirely useless for me because we are fully commited to standards compliant sites.

    Rob.

I am looking at updating the tutorial on my site at www.obrienit.se to cover the latest versions  -  but there really hasn't been that much interest in the topic. (Big thanks to the person that made a donation! Cheers Edward!)

I do find this quite disappointing as other open source projects such as Joomla are striving towards both XHTML compliancy and meeting accessibility recommendations. I feel that it will certainly not help DNN in the longer term and will become an increasingly common criticism once the other systems get their house in order. If you take a look at for instance Joomla, it validates as xhtml out of the box. DNN should at least aim for validation - this isn't the same as meeting accessibility recommendations such as avoiding tables for layout. I feel that releasing with a default layout that doesn't validate is akin to shipping code that doesn't compile.

---

www.OBrienIT.se | Free DNN skins in valid xhtml