Support » Plugin: Jetpack by WordPress.com » Troubled by the recent issues

  • Recently, it throws a big error when updating the plugin.

    Sounds nastier than what has resulted, mostly – only on one site did I have to do a big fix, but then, why should I have to do that? This plugin is one of those “recommended” by WordPress – part of WordPress..

    This has been happening on all of my sites that I maintain – luckily I don’t use Jetpack for backups – I go by the “don’t put all your eggs in one basket” methodology on that.

    All of my sites have different themes in use.
    All updated and current to latest WordPress.

    It’s irksome when Jetpack is supposed to be tested with the newest WP version.

    Had to uninstall/reinstall Jetpack, reconfigure, yada yada yada.

    To have to go back and jump through a bunch of hoops isn’t the best way to handle fallout from a bug i.e., “If that doesn’t work, you’ll need to access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), navigate to /wp-content/plugins/ and delete the whole /jetpack/ directory there.”

    Gosh, imagine a person who is just doing housekeeping on a website having to go and do a bunch of work at the file manager level to get something back again that got blown away by a plug-in update. Where’s the value in that?

    Not everyone wants to do this and hmmmm… it makes them think, “What other plugin can I use that does the same thing?” That’s how software developers lose customers…

    Kinda makes me think that more testing is needed ahead of the release that seems to be breaking, eh?

    Bottom line – and I realize that I’m just carping here, but this should provoke some thoughts that since Jetpack is an important WordPress plugin – if it is tested properly it should work properly when a new release comes out, with the current version of WordPress and with most OS’s,

    The users should not be testers, unless they know ahead that they are testing as, if this is a production release, if it throws a big error on update, it’s still BETA.

    ’nuff said. Hope this gets fixed soon.

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this review.