Fatal error

  • Resolved eesrefu

    (@eesrefu)


    3 days, 6 hours ago

    Hello,

    I want to report what looks like a plugin conflict between PixelYourSite 11.3.0 and the Angie plugin (by Elementor.com, “Agentic AI for WordPress”) version 1.1.12.

    WHAT HAPPENED
    On 13 August 2026 my site went down with fatal errors and was unreachable for roughly 2.5 hours (approx. 05:10-07:39 site time). Every fatal error logged during that window referenced Angie. The site recovered immediately and completely once Angie was deactivated, and has been stable ever since with PixelYourSite still active.

    WHY I THINK THIS INVOLVES PIXELYOURSITE’S MCP FEATURE

    • Angie 1.1.12 was released on 12 August 2026. Its changelog headline is “Angie MCP – Connect any AI client to your site with Angie”, and it says it “registered Elementor context, Code Snippets and Super Admin tools to Abilities API”.
    • My host’s auto-update installed that release overnight, and the crash began shortly afterwards.
    • PixelYourSite also ships an MCP server (PixelYourSite -> MCP) built on the same WordPress Abilities API. On that screen the connection test reports: MCP Adapter: PYS_PRO_GLOBAL\WP\MCP\Plugin loaded
    • So both plugins are loading an MCP adapter and registering abilities on the same WordPress 7.0 Abilities API in the same request.

    Notably, I had ZERO MCP tokens generated in PixelYourSite (0 of 25), so nothing was ever connected to the endpoint. The crash therefore happens at plugin bootstrap time, not when an MCP request is served.

    ABOUT THE ERROR LOG
    I have to be upfront: I can no longer retrieve the verbatim fatal-error line (file path, class/function name). By the time I went looking the site had been restored, the PHP error log is not exposed to me, and WordPress’ recovery-mode email was never delivered. So the causal link above is based on timing and on what each plugin’s own diagnostics screen reports – strong, but circumstantial. If you need the exact trace, I can enable WP_DEBUG_LOG, reactivate Angie briefly on a staging copy, and send you the result.

    WHAT I’D LIKE TO ASK

    1. Are you aware of a conflict with Angie 1.1.12, or with any other plugin that bundles the WordPress MCP Adapter library?
    2. Would you consider guarding the MCP adapter bootstrap (class_exists / function_exists checks, or deferred registration) so that a second plugin registering abilities cannot take the whole site down?
    3. Is there a supported way to disable PixelYourSite’s MCP server entirely? On the MCP screen I only found “Enable read-only mode”, which does not appear to prevent the adapter from loading.

    ENVIRONMENT
    WordPress 7.0.4 | PHP 8.3.32 (memory_limit 512M) | LiteSpeed origin behind Cloudflare | Linux 4.18 (CloudLinux)
    Angie 1.1.12 | PixelYourSite 11.3.0 (free)
    Also active: Elementor 4.2.2, Rank Math, WPForms, ACF, WPCode, LiteSpeed Cache, Really Simple Security, WPvivid, FileBird, Custom Post Type UI, Download Monitor, WP Mail SMTP

    For now I have left Angie deactivated so my Meta pixel tracking keeps working. Happy to provide logs, a staging site, or to test a patch.

    Thank you.

    The page I need help with: [log in to see the link]

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

    (@ehamati)

    2 days, 9 hours ago

    @eesrefu The bug occurred because PYS and Angie are bundling different copies of the WordPress MCP adapter. PYS uses a prefixed version (PYS_PRO_GLOBAL\WP\MCP\…), while Angie uses the standard version (WP\MCP\…).

    We’ve provided a fix for this issue. Please update the plugin to the latest version and check whether the issue is resolved.

    Thread Starter eesrefu

    (@eesrefu)

    2 days, 4 hours ago

    Thanks for the quick fix — a heads-up though: the update isn’t reaching sites yet.

    On my install (PixelYourSite 11.3.0, Angie 1.1.12) I forced a WordPress update check and it still reports “all plugins are up to date”.

    Checking the two wordpress.org endpoints directly: plugins/info/1.0/pixelyoursite.json returns 11.3.0.1 (last_updated 2026-08-14 11:34am GMT), but plugins/update-check/1.1/ — the endpoint WordPress actually queries — still returns no_update for pixelyoursite/facebook-pixel-master.php at version 11.3.0.

    So 11.3.0.1 is published but is not being served as an update yet. Could you check whether the Stable tag in trunk/readme.txt was bumped to 11.3.0.1? If it still points at 11.3.0, the update API will keep returning no_update no matter how long we wait.

    For the record, the exact fatal on my site was: [13-Aug-2026 05:10:07 UTC] PHP Fatal error: Uncaught TypeError: Angie\Modules\WpAbilities\Classes\Mcp_Server_Registrar::register_servers(): Argument #1 ($adapter) must be of type WP\MCP\Core\McpAdapter, PYS_PRO_GLOBAL\WP\MCP\Core\McpAdapter given.

    17 fatals between 05:10 and 07:35 UTC on 13 August. Angie is deactivated for now as a workaround.

    ehamati

    (@ehamati)

    1 day, 10 hours ago

    @eesrefu It’s possible that WordPress has a relatively new policy of delaying updates for 6 hours, so the update should be available by now. Please check.

    • This reply was modified 1 day, 10 hours ago by ehamati.
Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.