hmm.. now here's a problem.

I clicked the submit survey button and instead of submitting, a validation error popped up in the feedback form that is on the same page. That form is made in XMOD.. obviously something is crossing over between the forms.. perhaps their names. I'll have a look.

ok.. I've had a look.... I'm afraid this is slightly beyond me.

The previous survey module didn't cause this so it's something new in the beta that is making the feedback form submit and validate.

I'll shift the survey to another page for now until I've heard back here.

Thanks

ROb

Hi Michael,

I can try to confirm that it happens on a second site where I also have an XMOD feedback form and then I'll add a core feedback form to the page and check it with that.

Ok.. yep, when I add simple two-option survey to the same page as the XMOD form, and then submit it, the survey does submit, but the XMOD form also spits up a validation error on the email field.

Now I'll put the survey on a fresh page and add the core feedback module.... Ok, now submitting the survey doesn't cause the core feedback form to validate.

There is definitely some small change in the 4.0 survey over the old version however that makes it do this. I'll go and post this to the XMOD forum in case they can help. I'd expect it to be a name in common somewhere. I only bought XMOD last weekend and the form I'm using is the standard feedback form that is used in the XMOD tutorial with the addition of a dropdown list for the subject.

Rob

I've made a post in the XMOD forum and at the same time hunted and found a thread there that is probably related. I'll email you this as well in case it looks like the right ticket.

Here's the thread: http://dnndev.com/Forums/tabid/215/view/topic/forumid/1/postid/6182/Default.aspx

And specifically this bit:

This is, unfortunately, fairly standard behavior. Some modules - even the core modules - forget to turn off the "causesvalidation" flag on their controls.

When this is on, it causes all controls on the page (not just within the module) to validate. In response to this, I added the ability to turn off client-side validation for controls. You need to use the <validate> tag. Set the "enableclientscript" property to false and the "type" property to "required". See the <validate> tag in the help file for more info.