EvC Forum is now running on the new server with no dependencies on the old. I decommissioned (deleted) the old server yesterday and it no longer exists (it was a virtual server, as is this one).
The new server has a couple additional features provided by an updated control panel that make it much more secure. The reason we moved to a new server was because while investigating persistent break-ins I discovered that the OS on the old server was being EOL'd, and so we'd have to move because though I could continue using the EOL'd OS, software providers would no longer support their software on it. In fact, this had already happened for the server's control panel, which stopped receiving updates around a year ago, as also had the firewall, which perhaps created a weakness that was exploited to break in.
The new server is running Almalinux 8.6. Almalinux is an open source version of Linux intended to fill the gap left by the EOL of Centos, our old OS. It calls itself a "1:1 binary compatible clone of RHEL" (Red Hat Enterprise Linux). Hopefully it will be around for a long time.
I've just released a bunch of very minor code changes that affect a lot of files. Behavior of the discussion board is unaffected, but these changes make the code simpler and easier to support. Please post here if you encounter any problems.
When I use the Peek button on a message, it strips out the embedded newlines. The dBCodes do show up, but the entire text is one big run-on. Basically the same thing as if you wrote an HTML page without any <BR> or <P> tags.
Same thing happens if I'm replying to a message and I click on the Peek Mode radio button.
What follows may fall under the "more than you wanted to know" category for some people.
This bug brought a larger problem to my attention. Older messages do not work with the new peek, so I'm simply going to rerender them, i.e., make them follow the same rendering rules as current messages.
But this will cause a change in their appearance. For example, in the prior rendering all quoted sections were followed by double spacing in the rendered message, whether the original text had double spacing or not. In the current rendering the spacing after a quote is up to the user: he can use either single or double spacing, his choice.
This means that an old message where the original text had single spacing after quotes was rendered with double spacing after quotes. When rerendered it will have only single spacing after quotes. If anyone objects to this type of change in old messages (older than a month) please post here.