Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By Chad_Dupuis on
I am working on a test site so I cannot show the issue at hand, but would appreciate feedback.
I have upgraded my site - http://www.yinyanghouse.com/ from 4.7 to 5.2. I had a number of flexinodes and with the flexiconvert module I was able to convert everything to CCK pre upgrade and all was well to go to 5.2. (I did have to use the flexiconvert patch for long field names, but that's just fyi).
Now that I have converted to 5.2 all of my cck nodes that are within book pages (the others are still fine, and all were fine pre 5.2 upgrade) have the data show twice so:
My title:
My data is here
My other field:
My other data is here
[should end here, but I then get the same data again?]
My title:
My data is here
My other field:
My other data is here
When I look in the database the node revisions table has the correct data - so it appears to be something with the book module but I don't really know where to look. Any help would be appreciated - particularly from folks who have tried to update flexinodes in 4.7 to get to 5.2.
Thanks!
Comments
slight correction - this
slight correction - this happens in all the nodes I "converted" - not just those within the book outline.... and, again, all was well before the upgrade to 5.2 after the conversion of the nodes.
Just to offer my fix in case
Just to offer my fix in case others run into similar issues with the flexinode to cck converter.
As someone pointed out in the cases the converter has the potential (at least this is what it did for me and others it appears) to write the flexinode body data into the node revisions body table and the CCK fields data table so the data will show up twice.
To fix this I did an sql query in phpmyadmin in the node revisions table where body was LIKE %flexinode-body% - this will give you all the converted nodes. I then exported these in an sql file and then did a perl one liner to strip out all the body fields:
perl -0777 -pi -e "s#'<div class=\"flexinode-body(.*?)<\div>'#''#g" sqlfile.sqlthenperl -0777 -pi -e "s#INSERT INTO#REPLACE INTO#g" sqlfile.sql(so you can overwrite the values)then cut and paste all the replace into statements (everything below the table creation lines) into an sql query in phpmyadmin.
After this you will only see the CCK data....
I'm not sure this is the right way to do everything, but it worked for me.
Another way to do it
I had the same problem after a recent flexiconvert. I seem to remember that last time this happened, truncating cache_content fixed it, but not this time. Like Chad, I ended up removing the body of the relevant nodes in node_revisions. I used the following SQL - all usual warnings apply, don't use this unless you understand what it's doing, back up your db first, run it on a test db to check it does what you want, your home may be at risk etc.
update node n inner join node_revisions nr on n.nid = nr.nid set nr.body = '' where n.type = '<your_cck_type>'Dave Jenkins
Circle Interactive