Difference between revisions of "MediaWiki/archive/customizing"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
m (→‎Articles: stupid MW case-sensitivity :-P)
m (→‎Articles: Links: official MW customization page link)
Line 1: Line 1:
 
{{web software|MediaWiki}}: [[MediaWiki Customization|Customization]]
 
{{web software|MediaWiki}}: [[MediaWiki Customization|Customization]]
 +
==Links==
 +
* [http://www.mediawiki.org/wiki/Customization MediaWiki Customization] at mediawiki.org
 
==Articles==
 
==Articles==
 
* [[Modifying MediaWiki Menus]]
 
* [[Modifying MediaWiki Menus]]

Revision as of 00:29, 4 November 2005

computing: software: web: MediaWiki: Customization

Links

Articles

Code Notes

(From Woozle 20:59, 15 Jun 2005 (CDT). Eventually to be given their own section, I expect.)

  • Everything obviously starts with index.php
  • For the purpose of displaying a page (not saving changes or doing anything else), this calls $wgArticle->view(), in

Article.php (line 699)

  • $wgArticle->view() appears to be able to provide a few other formats besides the regular view (including difference engine and displaying redirections as subtitles), but I'm ignoring that for now
  • $wgOut seems to be the object which accumulates text to be output, via various methods:
    • $wgOut->addWikiText(...)
    • $wgOut->addHTML(...)
    • $wgOut->addPrimaryWikiText() # Display content and save to parser cache
    • $wgOut->addWikiText() # Display content, don't attempt to save to parser cache
    • $wgOut->setPageTitle()
    • $wgOut->transformBuffer(); # Put link titles into the link cache
    • $wgOut->addMetaTags(); # Add link titles as META keywords
  • ...and then it does these two lines:
    • $this->viewUpdates(); (found at line 1926 -- doesn't do much)
    • wfProfileOut( $fname );
  • It's not clear whether the navbar has already been pulled in by the time we hit viewUpdates -- possibly transformBuffer does it? The comment makes it sound like that, but the name "transformBuffer" in that case is not very descriptive. The code in there should probably be examined.