I pasted the generated mark up of Dynamic forms into the W3C validator and recieved 274 validation errors! My form isn't that large either, only 16 fields.

Most of them are easy, easy fixes: misformed tags, unclosed tags, captilization.

Is there any explination for this, or any way to make the code validate? It is the only part of my site that isn't xhtml compliant.

I'm hoping that Data Springs can shed some light on this. Is making the generated markup validate a priority? I think this module is superior to the others on the market, but I cannot use it if the end result doesn't even pass xHTML transitional.

You could literally fix this in about 2 hours

Hi Erik,

I know that we have fixed several items that were not xHTML transitional as they have been brought up to us.... so if you can give us specific examples we can review those more specifically. For example I know we changed BR tags that were hard coded to the correct /> syntax etc...

In some cases though this is difficult, even running this validator check against google.com, and microsoft.com gives you an many errors (or at least it used to). I just ran a quick test and it shows 355 errors on Microsoft.com. Not saying that we shouldn't be correcting these and sorry for the late follow up to this post, but if you give us some specifics we can fix them item by item and work towards fixing as many as possible.

-Chad

While I appreciate the offer to validate your code, but I'm a little swamped at the moment with other projects.

I think the best place for you to start is with building a form with all the options and elements, a "kitchen sink" if you please. And run the generated source through the w3c validator. You'll need a complaint skin to test on, but I haven't found any pages on this site that are XHTML compliant. (Perhaps DataSprings should purchase a compliant skin from snowcovered to test with?). Go to http://validator.w3.org/, and paste the page source in the direct input tab. I always start at the top of the error list and revalidate after each correction. Sometimes correcting 1 issue will fix a dozen errors.

Here's another thread from a different user.
http://www.datasprings.com/Products...aspx#11982

Here's my stance, I can't use Dynamic Forms, or any module, that breaks validation for my site. It's a professional standard, pure and plain, that is widely adopted and followed in the industry. FormMaster does validate by default, and although the product hasn't had updates in over 2 years, it works and I don't have to spend time cleaning up other developers code.

I hope you can appreciate this position. Compliance is often requested by clients (we do it regardless if they request or not) and in our best interests as web developers.

Thanks for your comments Erik,

We will continue to test this against future versions to see when we can correct and fix any related compliance issues. Possibly the best way would be to test with just the ModuleID in printer friendly mode... This way we are not referencing anything within DNN or a DNN skin and referencing just our module code that generates the form.

Thanks again for your feedback.

-Chad

I'm also struggling to get the form to validate to W3C standards.  Main issues are