$100 Bounty: Convert Flexinode nodes to CCK nodes

$100 Bounty: Convert Flexinode nodes to CCK nodes

The Skinny: Convert ~ 350 nodes that currently use Flexinode to the CCK module. At minimum the new CCK nodes must work appropriately (fully editable with the userreviews still "attached") in my Drupal 5.x upgrade (currently using Drupal 4.7.x).

It would be preferrable that this was done via the Flexinode to CCK Converter module so the updated module and documentation can be contributed back to the community to assist other Drupal users migrating from Flexinode to CCK.

Payment: $100 upon completion using Paypal unless other arragements are made.

Contact: fof@pluswebdesign.com

Website: http://www.tammysrecipes.com

Full Desciption of Issue and Request:

I am actively in the process of migrating from Drupal 4.7.x to Drupal 5.x. In this process I have one substantial hurdle: Flexinode is a 4.7 module with no planned 5.x build. Unfortunately, I have about 350 recipes using a custom node, via Flexinode, called "Recipe". The website is a Recipe website, so abandoning the Recipe nodes isn't an option.

Further complicating the issue is that "manually" converting the nodes by hand won't reach my objective because "attached" to each recipe node ID is a user recipe rating (over 850 in total), via the Userreview module. By creating a new node (and all the hassle and time of inputting content and messing with the clean URL paths) all the Userreview nodes would be "orphaned".

The good news is there is a Drupal module, Flexinode to CCK Converter, that converts Flexinodes to CCK nodes. It retains node IDs and should be perfect for the criteria I have (see below).

The bad news is I haven't been successful in converting these nodes (or even simple test Flexinodes) to CCK. The good news is that as I cannot even get a simple node to convert this is most likely a user (me!) error.

Objectives: Successfully convert my custom Flexinode "Recipe" nodes to CCK nodes so I can migrate to Drupal 5.x. A successful conversion is defined by the following:

* Convert the "recipe" Flexinode nodes to a CCK nodes. There are about 350 recipe nodes.

* All data must be retained.

* New CCK nodes, and all fields therein, must be editable.

* The pictures in the nodes, originally inserted using the Flexinode image field, must be retained.

* The node ID must remain intact for each node and not change (or another solution) so the user reviews (Userreview module) remain "attached" to the individual recipe nodes. I have over 850 reviews from users that I do not wish to be orphaned from the recipe nodes.

* New CCK nodes retain "clean URL" path as well as Taxonomy.

* The ability to use CCK to add new recipes to the "Recipe CCK" database.

=> If the Flexinode to CCK Converter module is used to accomplish the above goals, the resulting code contributed back to the community unless other arragements are made.

While I believe all of the above are technically achievable, I am willing to be flexible on some of the points if necessary.

FYI, my Flexinode node has about 10 fields, 1 being an image, and the others being a mix of text fields and text areas. You can see more about them on this troubleshooting post.

You can read some "back history" on the troubles I had with the "Flexinode to CCK Converter" module and the Userreview module node ID information below:

Flexinode to CCK Converter discussion: http://drupal.org/node/166843
Userreview and new nodes discussion: http://drupal.org/node/114102