-
Hello!
I noticed this issue in our logs over a month ago but I figured I would wait for the next update to see if it was fixed – but it’s still there.
Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>vbp/v1/sidebar/(?P<sidebar_id>[^/]+)</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>vbp/v1/save_sidebar</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>vbp/v1/user/upload_media_stream/(?P<file>\w+)</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>vbp/v1/user/upload_media_stream/(?P<file>\w+)</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/getreview/(?P<course>\d+)</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/verify</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/getallmembers</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/getmemberbyid</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/forums</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/topics</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/replies</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/user/verify</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/user/getallmembers</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/user/getmemberbyid</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/user/forums</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/user/topics</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/track</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/blog</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/blog/(?P<id>\d+)?</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/Course</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/Course/free_units</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/Course/free-unit/(?P<unit_id>\d+)?</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/track</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/blog</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/blog/(?P<id>\d+)?</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/Course</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/Course/free_units</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/Course/free-unit/(?P<unit_id>\d+)?</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/post/excerpt/(?P<post_id>\d+)?</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/getreview/(?P<course>\d+)</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/verify</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/getallmembers</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/getmemberbyid</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/forums</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/topics</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/user/replies</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/user/verify</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/user/getallmembers</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/user/getmemberbyid</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/user/forums</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/user/topics</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/track</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/blog</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/blog/(?P<id>\d+)?</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/Course</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/Course/free_units</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v1/Course/free-unit/(?P<unit_id>\d+)?</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/track</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/blog</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/blog/(?P<id>\d+)?</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/Course</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/Course/free_units</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/Course/free-unit/(?P<unit_id>\d+)?</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 wp-includes/functions.php on line 5311 Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>wplms/v2/post/excerpt/(?P<post_id>\d+)?</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 wp-includes/functions.php on line 5311Not an error, but it is filling up our logs and makes it hard to find other issues. Is this an issue on my side or something you will fix?
hi
well you can search out that how to remove this from the error logI have searched this and found these links
please check:
https://wordpress.stackexchange.com/questions/237195/how-to-stop-certain-warning-logging-in-error-loghttps://www.cyberciti.biz/faq/php-stop-notice-variable-warnings-errorlogs/
https://forums.cpanel.net/threads/remove-notice-from-logs.665609/
Thanks
I don’t want to remove notices from my logs, this is something that should be fixed in the plugin.
Ok adding to issue log : https://trello.com/c/gAr4R5Yv
will fix this in upcoming update .
Viewing 5 posts - 1 through 5 (of 5 total)
The topic ‘Notice: register_rest_route was called incorrectly.’ is closed to new replies.