The Blades Forge

Select ratingPoorOkayGoodGreatAwesomeGive it 6/10Give it 7/10Give it 8/10Give it 9/10Give it 10/10

No votes yet

You may have noticed that the site was behaving oddly in the past few days.

Last week, I realized I had not applied a Drupal software update to the Blades Forge in quite a while. That's bad, because these software updates often fix security problems. Since this site is deployed using the Drupal CVS repository, updating it is as easy as running "cvs up".

While running the core update (which went well) I decided to update the numerous addon modules as well. While doing that I managed to make a whole series of mistakes that led to deleting all addon modules (mental note: stay away from your website after 2 AM, and avoid many tears) ...

Since I had a list of the modules that were there, downloading them again was just a nuisance, but no big deal. Unfortunately, there were some holes in that list, so several modules were not downloaded. These were the "imagefield" and the "computed_field" module.

The immediate effect was that all graphics data (scenario icons and custom graphic sheets) were no longer displayed, though they were still in the database, and the Scenarios overview was empty, because "computed_field" was needed to determine whether or not a scenario was released.

A third problem was that I lost several customizations made to the addons, which were not in the official code. One of these was a feature that allowed text fields with a specially selected format - which was required for the "Avernumscript format" field in custom script nodes. The effect was that script content was no longer loaded or displayed.

Fortunately, I had a patch file that made that particular change, so I could reapply it to the official code, and now scripts work again.

If anything still does not work, then please drop me an email.