Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • WordPress WordPress
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • WordPressWordPress
  • Issues
  • #72
Closed
Open
Created Aug 30, 2020 by ryan_cog@ryan_cog

register_rest_route was called incorrectly, missing permission_callback argument via wp-cli

Several CiviCRM REST endpoints are being registered incorrectly with WordPress. The following messages occur when using wp-cli with Wordpress 5.5 and CiviCRM 5.28.3:

PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/url</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/url</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/open</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/open</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/authorizeIPN</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/authorizeIPN</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/ipn</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/ipn</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/pxIPN</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/pxIPN</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/cxn</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/cxn</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/widget</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/widget</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/soap</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>civicrm/v3/soap</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /var/www/htdocs/wp-includes/functions.php on line 5225
Edited Aug 31, 2020 by kcristiano
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking