webschuur.com

Untill today I run only one site on a recent HEAD of drupal. And I am not at all happy with how things go there. This, I have to stress, is not because of certain features, or people, its because, I, (as a part of “we”) made some wrong decisions, that got us in a spiral of issues, everytime more issues, and so it got us stuck with a heavily delayed release.

The problem is mostly that I have to meet deadlines. That I have to make plannings and quotes based on estimated amount of hours. And I have found that this is near to impossible when you want to be involved in development for HEAD. The “things” you might encounter are too uncertain. The severety of the open bugs is too uncertain, to start building a tightly budgetted project on top of.

This chapter contains all the requirements (what should it do), functional descriptions (what does what) and the targets (what we watn to achieve). Please log in to edit, this is a first draft.

These wiki pages are the home of the “modular file system”, or better known as “betterupload” module.

Today Tom did a great job on structure, defining and layout of the various flexinode content types that were created. here they can be found.

Last night our ibiblio MySQL server was down. I have a stron feeling that thios was due to our strange mysql but in the forums. The odd thing is that I tried to log into teh database, but found nothing there: no corrupted tables, nor anything else. Next thing I should do, is remove the forum things and start with a clean forum, but that is quite hard, because the forums cannot be cleaned from the web, because of that bug.

I am not sure what causes that erre, but I have a stron feeling it is due to a failed insert in the database on the exact moment a forum entry was created. It is not a known but, nor has anyone ever seen that error on any of their own installations.

I do not know what the exact reason is, but I think it has something to do with the overloaded servers at ibiblio. The connection crashed a few times already, so I think we have invalid content in the database now. I will have to log into the dattabase to see where the problem lies.