Closed (outdated)
Project:
Bibliography Module
Version:
6.x-1.9
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
21 Oct 2010 at 12:12 UTC
Updated:
21 Dec 2018 at 19:00 UTC
Jump to comment: Most recent
Comments
Comment #1
rjerome commentedI suspect the problem may lie in the the fact that the biblio related node information was not deleted from the node_revisions table, since every node has a corresponding entry in the node_revisions table.
Prior to your SQL command above, you should have executed...
Which would first clear the biblio data out of the node_revisions table.
The only other problem you might encounter with the scenario you describe (deleting nodes but not authors) is if you made and modifications to author names AFTER you imported them the first time. If so, the second import will create a new author, but if you are seeing more additional publications attributed to authors, I still suspect the node_revisions table issue.
Ron.
Comment #2
sebos69 commentedactually, priori to
I performed
Is it similar to what you suggested? Sorry for the bothering...
Comment #3
rjerome commentedYes, that appears to achieve the same result, so there must be a issue elsewhere. Thinking about this a bit more, you would have to empty the biblio_contributor (and biblio_keyword) table prior to reimporting because they both have references to nid's. Also, did you empty the biblio table prior to re-import?
Comment #4
sebos69 commentedI don't think so... the two SQL requests were the only command I typed.
But here is a funny fact: under the "admin" username (first Id), this bug appears, but it seems to disappear when logged as a normal user with administration permissions.
Comment #5
rjerome commentedDo you have some "unpublished" biblio nodes? Only the admin would see those.
Comment #6
sebos69 commentedNope, there are no unpublished biblio nodes. It seems that the biblio nodes deleted by hand (wyth SQL queries) are still counted in the contributors list.
Comment #7
rjerome commentedHmmm, I'm running out of ideas, here is the SQL that builds that page if that helps...
Comment #8
sebos69 commentedOK, after digging a little bit more, I found something interesting. We had a similar issue with keywords (which are easier to debug on). One keyword was not used in any node, but it was present is an old version of the node (an old revision). So the keyword was not qualified as an orphaned keyword. Deleting the revision actually made the keyword orphan and the problem is fixed.
I guess this problem can occur for authors as well?
Comment #9
liam morlandThis version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.