Plugin Broke my Site

Resolved bluemoontom
(@bluemoontom)

4 weeks, 1 day ago

I believe there was an update, and the plugin prevented me from accessing my admin site. hosting support had to disable the plugin to regain access. I received the following email, there is more detail to the message but i do not want to post that in a public forum:

Howdy!

WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Google for WooCommerce.

First, visit your website *** and check for any visible issues. Next, visit the page where the error was caught (***) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 7.0.2
Active theme: *** Theme (version 1.0.0)
Current plugin: Google for WooCommerce (version 3.8.0)
PHP version 8.3.32

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

Plugin Support shahzeen(woo-hc)
(@shahzeenfarooq)

4 weeks, 1 day ago
Hi @bluemoontom!

Thank you for bringing this to our attention and for sharing the details from the WordPress recovery email.

We’ve tried to reproduce this issue on our end, but we haven’t been able to replicate it. It’s possible that the latest version of Google for WooCommerce is conflicting with another plugin, your active theme, or a custom code snippet on your site.

To narrow down the cause, I’d recommend performing a conflict test:
1. Deactivate all plugins except WooCommerce.
2. Switch to a default WordPress theme, such as Storefront or Twenty Twenty-Five.
3. Activate Google for WooCommerce and check whether the fatal error still occurs.
4. If the issue is resolved, reactivate your plugins one at a time until the error returns. This will help identify which plugin or customization is causing the conflict.
We recommend performing these steps on a staging site so your live store remains unaffected. If you don’t already have a staging site, you can create one using the following plugin:

https://wordpress.org/plugins/wp-staging/

If the issue persists even after the conflict test, could you please share the following?
- Your WooCommerce System Status Report (WooCommerce → Status → Get system report)
- The PHP fatal error log related to this issue
You can share both using Pastebin and enable the Burn after Read option before posting the link here, so the information remains private.

Once we have those details, we’ll be happy to investigate further.
DawsonyWeb
(@dawsonyweb)

3 weeks, 6 days ago

the conflict seems to be with ActiveCampaign for WooCommerce we had the same issue with them both calling the same deprecated plugin hash for trigger_deprecation() on deprecation-contracts they both register the same hash for it.

Plugin Support shahzeen(woo-hc)
(@shahzeenfarooq)

3 weeks, 6 days ago

Hi @dawsonyweb!

Thank you for sharing your findings and for taking the time to investigate the root cause.

Based on what you’ve found, it does appear that the conflict is related to the ActiveCampaign for WooCommerce plugin, with both plugins attempting to register the same deprecated hash for trigger_deprecation() from deprecation-contracts.

At this point, I’d recommend reaching out to the ActiveCampaign plugin support team as well, as they may be able to provide a fix or workaround from their side.

In the meantime, I’ll also escalate this internally with our team for further investigation. If we receive any updates or identify anything that can be addressed on our end, I’ll be happy to update you here.

Thank you again for your patience and for helping us narrow down the issue.
DawsonyWeb
(@dawsonyweb)

3 weeks, 6 days ago
no worries i dropped a mu-plugin for a temporary fix

here it is if it helps anyone else
```
if (!function_exists('trigger_deprecation')) {
    function trigger_deprecation($package, $version, $message, ...$args)
    {
        @trigger_error(
            ($package || $version ? "Since $package $version: " : '')
                . ($args ? vsprintf($message, $args) : $message),
            E_USER_DEPRECATED
        );
    }
}
```
- This reply was modified 3 weeks, 6 days ago by DawsonyWeb.
Plugin Support shahzeen(woo-hc)
(@shahzeenfarooq)

3 weeks, 6 days ago

Hi @dawsonyweb!

I’m glad you were able to find a temporary solution. Hopefully, it will also help other users who run into the same issue while the underlying conflict is being investigated.

I’ll make a note of this and continue to follow up internally. If we have any updates or a permanent fix to share, I’ll be sure to post them here.

Thanks again for your contribution and for helping the community!

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

You must be logged in to reply to this topic.