• Resolved ulicgn

    (@ulicgn)


    Hi,

    on a site running both backwpup 5.7.2 and Woocommerce 10.8.1 I get the following error:

     wp action-scheduler run --batch-size=1 --batches=1                                                    [ERROR] Resource URI not found in ability meta for 'backwpup/docs-overview'. URI must be provided in ability meta data. Dump of get_meta():
    (
    [annotations] => Array
    (
    [readonly] =>
    [destructive] =>
    [idempotent] =>
    )

    [show_in_rest] =>
    [mcp] => Array
    (
    [public] => 1
    [type] => resource
    [uri] => groupone-backwpup-plugin://docs/overview
    [name] => BackWPup MCP Server Overview
    [mimeType] => text/markdown
    )

    )
    | Context: ["RegisterAbilityAsMcpResource::backwpup\/docs-overview"] | User ID: 0

    Even though backwpup has its own bundled mcp-adapter, the error above is triggered by:

    wp-content/plugins/woocommerce/vendor/wordpress/mcp-adapter/includes/Domain/Resources/RegisterAbilityAsMcpResource.php

    I added a dump of the meta array, and it expects the URI in $ability_meta[‘uri’] , not in [‘meta’][‘uri’].

    The error disappears once I disable Backwpup. Not sure whether it is a BackWPup or woo problem, but given that the error is referencing a BackWpUp ability, I report it here first.

    (Note this is on a not-yet-upgraded-to-7 instance running WP 6.9.x, but all plugins there are updated to their latest version. Maybe since 7 has its own mcp-adapter it should not be necessary any more to ship conflicting ones?)
    Regards
    Uli

    (Note to the Moderators of this forum: Would you please review the reason why my post are being flagged for moderation and consider changing that. I am not aware of ever having violated any forum guidelines. Thanks. )

    • This topic was modified 1 day, 10 hours ago by ulicgn. Reason: Asking for Moderator check
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Saransh

    (@saranshwpm)

    Hi Uli,

    Thank you for the detailed report and for taking the time to investigate it so thoroughly.

    I appreciate you sharing the error output and your findings regarding the MCP resource metadata. This is very helpful.

    I’ll discuss this internally with our developers and have them review the behavior further.

    As an additional data point, could you confirm whether you see the same behavior on a WordPress 7 installation as well? Since WordPress 7 includes native MCP support, it would be useful to know whether the issue is limited to pre-WordPress 7 environments or affects both.

    Thank you again for the report.

    Best regards,

    Plugin Support Saransh

    (@saranshwpm)

    Hi Uli,

    Thank you again for reporting this and for providing the detailed debugging information.

    I discussed this with our developers, and we’ve confirmed the issue on our side. We’ve opened an internal report and will work on a fix in a future update.

    At the moment, I don’t have an ETA to share, but I appreciate you bringing this to our attention and helping us identify the problem.

    Thanks again for the thorough investigation and report.

    Best regards,

    Thread Starter ulicgn

    (@ulicgn)

    Thanks for checking and confirming this report so quickly. Next week, I will start testing the site in question on WP7. If that still helps then, I can report back, but it seems as if you already found the problem.

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

You must be logged in to reply to this topic.