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.

Blank Form loaded in Preview - Corrupt Fields?

  1. I design fairly large forms, that span multiple breaks, and so I use the duplicate field feature a lot.

    I've recently encountered an error which I thought may have been related to server memory, but as it turns out - disabling plugins, increasing memory etc, all didn't seem to help.

    The symptoms are a form which displays perfectly in admin, but displays a blank preview form (still has the header, and message that the page might display differently - but there are no fields or buttons displayed).

    Luckily I update regularly and constantly check using preview so I was able to pinpoint the field which was the problem and it was a problem caused by duplication.

    Why it buggered the form I don't know, but I managed to duplicate a copy of the form with the error causing input field in case you guys wanted to check it out. Just hit me up and I'll give you access to trouble shoot what caused the bug.

    Simply deleting the field fixed the form - but I can imagine this would cause nightmares for people who create lots of forms and end up troubleshooting in the wrong place.

    Posted 11 years ago on Monday August 6, 2012 | Permalink
  2. Can you export the buggered form and email it to me at chris@rocketgenius.com - I'd like to see if I have the same experience on my server. Thank you.

    Posted 11 years ago on Monday August 6, 2012 | Permalink
  3. Emailed! Hope I'm able to help. :)

    Posted 11 years ago on Monday August 6, 2012 | Permalink
  4. Chris has helped me with this issue.

    By accident I put the CSS Ready Class (gf_left_etc) into the Maximum Characters field.

    Removing this CSS Ready Class from the Maximum Characters entry for the other forms fixes the problem.

    Chris also advised that yes, the field should accept integers only, and provide a different warning when bad data is entered.

    Thanks again team.

    Posted 11 years ago on Tuesday August 7, 2012 | Permalink
  5. Thank you for the update. Glad it was a simple solution.

    Posted 11 years ago on Tuesday August 7, 2012 | Permalink

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