Good luck on converting all 37k nodes. Your solution doesn't sound at all simple.
Flexinode was a major module. The decision to abandon it in favor of CCK wasn't made by some lone "maintainer" but by the people who decide the general direction of Drupal.
The fact that there's no easy upgrade path is an extraordinary oversight. It's an absolute red alert to anyone considering using Drupal. This isn't getting people to do my work for me. Rather, it's a pretty basic expectation of what a CMS ought to do. Nobody chooses a CMS just to be led to this kind of cliff.
And of course the ultimate irony is the attention paid to usability. What audience requires a CMS that's easy to use but not at all easy to preserve? Given the context, such concerns are pretty much superfluous.
Reply
Drupal4libcamp
February 27, 2009, Darien Public Library, Darien, CT
This work is licensed under a Creative Commons Attribution- NonCommercial- ShareAlike 2.5 License.
Easy enough to say...
Good luck on converting all 37k nodes. Your solution doesn't sound at all simple.
Flexinode was a major module. The decision to abandon it in favor of CCK wasn't made by some lone "maintainer" but by the people who decide the general direction of Drupal.
The fact that there's no easy upgrade path is an extraordinary oversight. It's an absolute red alert to anyone considering using Drupal. This isn't getting people to do my work for me. Rather, it's a pretty basic expectation of what a CMS ought to do. Nobody chooses a CMS just to be led to this kind of cliff.
And of course the ultimate irony is the attention paid to usability. What audience requires a CMS that's easy to use but not at all easy to preserve? Given the context, such concerns are pretty much superfluous.