Support » Plugin: MC4WP: Mailchimp for WordPress » PHP error after WordPress 5.5 update

  • Resolved saltykey

    (@saltykey)


    I’m getting the following error in the wp-admin area after updating to WordPress 5.5 (note: I have wp_debug turned ON):

    Notice: register_rest_route was called incorrectly. The REST API route definition for mc4wp/v1/form 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 /public_html/wp-includes/functions.php on line 5225

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Contributor Lap

    (@lapzor)

    Can you delete the MC4WP folder from your wp-content/plugins, see if that solves the issue?

    And then, when you have access to your wp admin again, install the latest version of MC4WP from the plugin repository, your settings should still be there.

    Hope that helps. If you have any questions, please let me know!

    Thread Starter saltykey

    (@saltykey)

    Tried this, but the PHP error did not go away. I’m also having trouble getting the form to submit. I get this error:

    “Oops. Something went wrong. Please try again later.”

    Plugin Contributor Lap

    (@lapzor)

    Hi,

    When you delete the plugin the error is gone, or it’s still there even when the plugin folder isn’t?

    Regarding the oops error, is there anything in the log on MailChimp for WP > Other page?

    Thanks for letting me know.

    Thread Starter saltykey

    (@saltykey)

    I didn’t check the page for the error when I deleted the folder, I only checked after I had re-installed the MC4WP plugin in wp-admin. I’ll try it again and see what happens.

    I get this in the MC4WP > Other page:

    [2020-08-13 02:18:01] ERROR: Form 511 > Mailchimp API error: 404 Not Found. Resource Not Found. The requested resource could not be found.
    Request:
    POST https://us17.api.mailchimp.com/3.0/lists/34bf365c43/members
    {“status”:”pending”,”email_address”:”mike@sa******.com”,”interests”:{},”merge_fields”:{},”email_type”:”html”,”ip_signup”:”99.17.63.120″,”tags”:[]}
    Response:
    404 Not Found
    {“type”:”http://developer.mailchimp.com/documentation/mailchimp/guides/error-glossary/”,”title”:”Resource Not Found”,”status”:404,”detail”:”The requested resource could not be found.”,”instance”:”74a76c68-0ad9-4685-90f0-40dff6f59a35″}
    [2020-08-13 02:18:34] ERROR: Form 511 > Mailchimp API error: 404 Not Found. Resource Not Found. The requested resource could not be found.
    Request:
    POST https://us17.api.mailchimp.com/3.0/lists/34bf365c43/members
    {“status”:”pending”,”email_address”:”mike@sa******.com”,”interests”:{},”merge_fields”:{},”email_type”:”html”,”ip_signup”:”99.17.63.120″,”tags”:[]}
    Response:
    404 Not Found
    {“type”:”http://developer.mailchimp.com/documentation/mailchimp/guides/error-glossary/”,”title”:”Resource Not Found”,”status”:404,”detail”:”The requested resource could not be found.”,”instance”:”41416912-6259-4a1e-a600-a052cec5337f”}
    [2020-08-13 02:26:07] ERROR: Form 511 > Mailchimp API error: 404 Not Found. Resource Not Found. The requested resource could not be found.
    Request:
    POST https://us17.api.mailchimp.com/3.0/lists/34bf365c43/members
    {“status”:”pending”,”email_address”:”mike@sa******.com”,”interests”:{},”merge_fields”:{},”email_type”:”html”,”ip_signup”:”99.17.63.120″,”tags”:[]}
    Response:
    404 Not Found
    {“type”:”http://developer.mailchimp.com/documentation/mailchimp/guides/error-glossary/”,”title”:”Resource Not Found”,”status”:404,”detail”:”The requested resource could not be found.”,”instance”:”c9c2e493-c621-40b9-959e-e4e036bb8912″}
    [2020-08-13 02:26:22] ERROR: Form 511 > Mailchimp API error: 404 Not Found. Resource Not Found. The requested resource could not be found.
    Request:
    POST https://us17.api.mailchimp.com/3.0/lists/34bf365c43/members
    {“status”:”pending”,”email_address”:”mcoo****@gm***.com”,”interests”:{},”merge_fields”:{},”email_type”:”html”,”ip_signup”:”99.17.63.120″,”tags”:[]}
    Response:
    404 Not Found
    {“type”:”http://developer.mailchimp.com/documentation/mailchimp/guides/error-glossary/”,”title”:”Resource Not Found”,”status”:404,”detail”:”The requested resource could not be found.”,”instance”:”4132620f-c895-4e66-a2bc-26d82e064fcf”}
    [2020-08-13 02:33:50] ERROR: Form 511 > Mailchimp API error: 404 Not Found. Resource Not Found. The requested resource could not be found.
    Request:
    POST https://us17.api.mailchimp.com/3.0/lists/34bf365c43/members
    {“status”:”pending”,”email_address”:”mcoo****@gm***.com”,”interests”:{},”merge_fields”:{},”email_type”:”html”,”ip_signup”:”99.17.63.120″,”tags”:[]}
    Response:
    404 Not Found
    {“type”:”http://developer.mailchimp.com/documentation/mailchimp/guides/error-glossary/”,”title”:”Resource Not Found”,”status”:404,”detail”:”The requested resource could not be found.”,”instance”:”85871e1f-fc9b-4e24-8c60-c1b6a150e5f9″}

    Thread Starter saltykey

    (@saltykey)

    I was the one who made the oops; I forgot to check the field next to the list I wanted people to subscribe to. Sorry for the mistake. Problem resolved.

    Plugin Contributor Lap

    (@lapzor)

    No more error now? Awesome!

    Thread Starter saltykey

    (@saltykey)

    Actually, the original error is still there. The form does submit successfully, however. Sorry for the confusion.

    Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hey @saltykey,

    Can you please clear the debug log and test again and then share the new errors?

    Saw the same issue on a staging site after upgrading to WordPress 5.5. I get the error while working with wp-cli, but the error message seem to match what @saltykey is seeing.

    I can reproduce the error consistently with the following sequence:

    Command (most wp-cli will trigger the error):
    wp @test user get 1

    Output:
    PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>mc4wp/v1/form</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 /vagrant/www/wordpress-test/wp-includes/functions.php on line 5225
    [followed by expected output]

    Disable the plugin:
    wp @test plugin deactivate mailchimp-for-wp
    wp @test user get 1
    [only get expected output]

    Delete and reinstall the plugin:
    wp @test plugin delete mailchimp-for-wp
    wp @test plugin install mailchimp-for-wp --activate

    Output:

    Installing MC4WP: Mailchimp for WordPress (4.8)
    Downloading installation package from https://downloads.wordpress.org/plugin/mailchimp-for-wp.4.8.zip...
    

    [additional output removed]

    Test the cli command again:
    wp @test user get 1

    Output:
    PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>mc4wp/v1/form</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 /vagrant/www/wordpress-test/wp-includes/functions.php on line 5225
    [followed by expected output]

    Plugin Author Danny van Kooten

    (@dvankooten)

    Hello @wundermatics @saltykey,

    This is a PHP notice that is added in WordPress 5.5 and will be gone in the next plugin update. Until then, you can safely ignore the notice. It is nothing to worry about and does not affect functionality in any way. WordPress just wants our code to be a bit more explicit as of version 5.5.

    Hope that helps!

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘PHP error after WordPress 5.5 update’ is closed to new replies.