fatal jetpack error updating 'other" plugins…

  • Unknown's avatar

    EVERY SINGLE ONE of my maintenance contract websites that got updated this month, had the exact same error: (and it starts like this)

    An error of type E_ERROR was caused in line 270 of the file /home/(user)/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/Listener.php

    and “uncaught” error…that’s just crappy coding, COME ON NOW!!! Every error should be “caught” if the stupid thing is coded correctly!

    I’ve hated jetpack for 10 years, and it just gets buggier and buggier all the darn time…lousy work. lousy plugin. But clients want it for some stupid reason (1 of them likes the stupid stats page it puts up, and uses it only for that!)

    FIX YOUR JUNK PLEASE!!!!!!! this error had absolutely nothing to with jetpack itself…the listener.php file kicked in when updating “other” plugins…which is WORSE!!

    The blog I need help with is: (visible only to logged in users)

  • Unknown's avatar

    IGNORE that last line that wordpress.com inserted into my post about the blog I need help with…that is COMPLETELY wrong ( like so much that they do) and erroneous statement, and I have absolutely no clue where they think they get that stupid information! Wow…see what I mean? Crappier, and crappier.

  • Hi there,

    You have posted in the support forums for free sites hosted on WordPress.com.

    For help with the Jetpack plugin for the open source WordPress.org software, please contact that plugin’s support at https://jetpack.com/contact-support/?rel=support

  • The topic ‘fatal jetpack error updating 'other" plugins…’ is closed to new replies.