Last modified: 2013-11-04 19:11:37 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 T58427, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56427 - getShortWikiText fails in SRF_process.php
getShortWikiText fails in SRF_process.php
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
SemanticResultFormats (Other open bugs)
unspecified
All All
: Unprioritized blocker (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-31 20:12 UTC by Hans Oleander
Modified: 2013-11-04 19:11 UTC (History)
3 users (show)

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


Attachments

Description Hans Oleander 2013-10-31 20:12:57 UTC
This seems to bei closely related to Nr. 30742 (https://bugzilla.wikimedia.org/show_bug.cgi?id=30742), only that it is process instead the vcard output format: The process result format fails when trying to render a graph using graphviz (the graphviz extension otherwise working by itself quite ok). The page was the "Basic Graph" example, provided among other on https://www.mediawiki.org/wiki/User:Hummel-riegel/SRF_Process

It also runs into a getShortWikiText()-Error:
Fatal error: Call to undefined method SMWDIWikiPage::getShortWikiText() in /var/www/wiki/extensions/SemanticResultFormats/GraphViz/SRF_Process.php on line 195

I tried to replace the $field->getContent() with efSRFGetNextDV($field), but it turned out to be not quite this straightforward.
Comment 1 Hans Oleander 2013-11-04 19:11:37 UTC
Hello Jeroen,
I just now found the version of SRF_Process.php updated by you 9 days ago on github which does not have this error anymore. My apologies for the false alarm. So I change it to "resolved/invalid".
Best, Hans

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


Navigation
Links