• Resolved bsmolyanov

    (@bsmolyanov)


    When the v. 1.6… versions started coming out I withheld from updating initially. Then, yesterday, I saw already v. 1.6.4 – Fixed a bug related to custom REST API endpoint – has already come out, and I decided to finally update directly to it.

    However, now in my scenarios I started seeing the following error, exactly in modules which call custom REST API endpoint, e.g. deletion of custom post taxonomy relationship.

    IMLError
    Function ‘displayError’ finished with error! Cannot read properties of undefined (reading ‘toString’)

    Please consider debugging the plugin once again. I am happy to provide additional information on my setup, in case this will help.

    The same WordPress setup worked without problems before the Make Connector 1.6…. update.

    • This topic was modified 8 months, 1 week ago by bsmolyanov.
Viewing 6 replies - 1 through 6 (of 6 total)
  • davidgurr

    (@davidgurr)

    Hi. Thanks for reporting this.

    We’ve just updated the WordPress app in Make to include better error handling and error messages.

    Could you try again? You should see an error message that gives more details on the source of the problem.

    Thread Starter bsmolyanov

    (@bsmolyanov)

    Hi, David,

    Since several days the error says:

    • [400] Invalid JSON in request body: Syntax error (error code: rest_invalid_json)

    However, nothing in the way the value (post ID) passed to Make.com has been changed on my side (in WordPress).
    Moreover, in the Make module itself there is nothing in the body. The post ID is passed as part of a custom REST API end point, like “posts/postID/delete-terms” where the postID if the variable from Make and ‘delete-terms’ is the custom end point, registered in WordPress via PHP code.
    Therefore I am not able to see what json is being sent/received.

    • This reply was modified 8 months ago by bsmolyanov.
    davidgurr

    (@davidgurr)

    Are you on a paid plan? If so please create a ticket from the Make Scenario Builder screen – click the “?” icon at the bottom left and follow the prompts.

    Thread Starter bsmolyanov

    (@bsmolyanov)

    It appears that I just had to add empty {} in the body of the API call and that resolved the issue.

    davidgurr

    (@davidgurr)

    Thanks for confirming. Which module of the WordPress app in Make were you using? Make an API Call?

    Thread Starter bsmolyanov

    (@bsmolyanov)

    Yes, exactly, the Make and API Call. The “Body” parameter was not filled-in and this caused the error. However, previously this was not an issue. Now, I inserted {} in the body and the error is gone. Method is POST.

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

The topic ‘Function ‘displayError’ finished with error!’ is closed to new replies.