This looks pretty funky...
A page with the title Main Page already exists. Would you like to edit the existing page?
Yes. I want to contribute to the existing page.
Yes. I want to contribute to the existing page.
Lack of interlinking tools means that this would promote creation of orphan pages, and the UI isn't very good. Doesn't seem to be a clear way to disable it in favor of alternate creation methods either.
* add 'Create a page' to default sidebar
* remove uniwiki/CreatePage from Translate
* remove uniwiki/CreatePage from UniwikiSettings.php
* add special page aliases of CreatePage extension to MessagesXx.php
* New WantedQueryPage class for all of these Wanted*s, moved some identical methods to it
* Removed sortDescending() because it was already defined as returning true @ QueryPage, no need to duplicate
* Add ustoken=userrights to list=users
* Move the non-UI part of UserrightsPage::saveUserGroups() to the static and more generic doSaveUserGroups()
* Add a $reason parameter to UserrightsPage::addLogEntry() and make it and its helpers static
* Move UserrightsPage::changeableGroups() and changeableByGroup() to the User class and make the latter static
* In doSaveUserGroups(), drop groups that the user doesn't have from $remove (and those that they do have from $add), and return array($add, $remove)
* Fix up a comment in ApiQueryRecentChanges
enabled. Image width and height are now recognized, and when using ImageMagick,
optional flattening to PNG or JPEG for inline display can be enabled by setting
$wgTiffThumbnailType
By default no thumbnailing will occur; only difference from previous will be that the image width/height is detected and displayed.
Not yet implemented:
* Multi-page support
* Cleverer thumbnailing for giant files
* Thumbnailing of any sort if not using ImageMagick
* r41081 was causing the job queue to be flooded with tiny htmlCacheUpdate jobs which were less than the batch size and so, according to the original logic, should have been done immediately. This was causing template updates to be delayed even when the template has few backlinks. This is fixed.
* Introduced a shared cache called BacklinkCache with the main purpose of sharing data from these backlink queries, thus recovering the performance of r41081.
* Refactored backlink partitioning code, which in r40741 was copied from HTMLCacheUpdate to LinksUpdate with a bug intact. The bug caused every htmlCacheUpdate or refreshLinks2 job to be split into at least two pieces even when number of rows is less than the batch size.
* Fixed a bug from r40741 causing refreshLinks2 jobs with end=false to be ignored.
* Made SquidUpdate::newFromTitles() accept a TitleArray
* Accessed through the export and exportnowrap parameters added to action=query
* To facilitate &exportnowrap, add ApiFormatRaw, a formatter that just spits out its input without any formatting (not accessible through &format= of course)
* Fix up the action=query description message to reflect the deprecation of query.php
-- Introduce tagging of individual changes (revisions, logs, and on recentchanges). The tags are customisable, and currently settable by the Abuse Filter and by the TorBlock extension. The tags can be styled on the various pages on which they appear.
-- Introduces a schema change, three new tables (valid_tag, change_tag, and tag_summary).
As Tim notes, the weird callback setup in $wgHooks isn't really something we want to replicate or ever rely on ever again, as PHP's native callback syntax already handles things fine and is more consistent (and used extensively in the rest of MediaWiki).
May be other remaining issues with the refactor on top of bugs already discovered, but if it's going to be refactored to use callbacks it should be done using regular callbacks.
XXX: The code seems to more or less work, but it obviously needs more testing, regarding both stability and memory usage. In particular, I have not tested file uploads yet -- there may be consistency issues there.
* Now subclasses SpecialPage like it should
* All of the individual sections were split off into their own methods for readability
* Fixed Brion's comments on code review (r44509): not using <small> in the message, breaking to a new line, and keeping the description message separate
* Since -tooltip is a misleading name for the message, I renamed them to -desc, all message files and messages.inc have been updated
This also caused a regression with PasswordReset extension (renaming PasswordResetForm to PasswordReset) since this extension also have a PasswordReset class
UDP isn't a very clear name for this, especially since we use UDP protocols for multiple different things!
This class should probably be genericized a bit for _change notifications_, which there might be multiple backend implementations for, including the UDP->IRC bot gateway.
