• Resolved antoninlr

    (@antoninlr)


    Since the new update I keep getting this error on form submission:

    ERROR: Contact Form 7 > Mailchimp API Error: Bad Request. Invalid Resource. The resource submitted could not be validated.
    – ip_signup : This value should be of type string.

    I’m connecting contact form 7 and mailchimp with the hidden input
    <input type=”hidden” name=”mc4wp-subscribe” value=”1″ />

    Please help!

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Lap

    (@lapzor)

    Hi,

    What is the exact version number of your MC4WP plugin?

    Thanks for letting me know.

    Thread Starter antoninlr

    (@antoninlr)

    Right that would probably help..
    Version 4.8.9 on a 6.0.2 wordpress
    Thanks for the quick response!

    Plugin Author Danny van Kooten

    (@dvankooten)

    Hi @antoninlr,

    Is that the complete message from your debug log? If not, could you please include the full request body from the debug log so that we can see what IP value the plugin was trying to send to Mailchimp?

    Thread Starter antoninlr

    (@antoninlr)

    Here is the complete message:

    [2022-09-15 09:36:03] ERROR: Contact Form 7 > Mailchimp API Error: Bad Request. Invalid Resource. The resource submitted could not be validated.
    - ip_signup : This value should be of type string.
    Request:
    POST https://us17.api.mailchimp.com/3.0/lists/78b12a736d/members
    {"status":"pending","email_address":"cont***@an***********.com","interests":{},"merge_fields":{},"email_type":"html","ip_signup":false,"tags":[]}
    Response:
    400 Bad Request
    {"type":"https://mailchimp.com/developer/marketing/docs/errors/","title":"Invalid Resource","status":400,"detail":"The resource submitted could not be validated. For field-specific details, see the 'errors' array.","instance":"d05fd2ab-5aef-1f58-8e6e-0bd7af34a27d","errors":[{"field":"ip_signup","message":"This value should be of type string."}]}
    Plugin Author Danny van Kooten

    (@dvankooten)

    Thank you @antoninlr,

    If you update to version 4.8.10 (just released) then this should be fixed.

    Thread Starter antoninlr

    (@antoninlr)

    Aw man my bad, I updated on the 14th, and you must’ve deployed the newest update a bit later..
    Thanks for the great support and sorry for wasting your time!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Bad request error since newest update’ is closed to new replies.