About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

WordPress "missing the required permission_callback argument" error

  • 27 October 2021
  • 1 reply
  • 408 views
L

I’m having the same issue of this post. 

 

is there any update on the matter?

ERROR:

register_rest_route was called incorrectly. The REST API route definition for zapier/v1/token is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.)

icon

Best answer by SamB 1 November 2021, 14:14

View original
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

1 reply

SamB
Rank
Userlevel 7
Badge +11

Hey @lucacapula,

Welcome to the Community and thanks for reaching out about this! :)

I’ve checked on the bug report that was discussed in that other post and it looks like the issue is still open. I don’t have an ETA on when it will be fixed but I’ve added you to the list of users affected by this. We’ll notify you by email as soon as it’s sorted.

As noted in the other post, the integration itself appears to still be running correctly despite this error being surfaced in the WordPress debug logs. 

Terms & Conditions