Title: Reset API Route errors
Last modified: February 12, 2021

---

# Reset API Route errors

 *  [regisit](https://wordpress.org/support/users/regisit/)
 * (@regisit)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/reset-api-route-errors/)
 * Since update to WP 5.3, getting numerous warnings in debug for POS like the following:
 * [12-Feb-2021 15:28:58 UTC] PHP Notice: register_rest_route was called **incorrectly**.
   The REST API route definition for `wc-pos/application/support` 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](https://wordpress.org/support/article/debugging-in-wordpress/)
   for more information. (This message was added in version 5.5.0.) in /var/www/
   vhosts/…/httpdocs/wp-includes/functions.php on line 5229
    [12-Feb-2021 15:28:
   58 UTC] PHP Notice: register_rest_route was called **incorrectly**. The REST 
   API route definition for `wc-pos/application/heartbeat` 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](https://wordpress.org/support/article/debugging-in-wordpress/)
   for more information. (This message was added in version 5.5.0.) in /var/www/
   vhosts/…/httpdocs/wp-includes/functions.php on line 5229 [12-Feb-2021 15:28:58
   UTC] PHP Notice: register_rest_route was called **incorrectly**. The REST API
   route definition for `wc-pos/application/allowed_location` 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](https://wordpress.org/support/article/debugging-in-wordpress/)
   for more information. (This message was added in version 5.5.0.) in /var/www/
   vhosts/…/httpdocs/wp-includes/functions.php on line 5229 [12-Feb-2021 15:28:58
   UTC] PHP Notice: register_rest_route was called **incorrectly**. The REST API
   route definition for `wc-pos/groups` 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](https://wordpress.org/support/article/debugging-in-wordpress/)
   for more information. (This message was added in version 5.5.0.) in /var/www/
   vhosts/…/httpdocs/wp-includes/functions.php on line 5229 [12-Feb-2021 15:28:58
   UTC] PHP Notice: register_rest_route was called **incorrectly**. The REST API
   route definition for `wc-pos/groups/ids` 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](https://wordpress.org/support/article/debugging-in-wordpress/)
   for more information. (This message was added in version 5.5.0.) in /var/www/
   vhosts/…/httpdocs/wp-includes/functions.php on line 5229 [12-Feb-2021 15:28:58
   UTC] PHP Notice: register_rest_route was called **incorrectly**. The REST API
   route definition for `wc-pos/groups/(?P<id>[\d]+)` 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](https://wordpress.org/support/article/debugging-in-wordpress/)
   for more information. (This message was added in version 5.5.0.) in /var/www/
   vhosts/…/httpdocs/wp-includes/functions.php on line 5229
 * Can you advise when these will be fixed?

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

 *  Plugin Author [bizswoop](https://wordpress.org/support/users/bizswoop/)
 * (@bizswoop)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/reset-api-route-errors/#post-14060813)
 * Thanks for raising the support post, could you please do us a favor and trigger
   a full debug log on your instance. We’d like to review the full list of warnings
   being triggered on your setup.
 * To send us the log, let’s do the following:
 * POS > Settings > Debug tab
 * Enable developer mode for debugging. Save changes.
 * Now go and launch a POS Station. Once the POS loads.
 * Click the upper left main menu. Select Support.
 * Under Support. Fill out the form, make sure to the option ‘Send POS system report’
   is enabled. Click Send
 * The debugs will send to us and create a support ticket. We will review the full
   logs and follow-up on a fix to address the warnings.
 * Don’t forget to go back and disable the debugging mode on the POS settings, as
   the debugging may impact performance of the POS.
 *  Thread Starter [regisit](https://wordpress.org/support/users/regisit/)
 * (@regisit)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/reset-api-route-errors/#post-14061859)
 * Done.

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

The topic ‘Reset API Route errors’ is closed to new replies.

 * ![](https://ps.w.org/point-of-sale-pos-woocommerce/assets/icon-256x256.png?rev
   =3308573)
 * [Jovvie Point of Sale POS for WooCommerce](https://wordpress.org/plugins/point-of-sale-pos-woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/point-of-sale-pos-woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/point-of-sale-pos-woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/point-of-sale-pos-woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/point-of-sale-pos-woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/point-of-sale-pos-woocommerce/reviews/)

## Tags

 * [PHP Notice](https://wordpress.org/support/topic-tag/php-notice/)
 * [register_rest_route](https://wordpress.org/support/topic-tag/register_rest_route/)

 * 2 replies
 * 2 participants
 * Last reply from: [regisit](https://wordpress.org/support/users/regisit/)
 * Last activity: [5 years, 3 months ago](https://wordpress.org/support/topic/reset-api-route-errors/#post-14061859)
 * Status: not resolved