Export citation results in empty files

Help
Anonymous
2011-08-14
2013-05-28

  • Anonymous
    2011-08-14

    Hi.

    I have refbase 0.9.5 with lighttpd 1.4.26, MySQL 5.5.13 on Fedora Core 15 64bit.
    Every time I export a citation of one record with Refbase I get an empty file, with every format.
    I've already chekced that bibutils is accessible to lighttpd and has path correctly configured, and that php session directory /var/lib/php/session is accessible to lighttpd. SElinux is disabled.
    I couldn't find help on the forum that suited the situation I've been experiencing.
    In the lighttpd error log it reports

    2011-08-14 17:54:48: (mod_fastcgi.c.2711) FastCGI-stderr: PHP Warning:  mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/lighttpd/refbase/includes/include.inc.php on line 5817
    PHP Warning:  date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/lighttpd/refbase/includes/include.inc.php on line 5851

    at every export operation. Is it relaetd to the problem?

    Do you have any idea on how I can fix that?

    thanks

     
  • You should set date.timezone in php.ini, as you are instructed to by that warning and in the php documentation.  However, that is probably not the reason for your export woes.  Are you sure that export to MODS XML fails?  Does it fail regardless of the record or records you attempt to export?  Does import of bibtex/MODS/other formats that rely on bibutils work?

    -Rick

     

  • Anonymous
    2011-08-24

    it was a problem with SELinux in the end, which I'm sure to have already disalbled some time ago.

    I aplogize for the confusion

    a.t.