Page MenuHomePhabricator

wiki/Special:ExportRDF - XML Parsing Error: xml declaration not at start of external entity
Closed, InvalidPublic

Description

Author: wolfkden

Description:
I installed ExportRDF with the semantic-bundle extension and attempted to parse "Main_Page", the result is a error page with oly one line of the RDF document printed in the browser: <?xml version="1.0" encoding="UTF-8"?>

I checked the code apparently there are null characters in the document which make it unreadable with standard php functions. Here is my site:

http://semantic.oviumzone.com/wiki/Special:ExportRDF

I found references to a similar problem that had no resolution.

The command line software seems to work and direct input of the RDF URI content into a text editor is readable but not presentable in an internet browser.

http://semantic-mediawiki.org/wiki/Special:ExportRDF seems to work fine with the same demonstration.

I am using php 5.2.13 and mediawiki 1.15.4 with SMW 1.5.1 release.

Any fixed I can make to quickly solve the problem.

Regards,

Wolf
wolfkden@sprintmail.com


Version: unspecified
Severity: enhancement
OS: Linux
Platform: PC

Details

Reference
bz24595

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:10 PM
bzimport set Reference to bz24595.

wolfkden wrote:

I reinstalled using 1.16.0, all is well, I do not know whst went wrong but possibly some other extensions I installed such as custom Nav corrupted the ExportRDF. I also noticed a lot of modifications in the skin code in mediawiki release 1.16

The problem might have been due to empty lines at the beginning of the RDF export. This is caused easily in PHP if loaded php files contain an empty line after a closing "?>" tag. This can be caused by any of the loaded files, even if completely unrelated to SMW or the export function. Even LocalSettings.php can cause this.

The modern way of preventing this is to not have closing ?> at the end of PHP files at all: no recent MW extension should have closing PHP tags at the end of its files, but of course there can always be black sheep (or simply very aged LocalSettings.php that have survived from the age of closing tags).

Anyway, this is not an SMW bug and it is not possible for SMW to fix it (the empty lines are sent to the browser even before SMW starts the export; SMW cannot take them back or even check if they are there).