PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

List field error help

  1. Chef2
    Member

    Hello, when filling out the form and I look a the final post the list field does not output as a table, it does rather this:

    a:2:{i:0;a:1:{s:0:”";s:11:”item 3”;}i:1;a:1:{s:0:”";s:16:”item 4”;}}

    With items 1 and 2 missing. Any idea why? Cheers.

    By the way it is set to support multi columns. I will check to see if single columns work.

    Edit - On single column it does this:

    a:3:{i:0;s:9:”item 1”;i:1;s:8:”item 2”;i:2;s:15:”item 3”;}

    Posted 12 years ago on Sunday September 18, 2011 | Permalink
  2. I am using the list field successfully here;
    http://gravity.chrishajer.com/family-reunion-rsvp/

    Do you have an example of where this is not working. I believe you're the second person to mention this, so I'd like to find out what's up.

    Posted 12 years ago on Sunday September 18, 2011 | Permalink
  3. Chef2
    Member

    Yes I'll send you an email with the details. Thank you

    Posted 12 years ago on Monday September 19, 2011 | Permalink
  4. Chef2
    Member

    Anyone?

    Posted 12 years ago on Monday September 19, 2011 | Permalink
  5. I am able to replicate this issue locally. It's an issue with the merge tag replacement. We'll take a look and get it resolved in the next beta release. Until we do that there isn't any fix to correct this, we have to fix it on our end.

    Posted 12 years ago on Monday September 19, 2011 | Permalink
  6. Chef2
    Member

    Any idea when the next beta is due? This feature is a must for my project.
    I'll try to overcome this limitation by just adding several text fields (it ain't gonna look pretty!)

    Cheers!

    Posted 12 years ago on Monday September 19, 2011 | Permalink
  7. We will probably release an update later this week. We will include this fix in that update.

    Posted 12 years ago on Monday September 19, 2011 | Permalink

This topic has been resolved and has been closed to new replies.