Since 7.x-1.0-beta1 up to today's dev all downloaded Bibtex / RIS / EndnoteXML-Files, regardless of single entries or longer lists, produce a file with something like this:

<br />
<b>Fatal error</b>:  Call to undefined function  biblio_get_contributor_category() in <b>[serverpath]/blog/modules/biblio/modules/bibtexParse/biblio_bibtex.module</b> on line <b>382</b><br />

The database is MySQL 5.1.43.
But it worked normally on this installation before, can anyone make sense of it?

Comments

rjerome’s picture

You definitely DON'T want to use beta1 (a nasty bug slipped into that one) but I can't reproduce your issue and I can't think of anything that would have changed to cause it.

Try clearing your caches (this is the Drupal equivalent of re-booting a Windows machine :-) it often fixes all the problems.

Thorsten’s picture

Unfortunately, clearing the cache doesn't help, and I'm having these issues with beta2 and the latest dev as well ... and I experienced this issue in multiple test installations with different data sets. E.g. http://www.thorsten-ries.net/biblio , which is a fresh setup with the latest devel of biblio.
However, RTF export is still working just fine.

rjerome’s picture

Although I can't reproduce this, I've pushed a change that should fix it.

http://drupalcode.org/project/biblio.git/commit/ec57c0e

Ron

Thorsten’s picture

THX A LOT! You rock, greets, Thorsten
Update: I applied the patch manually, confirm: works like a charm! Thanks again!

Thorsten’s picture

Ok, I overlooked one little thing while testing: now the export links for the whole bibliography work correctly, but the links for individual entries still act wacky ... maybe this magic codeline is still missing elsewhere ...

rjerome’s picture

Opps, I put it inside a conditional which (as you found out) only applies to the global link, I've move that line up a bit (out of the conditional) and it will apply to all exports now.

Ron.

http://drupalcode.org/project/biblio.git/commit/ada74f5

Thorsten’s picture

That's it! Works! :-) Thanks, again!

rjerome’s picture

Status: Active » Fixed

That's good to hear. I still don't know why that didn't happen on my installations, but that's not important.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

Added MySQL version, as this was asked on a similar issue.