Duplicate bibtex export
addoula - May 4, 2009 - 22:59
| Project: | Bibliography Module |
| Version: | 6.x-1.4 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
Hi,
I am using the latest 1.4 version (the problem also existed in older version).
I imported some publications using the bibtex import function. The problem is that whenever i want to export a bibtex for a publication, it is exported twice (same when using with the popups module).
The problem doesn't occur for publications created manually, or when i sign in to any user account. Only anonymous users have this problem.
| Attachment | Size |
|---|---|
| 2009-05-05_005754.png | 17.56 KB |

#1
Are you using any other access control modules like organic groups or taxonomy access control?
#2
Hi,
Yes, i am using Nodeaccess.. I disabled the module, and the problem was solved.
Re-enabling it, then rebuilding the permissions, and the problem is solved... :)
However, when i import a new bibtex, i need to rebuild permissions, in order to avoid the problem.
I guess there is a conflict with the nodeaccess module?
#3
I just installed and tested with nodeaccess and I don't see this problem. Did you set the defaults for biblio on the admin/user/nodeaccess page?
#4
Yes, View for all roles.. However, i checked "Give node grants priority".
I tested it again locally on a fresh installation, with only the two modules.. and the problem still exists. (duplications for anonymous users)
Only when rebuilding permissions, the duplication ends.
I am attaching a bibtex example (from wikipedia), where the problem happens.
#5
I don't suppose you would like to try the latest -dev version when it is rebuilt (with today's date). I think it should fix your problem.
#6
Yep, the problem is solved in the latest dev version :)
Thanks for your help.
#7
Great, then we'll call this fixed. That bug fix will be in the next release, but there is no harm in using the -dev version until then.
#8
Automatically closed -- issue fixed for 2 weeks with no activity.