Problem/Motivation

My node revisions table was hosed after running a Node Convert template against my Blog content. I bulk replaced ~140 nodes of type Blog with a custom content type. What I ended up with is ~140 nodes that largely duplicated four or five single blog posts.

Something that I do recall happening during the conversion: the conversion took three passes through my content, as I filtered on type "blog entry", checked the box to select all of the list, and then applied "Convert ". On the very first pass, I received no messages that the conversion had occurred, although the next two passes gave me a message for each node.

Proposed resolution

Workaround: I ended up fixing the hosed node revisions by re-importing that table alone from a backup I had made prior to installing Node Convert. Oh, and I had to "UPDATE node SET `changed`=`created` WHERE 1" to have the node mark "NEW" not show up and have my search results show a correct date -- every single node was updated with the dat of the conversion.