API errors since version 6.21 and 6.21.1

  • Resolved paulbnl

    (@paulbnl)


    9 months, 3 weeks ago

    After submission I use the API plugin to send data from A to B.
    V6.20 everything works fine.
    At the same time that 6.21 causes the spam issues my api calls also started to fail.

    I now get error 409 conflict on several fields. After rolling back to 6.20 on the receiving end (site B) all works fine. The same errors also appear on 6.21.1.

    Here is part of the log:

    {
    "headers":
    {
    },
    "body": "
    {
    "code": "frmapi_validate_entry", "message":
    {
    "field2763": "Original question text removed for privacy? is invalid", "field334": "Original question text removed for privacy? is invalid", "field375": "Original question text removed for privacy? is invalid", "field380": "Original question text removed for privacy"
    },
    "data":
    {
    "status":409}}", "response":
    {
    "code":409,"message": "Conflict"
    },
    "cookies":[],"filename":null,"http_response":
    {
    "data":null,"headers":null,"status":null}}

    Should I send in a support request on formidable site or is this ok here?

    • This topic was modified 9 months, 3 weeks ago by paulbnl.
    • This topic was modified 9 months, 3 weeks ago by paulbnl.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Njones35

    (@njones35)

    9 months, 3 weeks ago

    Hi @paulbnl,

    Could you please open a ticket in our helpdesk here? https://formidableforms.com/new-topic/

    We’re only allowed to support the Lite plugin here, and since the Pro API add-on is involved, the WordPress moderators mightn’t be happy if we try to resolve it here.

    Thanks for understanding!

    Best,
    Nathanael.

    Thread Starter paulbnl

    (@paulbnl)

    9 months, 3 weeks ago

    Ok will do!

    tnx

    Thread Starter paulbnl

    (@paulbnl)

    9 months, 2 weeks ago

    Solved. Caused by Radio buttons not matching multiple values between sites. Used to be no problem and handy for translating form submissions.
    See= changelog 6.21:
    New: Option values are now validated by default. If this causes issues with custom logic, this can be reverted using add_filter( ‘frm_option_is_valid’, ‘__return_true’ );.
    Solution:
    Either make sure the values match exactly on both sides or use snippet
    add_filter( ‘frm_option_is_valid’, ‘__return_true’ );
    See https://formidableforms.com/knowledgebase/frm_option_is_valid/

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

The topic ‘API errors since version 6.21 and 6.21.1’ is closed to new replies.

Tags