WP technicalitiesJetpack is a plug-in for WordPress.org users.  It gives me most of the bells and whistles that WordPress.com users have.  The main benefits are the sharing things, although for some reason I seem to have them working at present, statistics, follow buttons, and image layouts.  It also seems to affect ease of commenting – sometimes.

I only realised image layouts were part of it when I tried to do a post with illustrations yesterday.

Jetpack hiccups

You probably know that every now and then I upgrade the Jetpack plug, as one should, when the software gets updated.  Several times over the past few years it’s affected your ability to tweet of like my posts, and sometimes it stops people commenting, too.

The solution is generally simple enough – go into the file system on my host, disable the plugin, and reload a version that works.  Tedious, but simple.

Latest hiccup

So I upgraded from 7.6 to 7.7. and then to 7.7.1 which came out a day later.

Except it refused to upgrade to 7.7.1.  Whatever had caused problems with 7.7 wasn’t going away.  And it was giving problems; I was getting ‘fatal error’ messages, which mean something isn’t working in the file system.

So I went in to see what was happening, and deleted Jetpack and tried installing it again.

It refused to install.

Then I found my file system saying it was using  310GB and exceeding my allowance of 1000Mb.

It’s always midnight

Naturally enough, I had started doing this simple upgrade just before I shut down for the night.  It was now fast approaching midnight.  I looked through several sets of files to see what was going on, and discover several error logs with sized over 1GB.  But nothing added up to 310Gb.

Eventually I raised a ticket with the lovely people at my hosting company (Bargainhost).  Then it was deifnitely bedtime, but I had no Jetpack installed at all, and I wondered whether you’d even be able to see my posts, let alone comment on them. You saw a couple of comments from me on the last two, and suprisingly, I could.

The next afternoon I had a response from the support desk (I’d been out, it was the first time I had to look – and anyway, I’d only sent it as medium priority, since the site was working).

They had a look and sent me back a list of problem areas to check and delete if necessary.

I’m still trying to find time to work through that lot.

Maybe I’ll do it at midnight.

Normal service…

Normal service will be resumed as soon as I get around to solving the problems with size and reinstall Jetpack.  But I discovered that the image layout may not be working properly, so sorry about any fancy stuff that isn’t appearing as it should.

And I’m a bit busy at the moment.

PS… I may have fixed everything for now…  five minutes to midnight on Tuesday!

Website performance – Is it Jetpack or is it me?

4 thoughts on “Website performance – Is it Jetpack or is it me?

  • 11 September, 2019 at 3:37 pm
    Permalink

    New technology makes me feel like an idiot – that’s when I call my son-in-law, the king of IT and computers. We’re just the wrong generation – digital immigrants instead of natives.

    Reply
    • 11 September, 2019 at 8:52 pm
      Permalink

      Well, I’ve had a working knowledge of various IT systems since the mid-80s, but once object-oriented software came in I stepped back and let them get on with it. The trouble now is, my problem-solving skills are restricted. But I know enough to explain my troubles to the support desk. I just don’t really know what their answer means!
      I think my guys have upped my allowance as I was on the ‘old’ basic allowance.

      Reply
    • 13 September, 2019 at 9:23 pm
      Permalink

      Well, it has been better for a couple of years. These things happen… and I think my blog has needed more space for a while. It’s certainly loading quicker now.

      Reply

What do you think? Or just say hi!

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

Follow

Get every new post delivered to your Inbox

Join other followers:

%d bloggers like this:

Fatal error: Uncaught wfWAFStorageFileException: Unable to verify temporary file contents for atomic writing. in /home/jack3232/public_html/jemimapett.com/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:52 Stack trace: #0 /home/jack3232/public_html/jemimapett.com/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(659): wfWAFStorageFile::atomicFilePutContents('/home/jack3232/...', '<?php exit('Acc...') #1 [internal function]: wfWAFStorageFile->saveConfig('livewaf') #2 {main} thrown in /home/jack3232/public_html/jemimapett.com/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 52