Fun with Glitches

Over the past year, I've had a spate of glitches with Weebly, the service producer of this site. Most of them have been behind the scenes, so happily people here haven't been too troubled by them.  There was one recently, though, which did cause a "public" issue, when the wrong date was being stamped on posts and so they were going online out of order and unseen, so I shut things down a couple of times.

Most of the glitches, too, have been not only bewildering to me, but to the folks at Weebly, as well, who have been so flummoxed by them that they couldn't even duplicate what was going on.  This is known as the "Why Me, Lord?" Syndrome.

The commands to save a post would disappear, for instance -- which tends to make it difficult to...well, save a post.  I figured out a work around.  Or I'd edit a piece and save the changes -- but the changes wouldn't take.  So, I'd have to remember what I'd just edited and try again.  And sometimes again.  Or I'd go to post an article that I'd saved as a draft, only to find that all the graphic images and video players had jumped around the page and had to be repositioned.  And much more.  Fortunately, most seem to have been resolved -- either through updates to Weebly, updates to my browser, updates with Windows 10, or the whimsy of the world -- though not all.

Then another one popped up over the weekend.  I went back to edit an old post -- correct a typo I noticed -- but when I went to the article...it appeared fine to the public, but the version to edit was all screwed up.  Two of the last four paragraphs were missing (where I wanted to make the correction, of course...), and other text was different, from an earlier draft.

I wrote to Weebly text support and after several emails trying to explain things -- they were that bewildered by what I was trying to describe -- they finally grasped what I was saying.  The good news is that they actually were able to see that there was a glitch here!  (O huzzah -- no "We can't duplicate what you're saying, so we can't see what the problem is.)  The bad news is...well, they were totally flummoxed by it -- to the degree that they wrote, "We are pretty intrigued by this one since we haven't seen it before."

Needless-to-say, I am always happy to intrigue tech support folks with my glitches.  All the while adding another notch to my "Why Me, Lord?" Syndrome collection.

They needed my permission to dive into the editor and see if they can figure out what on earth is going on, and I joyfully gave it.  Think of it as my own personal sandbox for tech support folks to play in.  

I have no idea if they'll be able to figure it out and fix things, but I trust they'll get back to me.  Fortunately, this is from a few months ago, and the correction is small, so it's not a huge deal if they can't.  Except that I'd prefer it not happen again.