Category Archives: Computers

My existential angst as a dead blogger (part 2 / 4)

The PolyBlog
April 19 2021

In my previous post (The Fall of PolyWogg (part 1 / 4)), I covered the technical fall of my site. After the nuke went off, I spent a full week attempting to work through all the technical options to get my site back up and running. And repeatedly failing. I knew I had all the data, so there was that consolation, but the rest of the site? It was looking increasingly like I was going to have to erase everything, nuke the entire account, and start over. I had managed to partly fix two other sites that I host on my account, one for a friend and one for my brother, but beyond that, I was not positive either one were any more reliable than my main PolyWogg.ca site.

So as I reached the end of February, I had to accept the reality. My site was dead. 24y of content, 17y of running a website, and I was at square one. My blogger days were done.

Understanding the magnitude of the loss

I have a hard time explaining the loss to others, because there is no other word for it except loss. I was in shock. A major part of my identity is tied to that blog. I consider myself to BE PolyWogg. And the website is as part of that reality as my own body and soul. They go together. I pour my heart out on that blog, sometimes writing about stuff that I have never told anyone about before. Not even my wife. Or my son. Or best friends. I dig deep, I bleed out on the screen, and sometimes my psyche is so raw that when I’m done writing, I’m spent. I collapse into bed, exhausted. Like I have nothing left.

If I want to look at the numbers, I had 1600 posts and 200 pages of information up on the site. 1800 “docs” with some 1.6 MILLION WORDS. Almost every one of those words mine. There are only three things on the site that aren’t mine in that total count: a report on an HR conference that I still host that is almost 20y old, and two blog posts by my wife. The rest is ME.

If you want to comprehend the volume, 1.6M words is about the length of twenty mystery novels. Now think of it in those terms, as if an author lost all of their work-in-progress or a doctoral candidate lost their thesis. Perhaps they have drafts to rebuild from, but the thesis or the WIP? Gone. Now take into account I had lost 17y worth of work on the structure AND thousands of hours building and running the site over the years.

All of it gone.

It messed with my head

As I said, the loss put me in shock. I shut down emotionally and mentally, combining way too well with some challenges I was having with a leg wound. It messed with my head enough that it scared the crap out of me. How? Try this on for size.

I actually considered NOT rebuilding. I don’t mean I briefly thought about it, I mean I was seriously asking myself if I even COULD rebuild. If I had it in me to do. If I did a few nights a week, it would take me about six months to rebuild. It wouldn’t take much to even have it take me a full year. That is NOT a joke. That’s how much work was involved in rebuilding. I knew it would take an enormous amount of work.

And I didn’t have the energy to even think about committing to it.

Let me give you an equivalent for the leg wound. I was so frustrated with it that one day when I was getting examined, and I was waiting for them to come in with the diagnosis, I was running through dark scenarios in my head. And I realized that if they said they had to amputate, I wouldn’t have asked for a second opinion. In my head, I would have been like, “Okay, is this an out-patient thing we can do today?”. I just wanted to get through, I didn’t care about the “right” outcome.

For my website, I was looking at it and thinking, “Okay, maybe I should just let it go. Get a life somewhere or something.” Bearing in mind that I define myself as a WRITER, who exercises that muscle by BLOGGING, because I don’t feel like I have the time or energy to write full books right now. Yet when I retire, I have a long list of projects I want to undertake. Things I want to write about. And to post on my blog. It’s almost my ENTIRE retirement plan, outside of some fitness and travel. Andrea won’t be able to retire for several years after me, so this is my big scary goal.

But here I am saying to myself, “Okay, it’s gone, let’s move on.”

WTF?

What was GOING ON with my head?

A spark of energy

I’ve reached out in recent weeks for some mental health care, and the first question they always ask is, “Are you having any thoughts about harming yourself or others?”. And the answer is simple. No. Sure, I might have thought of a couple of thousand ways to torture the tech support person who killed my site, but not serious ones. Just fantasizing as therapy.

But IS IT that easy a question? No, I’m not thinking of harming myself, but I wouldn’t have pushed back too hard about amputation or just killing the site completely. That doesn’t exactly scream self-preservation or self-care either.

My GP consult doesn’t see signs of clinical depression and my regular counsellor thinks most of what I was experiencing was a combination of factors including frustration with the leg and shock at the loss of the site, helplessness in being unable to immediately fix either one, and a giant overlay of “COVID isolation sucks” dampening everything down.

I tend to think both are right. But at times I also wonder if because I don’t act like a typical patient that I could be faking them out. If a mental healthcare worker asks me a question, I don’t dodge it. I embrace it full-on usually. Getting me to talk? Never a problem. Getting me to get to the point in your 50-minute hour? Sure, THAT’S a problem. But getting me to open up, talk about things, diagnose the issues, and contextualize it within a larger frame? I can do that in my sleep. Yet it can also make it look like I’m more functional than I am. Let’s face it, I’m an analytical squirrel on a GOOD day. And that can mess me up.

But as the second week of my status as a dead blogger continued, some of the shock wore off, and I could more ask myself, “Really? Are you really going that way? CAN you go that way?”

And finally I asked my wife for a blunt assessment as the person who knows me second best to myself.

Could she see me ever being happy without rebuilding?

There was no need for the Jeopardy theme, she knew the answer without having to think about it.

Which I also knew, or I wouldn’t have asked the question. I was trying to protect my mind from the shock during week 2 by framing it as a choice. But there was never any real choice.

I had to rebuild.

We have the technology; could I rebuild it better, stronger, faster?

Continue reading at Building back better for my website (part 3 / 4).

The Fall of PolyWogg (part 1 / 4)

The PolyBlog
April 19 2021

I want to talk some more about my website, and if last September was version 5.0, then the version I had as of February of this year was probably about version 5.2. I had added a few extra features, added some functionality, and expanded the base. I had made extensive progress with my photo gallery, and overall, I hate to say it, but I was feeling pretty good about it. From January 2020 to February 2021, I had drastically upgraded a TON of stuff on the site, and I felt like it was generally under control.

Jinxing myself

If feeling like things are going well, then February was probably a karmic risk. I was spending a little extra time on my photo galleries, and I was starting to feel like I had almost reached critical mass. I had 2005, 2006, and 2007 on the site, plus “regular 2008” and most of “wedding 2008”. I hadn’t quite finished the wedding albums, but most things were working so it was only a matter of time until I did. I was about halfway through the wedding albums, with my eye starting to turn towards the honeymoon photos, and beyond.

Except I ran into a small problem with the galleries. When I went to upload photos, I basically would open an upload window in the NextGen Gallery plugin, upload all the photos, make a number of tweaks, upload the videos, make some more tweaks, save it all, and then share it to FB.

But the upload was throwing errors for some reason. It took a while to narrow down even what the error was about, but essentially it would start uploading, and regardless of the progress on any file in there, if any one file took more than 30s OR the whole process ran more than 2m, then the files would time out. Now you would think that would be easy to figure out where the problem was — obviously there was a server setting somewhere that was timing out on me. Yet when I worked with the Level 1 and 2 support people with the hosting provider, we could not adjust the settings to prevent it.

Of course, I had to work through standard initial responses. “It’s a plugin conflict” … nope, I already tried deactivating EVERYTHING else. “It’s a theme conflict” … nope, tried that too. “It’s a problem with the plugin itself” … except it was the same version as the month before, no updates, AND I have the premium version. No change in the plug-in, but suddenly my server wasn’t letting me upload consistently. We tried modifying a bunch of different variables, mostly to make it more efficient so it would complete before it timed out, but we couldn’t seem to stop the 30s and 2m timelines. The plugin developer gave me a work-around so that it would do one file at a time, no concurrent loads (the default is 6-8 at a time in segments), and it worked most of the time. Right up until a file reached 30s and then it would time out. The 2m limit was still active though.

Now, the simple solution normally would be to do much smaller batches OR upload using FTP, but both added a bunch of extra steps to the process, so I was still trying to find WHERE in the server I was timing out.

Enter the dragon

I don’t want to appear overly dramatic, but I don’t know how to avoid it. I want to be fair, but at the same time, someone screwed the pooch. With the multiple attempts to “fix” things, someone in Level 2 support got the bright idea that there was something wrong with the configuration of my WordPress install. That it was taking too much overhead, and that was why things were timing out. That’s completely unrelated, but whatever, let’s not quibble.

Anyway, they sent me an email on a Thursday morning that said basically, “Okay, I’ve run an optimization on your WordPress databases and activated compression. I know that you said you didn’t want compression on your site, but it will speed things up, and the uploads should be able to complete.” He included pics / screengrabs of the front end of my site to show that it was all working.

I got the email on my personal account while I was working, and my immediate thought was, “Oh, crap.”

First and foremost, I’ve run compression on my site and it screwed up a BUNCH of things. It took some effort to undo them. Now, I ran it at the plugin level, and he was running it at the server level, but it scared the crap out of me. If he had asked me, I would have initially said no, not a chance, but might have been able to be talked into it. Except compression on the site wouldn’t affect my uploads — that would make my site render faster for front-end facing, but it wouldn’t improve my uploads, would it? (Answer: No).

Secondly though, I was wondering about the optimization process. When you run optimization, it often asks you what you want to do as part of your optimization:

  1. Simple optimization, looking for deleted entries that need to be cleaned up, etc.;
  2. Deleting revision histories, i.e., if you made a change, the previous “x” number of versions of that post are still available if you have to revert to an earlier version;
  3. Deleting auto-save / auto-drafts, i.e. if you leave the post open in edit mode for awhile, while you’re doing something else, and don’t close properly, your last “auto-save” is sitting there;
  4. Emptying the trash;
  5. Removing old comments that are left unapproved;
  6. Removing old transients, i.e., unattached orphan bits of info;
  7. Removing ping-backs and trackbacks to other websites;
  8. Removing orphaned meta data for posts and comments; and,
  9. Removing orphaned relationship info.

Generally speaking, what you keep or delete can be “everything” or “nothing”, and every point in between. The first one (simple optimization) is generally done by everyone, without too many problems, as can removing orphaned meta data (#8), relationship info (#9), transients (#6) and the trash (#4). But the rest? That’s highly personalized. I tend to keep up to 4 revisions in my history on current files, just in case I screw something up and want to go back in time without having to do a restore from backup. Older stuff? Sure, no problem, but recent revisions? Some plugins set the cut-off at 2w, which is reasonable, but I had no idea what the support guy had run. Auto-saves? Old comments? I didn’t have anything in the pipeline at the time, but it wouldn’t be the first time in my website history if I had examples of both that I didn’t want to lose.

So I wasn’t exactly thrilled that they had run both compression and optimization without checking with me first. But, the front end was working still, so should be okay, right?

The best-laid backup plans

Later that night, I tried to login to my site and it wouldn’t let me in. I had to actually go in through the server settings, reset a plugin, and then login manually a different way. Odd. But I figured maybe the optimization had messed something up. No worries, all in, reset, all good. Except it wasn’t.

I noticed one of my pages on the front-end looked fine on the blog home page, but when you actually clicked on it to go to the main page, it threw errors. In fact, ALL of my posts were throwing an error when it was on the full page for the post. Umm…Then a few other glitches cropped up. Okay, something’s not right. Time to go to the backup and revert the current version.

As an aside, there are 4 types of backups generally for WordPress sites that are self-hosted. First, you can make a manual copy of the entire site and download it. It’s incredibly time-consuming on a large site, but you can do it. Second, you can run a plugin that will make a backup of the site and store a copy either on the server or send it to some sort of off-site cloud storage. Third, you can run an external software that will backup from the server to a third-party site. Or you can use server software to backup everything.

I had some older versions of the site fully downloaded, so that was always an option, just old. In addition, I ran a backup plugin that had some versions saved on the server. And the big option, the server software option, had daily full and incremental backups. I had run into glitches previously where I had to use the server backup offered by my hoster, and they have always worked well. Even though they screwed up my site Thursday morning, there was a full backup run and available as of 8:00 a.m. that morning. Perfect, I restored from there.

Except the restore only partially worked. It gave me a restore…from almost 14m before. None of my recent work in the last year had restored, nor any of the content. Huh? Okaaaaaay, how about Wednesday? Tuesday? Monday? Nope, none of them would restore properly. Nor would the full-download version of the backup or the plugin ones stored on the site. None of the backups would complete. F***.

I ended up dealing with a CSR who was actually decent, and he figured out that for some reason, the caching software that all of their servers were running, Litespeed, was interfering with the restore. In essence, it was telling the restore that the files were already there, so it wasn’t restoring all of them. Crap. That caching software can’t be disabled. It is at the full server level.

Between the CSR and myself, we managed to run a series of “manual” restores on the Thursday morning version and in the end, we got all of the data back. It wasn’t accomplished by the rules according to Hoyle, but it was done. Whew.

Enter the gremlins

The backup completed, and I seemingly had everything back, but then I started to notice some gremlins. I’d go to edit an old post, and the photos I had linked to wouldn’t show in the editor. If I did a preview, some of them showed, I would refresh, and everything would be fine. Okay, looks like a simple caching problem. Then I would come back to the page, and something else wouldn’t work. I tried editing again, and a paragraph would be “missing”.

It looked at first like it was just “gone”, but then I would notice that the block was still there, it was just NOT SHOWING the text. So I would click on it, switch to the HTML mode, and it would give me a really weird set of codes. Blocks that were the simplest blocks of all would suddenly have almost CSS-like styling codes embedded with them. Huh? Where did THEY come from? How are they merged with my HTML content? WTF?

For my photo galleries, I had been embedding them on pages (rather than as posts), so I was running a plugin that displayed the pages as “nested” trees. It makes it way easier to manage them than as part of the standard WP page interface, yet with the gremlins, the tree wasn’t working consistently. I couldn’t move pages up or down, or I could move one and then have to totally reload the page before trying to move another. WTF x 2?

And then I started noticing some other gremlins. A couple of key plugins that I use were not working / loading at all, I started to get errors in the admin screen, which I could dismiss, and then 20m later, I’d get a similar but just slightly different one.

Finally, I ran into a problem where none of my reusable blocks were loading. Okay, that’s a problem. I tried disabling a few plugins and reinstalling them, I even tried reinstalling the core WP files. Nada. The gremlins remained. It almost looked like I had malware or a virus working its way through the install, but I don’t think so.

I think it was just that the restore had not properly restored everything.

Which left me with a choice

I tried a bunch of things, no luck. No new options from the tech support people, although I was a little bit gun-shy about their help anyway. They were the ones who nuked things in the first place.

So I gradually came to the sad and sobering realization. I had 24y worth of data, and while I had it back, the website that I had crafted over the last 17y was basically now unreliable. The foundation was shot.

I knew I could rebuild, with a massive amount of work. Did I want to?

Continue reading at My existential angst as a dead blogger (part 2 / 4).

I’m finally back in business for my websites

The PolyBlog
April 19 2021

Well, it has been almost two months since the technical support people at my website hosting partner accidentally nuked my site. The changes they made screwed up the site and the backups wouldn’t restore properly, leaving me with a huge reliability problem for some of the content. Pages that would work one minute and crash the next, posts that wouldn’t display properly, some pages or posts that disappeared altogether yet were still “active” on the site. Glitches that were annoying and not something I could leave in the site nor was I able to simply “fix” them.

I had all my data, but I needed to nuke the account and rebuild everything entirely. I rebuilt two sites that I host for others, and the content of those was relatively easy with a few annoying features, but it was the main PolyWogg.ca site that was the biggest challenge. 200 pages, 1600 posts, 1.6M words, 400 comments…all needing to be reloaded. And, as I noted, some glitches were embedded in several posts that required me to essentially reload things manually.

Working around the clock

But after two weeks of existential angst and six weeks of working at least 4h/day (at least 10h/day on weekends), and about 260 hours of work in total, my sites are back in business.

Because I had to rebuild the sites, and I didn’t want people getting daily update notices, I had to “force unsubscribe” anyone who was subscribed to my original feed for PolyWogg. Back on March 6, I sent them all emails to say, “Well, the site is down, and I’ll email you again when it comes back up”, while redirecting people to Facebook or Twitter to find me for now or in the future. I’m a little sad that many of them won’t resubscribe, but that’s the nature of the beast when running websites.

Today, I re-invited everyone to rejoin, we’ll see how many do. I now have two feeds though, one for each website.

PolyWogg.ca which includes my more formal “products”, such as my HR Guide, reviews, recipes, and astronomy-related posts;

and

ThePolyBlog.ca which includes my more informal blog posts, such as posts on Life (experiences, family, humour and computer-related topics like the website itself); The Little Grey Cells (more thoughtful topics like learning and ideas, writing and publishing, quotes, and health and spiritualism); goals; and my annual reading challenges.

If anyone else wants to subscribe by email, here are the two links:

Of course, people may prefer to access my posts through Facebook (PolyWogg.ca) or via my Twitter feed (@ThePolyBlog), as I try to post notices of new content to both feeds. I had to “force stop” the feeds during the rebuild process too, albeit one seemed to occasionally update anyways on Facebook for a few posts, but everything is back live again.

Of course, the work is never done

I have a few areas that will require more work still, but that isn’t entirely due to the website torching. As I rebuilt, I took the opportunity to redirect some of my efforts in a bit different direction. As a result, some of the solutions are not totally compatible with the previous structure. My trivia efforts had to be reset, my photo gallery is moved over to Flickr, and I’m taking a whole new approach to my PolyWogg Guide to Astronomy. Most of that change though is that as I did the other changes, I figured out better ways to handle those options too. That’s a longer term project though, and I’ll get to it over time. I don’t need to relaunch with those today.

On the other hand, I’ve done pretty well. Both sites (PolyWogg.ca and ThePolyBlog) are running about 45 plugins in total, and about 20 or so are new ways to handle the content (replacing older plugins that I was running before). I’ll blog about that in a bit more detail as the week goes on. More importantly to the reader, I have 604 posts / 45 pages / 570K words on PolyWogg.ca. Plus about 230 comments, most related to my HR Guide. Meanwhile, ThePolyBlog has 879 posts / 14 active pages / 981K words, plus about 220 comments. I’ve also streamlined the categories on both sites quite a bit.

As the planet starts to emerge from the COVID pandemic, one of the phrases being used is “Build Back Better”. I’m not 100% certain that it’s perfectly re-built, but it’s definitely better than it was, with more extensive branding for sub-areas, particularly the PolyWogg “products” like my HR Guide.

And more importantly?

It’s all the way back, baby! Onward!

Update on my rebuilding of my websites

The PolyBlog
April 17 2021

Well, it is almost two months from the fateful day when I received the email from my hosting company’s tech support that they had run a compression option on my website AND an optimization plugin. Either one alone was enough to send me into shock as compression has NEVER worked well on my site with the plugins I run, and optimization runs by deleting orphan elements in your database. Except there’s really no such thing as a universal orphan — some plugins treat autosaves that you haven’t worked on in two weeks as orphans and wants to delete them.

Sure enough, it nuked my site. Restores from backups ran into conflicts with the caching software and the result was that everything did NOT restore perfectly. Some posts would look fine one day and the next would crash when loading; some plugins on the backend wouldn’t load at all, and then an hour later worked fine. I suspect, but cannot be sure, that the fault was a combination of incomplete restores AND the caching software at the server level. In the end, the only way to rebuild in a way that was entirely reliable was to nuke everything and restore generally from zero. I had all the data, but the rebuilding still required me to pretty much update each plugin first AND to open and resave each post to make sure the data was complete. In several cases, I found glitches in the middle of posts — parts that DIDN’T restore properly — which supports my theory that the restore didn’t quite work perfectly.

Anyway, I’ve been heavy in the weeds for sometime, averaging 3-4h a night on the rebuild process, and I’m making progress. Here’s the status:

AstropontiacMCSIncPolyWoggThePolyBlogTotal
Active plugins12124847119
Total plugins13134948123
%92%92%98%98%97%
Active pages12541765
Total pages1256544126
%100%100%63%16%52%
Active posts——6014191020
Total posts——6048981502
%——~100%47%68%
Active pages+posts1256424261085
Total pages+posts1256699421628
%100%100%96%45%67%
Overall
(1/3 plugins,
2/3 content)		97%97%97%63%77%

It feels good to be over 77% done, although it’s hard to tell if the weighting is correct. I estimated 1/3 to get the plugins right, and 2/3 to rebuild the content overall. If I reweight it 50/50, it goes to 82% overall. If I reweighted the content higher, perhaps a 10/90 split, it would change to 70%. Soooo, I’m somewhere between 70-82% I guess. The stuff I’m doing now isn’t long per post, but it is REALLY mindless.

Dumb website…

The PolyBlog
February 8 2021

I like running my blog, but I confess, I’m not a big fan of the upkeep behind the scenes. Basic stuff is fine, it goes with the territory. I could pay someone to maintain my site, but since my site does not and will not ever generate revenue, I need to keep the costs as low as I can.

But some of the overhead is of my own making, sure. Or perhaps even a result of my own ambition. I’m not satisfied with using some site like Amazon Photos or Flickr, I want my own site to host my pics.

And so I have some extra admin headaches managing a large collection of photos and galleries. Like the fact that I noticed that some of my Galleries had inconsistent structures to the weburl. What does that mean? It means that the right setup is supposed to be, say for my seventh gallery of my wedding collection from 2008:

  • URL: http://www.polywogg.ca/pandagallery/yr2008/w07-bachelor party
  • Page title: 2008-W07 Bachelor Party
  • Gallery: 2008-W07 Bachelor Party

The URL had yr2008/2008-w07 (2008 listed twice), the page title was fine, and the gallery in some cases was messed up and said 2008-2g Bachelor Party because that was the old filenaming I did, and it hardcoded it into the directory structures. Is it a problem?

Yes and no. It starts off no but quickly becomes a yes when I start linking to things, and suddenly something that should link just fine, instead has a really weird file structure to it and a picture doesn’t load when it should. I was ducking and covering, letting it go, until I hit a snag tonight reading where the WordPress environment is going and realizing my little booboos are going to become bigger booboos later and it is better to fix them now.

Okay, it’s annoying, but an hour or two of quality control has me having corrected some past mistakes and I’m good to go again. Except I’m not.

I’ve got a gremlin. I don’t know what’s causing it, I don’t know when it started, I just know that for some reason, a gremlin is visiting my website.

Here’s the deal. For my gallery, I basically say “CREATE NEW GALLERY”, type in a gallery name, press enter, and then drag and drop all my photos for that gallery into the browser window. I press UPLOAD, and it puts everything onto the server and into the gallery for me. Easy peasy lemon squeasy.

It has worked this way for years. And now it doesn’t.

For some reason, my website has decided to time out in the middle of file uploads. Oh, no, not consistently. Just enough to be a PITA. It gives me an error message, saying out of 21 photos only 16 uploaded. So I note the five that it says didn’t upload. I reupload those. And it rejects one as already uploaded. Hmm…Okay, whatever, it took the four. So I go to the gallery and it says I have 24 photos. Wait, what? I had 16, I added 4 new ones, I should have 20 perhaps or 21 if the duplicate was an error. But how did I get 3 more than I started with?

Oh, right. Not all of those errors were actual errors. In fact, of the 5 it said it didn’t upload, it actually uploaded 4 of them. So I was only missing 1, right? Nope. Another two didn’t upload. No error, should have worked, but when I look at the photo, it is blank or incomplete. Umm, okay.

Plus, for some weird and wonderful world, one of the pics that didn’t upload, and isn’t in the directory, did upload the second time as it should have, but for some reason and some how, WP decided it was a partial duplicate. Not enough to block it, but enough of a duplicate to rename my filename to something like 1_image_xxxx.jpg.

Son of a firetruck.

Deep breath, dive into the rabbit hole.

Generally speaking, a problem with uploading pictures is USUALLY a problem with certain settings. And there are sites that list what the most common problems are for that error, and 8 different ways to fix them. Except none of those 8 ways apply to me. I know, because I had another problem back in December that WAS of that type and I fixed it. Or so I thought.

The app that is giving me errors is one I actually paid for, including support, so I’ve reached out to them for official suggestions. They gave me two solutions, I tried both, seemed okay, thought I was sorted, but tonight, it started throwing errors again.

Okay, debug time. What is the first step? Deactivate a bunch of other plugins to see if they’re conflicting. Yes, it works without them. Great, slowly reactivate them one by one until you find the one that’s a problem. It isn’t usually necessary to literally go 1×1, I find 5×5 is a good enough sort technique, reminiscent of advanced sorts in programming. I got about halfway through my list of plugins and hit a conflict. It stopped working. Great, that’s the problem.

Oh wait, I put another 5 in with no problem and then the next 5 conflicted again. Wait, there’s more than one conflicting? That’s unusual. Particularly for the narrow area I’m having the error in. Most plugins would never conflict with that. Weird. Okay two conflicts.

No, wait, a third. And a fourth? WTF? A fifth and a sixth? That is NOT possible. The plugin works normally, it’s a simple upload feature. It’s used by hundreds of THOUSANDS of people around the world. I know it works. WTF????

Okay, so it isn’t a real conflict. Maybe it’s a load issue? Like if I load 20 plugins, the server doesn’t want to run 20 anymore? I have 40 in total, mostly light load. They should run fine.

Sigh. Okay, I’m out of options. I reached out to the plugin again to see if they have other suggestions, and to my official server support to see if they know what would be causing it to time out after 30s when every variable in the system is at least 60s and I’m not over any obvious memory load. Hmm…

Why is this a big problem? Because it means I can’t easily upload my pictures right now.

Don’t get me wrong, there are other ways to put them on the server, including the most obvious one is to do a side-load equivalent to upload them using better software directly to the server and then have the app “copy” them from the server into the gallery. It adds about four steps to my workload to do all that, and it’s a totally separate PITA.

I can do it, but I sure don’t want to. I need to fix the original problem.

The plugin support did mention they have a beta app coming soon which would potentially indirectly fix my problem, it would just potentially slow the upload to a crawl. I CAN do that, I don’t know if I WANT to do that.

Did I mention that some days I think it’s a dumb website?