• Resolved Nino Mihovilic

    (@ninomiho)


    Hi!

    I keep seeing in logs PHP Fatal error: Cannot declare class WCK\Blocks\CheckoutIntegration, because the name is already in use in /srv/htdocs/wp-content/plugins/klaviyo/includes/blocks/CheckoutIntegration.php on line 16 error.

    I searched all files on my site and cannot find any CheckoutIntegration re-declaration. Do you know what could be an issue? It happens when I visit the checkout page.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author klaviyo

    (@klaviyo)

    Hi there – That isn’t an issue we’ve heard of before. Would you be able to open a ticket with our support team so we can dig into it together? You can follow these instructions to create a support ticket: https://help.klaviyo.com/hc/en-us/articles/115001002272

    We suspect it might be some conflict with another plugin so when you make the ticket, please share what other plugins you use. Thanks!

    Adam Heckler

    (@adamkheckler)

    Hello! Chiming in here because I know what the issue is. ??

    I work for Automattic, specifically on WooPayments, and it seems that our WooPay Direct Checkout feature was conflicting with Klaviyo on your site. How do we know this? We monitor the server logs for WooPay, so when this fatal error was flagged for us in those logs, our developers proactively disabled Direct Checkout on your site. (We can do this without accessing your site in any way because Direct Checkout relies on our WooPay server.)

    In short, you shouldn’t see this error occur again! You can keep using Woo and WooPayments as normal.

    We’re discussing internally how to address this problem in our code as well, so that WooPay Direct Checkout and Klaviyo will be compatible in the future. If our devs file a public GitHub issue for this, I’ll circle back and post the link here.

    Sorry for the trouble!

    Plugin Author klaviyo

    (@klaviyo)

    Thanks Adam!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.