aboutsummaryrefslogtreecommitdiffstats
path: root/RELEASE-NOTES-1.22
Commit message (Collapse)AuthorAgeFilesLines
* Add page language to prop=infoumherirrender2013-05-221-1/+1
| | | | | | | | This can be useful to determine the language of a page, for example javascript has english as page language. MediaWiki pages has it page language corresponding to the lang code in the sub page. Change-Id: Idd0412574b314ecf52d92243a3f8a08755474663
* Merge "TitleSquidURLs hook for changing the URLs to purge"jenkins-bot2013-05-211-0/+2
|\
| * TitleSquidURLs hook for changing the URLs to purgedaniel2013-05-211-0/+2
| | | | | | | | | | | | | | This allows extensions to purge derivative resources that need updating when a wiki page is changed. Change-Id: Ic28ce7f57f29376b041627288979981fcb218a44
* | Deprecate $wgJsMimeTypeTimo Tijhof2013-05-211-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | It hasn't been used for its documented purpose for a while. In fact the one significant thing it can cause wasn't even documented. If set to anything other than "text/javascript" it will cause action=raw to no longer respond to ctype=text/javascript requests (such as done by wikibits' importScript function). Follows-up 97caae596d5493. Change-Id: Ib04ff5b21eb0ae172b94e31bc0dc16c9649e1864
* | Remove the $wgHandheldStyle config variable entirelyMatmaRex2013-05-191-0/+1
|/ | | | | | | | | | | | | | | | Added back in 2008 (dc821ec1 / r38116), it was only ever implemented for Monobook and didn't do anything in other skins. The only use-case given was using Chick's CSS for mobile devices with Monobook being the default skin - and now Chick is no more and Monobook isn't the default. It was also used to decide whether to load styles from MediaWiki:Handheld.css (they were loaded if it was set to anything). That message has been removed as well. Bug: 47504 Change-Id: Ia8d79b4a637a227eb1879fbb874173fdd9bd6d99
* (bug 47216) API: indicate default and skipped skins in meta=siteinfoBrad Jorsch2013-05-171-0/+2
| | | | | | | | | action=query&meta=siteinfo&siprop=skins can easily indicate which of the returned skins is the default and which are unusable (e.g. because they're listed in $wgSkipSkins). So we may as well do so. Bug: 47216 Change-Id: Ib4ea5fe85e1b02895dba15f3a245c7a7d8724470
* Drop support for XHTML 1.0Daniel Friesen2013-05-151-0/+8
| | | | | | | | | | | * $wgHtml5 = false; is now ignored completely. * $wgDocType and $wgDTD have been removed. * $wgXhtmlDefaultNamespace is now ignored. * XHTML5 will be output if $wgMimeType is set to an XML mime type (according to HTML5's rules). * For backwards compatibility with extensions $wgHtml5 and $wgXhtmlDefaultNamespace are set in Setup.php but depending on them is deprecated. Change-Id: Iad9634e2ee420b5a3bbffe550421fde4fa1819b0
* Fix typo in RELEASE-NOTESAlexandre Emsenhuber2013-05-141-2/+2
| | | | | | Follow-up a2c6734 (I42be68c6a0): a "is false" was missing. Change-Id: Ia81fbcded13c2da4354f1dce383bf5b854b99e49
* (bug 41545) Allow kbd, samp, and var to be nested.Daniel Friesen2013-05-131-0/+1
| | | | | | | | | | | | | HTML5 has various semantics that allow -- or rather require -- <kbd> and <samp> and even <var> to be nested. eg: <kbd><kbd>Shift</kbd>+<kbd>F3</kbd></kbd> eg: <var>x<sub><var>i</var></sub></var>, <var>y<sub><var>i</var></sub></var> This fixes the sanitizer to permit their nesting and adds test cases to ensure that some of HTML5's special semantics are permitted by our sanitizer and not broken. Change-Id: I6ad64e6eb4c9b5bdc15be513f55c58f6717c3939
* Whitelist a bunch of url protocols.Daniel Friesen2013-05-121-0/+2
| | | | | | | | | | Our url whitelisting is just to reject unsafe protocols like javascript:. We have no reason to reject a bunch of urls to open standardized schemes. Whitelist a bunch of them: ftps, ssh, sftp, xmpp, sip, sips, tel, sms, bitcoin, magnet, urn, and geo. Change-Id: I941190203ee1442d912d46144584bf2e7733f32c
* Add $wgCascadingRestrictionLevelsMatmaRex2013-05-121-0/+3
| | | | | | | | | | | | | | | A page can only be protected with cascading protection if the requested restriction level is included in this array. This replaces previously hard-coded values of 'sysop' and 'protect'. This is necessary, because if any protection could be cascading, users could who cannot normally protect pages could "protect" them by transcluding them on protected pages they are allowed to edit. Bug: 47617 Change-Id: I5f8bcc899b46d466161894606cd27bf3b8624bd0
* Add identifying info (img_timestamp and img_sha1) to upload log.Brian Wolff2013-05-101-0/+2
| | | | | | | | | | I came across people complaining that it was hard to associate upload log events to actual images since img_timestamp could be different from log_timestamp, and generally no unique id. Well I was there I made uploads use the new logging system. Change-Id: Icd8662ecb9eb0f6c0ff9841bdbd5736d6dd0d015
* Merge "Remove hphpc support and deprecate related functions"jenkins-bot2013-05-081-0/+2
|\
| * Remove hphpc support and deprecate related functionsTim Starling2013-05-091-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | hphpc has been superseded by hhvm, so support for hphpc is no longer needed. * Continue to use Preprocessor_Hash under HipHop since it is still faster under hhvm * Keep $wgCompiledFiles for now, so that wikihiero doesn't give an error before Ic9d1e795 is merged * Migrate the run-server script and associated configuration file to hhvm. Enable EnableStaticContentFromDisk since it doesn't seem ridiculously inefficient at first glance. Run from $IP rather than $IP/.. since hhvm is apparently not picky about sourcing files from outside of the current directory. Change-Id: Ic3e769f1fbad4f7ad26dd819406796fee48c6b45
* | Merge "Remove Parser_LinkHooks and CoreLinkFunctions classes"jenkins-bot2013-05-081-0/+1
|\ \
| * | Remove Parser_LinkHooks and CoreLinkFunctions classesReedy2013-05-021-0/+1
| | | | | | | | | | | | | | | Bug: 45371 Change-Id: I06f890153df0cb8f4fb84a73a06a6f5f4817cf3b
* | | Add content model to prop=infoumherirrender2013-05-081-0/+1
| | | | | | | | | | | | | | | | | | Fields of page table are shown by default in prop=info Change-Id: Id8b90c341dea19337558ed355975ab890f0663e2
* | | Merge "(bug 46751) Make Buryat (Russia) (буряад) (bxr) fallback to ↵jenkins-bot2013-05-081-0/+2
|\ \ \ | |_|/ |/| | | | | Russian"
| * | (bug 46751) Make Buryat (Russia) (буряад) (bxr) fallback to RussianFederico Leva2013-04-291-0/+2
| | | | | | | | | | | | | | | | | | See bug for details. Change-Id: Ib017991214955d214710419e10cd8888fc89c744
* | | Merge "Adding GetNewMessagesAlert hook and wgUserNewMsgRevisionId JS global"jenkins-bot2013-05-061-0/+6
|\ \ \
| * | | Adding GetNewMessagesAlert hook and wgUserNewMsgRevisionId JS globalkaldari2013-05-041-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This hook allows extensions to disable or modify the new messages alert ('orange bar of doom') while still allowing the user_newtalk table to be updated. The wgUserNewMsgRevisionId JS global allows gadgets and extensions to create their own new message alerts on the client side. I also threw in a few comment updates for good measure! See also Echo change I3f35a56b which utilizes this. Bug: 47962 Change-Id: I2105bdd2bcd5b27f6f36ec8d8fa7fa99d60a2d82
* | | | Merge "Remove SkinLegacy.php"jenkins-bot2013-05-061-2/+4
|\ \ \ \
| * | | | Remove SkinLegacy.phpMatmaRex2013-05-061-2/+4
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Followup to Ia6d73c2d (the great skin removal event of 2013). The two classes this file defined, SkinLegacy and LegacyTemplate, were already removed from AutoLoader.php in the aforementioned commit, but the file itself somehow stayed. The Nostalgia extension includes its own copy, and I've rewritten Cologne Blue to use SkinTemplate last year, which means that nothing needs the legacy classes anymore. I grepped mediawiki/extensions just in case and there were no hits apart from Nostalgia. Change-Id: Ib36edff3f9b617357386914980b56fa5b1f6a83b
* / / / Revert "Remove Special:ActiveUsers"Chad Horohoe2013-05-051-1/+0
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 27104686abe2aaf464d8d654a71e946326a0926d. Revert "Remove link to Special:ActiveUsers from Special:Statistics" This reverts commit 62949af09ea3ceb96d897ec8aab74afdadb02d4e. I used a sledgehammer where a scalpel would've done--and I should be whacked with the cluebat. This should be done per-wiki, plus improvements. Change-Id: Ib43b42057b8d9f714a8a71ba9cbe375385254b7c
* | | Merge "Implement mw.log.warn and mw.log.deprecate"jenkins-bot2013-05-041-0/+3
|\ \ \
| * | | Implement mw.log.warn and mw.log.deprecateTimo Tijhof2013-05-031-0/+3
| | | | | | | | | | | | | | | | Change-Id: I1eadd01d7086aecb1bdf7e950c49778fd63b5414
* | | | Merge "Monobook: Remove OperaNFixes.css files"jenkins-bot2013-05-031-0/+1
|\| | |
| * | | Monobook: Remove OperaNFixes.css filesMatmaRex2013-05-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We were providing fixes for Opera 6, 7 and 9, even though it's 2013, Opera is at version 12, and even as a grade B browser we're only supporting Opera 10. Given the amount of various changes to the codebase over the years, I'd be surprised if any of those were still doing anything for the compatibility. Change-Id: I9925cc98d11c4e2eecedd305a724f0763a62a782
* | | | Allow iiurlheight to be used without iiurlwidthCatrope2013-05-021-0/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Wanting to get a thumbnail with only the height constrained is a reasonable use case, the only reason we don't support it in the API is because the backend doesn't support it directly. This is easy enough to emulate by setting the width to the full width of the image if only the height is specified. This makes the transform function use a bounding box of size w x h, and if w is the width of the original image that's equivalent to just bounding the height. Change-Id: I28c7c22ee91669469cbd9e7d25f09100933582de
* | / SpecialRedirect: Add @since documentation and add release notesC. Scott Ananian2013-05-021-0/+3
| |/ |/| | | | | | | | | | | The Special:Redirect page was added in change I8b0785f4fbdb3dd438a7a45263c5f375ff9d2208. Change-Id: I1a4b9a8b0a008f16e554f7edc2f21b7142fde8d4
* | Merge "rebuildLocalisationCache: Implement --lang option"jenkins-bot2013-05-011-0/+2
|\ \
| * | rebuildLocalisationCache: Implement --lang optionAntoine Musso2013-05-011-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It would rebuild all language caches by default. We were lacking an option to rebuild only one language, for example when it get corrupted or the cache file for a language got removed. The new --lang accepts a list of comma separated langs to rebuild the cache for. Example usage: php rebuildLocalisationCache.php --lang en,fr,de Nonexistent languages are simply ignored. The script dies if it ends up with no languages to rebuild. Change-Id: I4c5e69abb76ffd8b88b595e3687edab3bb267ccc
* | | Clarify wfRandomString release noteKevin Israel2013-04-301-1/+1
| | | | | | | | | | | | | | | Change-Id: I54b39488eeab0ca54cc44c6ba592da311604a39b Follows-Up: Ic19b5b97c582485780b24fd35ffef2111cc8b3ca
* | | (bug 47219) Allow specifying change type of Wikipedia feed itemskaligula2013-04-301-0/+1
|/ / | | | | | | | | | | | | | | It exposes field /rc_type/ as ApiQueryRecentChanges does thus allowing user to define which (edit, external, new, log) changes to show in feed. Bug: 47219 Change-Id: If22827129b04d423711f921307dc820d4840d9d1
* / Add chosen support to HTMLForm's multiselect fieldRyan Lane2013-04-291-0/+2
|/ | | | | | | | | For very large multiselects, the list of checkboxes is overwhelming. This change adds support for using jquery.chosen conditionally on multiselect fields, if 'chosen' is used for the cssclass parameter. Change-Id: If1eba7fb705089deb4cff7a326db0ac803a522ec
* (bug 45535) Hook for changing language links.daniel2013-04-291-0/+9
| | | | | | | | | | | | | | | | | | | | | | This adds a new hook called LanguageLinks which is called whenever a list of language links is returned to the user. This gives extensions the option to manipulate the links on the fly. Note that this change only covers the language links used in OutputPage and by ApiParse. Adapting ApiQueryLangLinks is left as a follow-up task. As explained on bugzilla, this is a precondition to allowing Wikibase/Wikidata to update languagelinks without forcing a (redundant) re-parse of the page content. This change also introduces the notion of link flags that can be used to associate flags with language links. This will be integrated with ParserOutput and OutputPage in a follow-up. Change-Id: Iaec0faa131413a291fc8f77496e4f371addb3b99
* Merge "wfRandomString: Correct bias toward digits 1-7"jenkins-bot2013-04-291-0/+2
|\
| * wfRandomString: Correct bias toward digits 1-7Kevin Israel2013-04-291-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Two problems with a single line of code: * dechex() does not include leading zeros, so the first digit generated in each iteration cannot be zero unless the return value of mt_rand() is 0. This also means wfRandomString() is extremely unlikely to start a string with '0'. * mt_rand() does not actually uniformly distribute values over [0,2^32-1]; it actually right-shifts one of the bits off (just because "[...] the previous php_rand only returns 31 at most"), so the maximum value is 0x7fffffff, not 0xffffffff. This means wfRandomString() will never start a string with any of the digits 8-f. Including leading zeros and using only the 28 LSBs to form seven hex digits at a time is the simplest fix. Change-Id: Ic19b5b97c582485780b24fd35ffef2111cc8b3ca
* | (bug 41729) Move section edit links to after the headingsMatmaRex2013-04-291-0/+7
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | This requires minor changes in various parts of MediaWiki, and being extra careful about cached rendered pages' HTML. Fun fact: editsection links are not made in Parser. They're made in Linker, in Skin *and* in ParserOutput. Client-side code and screen-scrapers will have to be adjusted to handle both cases (old HTML will still be visible on cached page renders until they are purged); extensions using the DoEditSectionLink or EditSectionLink hooks might need adjustments as well. * Linker: Change the HTML of pages to move the link itself from the beginning of the heading (before <span class="mw-headline">) to the end of the heading (after the span). * Skin: Change the class from .editsection to .mw-editsection; we use this opportunity to clean up old cruft, and this makes it much easier to handle cached renders (by just detecting the old class). * ParserOutput: Implement a horrible hack to support cached parser outputs with the old order of items. * Ensure everything that should support both classes supports both classes (this includes print stylesheets and some scripts). * Implement styles for the new look for all the skins (did this in shared.css; the styles are non-intrusive and can be overridden easily, and all of the skins were using the same look before). Change-Id: I6a6c12a90de3604012420b20c1f520e0ece170ab
* {{PAGESIZE:{{FULLPAGENAME}}}}, {{{{FULLPAGENAME}}}} not outdatedBrian Wolff2013-04-271-0/+2
| | | | | | | | | | | | | | | | | | | | | | | Previously, when parsing {{PAGESIZE:{{FULLPAGENAME}}}} or {{ {{FULLPAGENAME}} }} (a self-transclusion), we used the version currently in the db, which is outdated because the moment we save the page there will be a new version. This often causes confusion when testing templates that often have examples of template use in the doc section which would be one version out of date. This change causes those variables to give results for the most recent version of the page. For self-templates that's done by reparsing the page after save. For self page sizes this is done by taking the size of the input to Parser::parse. Note that {{subst:PAGESIZE:{{subst:FULLPAGENAME}}}} will still yield previous revision like before. bug: 39590 Change-Id: Idfac13de37d05317f65e4131534543e66cf74873
* Add parentid to output of list=usercontribsBrian Wolff2013-04-241-0/+1
| | | | | | | This makes it consistent with prop=revisions. Was requested on irc by Betacommand. Change-Id: Idfbee9b4f089738ab70825c11945faf8dd3da66d
* Merge "Create account form with vertical form appearance"jenkins-bot2013-04-241-3/+8
|\
| * Create account form with vertical form appearanceMatthew Flaschen2013-04-231-3/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Similar to the login form (change 55847), this presents a compact vertically-stacked form, if a global variable is set or if you add ?useNew=1 to the query string. The redesigned create account form also: * Removes the remember me checkbox (see bugzilla 47267) * Displays some wiki statistics in a benefits column. * Repositions the FancyCaptcha image if present using JavaScript (see bugzilla 47372). * Sets the template skin as in change 59577. Bug: 44628 Bug: 47267 Change-Id: I9b03d519af43de147bff0ac509a1154f67cd3a0a
* | Remove is_numeric check from Title::checkUserBlockKevin Israel2013-04-241-0/+1
|/ | | | | | | | | | | | | | This should allow the usernames of administrators such as "7" to show correctly on permissions error pages. I extracted the working code from UserBlockedError::__construct into a separate method Block::getPermissionsError, called from both places with context provided as an argument. Additional changes to get the test suite to pass are included. Bug: 46768 Change-Id: I49d973992a99e03b4e8de112b47b737037a85338
* Merge "Introducing a new variable {{ROOTPAGENAME}}"jenkins-bot2013-04-231-0/+2
|\
| * Introducing a new variable {{ROOTPAGENAME}}blotmandroid2013-04-241-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduced a new variable ROOTPAGENAME which has similar content like BASEPAGENAME. ROOTPAGENAME only contains the name of the topmost page without namespace, e.g. for "User:Name/Article/Subarticle" it should be "Name". BASEPAGENAME would be "Name/Article" here. Update : fixed indentation in maintenance/fuzz-tester.php Added to RELEASE-NOTES-1.2.2 Bug: 6747 Change-Id: I71ef0a15c95c9145462f3aa7fdb3ed11dac79265
* | Move "SpecialSearchResultsPrepend" note back to 1.21Kevin Israel2013-04-231-1/+0
|/ | | | | | | | | | Partial revert of I6a51e3ee: the hooks were actually added before the branch point (in Ib3843314), not in I226349aa, which merely added the release note. The author of I226349aa has already backported the change. Change-Id: Ifc2728133c6ca52ef866ce963c28bd3d06eab05a
* mediawiki.util: Fix roundtripping of tooltip in portlet linksTimo Tijhof2013-04-221-0/+8
| | | | | | | | | | | | | | | | | | | In 558985f72a ctrl-option- for Chrome on Mac was added, but it didn't add "option-" to the regex. Since then the tooltip in Chrome on Mac (and later when we started referring to option instead of alt on all Mac browsers) was never detected by this regex, sometimes resulting in double tooltips (when adding) or outdated tooltips (when updating). Now we always look for an accesskey hint in the tooltip and strip it it's there. Also fixed a bug where an undefined error can occur if accesskey is given but tooltip not (the method unconditinally appended text to the tooltip varible which might be undefined causing a tooltip like "undefined[a]"). Change-Id: I0bde1a228983c58b20cad0c09a8e5efe8225ea23
* (bug 25592) LogEventsList:showLogExtract should ignore WebRequestBrad Jorsch2013-04-221-0/+4
| | | | | | | | | | | | | | LogEventsList:showLogExtract currently pays attention to WebRequest parameters such as offset, dir, order, and limit (although limit is typically overridden by callers, and offset sometimes too). While these make sense for a pager that is driving the whole page, it doesn't make much sense for the "most recent log entry" boxes that are displayed using LogEventsList:showLogExtract. So let's have LogEventsList:showLogExtract ignore these, and for good measure add in a parameter to use the old behavior in case any caller really needs that. Change-Id: Id4380cd863ba69fc9b9afb5a0034d82ad4d9cc34
* API: Add new hook 'APIGetPossibleErrors'umherirrender2013-04-191-0/+2
| | | | | | | This allows extensions to modify the array. This completes the serie of hooks for similar get methods in ApiBase. Change-Id: Ib398f5815ab57f25d56356b0997c55a03fd96874
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-24 11:13:22 +0000