Bibtex file import actually works, however, a blank page is returned instead of a confirmation page.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 247058_blank_page_after_import_02-d6.patch | 2.94 KB | soxofaan |
| #5 | 247058_blank_page_after_import_01.patch | 4.52 KB | soxofaan |
Bibtex file import actually works, however, a blank page is returned instead of a confirmation page.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 247058_blank_page_after_import_02-d6.patch | 2.94 KB | soxofaan |
| #5 | 247058_blank_page_after_import_01.patch | 4.52 KB | soxofaan |
Comments
Comment #1
rjerome commentedSounds like a PHP problem to me. Most likely you are running out of memory or the script is exceeding the maximum run time limit. If you have access to the php.ini file on your server, you should try increasing the memory limit first.
Ron.
Comment #2
dlx commentedI have 64M memory limit for php. Version 1.13 did not have this problem.
Comment #3
rjerome commentedOk, That should be sufficient. Do you see any errors in the PHP logs? (Not the drupal logs, but the actual php log)
There was a change in the bibTex parser since 1.13, so I'll check to make sure everything is working as expected.
Comment #4
dlx commentedHi Ron,
The php error is:
Cannot modify header information - headers already sent by (output started at ~/public_html/sites/all/modules/biblio/bibtexParse/PARSEENTRIES.php:617) in ~/public_html/includes/common.inc on line 314.Alex.
Comment #5
soxofaan commentedThe reason is that some include files from the bilbio module have whitespace after the closing "?>" tag.
This whitespace is emitted before the headers are sent, which is why you get the "headers already sent" error message.
The easiest fix is to omit the "?>" closing tag all together at the end of module and include files.
This is a feature of PHP (see the note on http://www.php.net/manual/en/language.basic-syntax.instruction-separatio...),
and common use in Drupal code (see http://drupal.org/node/545).
Comment #6
rjerome commentedYour quite right, thanks for pointing that out.
Ron.
Comment #7
soxofaan commentedshould be also fixed in DRUPAL-6--1 and HEAD probably
in attachment, patch for DRUPAL-6--1
Comment #8
rjerome commentedAlready done...
Thanks,
Ron.
Comment #9
soxofaan commentedyeah, sorry, I was too fast ;)
But I think you forgot bibtexParse/PARSEMONTH.php and bibtexParse/PARSEPAGE.php in both DRUPAL-5 and DRUPAL-6--1
And in HEAD there also seem to be some trailing "?>" in:
biblio_style_apa.inc
biblio_style_classic.inc
biblio_style_cse.inc
biblio_z3950.module
bibtex.php
endnote7_parser.inc
endnote8_parser.inc
Comment #10
rjerome commentedComment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.