Last modified: 2012-05-06 13:18:29 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 T38558, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36558 - bug in array code blocks usage with certain versions of ArrayExtension
bug in array code blocks usage with certain versions of ArrayExtension
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SemanticResultFormats (Other open bugs)
unspecified
All All
: Unprioritized major (vote)
: ---
Assigned To: Jeroen De Dauw
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-05 19:59 UTC by Dr Ishmael
Modified: 2012-05-06 13:18 UTC (History)
3 users (show)

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


Attachments

Description Dr Ishmael 2012-05-05 19:59:44 UTC
Discovered this on my site Referata, they currently have SRF 1.8alpha and ArrayExtension 1.3.2.  (http://guildwars2.referata.com/wiki/Special:Version) Attempting to use the array format at all returns this error:

Fatal error: Class 'ExtArrayExtension' not found in /home/yaron57/public_html/w/extensions/SemanticResultFormats/Array/SRF_Array.php on line 223


It looks like a simple typo on that line.

222	if( defined( 'ArrayExtension::VERSION' ) ) {
223	    $version = ExtArrayExtension::VERSION;
224	} elseif( defined( 'ExtArrayExtension::VERSION' ) ) {
225	    $version = ExtArrayExtension::VERSION;
226	}


Shouldn't that global name match the name on the line above? Like this:

222	if( defined( 'ArrayExtension::VERSION' ) ) {
223	    $version = ArrayExtension::VERSION;
224	} elseif( defined( 'ExtArrayExtension::VERSION' ) ) {
225	    $version = ExtArrayExtension::VERSION;
226	}

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


Navigation
Links