I am hesitant to say that I have good news or that I have fixed anything… I honestly don’t know if there is anyone left still using this site after all the problems we’ve had.
That said, I noticed that there were some very recent (as in yesterday/today) commits to the development branch of kbin that look like they address the issues that fedia has been experiencing. I moved fedia to the development branch and reloaded some things, and so far, no error 500’s.
But, caveat emptor, we are on the development branch of early-in-its-lifecycle open source software.
I have discovered that the vast majority of my 500 errors have gone away after removing the PWA version off my windows machine. It was using MS edge. Using.firefox, even with highest security settings and ublock origin.
I noticed.first.that in the pages header that magazine was not showing as an option. This sent me.down a.rabbit hole of messing with Edges settings and finally giving up on it and resorting to removing the PWA version.
Once I did that, the 500 errors stopped. Now I only get a 404 trying.to open my profile.
I found/fixed the issue with your profile getting a 404.
If you find any repeatable 500’s, please let me know.
Appreciate it. Although more 500’s popping up. Posted on the.June 29 update thread.
It’s more instances of a problem I thought was fixed: magazines, posts, comments, and users can have associated images. For some reason, kbin thinks it received and created a record in the “images” table, complete with a unique record ID, and associates that image ID with the magazines, posts, comments, and users as appropriate. For some reason, though, that image record doesn’t actually get created. When kbin goes to render a magazine, post, comment, or user, it sees that there should be an image associated and tries to look up the image to get the file name - that query fails and kbin doesn’t elegantly handle that, so an error 500 results any time that happens. I have to fix it by running a series of queries that null out missing image IDs. The bad part is that I am no longer seeing errors that are causing that behavior, so it’s more tricky to debug the remaining issues now, but I am working on it.