Last modified: 2008-09-11 09:13:55 UTC
Error message when calling either $wgTitle or $wgOut->addWikitext (but not addHTML!): $wgTitle results in: Call to a member function escapeLocalUrl() on a non-object in e:\\my homepages\\ChemWiki\\extensions\\Chemistry\\SpecialListPage.php on line 74 disabling this line gives: Internal error Parser::replaceInternalLinks: $this->mTitle is null Backtrace: #0 e:\my homepages\ChemWiki\includes\Parser.php(977): Parser->replaceInternalLinks('<_SearchExpl...') #1 e:\my homepages\ChemWiki\includes\Parser.php(300): Parser->internalParse('<_SearchExpl...') #2 e:\my homepages\ChemWiki\includes\OutputPage.php(299): Parser->parse('<_SearchExpl...', NULL, Object(ParserOptions), true, true, NULL) #3 e:\my homepages\ChemWiki\includes\OutputPage.php(286): OutputPage->addWikiTextTitle ('<_SearchExpl...', NULL, true) #4 e:\my homepages\ChemWiki\extensions\Chemistry\SpecialListPage.php(76): OutputPage->addWikiText ('<_SearchExpl...') #5 e:\my homepages\ChemWiki\extensions\Chemistry\SpecialListPage.php(46): SpecialListPage->getParams() #6 e:\my homepages\ChemWiki\extensions\Chemistry\SpecialChemicalsources2.php(49): SpecialListPage- >ShowListPage() #7 e:\my homepages\ChemWiki\extensions\Chemistry\SpecialChemicalsources2.php(31): SpecialChemicalsources2->SpecialChemicalsources2() #8 [internal function]: wfSpecialChemicalsources2() #9 e:\my homepages\ChemWiki\includes\Setup.php(189): call_user_func('wfSpecialChemic...') #10 e:\my homepages\ChemWiki\includes\WebStart.php(80): require_once('e:\my homepages...') #11 e:\my homepages\ChemWiki\index.php(4): require_once('e:\my homepages...') #12 {main} (code to follow in next post)
Created attachment 2530 [details] the files giving the error both SpecialListPage.php and SpecialChemicalsources2.php must be activated in localsettings.php. Calling the new specialpage (special:Chemicalsources2) should result in the error.
Did you intend to resolve this as LATER?
I'd still like to try and generalise the extension (see chemistry extensions in svn, the specialpage) further than I am currently capable of, but this seems not to be the way, problems in inheritage of classes, I guess. Shortly, the thing has not been resolved, I don't know where or why it exactly breaks, and yes, I will try again and make it work, later. I'll repost if I know whát goes wrong, and how to work around.
LATER is more for "it's not possible to do at present", because standards/browsers don't support or whatever. Like a bug opened asking for routine inline SVG display or something.
Fixed in r40724
