Support

Questions, problems and ideas go to User talk:Fenakhay on Meta-Wiki. Say which browser and which version of Uncommon you use, and which script is concerned.

What it needs

• Chrome or Microsoft Edge 138 or later, or Firefox 144 or later.
• An account on a Wikimedia wiki: the scripts of a profile run only while its account is logged in.

Allowing user scripts

Browsers ask before an extension may run user scripts. The dashboard shows the steps until it is done.

Chrome and Edge

1. Open chrome://extensions (Chrome) or edge://extensions (Edge) and choose Details on Uncommon.
2. Switch on "Allow User Scripts".

Firefox

1. On Uncommon's dashboard, choose Allow.
2. Firefox asks in its own prompt for the permission to run user scripts. Allow it.

When a script first runs on a wiki, the browser also asks to let Uncommon reach that wiki. Settings lists the wikis it may not reach yet.

Moving over from common.js

1. On the dashboard, create a profile with your wiki username.
2. Open Import, read your common.js (or common.css, global.js, global.css) and add the pages it loads.
3. Blank that page on the wiki yourself: Uncommon never edits a wiki. Until then each script runs twice, once from the wiki and once from Uncommon. The page's history keeps the old text.

A script doesn't run

• Check that you are logged in with the account of the profile the script belongs to.
• Check that the record is switched on and runs on this wiki (its page, Overview, "Runs on").
• Check its page rules: namespaces, actions, special pages and content models.
• Nothing runs with ?safemode=1 in the address, or while Uncommon is paused.
• The toolbar button's popup shows what ran on the current tab and why a script was skipped; the Activity page shows the last 200 page loads, with the errors scripts threw.
• A script that relies on its top-level names being globals has to assign them to window itself, since each script runs inside a function.

Updates of a script

Uncommon checks the wikis every 30 minutes (Settings changes the interval), and at once with "Check now". Revisions saved by your own account run straight away. A revision saved by somebody else waits on the record's Updates tab, with its diff, until you approve or skip it; the approved revision keeps running in the meantime.

Keeping a copy

Your scripts and settings live in the browser. Settings exports them to a state file, which Settings in another browser imports.