mediawiki_hostname/
w/
load.php make kssopen
To rebuild without opening the web browser,
run:
When modifying styleGuideModules.txt, keep the
list in strict alphabetical
order (with no extra formatting), so CSS loads in the same
order as
ResourceLoader's addModuleStyles doesand give any other recipients of the Program a copy of this License along with the Program You may charge a fee for the physical act of transferring a and you may at your option offer warranty protection in exchange for a fee You may modify your copy or copies of the Program or any portion of thus forming a work based on the and copy and distribute such modifications or work under the terms of Section provided that you also meet all of these that in whole or in part contains or is derived from the Program or any part to be licensed as a whole at no charge to all third parties under the terms of this License c If the modified program normally reads commands interactively when run
mediawiki_hostname/w/load.php make kssopen For example, MEDIAWIKI_LOAD_URL=1.2.3.4/w/load.php make kssopen If MediaWiki is running on localhost, you can omit MEDIAWIKI_LOAD_URL. To rebuild without opening the web browser, run: MEDIAWIKI_LOAD_URL=mediawiki_hostname/w/load.php make When modifying styleGuideModules.txt, keep the list in strict alphabetical order(with no extra formatting), so CSS loads in the same order as ResourceLoader 's addModuleStyles does MEDIAWIKI_LOAD_URL
Dynamic JavaScript and CSS resource loading system.
deferred txt A few of the database updates required by various functions here can be deferred until after the result page is displayed to the user For example
deferred txt A few of the database updates required by various functions here can be deferred until after the result page is displayed to the user For updating the view updating the linked to tables after a etc PHP does not yet have any way to tell the server to actually return and disconnect while still running these but it might have such a feature in the future We handle these by creating a deferred update object and putting those objects on a global list
design txt This is a brief overview of the new design More thorough and up to date information is available on the documentation wiki at etc Handles the details of getting and saving to the user table of the and dealing with sessions and cookies OutputPage Encapsulates the entire HTML page that will be sent in response to any server request It is used by calling its functions to add in any order
This document is intended to provide useful advice for parties seeking to redistribute MediaWiki to end users It s targeted particularly at maintainers for Linux since it s been observed that distribution packages of MediaWiki often break We ve consistently had to recommend that users seeking support use official tarballs instead of their distribution s and this often solves whatever problem the user is having It would be nice if this could such and we might be restricted by PHP settings such as safe mode or open_basedir We cannot assume that the software even has read access anywhere useful Many shared hosts run all users web applications under the same so they can t rely on Unix and must forbid reads to even standard directories like tmp lest users read each others files We cannot assume that the user has the ability to install or run any programs not written as web accessible PHP scripts Since anything that works on cheap shared hosting will work if you have shell or root access MediaWiki s design is based around catering to the lowest common denominator Although we support higher end setups as the way many things work by default is tailored toward shared hosting These defaults are unconventional from the point of view of and they certainly aren t ideal for someone who s installing MediaWiki as MediaWiki does not conform to normal Unix filesystem layout Hopefully we ll offer direct support for standard layouts in the but for now *any change to the location of files is unsupported *Moving things and leaving symlinks will *probably *not break but it is *strongly *advised not to try any more intrusive changes to get MediaWiki to conform more closely to your filesystem hierarchy Any such attempt will almost certainly result in unnecessary bugs The standard recommended location to install relative to the web is w(so, e.g.,/var/www/w). Rewrite rules can then be used to enable "pretty URLs" like/wiki/Article instead of/w/index.php?title
MediaWiki has optional support for a high distributed memory object caching system For general information on but for a larger site with heavy load
1.10.0