iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
The quickest way to see a wiki’s running MediaWiki release is to open Special:Version. The page shows the complete MediaWiki version and, when available, the PHP and database details, installed extensions, skins, libraries, parser extension tags, and parser-function hooks. For repeatable checks, obtain the same site information through the Siteinfo API. If you have shell or SSH access to the server, run php maintenance/run.php Version.php from the MediaWiki installation directory on current releases; MediaWiki 1.39 and earlier generally use php maintenance/version.php. After an upgrade, check Special:Version again to verify that the expected release is active.
What a MediaWiki version check tells you
A MediaWiki version check identifies the software release that is actually running on a particular wiki. Record the entire value, including every patch number. A value such as 1.xx.y is more useful than only the major and minor numbers because compatibility fixes and security updates are often tied to the patch level.
Free tools Windows power users keep installed
One-click scans. No signup required.
The version number is only one part of the information that matters when diagnosing an upgrade or extension problem. Special:Version also presents the environment around MediaWiki: dependency versions, installed extensions, skins, libraries, parser extension tags, and parser-function hooks. Those details can explain why two wikis on the same MediaWiki release behave differently.
Use the browser page for a quick, one-off lookup; use the API or command line when you need an inventory that can be repeated, saved, or compared after a change.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Choose the right checking method
| Method | Access required | Best use | Information and repeatability | Release considerations |
|---|---|---|---|---|
| Special:Version | Browser access; some wikis require sign-in or additional permissions | Fast manual check and post-upgrade confirmation | Shows MediaWiki plus dependencies, extensions, skins, libraries, parser tags, and parser-function hooks | Works through the wiki’s normal URL pattern |
| Siteinfo API | Access to the wiki’s API; permissions depend on the installation | Monitoring, inventory scripts, support reports, and repeatable collection | Returns the data represented by Special:Version in a machine-readable response |
Use the API documentation exposed by the target wiki for the release-specific endpoint and parameters |
| Version.php maintenance script | Server shell or SSH access and a working PHP command | Administrators who need a local check or build information | Prints the version on which the script is run and can include build or patch-date details | Current releases use maintenance/run.php; MediaWiki 1.39 and earlier generally use direct script invocation |
Check the version in a browser with Special:Version
1. Sign in when the wiki requires it
Open the wiki in a browser and sign in if its permissions restrict special pages. Public installations may allow the page without an account, while private or hardened sites may limit it to administrators or other trusted users. A login requirement does not indicate a problem with MediaWiki; it is an access policy set by that wiki.
2. Open the special page
Enter Special:Version using the URL style used by the wiki. Common forms are /wiki/Special:Version and /w/index.php?title=Special:Version. Starting from the wiki’s base address and appending the appropriate path avoids accidentally checking a different installation on the same server.
3. Read the MediaWiki release near the top
The page identifies the running MediaWiki release near the top. Copy the complete version string, including the patch level. If the page displays an LTS marker or a build date, record those alongside the number. Do not shorten the value when opening a support case or checking extension compatibility.
4. Capture the surrounding environment when troubleshooting
For an ordinary lookup, the release number may be enough. For an upgrade, extension, or skin investigation, capture the PHP version, database type and version, installed extensions, installed skins, and listed libraries as well. Also note parser extension tags and parser-function hooks when the failure involves templates, wikitext parsing, or a parser-related extension. This inventory helps distinguish a MediaWiki core issue from an extension or environment mismatch.
5. Save evidence in a useful format
Copy the text into a ticket or export a screenshot that includes the wiki identity and the version line. Keep the date and time of the check, especially when a maintenance window is in progress. If several wikis are involved, label each record with its site name so that a valid result from one installation is not mistaken for another.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
How to interpret the information on Special:Version
MediaWiki version
The MediaWiki entry is the core release currently serving requests. It is the value to compare with the release you intended to install. A page showing the old release after an upgrade usually means that the web server is still pointing to the old files, the update did not complete, or a different wiki was opened.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsPHP and database details
Dependency information describes the runtime used by the wiki. Keep the PHP version and database type or version with the MediaWiki number when investigating a compatibility error. An extension may support a particular MediaWiki release but still fail because the PHP runtime or database software differs.
Extensions and skins
The installed-extension and installed-skin lists reveal what has been enabled on that specific wiki. Two otherwise identical MediaWiki installations can produce different results when one has additional extensions or a different skin. Record the exact names and, when the page provides them, their versions.
Libraries and parser hooks
Libraries are supporting components used by MediaWiki or its extensions. Parser extension tags and parser-function hooks show extra syntax or functions supplied by installed extensions. These entries are particularly relevant when a template stops rendering, a tag is unknown, or a parser warning appears after an upgrade.
Use the Siteinfo API for repeatable checks
The information displayed by Special:Version is also available through MediaWiki’s Siteinfo API. An API request is useful when a browser visit is impractical, when you manage several wikis, or when a monitoring job needs to detect a change.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Find the wiki’s API endpoint and documentation
Use the API help or API documentation provided by the target wiki rather than assuming that every installation exposes the same path or accepts the same parameters. The release-specific documentation identifies the Siteinfo request and the properties that return version, dependency, extension, skin, and related data. A private wiki may require authentication, and an administrator may restrict API access.
Build a small inventory process
- Identify the exact wiki to query and authenticate if its API requires it.
- Use the documented Siteinfo operation to request the version information needed for your inventory.
- Store the complete MediaWiki version, not just the first two components.
- When diagnosing compatibility, store the dependency, extension, skin, and library data returned with the version.
- Record the collection date and the wiki name so later results can be compared reliably.
For monitoring, compare each new response with the previous record. A changed MediaWiki version should coincide with a planned maintenance event. An unexpected change in extensions, skins, or dependencies can explain a behavior change even when the core version is unchanged.
When the API result and browser page appear different
First confirm that both requests target the same wiki and use the same authentication context. Then check whether a proxy, cache, or load-balanced server is directing requests to different application files. Repeat the browser check and the API request after the maintenance window, and compare the complete version strings. If the disagreement remains, involve the server administrator because the requests may be reaching different installations or nodes.
Check the version from the server command line
Current-release command
From the MediaWiki installation directory, run:
php maintenance/run.php Version.phpCurrent MediaWiki documentation recommends invoking maintenance scripts through php ./maintenance/run.php (the leading ./ is optional when the path is already resolved). The command runs Version.php and reports the release on which that script is operating. Its documented output begins with MediaWiki version:. The script can also show build information such as patch or build-date details.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchLegacy command for MediaWiki 1.39 and earlier
MediaWiki 1.39 and earlier generally use the direct maintenance-script form:
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
php maintenance/version.phpUse the script layout that exists in the installation you are checking. Do not copy the current run.php syntax into an older checkout that does not contain that runner, and do not use the legacy path merely because it worked on a previous release.
Run the command from the correct directory
- Open a shell locally or connect to the server through SSH.
- Change to the directory containing the wiki’s
maintenancedirectory. - Run the command appropriate for the release family.
- Read the line beginning with
MediaWiki version:and copy the complete value. - Save any build or patch-date information printed with it.
Maintenance scripts reside in the installation’s maintenance directory and normally require command-line access. Running the command from a parent directory, a backup copy, or a different virtual host can produce a valid-looking result for the wrong installation, so verify the path before recording the output.
What a command-line result proves
The script reports the version of the codebase on which it is run. That makes it valuable when the web server may be serving another directory. However, a successful local command does not by itself prove that the browser is using those files. Always check Special:Version after an upgrade to verify the web-facing installation.
Verify the version after upgrading MediaWiki
Check the files and database separately
Version checking is verification; it does not update MediaWiki files or the database. Complete the upgrade procedure first, including the required database update. If you do not have shell access, MediaWiki’s upgrade documentation identifies the web updater as the browser-based route for running the update process.
Confirm the active release in the browser
- Open the same wiki URL used before the maintenance work.
- Navigate to
Special:Version. - Confirm that the expected complete version string is displayed.
- Check the PHP and database entries and verify that the expected extensions and skins are present.
- Compare the result with the pre-upgrade record and save the date of verification.
If the expected number is not shown, do not assume that the upgrade failed immediately. The web server may still point to an old directory, a load balancer may be sending traffic to an un-upgraded node, or the browser may be open on a different wiki. Resolve the path or deployment issue before repeating database work.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Use the command line as a cross-check
When shell access is available, run the appropriate Version.php command from the directory you intended to deploy. Matching command-line and browser results provide stronger evidence that both the files and the web configuration are aligned. If they differ, preserve both outputs and investigate which installation each request reached.
Troubleshoot common version-check failures
The Special:Version page is missing or inaccessible
- Check the URL spelling and the wiki’s URL style. Try the form that matches the installation, such as
/wiki/Special:Versionor/w/index.php?title=Special:Version. - Sign in with an account that has permission to view the special page.
- Make sure you opened the intended wiki, not a documentation site, staging copy, or neighboring virtual host.
- If the site deliberately restricts the page, ask an administrator to provide the version and environment inventory.
The page loads but shows an unexpected version
- Compare the complete version string with the planned release, including the patch number.
- Check whether the browser URL points to a staging or backup installation.
- Ask whether all web servers behind a load balancer were updated.
- Run the maintenance command in the deployed directory and compare its output with the browser result.
- Repeat the check after the maintenance window if deployment or cache changes are still propagating.
The command reports that a file cannot be found
- Confirm that the current working directory contains
maintenance. - Use
php maintenance/run.php Version.phponly on releases that include the runner. - On MediaWiki 1.39 and earlier, try
php maintenance/version.php. - Verify that you are examining the live installation rather than an archive, backup, or source checkout.
PHP or permission errors appear
Maintenance scripts require a usable PHP command and appropriate filesystem access. Ask the server administrator to run the command under the same deployment account and PHP environment used by the wiki. Record the PHP version shown by Special:Version because a command-line PHP binary can differ from the web server’s PHP runtime.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →An extension or skin is blamed after an upgrade
Capture the MediaWiki version together with the extension, skin, library, PHP, and database entries shown on Special:Version. Check whether the failing feature corresponds to a listed parser tag or parser-function hook. This evidence is more useful than reporting only that “MediaWiki was upgraded,” because the surrounding components may be the source of the incompatibility.
What to include in a support report
A concise but complete report should contain:
- The wiki’s identifying URL or internal site name, subject to your organization’s security policy.
- The complete MediaWiki version, including patch level and any LTS marker.
- The build or patch date when displayed.
- The PHP version and database type or version.
- Installed extensions, skins, and relevant libraries.
- Parser extension tags or parser-function hooks related to the failure.
- Whether the value came from
Special:Version, the Siteinfo API, the command line, or more than one method. - The date and time of the check and whether it occurred before or after an upgrade.
This format lets another administrator reproduce the check and see whether the reported environment is still current.
A practical decision rule
- Need one answer quickly: open
Special:Versionand copy the complete release string. - Investigating compatibility: capture the dependencies, extensions, skins, libraries, and parser entries on that page as well.
- Managing multiple wikis: use the Siteinfo API to collect comparable records on a schedule.
- Working during deployment: run the version script in the installation directory, then confirm the web-facing result in
Special:Version. - Using an older release: select the maintenance-script syntax that matches the files present, with direct
maintenance/version.phpinvocation generally applying to MediaWiki 1.39 and earlier.
Checking the version is a read-only inspection. It tells you what code and environment are active; it does not perform an upgrade, alter the database, or install an extension.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
