Hello there!
I´ve been reading that there´s a HEAD version of Flexinode, so I think that maybe there will be a 5.0 version... but as I´ve been reading about the CCK vs Flexinode dilemma, and I want to remain at the Flexinode side of the life, well... I just wanted to check if there are plans for Flexinode in the near future.

I´ve been searching about this, to avoid creating a duplicate post, but didn´t find anything.

Thanks!
Rosamunda

Comments

Bèr Kessels’s picture

Bèr Kessels commented
Status: Active » Fixed

There is no 5.0 version, but we (me) are working hard on it. However, since the 4.7 release was .... (I won't say nasty words here) I decided we go trough a solid 4.7 release first. That is what HEAD is.

You will find more information below:
http://groups.drupal.org/flexinode-developers
http://webschuur.com/taxonomy/term/68
http://webschuur.com/node/643

Bèr

Rosamunda’s picture

Rosamunda commented

Thank you Bèr!!!!!!!!!!!!!!!!!

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)
desm0n’s picture

desm0n commented

Well i'm pleased its being worked on for 5.0 as i am not so keen to upgrade to CCK.

Rosamunda’s picture

Rosamunda commented

I feel the same way as you :-)
I just want to add to thios topic a question about the compatibility between 5.0 and flexinode.
I´ll keep walking the flexinode path, of course, but this post that I´ve just read, made me think about upgrading...
I understand that 5.0 version does NOT add cck to the core, but takes a little stuff from it...
I think I´ll stay on 4.7 for my production sites for a while.
Any thoughts about this?

Rosamunda

Bèr Kessels’s picture

Bèr Kessels commented

Drupal 5.0 has a little piece of CCK in core. BUT:
that conflicts with CCK itself. This made the upgrade of the CCK code to 5 a lot harder, because it now should either upgrade and work around that conflict (a real hack) or integrate (a looong and windy road).

My plans for flexinode are:
1. get a stable 4.7 ready
2. get a stable 5.x ready (the hack route, working in parrallel to the flexible content types in 5.x)
3. get a better 5.x version ready: integrate with core.
4. get a much nicer, normalised database architecture for flexinode in place.