If you notice that the Forum site is slow or glitching

I noticed that the top left logo is not linking to the main wiki site. I think that Forest did something to temporarily stabilize the wiki but it's now hard to get there, and the page formatting is kinda minimal.

To me, the most important and used location is the SEP, which you can reach here :
https://www.tmswiki.org/ppd/Structured_Educational_Program

 

That's the most frequent error I get, but sometimes it's just a timeout.

Well, we're all exhausted these days...

 

I just doubled the amount of memory available to the forum software, but it didn't help. The previous messages indicated that the memory size of 67108864 bytes is exhausted, but now the memory size is 134217728 bytes is available (twice as many). Sadly, it didn't help.

I'm also working on upgrading the server with twice as much RAM and twice as many CPU cores. I don't think it's going to help, but it's going to take so long to build the new server that I'm willing to try anything (my current informal estimate is 3 weeks to 1 month).

I remember when I was young, I had to eat "3 bites" of every dish at dinner.

134217728 bites would have been a whole other issue...

 

Indeed. But XenForo is such a massive system that it would be a huge project for an outsider to debug a memory leak.

Much more importantly, it wouldn't fix the core issues that the software will never be stable until it's replaced with a newer version.

The conversion is coming along slowly. My day job is time consuming and my mother-in-law just passed away, so that it putting additional stress on my family.

I'm beginning to think that the instability of the current system means that I shouldn't worry about tweaking things until the new server has things like bookmarks, tags, and keywords fully implemented yet.

The new version of the core software will just run many many times more smoothly and reliably, so I'm thinking that as soon as I can, I should just switch over to the new software. After that is done and we have a reliable server, I can worry about things like bookmarks, tags, and keywords. (It turns out that getting bookmarks, tags and keyworks set up will be a long slog because after I find new addons for each of those functionalities, I'll have to do a complex data transformation.)

 

Yeah, I think that's right. That being said,
I would hate to lose all my bookmarks, although I have so many at this point it's pretty overwhelming to try to find anything, and there's no way to search your own bookmarks. But still...

Sort of a bookmarky thing is a new feature in the upgrade that I really look forward to using, which is the ability (of mods) to select certain threads as "Featured". Featured will be a new selection in the "Recents" menu - I can't wait to use it for real.

As for the keywords, I've always thought they were kind of quirky. It seems like a great idea to have keywords linked to the wiki's index of symptoms for all the various words describing areas of the body where symptoms can be experienced - but it can get a little ridiculous when those words are used in other contexts as they so often are. I have to chuckle whenever I see those links auto-inserted when someone with, say, back pain, says something like "shoulder the burden", "can't stomach the pressure" "a pain in the neck" etc. So many body part words are used in everyday contexts that are completely unrelated to symptoms! It's actually a little distracting.

The most useful ones are, I think, the links that lead to our most significant resources, especially the locations of our programs. Just last year I updated the auto-links so that the acronym "SEP" came up with the relevant URL, and for Alan's two programs, I think I added a couple of variations that people often use to describe those, so they can go straight to the source from any casual references without having to ask for clarification on older threads.

Having been in the "back rooms" of the software a fair number of times, there's a lot of stuff there. The prospect of redoing or somehow transferring these big databases is indeed daunting. And I certainly agree that these are things which can be put off, with focus going to a beautiful new stable server and software which meets the requirements of current protocols!