Flexinode

I just released flexinode's 4.7 third preview release.
If you want to keep up-to date, follow flexinode news here (RSS).

I just released flexinode's 4.7 first preview release.
If you want to keep up-to date, follow flexinode news here (RSS).

The stroked fields are confirmed, tested and thus ready to go for 4.7:

Critical fields:

• textfield
• textarea
• datefield/timestamp
• number
• image
• general file
• selectlist
• checkbox
• url
• email
• multiselect

None critical fields (contribs)

• podcast_author
• address
• table
• usergroup
• colorpicker
• external_attachment
• gallery
• mp3
• imagegal

I am trying to weed out the many broken or duplicate flexinode fields.

The first differentation I want to make is between critical and non-critical fields. With a new release (4.7 and 5.0) the critical fields should all be released and working. Non-critical fields can be updated later.

I want to know what you consider critical fields, my personal list is included below.

• textfield
• textarea
• datefield/timestamp
• number
• image
• general file
• selectlist
• checkbox
• url
• email
• multiselect

Please leave your list in a comment.

Hello flexinoders,

I am working on a new, better 4.7 release, as you may have noticed. This is the first step in preparation of a 5.x release.

For that, I am looking for real-world databases to test and develop the upgrade with.
Do you have 4.6 flexinode data lying around?

Crossposting from my blog.

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.

Flexinode still has potential. A lot.
I started off with, what I beleive to be the Perfect Normalised Usable, yet Simple fields system. I posted the ERD and some notes on my website. We should get that somehow into some wiki, to create the Ultimate Architecture and Plan.

I posted a recent flexinode update on my blog. Please read that, to see where we are now and where we are heading.

The most important part from that post is:

1. First we must clean out all the code and remove broken fields.
2. Then fix all critical bugs.
3. Then fix the upgrade path from 4.6 to 4.7.
4. Once stable, a 4.7-2.0 release will be brought out. and a 5.0 branch is opened.
5. Then I will start committing patches to prepare for a 5.0 release.
6. Once stable, a 5.0-1.0 release will be brought out.
7. Then new features make a chance o