OroCRM Forums

Covering OroCRM topics, including community updates and company announcements.

Forums Forums OroCRM OroCRM – Installation/Technical Issues or Problems Using request of type 'patch' to update a user's profile fails from web client

This topic contains 4 replies, has 2 voices, and was last updated by  stef 7 years, 4 months ago.

Starting from March 1, 2020 the forum has been switched to the read-only mode. Please head to StackOverflow for support.

  • Creator
    Topic
  • #27442

    stef
    Participant

    I get this error when calling the api call api/users/1
    to update a user:

    {“code”:500,”message”:”Processor failed: \”oro_api.get_metadata.load_metadata\”. Reason: Class users does not exist”}

    The weird part is, this call succeeds when called from curl.

    The payload is as follows:

    Any suggestions on how to resolve this would be greatly appreciated!

    Stef


    Dream, in a pragmatic way.
    — Aldous Huxley

Viewing 4 replies - 1 through 4 (of 4 total)
  • Author
    Replies
  • #27443

    stef
    Participant

    I also get this message, sometimes:

    The group "normalize_data" is not defined. Processor: "oro_api.create.load_normalized_entity".<br />
    Thanks!


    Dream, in a pragmatic way.
    — Aldous Huxley

    #27444

    Mike Kudelya
    Participant

    Hi

    It is very strange, i have tried your json with PATCH method via curl_exec function and successfully updated my entity. Can you put this code there and show me the result ? Which version of oro are you using ?

    #27445

    stef
    Participant

    Hi Mike,

    Here is the stack trace:

    * Of interest is the other error message that is returned:

    {“code”:500,”message”:”Processor failed: \”oro_api.get_metadata.load_metadata\”. Reason: Class users does not exist”}

    * Also, when the request is made from Curl, the class loaded in MetadataPovider::getMetadata() is:

    When called from external source:

    Stacktrace:


    Dream, in a pragmatic way.
    — Aldous Huxley

    #27446

    stef
    Participant

    UPDATE: Issue is resolved.

    The client code had semi-colon at the end of the content-type header.

    PS: Big thanks to Mike for the debugging cue.


    Dream, in a pragmatic way.
    — Aldous Huxley

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

The forum ‘OroCRM – Installation/Technical Issues or Problems’ is closed to new topics and replies.

Back to top