This tool is designed primarily with Fandom wikis in mind, but should work for any wiki running on the MediaWiki codebase. For problems with non-Fandom wikis, click here.

This script can be found on GitHub, along with a changelog.

Installation

Usage

All that's truly needed after the script is installed is a <div> with the rc-content-multiple class and a bullet list with the link of the wiki's domain (the <div> will need to be added via source mode). Duplicate entries are ignored. Example:

<div class="rc-content-multiple">
*https://runescape.fandom.com/fr/
*wowpedia.fandom.com
*https://dev.fandom.com &bgcolor=green
</div>

Basic Features

While not part of Special:RecentChanges, these are some additional features included by default.

• AjaxRC: Inspired by AjaxRC, an "auto-refresh" option is available, that when ticked will cause the list to be refreshed every 60 seconds. A cookie is used to store the setting of the checkbox once clicked.
  • Notifications (optional): Upon activating, you'll be prompted to activate HTML5 notifications (optional), which will inform you of updates when you navigate away from the window/tab. To disable them after enabling them, click the gear icon on a notification.
• AjaxDiff: Inspired by AjaxDiff / QuickDiff / LastEdited, you can view the "diff" of a change without changing pages, by hitting the icon to the right of the "diff"/"prev"/"changes" link.
• AjaxGallery: By clicking the photo icon next to files changes (be it upload log or file page edit), you can preview the image it's related to. For grouped upload logs, you may preview a gallery of all images in the list.
• AjaxPagePreview: Allows you to view the page without leaving your current page.
  • Note: This feature is fairly unpolished. Multiple CSS and JS files are not run on the preview. Thus the preview only uses the CSS from the current wiki to display pages. On browsers that support editing the shadow dom (Chrome as of writing this) or scoped styles (Firefox) some custom CSS from the wiki is applied (common.css it seems) as well as some JS is applied (for shadow dom), though still not all. It's still good for viewing comments/walls message in most cases, but for article viewing keep in mind the page may appear broken / different than expected.
• Discussions: Inspired by DiscussionsFeed, you may now see discussions in the script. See below for information on various caveats.
• Social Activity: Content found on Special:SocialActivity is also included on the list by default.
• Abuse Logs: If a wiki on the list has the AbuseFilter extension enabled, a filter option to list abuse logs will appear.
• Wiki Info Panel: Clicking one of the favicons in the "wikis loaded" section at the top of the script (or along the left side of the script) will give you a list of links to some common pages for that specific wiki, as well as some statistics for that wiki. This panel also allows you to temporarily hide wikis encase one wiki on the list is to busy. If the instance only has one wiki, this panel will open by default.
• Multiple instances: Multiple instances ("containers") may be run on the same page.
  • This includes those within tabbers.
  • It is possible to have each instance only load 1 wiki, thus allowing a more typical recemt chamges design while still viewing multiple wikis on 1 page. It's also possible to refresh all instances using the rcm-refresh-all feature.
  • Keep in mind however that some of the additional parameters below are only checked on the first instance and affect all those on the page (data-lang, data-hiderail, data-loaddelay, data-timezone).

Additional Parameters

While the above works and that's all that may be needed, there are also many other additional parameters that can be added, in 3 ways: 1 that affects every RCM, 1 that affects every wiki on a specific RCM list, and one that affects a specific wiki.

URL variables

This affects every RCM on the page. Currently the only URL variables accepted are those used by a standard RecentChanges page. See more at RC Params below: https://yourwiki.fandom.com/wiki/RecentChangesMultiplePage?hidemyself=1&days=7

Dataset

These affect every wiki / the script as a whole for a single instance.

Ones labeled [Global] only are checked on the first instance, and are used for all other instances. Note: If you edit global parameters in the UCP editor the changes won't appear until you refresh the page.

Example

Datasets go directly inside the <div>, like so:

<div class="rc-content-multiple" data-params="hidemyself=1&days=10&limit=50" data-hideusers="TestUser,My awesome username,ILikePIE">
*List of wikis
</div>

On List Items

Every item on the list must start with the wiki's base URL, in the format "name.fandom.com" (or name.fandom.com/lang/, or "wikiname.com" (or other top level domain if the wiki doesn't have "fandom"/"wikia" in it).

These allow you to customize a specific wiki's results, instead of requiring every wiki listed to use the same options.

Each list item may have parameters added to add additional functionality for how that wiki is displayed / loaded. This can be done in one of two ways:

• Adding &paramname= after the URL. ex: dev.fandom.com &bgcolor=green
• Adding a sub list below the entry (with or without a "&" in front of param name). ex:

*dev.fandom.com
**bgcolor=green

Examples

<div class="rc-content-multiple">
*https://fewfre.fandom.com &hideusers=Fewfre,FewBot
*https://pixelmonmod.com &scriptdir=wiki&params=hidemyself:1,limit:5
*https://wiki.guildwars2.com
**favicon=wiki.guildwars2.com/images/thumb/d/df/GW2Logo_new.png/180px-GW2Logo_new.png
</div>

Options Panel

Offers a way to tweak "data-params=" options in real-time. The options panel does have a setting to remember the options you changed via localStorage (off by default). Any options changed before turning this feature on will also be remembered. Clicking this off again will remove the info from storage. One of the above methods should be used if you want the change to persist on a different computer / without using localStorage. The options panel also allows a way to toggle Fandom Discussions on/off.

Due to these options changing display requirements, all current changes listed on the page will be cleared and then refreshed.

RC Params

To help emulate Special:RecentChanges as much as possible, this script accepts RC-style URL params (used as explained above with "data-params", "&params", URL variables, or the options panel). There are multiple params, as explained below. Please note that these affect each wiki individually (so a limit of 50 for 4 wikis is actually a limit of 200 total).

There are a few ways to specify params in the script. If more than one is specified, they will "fall through", with the more specific one overwriting the less specific one (ex: "&params" is more specific than "data-params"), but only if they both change the same thing (such as "days"). The order of specificity is as such:

1. [Default values]
2. User settings - uses the 4 settings under "Special:Preferences > Under the Hood > Recent changes"
3. URL variables – same as a normal recent changes page.
4. data-params
5. Options panel (run-time options)
6. &params (note that the "options panel" will not overwrite these)

Note that for "true/false" boolean switches, "0" is false, and "1" is true.

Extra Features

Refresh All

• If using multiple instances on the same page, they can all be refreshed at once by giving the "rcm-refresh-all" class to an element on the page. ex:

<span class="rcm-refresh-all button">Refresh All</span>

CSS Styling

This script uses as many default recent changes classes as possible to allow styling to be consistent. Most RCM-specific features also use class names to allow for customization. Some useful classes are:

• .rc-entry-$1 surrounds an entire entry / entry group, with $1 being the URL domain with dots as dashes (ex: "dev-fandom-com"). By default this is used to style ".rcm-tiled-favicon", but it can be used to customize any data different based on its wiki.
• .rc-entry-ns-$1 surrounds an entire entry / entry group, with $1 being the number of a namespace (ex: 0 for mainspace, 1 for talk, etc).
• .rcm-favicon-goto-button represents the icon to the left of each entry. Can be used to modify the icon / remove it.

So long as "data-extraLoadingEnabled" is not turned off, user links also have attributes added once the data is fetched. .rcm-userblocked signifies a user is blocked on that wiki, .rcm-usergroup-$1 allows you to customize names based on the user's group (with "$1" being the unique ID for that group), and .rcm-useranon is added for anonymous users. You can find common group IDs here (listed as "group-$1") and you can find a list of all groups (and the rights that come with them if curious) here; simply change the wiki in the URL to see it for your target wiki (if it has a custom group). ex: .rcm-usergroup-content-moderator

There are many other classes (either custom or recent changes classes) that can be utilized to customize the script. Best way to find them is to just inspect the element you want to customize and go from there.

Discussions

In late 2016 Fandom started pushing their discussion system onto new wikis, eventually working towards placing it on all wikis. Edits made inside the discussion area do not show up inside recent changes, so support has to be tacked on. This has a few potentially unexpected results:

• As of 2020, wikis that have had their MediaWiki version updated will have any Message Walls and Article Comments moved into the discussion system (although not showing up in the Discussions page). As such, most of the notes here apply to them as well.
• Discussions are turned on by default. It can be toggled off on the option panel, or via the data-discussions-enabled attribute.
• Not all discussions have titles, so if a title is not present, the first 35 characters of the original post are used to identify it instead.
• As the title of a thread is not included in the API information returned for a specific post, titles often need to be retrieved separately (using the same second-load mechanic as wall/forum titles; just like those, this feature can be disabled via the data-extraLoadingEnabled attribute).
• Many options do not affect discussions. Some that do work are: hidemyself, hideusers, onlyshowusers, limit & days (see below for specifics).
  • limit - only goes up to 50. Having a limit less than 50 will work.
  • hidemyself / hideusers - will affect the max number of discussions you see (since these are removed from the loaded list).
• These changes are loaded in addition to normal changes. If a limit is set to less than or equal to 50, this can possibly double the results displayed for that wiki.
• Discussions are only checked for on Fandom wikis (as they are Fandom-specific). However, the first time a script loads changes it needs to check all wikis to see if they exist. If they return a 404, an attempt to load that specific wiki will not happen again.
• Since the API returns avatars and vote totals, this information is included as well. They can be removed with custom CSS using the .rcm-avatar and .rcm-upvotes classes respectively.
• Due to how the API works, edits to posts are not shown as a separate change. Instead the post will simply appear higher up on the list (if it's creation date is still within the top 50). One possible unexpected side-effect this has is that if someone edits a post the day after they created it, it won't show up under both days.

HTTPS

Since all Fandom wikis have HTTPS enabled, you will not be able to load content from wikis without HTTPS.

If you are having HTTPS loading issues running the script on a fandom.com wiki, try changing any wikia.com wiki links in your list to fandom.com. All wikia wikis are now converted to Fandom, so shouldn't be an issue.

This issue will still affect some external wikis however that will continue to run without HTTPS. There is currently no workaround for this issue.

Non-Fandom wikis

This tool is designed primarily with Fandom wikis in mind, but should work for many wikis by default, and has some settings to handle special cases for certain non-Fandom wikis (such as "&scriptdir=" above). When adding non-Fandom wikis, it's important to note that this script is designed for MediaWiki wikis only, and requires the Mediawiki API to be enabled on a wiki to run (usually on, but some wikis do have it turned off).

Also note that as Fandom uses HTTPS, wikis running on HTTP cannot be loaded using this script.

Notes

• "Red links" for pages that don't exist won't show up on most logs, since this information would have to be retrieved individually for every page. Ones that do show up red were retrieved that way by default.
• Patrolling not supported at this time. This is due to MediaWiki security that prevents patrol info from being accessed unless authorized (severely breaking to script if it attempts it without authorization). Even if the right exists, the info cannot be accessed due to login being required on that wiki which is not available via cross-domain (browser security).
• Logs:
  • Logs may do weird things on "rare" cases (like staff-only actions and rare extension-only actions). Support for these can be added, but aren't in by default since each needs to be manually checked for each type (and sometimes each specific action).
  • (Rights log) – the rights will be listed using their ID instead of a translation of the user group. So it'll be things like sysop. Not all wikis have same groups, so getting translations from each wiki is more of a burden than it's worth.
• This script retrieves recent changes translations directly from the server. As such translations might differ when using non-Fandom wikis. If the loading failed enough times, it'll just default to English text.

Other

• "http://"はそれが自動的にリンクになるのを避けるために使われるべきではなく（扱いにくくなります）、Special:LinkSearchには外部リンクのあるページとして現れます（望ましくないかもしれません）。
• FandomのWiki用に設計されていますが、どのWikiでも機能するはずです（それが古すぎないことを前提として）。
• Fandom以外のWikiの中には、それらがどのように設定されているか（MediaWikiのバージョンが古い、APIが無効になっている、など）で、単に動作しないように見えるものもあります。
• スクリプトはcode.2.jsを使用して実行する必要があります。もうサポートされていませんが、オリジナルのアトムフィードバージョンはcode.jsで見つけることができ、それに関するドキュメントはここにあります。

必要事項

• JQuery
• 起動先のWikiは・・・:
  • Mediawiki(Version 1.16+)であること
  • Mediawiki Apiが使えること
• ECMAScript 5のさまざまな側面をサポートするブラウザであること（最新のブラウザであれば基本的に問題ありません）。
• 起動元はFandomのWikiであること（リストを折りたたむためのコードのようなものに確実にアクセスできるようにするため）