Works brilliantly when it works. Docs and debug fairly poor.

  • Since I got this working (with some quick and helpful advice from the author) it has worked very well. I love the flexibility of the API/form processor approach, which basically lets you do anything API v3 can do. The functionality is better than the Caldera Forms it replaced and it’s free!

    The catch is it’s really quite difficult to set up because the documentation is incomplete and debugging is difficult (the “API REST Log” extension in CiviCRM looks useful but I couldn’t get it to work).

    The two big “gotchas” that caught me were the example CiviCRM path was wrong for WordPress (should be wp-json/civicrm/v3/rest) and the names of the form fields must match the entity names in the API, some of which (custom fields) are quite hard to discover.

    The problem is, there are a lot of things you have to get right (paths, permissions, API keys, variable names, API and PHP versions) and there are so many permutations of all of these that if it doesn’t work you can spend days and days googling for clues and tearing hair out.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author aydun

    (@aydun)

    Hi Phil
    Many thanks for taking the time to document your experience. If you could create a PR to https://github.com/aydun/contact-form-7-civicrm-integration with any improvements to examples, documentation etc – that would be great.

    As you say, there are lots of things to get right so anything you can contribute to help make it easier is very welcome.

    thanks
    Aidan

    ramblinollie

    (@ramblinollie)

    Thanks for your comment Phil, the details you shared enabled me to return a “Validation successful” message in the plugin settings. What I’m getting though when I make an actual request (using the Boomerang REST client from the Chrome store) is the following message. Do you have any more tips about how to get this working? Thanks!

    {
    “code”: “civicrm_rest_api_error”,
    “message”: “Missing or invalid param \”api_key\”.”,
    “data”: null
    }

    Thread Starter Phil McKerracher

    (@phil-mckerracher)

    I generated the API keys using the “API Key Management” extension in CiviCRM. I think any contact in CiviCRM who is also a user in the host CMS with appropriate permissions can be used to generate the keys you need. I couldn’t quickly find a documentation link for this, sorry.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Works brilliantly when it works. Docs and debug fairly poor.’ is closed to new replies.