• Resolved xgenious

    (@xgenious)


    i get this error while i am creating new page

    Notice: register_rest_route was called incorrectly. The REST API route definition for give-api/v2/form/(?P[\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 for more information. (This message was added in version 5.5.0.) in /Users/dvrobin/Desktop/Sharifur-Backup/localhost/ht/wp-includes/functions.php on line 5225

    Notice: register_rest_route was called incorrectly. The REST API route definition for give-api/v2/form-grid 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.) in /Users/dvrobin/Desktop/Sharifur-Backup/localhost/ht/wp-includes/functions.php on line 5225

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Ben Meredith

    (@benmeredithgmailcom)

    Hi @xgenious

    It looks like you are adding some custom endpoints or something to the GiveWP API, based on that error message. I see give-api/v2/form-grid and give-api/v2/form/(?P[\d]+) as endpoints, and those are not default endpoints included in GiveWP.

    Additionally, those are PHP notices that should only show on sites with WP_DEBUG enabled, and not on production sites.

    Can you clarify some steps for me to be able to replicate a problem?

    Also, please send along your System Info.

    Navigate to Donations –> Tools –> System Info (tab) and click the button to “Get System Report” and copy/paste that in your reply here.
    ?
    ?That will give me some more context to be able to help.

    Plugin Contributor Ben Meredith

    (@benmeredithgmailcom)

    To elaborate on my previous reply here:

    You can make those notices go away by turning off WP_DEBUG on the live site by adding the following to wp-config.php:

    
    // Turn debugging on
    define('WP_DEBUG', true);
    
    // Tell WordPress to log everything to /wp-content/debug.log
    define('WP_DEBUG_LOG', true);
    
    // Turn off the display of error messages on your site
    define('WP_DEBUG_DISPLAY', false);
    
    // Hide general PHP errors 
    @ini_set('display_errors', 0);
    

    That will hide the errors from the front end, but still log them to a file at wp-content/

    ??We are looking into what might be causing this issue in our code, as I’ve gotten a handful of other reports, so this turns out not to be an issue of custom endpoints.

    In the meantime, hiding the notices will resolve it for now.

    Let me know if that resolves things, or if you need further assistance. ?Thanks for using GiveWP! Have a great day.

    Plugin Contributor Ben Meredith

    (@benmeredithgmailcom)

    Hey @xgenious just a note that this issue has been replicated, patched, and is in testing for release from our development team. Thanks so much for reporting it!

    The workaround of not displaying those errors will work in the meantime.

    Plugin Contributor Ben Meredith

    (@benmeredithgmailcom)

    ?Just a heads up that the problem that was creating those notices with WP_DEBUG in version 2.7.5 and WordPress 5.5 have been resolved. They were not affecting functionality at all, but it’s always good to get things looking nicer!
    ?
    ?Let me know if that resolves things, or if you need further assistance. Thanks for using GiveWP! Have a great day.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘getting error after upgrade to wp version 5.5’ is closed to new replies.