Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • I continue to have to retain legacy Caldera Forms 1.5.0.6 for Contact Form DB to be able to successfully access data submitted in my form.

    I too have been having an issue using both Contact Form DB (CFDB) and Caldera Forms (CF), starting with CF version 1.5.0.7. I had to fallback to using CF version 1.5.0.6 with the latest version 2.10.29 of CFDB. The data from the CF entry fields were no longer transferring over to CFDB from CF but work fine after I revert to CF 1.5.0.6.

    Why do I use both? I combine the two to achieve a random sampling of submitted surveys for a drawing for prizes at a live event each month. We want to encourage feedback for the meeting, so people have to submit a survey that includes a ticket number from a carnival style ticket given to them at check-in. The drawing is performed automatically and a list of 30 numbers is posted on a private web page for the meeting host to call announce the winning numbers. Here’s the CFDB shortcode I use on results page:

    [cfdb-table form=”Monthly Meeting Survey” show=”Please enter your white ticket number for the drawing.” random=”30″]
    [/cfdb-table]

    Thread Starter johndkent

    (@johndkent)

    Thank you for your reply. Yes, my client’s user list does have some frequent email changes each month via the parent organization.

    Also I noticed that when I perform manual user sync some errors are occurring. I’m thinking there’s an issue with the regex for valid email addresses:

    18:53:20 Updating #145 ddddd < xxx_yyy@mcafee.com>
    18:53:20 Error: Bad Request. xxx_yyy@mcafee.com looks fake or invalid, please enter a real email address.

    18:58:44 Updating #780 ddddd <xxxx.y.zzzz@usace.army.mil>
    18:58:45 Error: Bad Request. xxxx.y.zzzz@usace.army.mil looks fake or invalid, please enter a real email address.

    Thank you

Viewing 3 replies - 1 through 3 (of 3 total)