Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-2948

Docs for v2 API are incomplete


    • Type: Bug
    • Status: Done/Fixed
    • Priority: Major
    • Resolution: Fixed/Completed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.1
    • Component/s: None
    • Labels:


      Several API functions from 1.x changed or were removed after early releases of 2.0. CRM-2691 requested the removal of several 1.x API functions but their replacements are either not yet available, or not immediately obvious.

      Some of the new API docs are not yet complete, making it difficult to migrate to the new API. Where no 2.x API function will be made available to replace the 1.x equivalent, it would be very helpful to have a documented method of using the internal functions to achieve the same functionality.

      Several forum threads indicate that there is demand for this to be resolved:

      Several 1.x API functions were removed a couple of weeks after 2.0 went beta, and we didn't anticipate API functions would be removed at that point.

      I'd be really happy to contribute docs where possible for this issue, but I don't feel I'm familiar enough yet with CiviCRM internals to identify the best way to achieve replacement functionality for the functions which have gone, so I'd want to liaise with other developers who can advise on the best way to document them.




            • Assignee:
              lobo Donald A. Lobo
              xurizaemon Chris Burgess
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: