• Resolved Flexer

    (@flexer)


    Debug Log
    ==
    [2020-07-14 12:31:28] API.INFO: ConstantContact_API::add_contact:522 – http.status.conflict – There was a conflict between the supplied data and the existing resource. [] []
    [2020-07-14 12:31:28] API.INFO: Submitted contact data [“Extra information”,[{“first_name___14885d6e33eb9aa248dc1bf153649bcd”:{“key”:”first_name”,”val”:”XXXXXX”},”last_name___c881df591efd168b7e99246c7cdc864b”:{“key”:”last_name”,”val”:”Flexer”},”email___faa30048c92b977e5dfad10947f448d7″:{“key”:”email”,”val”:”***@flexer.ca”},”email”:”***@flexer.ca”,”company___cd9ba73de806bce9c408b1337ca1be7f”:{“key”:”company”,”val”:””},”custom_text_area___1d245fb62b2c755cf0488c33037f68df”:{“key”:”custom_text_area”,”val”:”Test”},”list”:”1482254953″}]] []
    ===

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Constant Contact

    (@constantcontact)

    Hi @flexer

    If at all possible, and hopefully any email notification received can be checked, can you see if this email address is perhaps pending or already on the list in question?

    I’m checking around and the error at the top seems to be indicating that it’s trying to potentially update a contact but is being rejected due to data conflicts.

    Thread Starter Flexer

    (@flexer)

    As the full email address is removed we cannot tell!
    (We are testing the form with various unique emails at my domain flexer.ca)
    > Could data such as compnay name fail if repeated for different email addresses?

    > Is using the form without a subscription request for someone that is already sign up. https://magiclite.com/contact/ Does that fail?

    See this from another site using the same CC account but a different list
    ==
    [2020-07-14 11:57:03] API.INFO: Contact set to be updated [“Extra information”,[{“form”:”Contact Page”}]] []
    [2020-07-14 11:57:03] API.INFO: Submitted contact data [“Extra information”,[{“first_name___14885d6e33eb9aa248dc1bf153649bcd”:{“key”:”first_name”,”val”:”Daveed”},”last_name___c881df591efd168b7e99246c7cdc864b”:{“key”:”last_name”,”val”:”Flexer”},”email___faa30048c92b977e5dfad10947f448d7″:{“key”:”email”,”val”:”***@flexer.ca”},”email”:”***@flexer.ca”,”company___cd9ba73de806bce9c408b1337ca1be7f”:{“key”:”company”,”val”:””},”custom_text_area___1d245fb62b2c755cf0488c33037f68df”:{“key”:”custom_text_area”,”val”:”Test”},”list”:”1739048028″}]] []
    [2020-07-15 01:12:28] API.INFO: Contact set to be updated [“Extra information”,[{“form”:”Footer Email Only”}]] []
    [2020-07-15 01:12:29] API.INFO: ConstantContact_API::add_contact:522 – http.status.conflict – There was a conflict between the supplied data and the existing resource. [] []
    [2020-07-15 01:12:29] API.INFO: Submitted contact data [“Extra information”,[{“email___dd9bc7c046c0a3677d08c15b45f61e4c”:{“key”:”email”,”val”:”***@flexer.ca”},”email”:”***@flexer.ca”,”list”:”1739048028″}]] []
    [2020-07-15 01:57:33] API.INFO: Contact set to be created [“Extra information”,[{“form”:”Footer Email Only”}]] []
    [2020-07-15 01:57:33] API.INFO: Submitted contact data [“Extra information”,[{“email___dd9bc7c046c0a3677d08c15b45f61e4c”:{“key”:”email”,”val”:”***@flexer.ca”},”email”:”***@flexer.ca”,”list”:”1739048028″}]] []
    ====

    Plugin Author Constant Contact

    (@constantcontact)

    Let me reach out to some people to get some more insight on this error in question. Stay tuned.

    Plugin Author Constant Contact

    (@constantcontact)

    Very sorry for the delay here.

    I’ve been told by our API developer team that this error typically happens in one of two situations. One, if the contact is already an existing contact and you try to POST to create a new one. And two, if a contact exists already and is in a type of confirmed state that prevents the account owner from making changes.

    This would also be the error returned if you tried to create a list with the name of an existing list as well. However, not the case here, as we’re trying to create contacts for your list(s).

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Warning’ is closed to new replies.