Jetpack is being a headache. Again.

It gets old to write or think that phrase.

I updated the plugin like a good little boy.

Something about updating Jetpack crashed my site two days ago. I had to dig into the backend files and employ some minor fixes to get the site running again. It was down a whole 7 minutes. It may have been the server glitching, but other things started breaking with the new Jetpack update, so you begin to wonder if my woes are all related.

Known broke items:

  • All my settings changed without warning or notification.
    • I had to go through and figure out which toggles I had set previously.
    • I had “this post does not exist” as a popup on my post from yesterday. Staring me in the face… But it did not exist, apparently. This seems to have been a problem with the aforementioned modified settings once I resaved it.
  • I am now forced to use the Gutenberg “like” block instead of the legacy “like”
    • This breaks notifications on Reader. I do not receive “Likes” notifications on Reader when I use the block version of the tool.
      • This means I have to visit my posts via Reader or the post listings if I want to see how many (or if any) people like my posts.

The Like block has acted this way since they tried to push for us to leave the legacy Like function. Always: there are no web or app notifications (for me, anyway, and across several sites). I use the Twenty-TwentyFive template with only cosmetic tweaks outside of the plugins. And it happens on site running low-or-no plugins.

I would blame my own security fixes, except that everything worked fine until I updated the plugin. Those security fixes block some known bad actors from accessing the site (scraper and hacker bots); WordPress is given a full pass on security.

In a quick discussion with Claude to see if I was overlooking anything in any of my settings (it agreed with me that this shouldn’t happen based on information I shared) we decided to give me a a plugin for a “recent likes” panel on the admin page. It took about 2 minutes and looks like this:

Now I just need to have someone “like” something so I can see how it works, LOL.

It might be a while…

Comments for this post are intentionally closed. I’m just venting.


3 responses to “Jetpack is being a headache. Again.”

  1. lyndhurstlaura Avatar

    Tech stuff totally over my head, as mentioned before, but I get that you’re having issues and extend my hopes that you get it sorted – along with a pack of headache tablets. Hope tomorrow is better. 🙁

    1. michael raven Avatar

      Probably not. Without the old “like” button, if no one fixes the block one for self hosted installs of WordPress, I’ll have to use workarounds.

      In a way, it pushes me to look at how I handle things and I am now forced to reassess the value certain tools provide.

  2. erroneouschoices Avatar

    Stop closing comments! 🤔

Leave a comment. Markdown permitted.

This site uses Akismet to reduce spam. Learn how your comment data is processed.