• Resolved Fernando Tellado

    (@fernandot)


    After updating to version 9.5.0 a plugin that, with the previous version (9.4.1) was perfectly compatible with HPOS, suddenly, WooCommerce indicates that it is not, gives fatal error, and the website breaks. When entering recovery mode the affected plugin shows this error:

    Se ha producido un error del tipo E_COMPILE_ERROR en la línea 345 del archivo /home/customer/www/12345.com/public_html/wp-content/plugins/yith-woocommerce-subscription-premium/includes/gateways/woocommerce-gateway-stripe/class-yith-wc-subscription-wc-stripe.php. Mensaje de error: Declaration of YITH_WC_Subscription_WC_Stripe::get_upe_enabled_payment_method_ids() must be compatible with WC_Stripe_Payment_Gateway::get_upe_enabled_payment_method_ids($force_refresh = false)
    ⚠ Este plugin es incompatible con la característica activa de WooCommerce «Almacenamiento de pedidos de alto rendimiento». No debería estar activado. Gestionar características de WooCommerce

    After make the rollback to v. 9.4.1 of WooCommerce Stripe Gateway, the other plugin, again, is compatible with HPOS :/

    Thanks!

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

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hi @fernandot,

    Thanks for providing the error details and taking the time to test things on your end — that’s really helpful, and I appreciate your effort!

    From what you’ve described, I understand how frustrating it can be when a plugin works perfectly with one version and then suddenly stops functioning in another. Please know that we’re here to support you and help you work through this.

    An error of type E_COMPILE_ERROR occurred on line 345 of the file /home/customer/www/12345.com/public_html/wp-content/plugins/yith-woocommerce-subscription-premium/includes/gateways/woocommerce-gateway-stripe/class-yith-wc-subscription-wc-stripe.php.
    Error message:
    Declaration of YITH_WC_Subscription_WC_Stripe::get_upe_enabled_payment_method_ids() must be compatible with WC_Stripe_Payment_Gateway::get_upe_enabled_payment_method_ids($force_refresh = false).

    This error suggests that the YITH plugin you’re using attempts to integrate with Stripe, but there’s a mismatch in the way certain parts of the code are written, leading to compatibility issues. To resolve this, it’s best to contact YITH support directly, as they are the ones who can ensure their plugin works correctly with Stripe and address any integration conflicts.

    ⚠ This plugin is incompatible with the active WooCommerce feature “High-Performance Order Storage.” It should not be enabled. Manage WooCommerce features.

    Regarding the second error, since WooCommerce regularly releases updates, any plugin that integrates with it—including Stripe—must also stay updated to maintain compatibility.

    Based on the error message, the issue appears to stem from the YITH plugin itself. Their team is in the best position to help troubleshoot this further, as the problem involves how their plugin interacts with both WooCommerce and the Stripe integration.

    Thread Starter Fernando Tellado

    (@fernandot)

    The other plugin was integrated with Stripe until your plugin’s last version, and also was HPOS compatible. I’ve noticed Yith’s support the issue but I think something should be of interest in your side, because this type of bug could happen with other plugins, that yesterday were compliant with HPOS and WooCommerce latest standards and, since updated to Woo Stripe Payment plugin v. 9.5.9 suddenly aren’t compliant :/

    Hi @fernandot,

    Thank you for following up. It’s a positive step that YITH is aware of the issue and already working on it. I completely understand your concerns regarding compatibility, and it’s definitely something we’re taking into consideration.

    Just to clarify, we follow a specific process when it comes to handling bugs and integration issues. For third-party plugins that work alongside the Stripe payment plugin, the responsibility for ensuring compatibility lies with the plugin’s developers. In this case, YITH will need to investigate and determine the root cause of the issue and resolve it on their end if it originates there.

    If the problem is found to stem from Stripe or involves something on our side, the YITH team would typically contact us or open an issue on GitHub. Our developers would then review it and collaborate with YITH to address the problem.

    Regarding HPOS compatibility, this falls under WooCommerce core and is beyond the scope of the Stripe plugin. That said, the same general approach applies—YITH would need to investigate, and if the issue is related to WooCommerce itself, they can open a GitHub issue for further review by the WooCommerce team.

    If you have more questions about HPOS compatibility specifically, I’d recommend posting a topic here:
    👉 WooCommerce Support Forum

    Once you hear back from YITH, feel free to update us. In the meantime, we’d appreciate it if you could leave an honest review for the Stripe plugin—we take feedback seriously and use it to improve the plugin:
    👉 Leave a Review

    Plugin Author Dale du Preez

    (@daledupreez)

    Thank you for reporting the issue, @fernandot!

    Our development team have reached out to the YITH team to try and get this resolved. We have created a tracking issue in our GitHub repository if you’d like to keep informed of any changes that we make to get this resolved: https://github.com/woocommerce/woocommerce-gateway-stripe/issues/4324

    Thread Starter Fernando Tellado

    (@fernandot)

    Thank you @daledupreez

    Today, the Yith team has also updated their plugin 😉

    Andrea Grillo

    (@agengineering)

    Hi everyone,

    I confirm the problem was solved in the version 4.9.0 of YITH Subscription plugin released yesterday.

    Plugin Author Dale du Preez

    (@daledupreez)

    Thanks for the fix and for following up, @agengineering! It is very much appreciated on both counts.

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

The topic ‘9.5.0 error with HPOS compatible plugins’ is closed to new replies.