Last modified: 2011-05-25 06:44:05 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T31052, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29052 - Export RDF using either recursive=1 or backlinks=1 ends in fatal error
Export RDF using either recursive=1 or backlinks=1 ends in fatal error
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Markus Krötzsch
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-05-19 14:11 UTC by Andreas Plank
Modified: 2011-05-25 06:44 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Andreas Plank 2011-05-19 14:11:25 UTC
When exporting RDF the normal Special:ExportRDF works fine. Using additional GET parameters like recursive=1 or backlinks=1 causes a fatal error. See for instance on http://semantic-mediawiki.org using r80102 or http://species-id.net/w/index.php?title=Special:ExportRDF/Petal&backlinks=1 using r82579

For property Area on http://semantic-mediawiki.org adding backlinks=1 or recursive=1
Fatal error: Call to a member function isAllowed() on a non-object in /domains/semantic-mediawiki.org/www/w/extensions/SemanticMediaWiki/specials/Export/SMW_SpecialOWLExport.php on line 147 (or 140)

Any fix possible? Thanks.

Andreas
Comment 1 Markus Krötzsch 2011-05-25 06:44:05 UTC
I cannot reproduce these issues in the current development version of SMW (see sandbox.semantic-mediawiki.org), so I assume that the problem has been fixed as part of the recent restructuring of the OWL/RDF export.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links