So…it turns out that there’s a serious remote exploit vulnerability in the download manager I use here on the Codex. Or, at least, in the legacy version of it I’ve been using these past few weeks, since the developers released version 2.7 of the plugin.

Because, you see, with version 2.7, they fundamentally changed how they handle download entries, in such a way that the new version of the plugin is incompatible with extant downloads from older versions. Upgrading would have meant re-doing each of the nearly 500 downloads hosted here at the Codex manually, one at a time.

Oh, and for added giggles, the new version of the download manager I use is also buggy, and may or may not occasionally corrupt a file here and there. This in addition to requiring me to re-create all the download entries one at a time. As such things go, I would hesitate to call this a winning thing.

But upgrading is an option, albeit one I had hoped to put off entertaining for the foreseeable future.

The other option is to switch to a different download manager. If I go this route, I’ve still got to re-create all the download entries manually, but…well, hopefully the new plugin wouldn’t be as buggy as the updated version of the current one evidently is.

But anyway…the download manager needs to be deactivated for the time being, and for that I apologize. This won’t impact the files themselves; they’ll still be on the server, and I can probably provide direct links as needed. But at least for the next little while, there won’t be readily-available downloads on any of the project entries.

Now if you’ll excuse me, I need to go flip a table or something.