Not signed in (Sign In)

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

  1.  
    We are experiencing a problem with one of our forms. We have large drop-down lists with conditional tags and all works well, however once the CSS values start reaching '.onstate-xl' things start to go crazy. The next value is '.onstate-~n', a trend that continues until it then randomly returns to '.onstate-a' for awhile before changing to '.onstate-|a' and then repeating itself. It even begins to use '.onstate-}a', much to the distress of the following CSS as it receives a close tag mid-label.

    We have edited, re-edited, saved, and re-saved this form but always with the same result. It looks to be something automated, are you able to help us?

    http://app.formassembly.com/forms/view/27826
    • CommentAuthorcedsav
    • CommentTimeJul 21st 2008
     
    Yes, sorry about the inconvenience, it's a bug. We didn't think anyone would need hundreds of conditional sections in a single form, so we didn't account for it.

    We have on occasions recommended using conditional sections to simulate dependent lists, but in your case it's really pushing the limits and we need to think of a different approach.

    I've made a copy of your form and I'm going to try a few things. I'll get back to you as soon as possible.

    Cedric Savarese
    FormAssembly.com
  2.  
    Thanks for looking into this mate. We ended up taking a different approach that required less conditional sections. Not as clean, but it is working well. Keep us posted :)