Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Nick Ciske

    (@nickciske)

    Do you have a name field? That can cause issues as it’s a reserved query variable in WordPress. It’s fixed in the v3 version on GitHub. I have a fix for the 2.7 branch but haven’t had a chance to release it yet.

    Thread Starter jebraweb

    (@jebraweb)

    Yes, we do have a name field. Within this plugin, it seems like we can’t edit the name of the “name” field or any field. Am I missing something? Do we literally have to start over completely with this form?

    Plugin Author Nick Ciske

    (@nickciske)

    Correct, you cannot edit a field name.

    You can create a new field and simply disable or delete the old one.

    Or you can wait until I release a version that fixes this by prefixing all field names… should be out in the next week or so.

    Thread Starter jebraweb

    (@jebraweb)

    Thank you, Nick — this worked. Now I get my thank-you page AND an email copy of my results, but our Salesforce consultant tells me that a Case is not being generated in Salesforce. Because I have no error on my end and I can see that the form is being successfully submitted, I’m at a loss. Any ideas?

    Plugin Author Nick Ciske

    (@nickciske)

    Turn on debugging and Salesforce should email you with why the “case” is being rejected.

    From the FAQ:

    *I’m not seeing any errors, but the entry didn’t get added to Salesforce!*
    To turn on in browser debugging, add a hidden field (enabled) named debug and set the value to 1.

    To turn on debugging via email, add a hidden field (enabled) named debugEmail and set the value to [email protected] (your email address).

    Also check for debug logs at SalesForce to see if a validation rule is the culprit:
    Administration Setup | Monitoring | Debug Logs

    • This reply was modified 8 years, 3 months ago by Nick Ciske.
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Error on submit’ is closed to new replies.