WPIntell

Source evidence

Fatal Errors with version 6.0.1

Sezzle Woocommerce Payment · support · 2025-09-17T12:09:00+00:00

complaintsentiment
highseverity
0.7relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

9 / 39 rows with source links

23.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
um84 unresolved
We’re seeing this fatal error across multiple sites when using v6.0.1: Fatal error: Uncaught Error: Failed opening required ‘/srv/htdocs/wp-content/plugins/sezzle-woocommerce-payment/includes/class-service-v2.php’ (include_path=’.:’) in /srv/htdocs/wp-content/plugins/sezzle-woocommerce-payment/woocommerce-gateway-sezzle.php:39 We confirm that the issue is not happening in version 5.0.16. Same issue here. Worked around it by commenting out line 39 here: woocommerce-gateway-sezzle.php Looks like v6.0.2 was released and resolves the issue 😀 Confirmed! Updated and the missing file in the includes folder is now there. We sincerely apologize for the inconvenience. An issue in the release process of v6.0.0 and v6.0.1 on September 16 caused the error you experienced. We addressed it promptly in v6.0.2, released the following morning, and have updated our release documentation to help prevent similar issues going forward. We appreciate your patience and understanding.

Comments

4 shown
websavers 2025-09-17T13:20:00+00:00

Same issue here. Worked around it by commenting out line 39 here: woocommerce-gateway-sezzle.php

um84 2025-09-17T16:03:00+00:00

Looks like v6.0.2 was released and resolves the issue 😀

websavers 2025-09-17T16:05:00+00:00

Confirmed! Updated and the missing file in the includes folder is now there.

Sezzle 2025-09-18T14:27:00+00:00

We sincerely apologize for the inconvenience. An issue in the release process of v6.0.0 and v6.0.1 on September 16 caused the error you experienced. We addressed it promptly in v6.0.2, released the following morning, and have updated our release documentation to help prevent similar issues going forward. We appreciate your patience and understanding.