Most converted nodes failing to display [#149460]

All nodes appeared to convert OK and all seem present and correct in the relevant content_type_X table. However the majority do not show any data when viewing or editing the nodes: all fields appear empty, even though the data is manifestly there for each field in content_type_X. This problem occurs whether or not Contemplate is enabled. I have pored through the database trying to figure out what distinguishes the minority of X-nodes that display & edit correctly from the majority that do not, but I haven't found any distinguishing features in their entries in the content_type_X, node or node_revision tables. Is there anywhere else I should look? Newly created X nodes work fine.

Thanks for any suggestions,

Dave

Comments

Comment #1

Darko commented 5 June 2007 at 20:48

I needed to convert several flexinodes to cck, and today i installed and ran flexinode converter. I encountered the same issue as you describe. Looking at the database and parsed pages the issue seems to be that the content from the node_revisions populates the body field with the old flexinode data.

Try this to confirm: Take one of the converted nodes, go to the edit screen and populate the empty fields. The node will now have both contents, the old one as flexinode div and the new one as the cck div (mixed together most likely).

Working on it right now and i will post the solution, unless someone already has it.

Comment #2

Darko commented 6 June 2007 at 02:27

TRUNCATE TABLE `cache` will solve the issue.

Comment #3

davej commented 12 June 2007 at 11:40

Thanks for the suggestion but truncating the cache table didn't make any difference for me. I'm not using caching on this site at present. Just to emphasise, the majority of my converted nodes do not show any data when viewing or editing the nodes: when editing, all fields are empty. It's not just a display issue.

I had to use my patch - see node type not updated when there are existing CCK nodes - to get the conversion to work, so it's possible that the problem is related to that. I think the patch is innocuous - it just counts the CCK nodes before & after conversion instead of assuming that the number after conversion is the number converted - but perhaps it exposes a further issue that occurs when there are preexisting CCK nodes prior to running flexiconvert.

Comment #4

davej commented 12 June 2007 at 14:15

I'm happy to report that truncating cache_content solved the problem. :-)

Comment #5

Chad_Dupuis commented 19 August 2007 at 04:11

While marginally related to this issue - my data was showing up twice as the previous poster mentioned data getting put into the cck fields and the node revisions body table. This is how I fixed this:

http://drupal.org/node/168549#comment-263361