• Resolved TheStingPilot

    (@thestingpilot)


    Hello,

    After updating the Tiered Pricing Table plugin to 7.1.4, our website started returning a HTTP 500 error.

    The WordPress debug.log repeatedly showed the following fatal error:

    PHP Fatal error: Uncaught Error:
    Class “TierPricingTable\Integrations\Plugins\WooCommerceSubscriptions” not found
    in wp-content/plugins/tier-pricing-table/src/Integrations/Integrations.php on line 97

    The stack trace shows that the crash happens while the plugin is initializing:

    tier-pricing-table.php
    → TierPricingTablePlugin->run()
    → TierPricingTable\Integrations\Integrations->__construct()
    → TierPricingTable\Integrations\Integrations->init()

    It looks like the plugin is trying to initialize the WooCommerce Subscriptions integration, but the class:

    TierPricingTable\Integrations\Plugins\WooCommerceSubscriptions

    is not available.

    I searched online and could not find any public reports of this exact missing class issue. However, I did find several support topics mentioning fatal errors in recent versions of Tiered Pricing Table, so this may be a new or not-yet-publicly-reported regression introduced by the latest update.

    Could you please check whether a file or autoload entry is missing in the latest release, or whether this integration is being initialized without checking if the class exists first?

    Thank you for your help.

    With kind regards,
    TheStingPilot

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Mykola Lukin

    (@bycrik)

    Thank you for the report.

    You are correct. This was caused by a packaging mistake in version 7.1.4. A required file for the WooCommerce Subscriptions integration was accidentally omitted from the SVN release, which resulted in the missing class error.

    The issue was fixed in version 7.1.5. Please update to the latest version and the error should be resolved.

    Sorry for the inconvenience, and thank you for bringing this to our attention.

    Thread Starter TheStingPilot

    (@thestingpilot)

    Thank you for your reply. The issue has been solved now.

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

You must be logged in to reply to this topic.