Posted by chris55 on June 21, 2008 at 11:00am
Jump to:
| Project: | Revision Deletion |
| Version: | 4.7.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Nodes that have been created with cck and then revised don't appear in views after running revision_deletion.
I've checked the node_revision table and it seems to have done its job correctly. ie. the latest vid has been retained and the earlier ones deleted. But in the cck node_content table the original vid is still recorded and as yet I haven't discovered how it's supposed to get to the latest version.
Comments
#1
Ok, I think I've worked out what's going on.
For each cck content type there is a table node_content_ccktype which mirrors the node_revisions table in that there is one entry per version. What had happened was that the most recent version of each node had disappeared (leaving the older versions there).
I'm not exactly sure of the route, but I assume that when a node is deleted, cck deletes the node_content entry and chooses the most recent version to delete. I haven't found the mechanism yet.
So it's debatable whether it's cck's fault or revision_deletion's. But in any case, DON'T USE THIS MODULE if you are using cck.
I can supply a subset of the tables if someone wants to debug this. But they are pretty large - node_revisions was 21MB (uncompressed) in my case.
Chris
#2
Thank you for finding the cause for this issue. Since CCK is so widely used, I will need to figure out how to make these compatible.
#3
Actually, I just noticed that I had a bug fix that I never committed to CVS. I have updated both D5 and D4.7 versions, with the explicit revision number callout for the deletion execution. Should be fixed now.
#4
Code fixed and released in June 22 release. Will leave for another week in case it is not fully functional.
#5
just finished testing the module 5.x 1.1 on a test site with cck and ubercart and over 5000 nodes, i couldn't reproduce the bug, so i confirm that the bug.fixed.
#6
Thank you for verifying. Closing issue.