Support » Plugin: Jetpack - WP Security, Backup, Speed, & Growth » Fatal Error Plugin Activations

  • Resolved kookookjew

    (@kookookjew)


    get this message when I try to activate the latest version of the plugin. Using WordPress 5.5

    Fatal error: Cannot redeclare
    Automattic\Jetpack\Autoloader\enqueue_packages_caf890f17f58d4849def9dd43df3b33a() (previously declared in /home/XXX/public_html/wp-content/plugins/woocommerce/vendor/autoload_packages.php:183) in /home/XXX/public_html/wp-content/plugins/woocommerce/vendor/autoload_packages.php on line 183

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

Viewing 11 replies - 16 through 26 (of 26 total)
  • @james,

    My site is working with these new updates, but I had succeeded in getting my site working some days ago after I changed the name of JetPack via ftp, disabled Braintree, removed JetPack entirely then re-installed JetPack.

    So yes, running JetPack 8.8.2 and Woocommerce 4.4.1 (plus a couple other brand new Woocommerce updates that rolled in yesterday), my site is still up – HOWEVER, I have NOT re-enabled Braintree – I’m concerned Braintree may have been conflicting with JetPack.

    I’m curious if others are using the latest Woocommerce/Jetpack versions with Braintree enabled?

    Any news about Jetpack 8.8.2 and WooCOMMERCE 4.4.1? How to resolve problem with Jetpack?

    I see this has been Resolved – but don’t see a conclusion in the above thread… Can we safely conclude that the problem was caused by a conflict between Jetpack and Woocommerce 4.4.0, and that this conflict was resolved with Woocommerce 4.4.1? But I’m still wondering if Braintree is safe to enable (per my last comment in this thread).

    @topboj is your site still compromised?

    @susantau everything works fine now (Woocomerce 4.4.1 and JetPack 8.9)

    I am having this issue.

    I only deactivated jetpack to trouble shoot a woocommerce problem. Then, I reverted to a complete cpanel backup, and got the same critical error. Renamed in ftp to be able to log in, and was able to log in but i can not reactivate jetpack.

    @mellowvision Did you try removing and re-installing Jetpack? I believe that’s what I had to do…

    @topboj) Glad to hear all is working now – thanks for replying.

    I was able to delete and reinstall but then had other issues. but each time i revert to any backup, I am getting this error.

    So your restored backup is just resetting to some point in time when Woocommerce and Jetpack versions were still in conflict, so it makes sense you’ll get that error and restoring won’t help – unfortunately. If I were you, I would regain access to the admin dashboard again by temporarily changing the name of the Jetpack folder via FTP — but after you’re in, change that folder name BACK to the correct name and immediately update both the Jetpack and Woocommerce plugins before you log out again. That’s what I would do… I hope this helps!

    I have deleted the Jetpack plugin and I have the same issue. I felt quite certain that Jetpack was disabled as it caused problems last time.

    I’ve restored from an older backup that was working and did not have this issue. I think the updates have littered my server with files that are in addition to my restored backup.

    Any ideas?

    I have just found this problem on a customer’s site too. The thing is we decided to get rid of jetpack for performance issues. And it still worked quite badly.

    I found this error while trying to run p3, and looked at the files… and there are some Jetpack folders and files like this still into WooCommerce! Why is that? I don’t see why are they there if jetpack is not installed.

    Plugin Contributor Dan (a11n)

    (@drawmyface)

    Hi @taisa1984

    Could you please start your own thread, as per the Forum Welcome?
    https://wordpress.org/support/plugin/jetpack#new-post

    And please let us know which specific folders/files you’re referring to.

    Thank you!

Viewing 11 replies - 16 through 26 (of 26 total)
  • The topic ‘Fatal Error Plugin Activations’ is closed to new replies.