Okay
  Public Ticket #4574386
Fatal error in Vendor Dashboard with WooCommerce Subscriptions 9.0.0 (MarketKing 2.1.40)
Open

Comments

  • George Lewis started the conversation
    1 day ago on Thursday at 3:23pm

    Hello,

    I believe I found a compatibility issue between MarketKing 2.1.40 and WooCommerce Subscriptions 9.0.0.

    Environment
    • WordPress 7.x
    • WooCommerce 10.9.4
    • WooCommerce Subscriptions 9.0.0
    • MarketKing 2.1.40
    • PHP 8.3
    Issue

    After updating MarketKing to version 2.1.40, the Vendor Dashboard throws a fatal error.

    The error log shows:

    PHP Fatal error: Failed opening required
.../wp-content/plugins/woocommerce-subscriptions/includes/apfs/includes/admin/class-wcs-att-admin-notices.php
    Investigation

    The issue appears to be in:

    marketking-multivendor-marketplace-for-woocommerce/public/dashboard/marketking-dashboard-login.php

    where MarketKing loads:

    require_once( WCS_ATT_ABSPATH . 'includes/admin/class-wcs-att-admin-notices.php' );
require_once( WCS_ATT_ABSPATH . 'includes/admin/class-wcs-att-admin.php' );

    However, in WooCommerce Subscriptions 9.0.0, those files are actually located at:

    wp-content/plugins/woocommerce-subscriptions/includes/apfs/admin/

    instead of:

    wp-content/plugins/woocommerce-subscriptions/includes/apfs/includes/admin/

    So MarketKing is looking for:

    apfs/includes/admin/

    while the current plugin structure is:

    apfs/admin/

    As a result, the Vendor Dashboard crashes with a fatal error.

    Could you please confirm whether this is a known compatibility issue with WooCommerce Subscriptions 9.0.0?

    Thank you very much.

  •  2,735
    WebWizards replied
    12 hours ago

    Hi George,

    Thanks for reaching out and for the detailed investigation.

    I looked into this and indeed I found a compatibility issue caused by a recent path change in WooCommerce Subscriptions 9.0.0.

     

    I've attached an updated version of MarketKing Core that resolves this. To update:

    1. Deactivate your current MarketKing Core version
    2. Upload and activate the attached file

    This fix will also be included in the next official MarketKing release, so once that comes out you can update normally through the standard process without losing anything.

     

    Let me know if you run into any issues,

    Kind regards,
    Stefan

    Attached files:  marketking-core-2141.zip