webschuur.com

I have been receiving quite some (aggressive and unkind) requests for flexinode. I don’t really mind if people are rude, I just hope these people understand that by being rude they actually reach the opposite of their goal: instead of me jumping up and fixing their problem, I’d think: well, if this is all I get for the effort, why bother. It strengthens my believe that Open Source is a scratch your own itch, selfish, concept.

In any case, I think its time for a short update on the status and plans. Flexinode for Drupal5 may never get to see the light, but then again, it may just as well get released very soon. Why so vague?

I just released the third release for 4.7 flexinode. This is a preview release, so I advice you not to run it on your production site yet. That said, I expect this release to already be far more stable then the 4.7 “release” we had earlier 2006.

The main difference is that we no longer recursively search for fields.
Another mayour milestone, is that all core./critical fields are now tested and included.

Please test it, and provide feedback.

I just added ‘recursive FALSE’ to filescandirectory: fields in contrib and other subdirectories are no longer automatically added to the fieldlist. One needs to copy the fields to the root dir, in order to activate them.

Only the ‘core’ fields are available byt default now.

The reason is twofold:

1. Organise the fields better. This is the first step, vote about your preferences here.
2. Stop the many issues on broken and not maintained fields from pooring in. Flexinode only supports the core fields, all other fields are contribs and people’s own responsibility. This change highlights that.

I just released the first release for 4.7 flexinode. This is a preview release, so I advice you not to run it on your production site yet. That said, I expect this release to alerady be far more stable then the 4.7 “release” we had earlier 2006.

Please test it, and provide feedback.

This morning I waded trough all the image-field bugs for Flexinode. Most of the issues were duplicates (Folks, please, search and read other issues when filing new ones), but there were some serious validation problems.

All but one are solved now, the last one, is a problem that will occur when upgrading/updating. In 4.7 a few new configuration features (regarding resizingof images) were introduced, yet no-one ever created a way to make all the old content update to these new settings. Nor did someone think of a way to insert default settings in case of an upgrade.

This last one, is a particular nasty one.

The list of flexinode issues has shrunk a lot. I closed about 30 per day, and think I have now got a list with bugs that actually exist, or need to be confirmed.

A dynamic up-to-date list is here. By time of writing it were 25 bugs left for ‘core fields’ and flexinode itself.