This one blows me away.

Who decided to start automatically injecting class names into every module instance? And worse.. why on earth would they inject the module's unfriendly name and not at least the desired friendly name as applied by portal hosts?

Yes, I appreciate the ability to target modules with styles, but do it with some forethought. My page source is now all full of garbage classes.. it's just a mess.

It gets even worse because of the way it constructs the class using the module developer's silly name plus the word "Content". When a module does not have a name, and this happens when a module is injected using ctl.. i.e. the login, registration, terms, privacy and so on... the resulting class name becomes "Content" which just happens to be a very popular class elsewhere in skinning and is already in use all over the place. Took me a while today to figure out why my skins had all gone bananas.

How can I disable this nightmare?? It is being done in one of the vb files somewhere? I'm looking hard.

Thanks for any advice on this one
Rob

Here's anotehr reason to turn it off - Illegal characters - Developer uses an ampersand in the modulesillyname and the page no longer validates, and/or the desired styling fails. The framework really has no place adding this stuff in this manner.

Exactly.. it's easy to add automatic class injection in skins and I've been doing so all along for unique per-page classes. However, I learned very quickly to never use a construct based on page names, and instead I use the tabID, which is always unique and never illegal.

But yes, the simple truth of the matter is that the application framework should not be inserting anything like this automatically.. It's a decision for skinners to make and apply.

If it turns out there's no means of disabling it, I'll go ahead and put a ticket in with a request.
Regards,
Rob