And does the UI remember your choice? Maybe due to some core changes in Umbraco will check

And page is published right? That you are sending to?

If by UI you're thinking about whether or not the setting in Contour is remembered? Then yes it is :)

And yes the page is published since it's pointing to the frontend of the site.

Thanks Tim.

Cheers, Jan

Ok will have to check it then, will try to reproduce

Hi Tim,

The UI doesn't remember the selected/filled in values and the page it should be sending to is published correctly.

When we click on the submit button, it posts to the same page (or it looks like it does, since the page blinks), but no entries are registered.

We have though discovered that after we submit, if we recycle the app pool and then resend the form (that would mean: first submit, second refresh -> which should cause a re-submission), it works. And it looks like upon re-submission after recycling, the entries are also registered..

Best,

Iulia

Ok so it doesn't remember the selected page, that would be the problem then, looking into it, as a temp workaround you could just update the value in the db (sendtopage column on ufform table)

Hi Tim

YES! It DOES remember the page we select. The UI Iulia is referring to is the form fields rendered on the frontpage.

On the "Settings" tab on the form the selected page is remembered and the page is published.

Sorry about the confusion.

/Jan

Thanks Jan :) Sorry Tim :P

Ok no worries, taking a look tomorrow so more details then :)

Jan, are you by any chance using code first to create your forms?

We've been experiencing similar issues using code first

http://issues.umbraco.org/issue/CON-523

Hi Rasmus

Good input - but unfortunately not. I'll give the issue a vote anyhow.

/Jan

I have also just run into this issue (version 3.0.18). Message on submit works but not Send to page (the only effect Send to page has is it effectively disables the Message on submit).

Hi,

Any news?

/Iulia

Looking into it... update later today :)

Works fine on Umbraco 7, just tested 

Will try on v6

Test latest Contour on 6.1.6 and that also works fine... so not sure what is going wrong... maybe you have a workflow attached that is doing a redirect? Also make sure you don't have a value for the xpatch setting (when sending to a page) 

Could you send me the site tg at umbraco dot come then I can debug

Hi Tim

Thanks for getting back to us. We don't have a workflow that does any redirecting as far as I know.

But we'll see if we can provide you some access to the site on monday if you don't mind? Just saw your reply now...and now it's a little late...right? :)

Have a nice weekend mate!

/Jan

Just tested with Jan and Iulia's site and it works fine, if I preview the form it does the redirect... just make sure you don't have nested forms and that you are not redirecting to the page the form is on...

So must be something with the markup on the site, make sure you don't have nested forms..

Hi Tim

Thanks for your response and for looking into this.

This morning I just gave Contour a spin on a fresh install of Umbraco 6.1.6 rendering forms using @Umbraco.Field() on the template and it worked fine. Tested using Webforms and MVC. No problems.

Then I had a look on another client of ours where the functionality is working fine too...The thing is...where using an XSLT file to render the page.

On the client where it all works fine we're using the umbraco.library:Item extension in order to render content from the rich text field and ensuring that macroes can be rendered. The client where this is working is running Umbraco 4.11.10

<xsl:value-of select="umbraco.library:Item($currentPage/@id,'content')" />

But this snippet does not work since the release of Umbraco 6.1 so we've changed it to use the umbraco.library:RenderMacroContent extension instead like this

<xsl:value-of select="umbraco.library:RenderMacroContent($content, $currentPage/@id)" disable-output-escaping="yes"/>

I suspect that this is where things go wrong for some reason - Could you try and have a look at this scenario? Is there an easy workaround?

I should mention that most of the page-rendering is structured in this particular XSLT file so it's not an option for us to refactor using Razor or @Umbraco.Fields at the time of writing.

Looking forward to hearing from you.

/Jan

is working on a reply...