Have you found a solution for this issue? I'm having exactly the same problem.

Yeah please update to latest WIP version you can find it here

http://nightly.umbraco.org/Umbraco%20Contour/3.0.15%20WIP/

upgrade instructions here

http://our.umbraco.org/projects/umbraco-pro/contour/documentation/Installation/Upgrade

And how is it supposed to be used?

True, Yes, 1 ?

I'm having this issue now with Umbraco Forms 4.1.4 .

I have a checkbox labelled 'Other' that, when checked, should show a textbox. This does not work at all, even with a simple checkbox list.

did you find a solution to this?

Im having the same issue with showing textbox conditionally based on selection of radio-button value on other field.

would appreciate if you can shed some light

Linked to this one too: https://our.umbraco.org/forum/umbraco-forms/80761-problem-with-conditional-fields-not-working. There are quite a few unresolved issues in the issue tracker about conditionals not working.

Not to mention it's a "paid for" licence. Or at least it will be when I see it working properly ;)

Okay, I got this to work for me. It was a problem on my end since I'm using a custom view for front-end rendering. Turns out that it's important to maintain certain classes on the front-end form since they're being used to fetch specific elements in the DOM. Those classes are:

• contourPage
• contourField

I think these class dependencies should really be listed on the doc page, which mentions that Form.cshtml is customizable. Some thought should also be given to decoupling the default styles from these classes.

@Craig100, your issue is different since I can see that your front-end view very closely resembles the original one and includes the classes I listed above. The problem is that you're missing several scripts that should be included with the package. I think something is amiss with your form picker datatype or macro.

This page might give you some clues.

Hi Matthew,

'fraid not. Already have that covered. The only thing I've changed in forms.cshtml is to use ResponsiveBP instead of Bootstrap. Also added a conditional statement to put out the "*indicates madatory field" message (http://issues.umbraco.org/issue/CON-1305). Oh and I'm using more up to date versions of JQuery and the validate scripts, which aren't causing any console errors.

The problem with the conditional action not working has been there out of the box, before I made any other changes and when I was using the script versions declared in the docs (from asp.net CDN).

So you're saying you have conditionals working? Do you have a live example? I'm just about to put some js together to see if I can force it to work.

Unfortunately, I don't have a live version available just yet as we're still in pre-release.

Those jQuery scripts are actually only half of the dependencies. The others are being included by /Views/Partials/Forms/Script.cshtml . They are:

• umbracoforms-dependencies.js
• umbracoforms.js
• umbracoforms-conditions.js

I didn't see those anywhere when I viewed source on your site's form.

It could very well be that those aren't working out of the box, though it's worth noting that Umbraco Forms doesn't actually work out of the box to begin with. Developers are still required to setup a datatype that makes proper use of the form picker. I found documentation to be rather weak in this area, especially when it comes to using the form picker in the grid editor.

I actually found it necessary to include the following snippet in my layout in order to properly load those scripts where I needed them:

@if (TempData["UmbracoForms"] != null)
{
    foreach (var form in (List<Guid>)TempData["UmbracoForms"])
    {
        Html.RenderAction("Render", "UmbracoForms", new { formId = form, mode = "script" });
    }
}

Also be sure to add the mode = "form" attribute in your FormPicker view:

Html.RenderAction("Render", "UmbracoForms", new { formId = g, recordId = recordGuid, mode = "form" });

Hope this helps.

Hi Matthew,

I had the mode="form" thing done, because it was clearly in the docs. The other thing, however, was not. Adding your bit of razor got conditionals working for me, so thank you very much.

A slight complication I faced was the form macro being inserted in an RTE rather than in code in the template. Next I'm going to do a PR on the documentation so it's CLEAR! :)

Then after that I'm going to eat humble pie and comment on a few previous posts ;)

is working on a reply...