To disable MediaWiki’s built-in page caching across an entire wiki, add these two settings to LocalSettings.php:
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
$wgParserCacheType = CACHE_NONE;
$wgCachePages = false;$wgParserCacheType turns off the ParserCache that stores rendered page output. $wgCachePages = false turns off MediaWiki’s client-side page caching. This does not disable a separate Varnish, CDN, or other reverse-proxy cache; those systems must be purged or reconfigured independently.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What MediaWiki caching includes
“Caching” in a MediaWiki installation can refer to several different layers. Changing one setting will not necessarily affect the others, so identify the layer producing stale output before changing configuration.
| Layer | What it stores or controls | Where it is controlled |
|---|---|---|
| ParserCache | Rendered HTML generated from wikitext for page views | $wgParserCacheType |
| Client-side page caching | Whether browsers may reuse page responses and whether MediaWiki can honor HTTP_IF_MODIFIED_SINCE |
$wgCachePages |
| Reverse proxy or CDN | Responses held by infrastructure in front of MediaWiki, such as Varnish or a CDN | The proxy or CDN’s own policy and purge tools |
| API HTTP caching | Freshness of GET responses in browsers and shared proxies | API maxage and smaxage parameters |
MediaWiki’s ParserCache is the primary caching mechanism for serving page views. It is separate from a reverse proxy or CDN: a page can be freshly rendered by MediaWiki while an upstream proxy still serves an older response.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Disable all built-in page caching
1. Edit the local configuration
Open the wiki’s LocalSettings.php and add:
$wgParserCacheType = CACHE_NONE;
$wgCachePages = false;The MediaWiki FAQ documents these two lines as the complete recipe for disabling the built-in caches relevant to normal page delivery. Keep the statements in the active configuration for the wiki you intend to change; a different configuration file or a different wiki installation will not be affected.
2. Understand the first setting
$wgParserCacheType selects the storage backend used for rendered parser output. Setting it to CACHE_NONE means MediaWiki does not cache that rendered output. Pages therefore need to be rendered again instead of being served from ParserCache.
3. Understand the second setting
$wgCachePages controls client-side page caching and is enabled by default. With client caching enabled, MediaWiki can process a browser’s HTTP_IF_MODIFIED_SINCE request and answer 304 Not Modified when the browser’s copy is still considered current. Setting it to false disables that MediaWiki behavior.
4. Test the result at the correct layer
After saving the configuration, test a page that has recently changed, preferably from both a logged-in and a logged-out session. If the response is still old, determine whether the old copy is coming from an upstream proxy or CDN rather than ParserCache. A LocalSettings change cannot purge an independently managed shared cache.
What this complete recipe does—and does not do
It disables MediaWiki’s normal rendered-page cache
The combination of CACHE_NONE and $wgCachePages = false addresses the two settings MediaWiki identifies for completely disabling its built-in page caching: rendered output inside MediaWiki and client-side page caching.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
It does not control a reverse proxy or CDN
Varnish, a CDN, or another reverse proxy sits outside the ParserCache layer. It can continue returning an older response even after MediaWiki renders a new one. To resolve that situation, change the proxy’s caching policy or use that service’s purge mechanism. Make the change in the infrastructure that owns the stale response rather than adding unrelated MediaWiki settings.
It does not make every API response uncachable automatically
MediaWiki’s API has its own HTTP controls. For GET requests, maxage targets browsers and smaxage targets shared proxies. API clients can therefore receive caching instructions even when page-view caching has been disabled.
Choose a narrower change when a site-wide shutdown is unnecessary
Disabling caching everywhere is useful for troubleshooting or a wiki with a strong requirement for freshly rendered output, but rendering is expensive. The ParserCache manual recommends preserving a good cache hit rate where possible. Use the narrowest control that fixes the actual problem.
| Goal | Control | Scope | Version note |
|---|---|---|---|
| Disable rendered page caching everywhere | $wgParserCacheType = CACHE_NONE |
Whole wiki, ParserCache layer | Use the setting supported by the target wiki version |
| Disable MediaWiki client-side page caching | $wgCachePages = false |
Whole wiki, browser-facing page responses | Enabled by default unless changed |
| Stop client caching for an extension special page | $wgOut->enableClientCache(false) |
One special-page response | Current documented extension pattern |
| Prevent parser-tag output from remaining fresh | $parser->getOutput()->updateCacheExpiry(0) |
Output produced by a parser tag | Current parser-output pattern |
| Suppress ParserCache for one namespace | $wgParserCacheFilterConfig with minCpuTime => PHP_INT_MAX |
Namespace-specific parser caching | Documented from MediaWiki 1.42 |
| Expire old entries while retaining caching | $wgCacheEpoch |
Entries older than a chosen timestamp | Invalidation, not a total cache disable |
Disable caching for an extension special page
Extensions that generate dynamic special-page output can disable client caching for that response instead of changing the entire wiki. The current documented pattern is:
global $wgOut;
$wgOut->enableClientCache(false);Place this in the extension code path that builds the special-page response. The global declaration makes the output object available in that scope. This targets client-side caching for the response; it is not a replacement for configuring an external reverse proxy or CDN.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Set zero cache expiry for parser-tag output
When an extension’s parser tag emits output that must not remain cached, update the parser output’s cache expiry:
$parser->getOutput()->updateCacheExpiry(0);This is the current parser-output approach. Older examples may show $parser->disableCache(), but that method was deprecated in MediaWiki 1.28 and removed in MediaWiki 1.35. Code using the removed method must be updated rather than copied into a current extension.
Suppress ParserCache for one namespace
MediaWiki documents namespace-specific filtering through $wgParserCacheFilterConfig. For a namespace where parser output should not be cached, configure its minCpuTime threshold as PHP_INT_MAX. That makes the threshold effectively unreachable and disables parser caching for that namespace.
A value of 0 has the opposite meaning: it always allows caching. This setting is documented as introduced in MediaWiki 1.42, so check the target wiki’s version before using it. A wiki older than 1.42 needs a version-compatible approach, such as a broader ParserCache setting or extension-specific output control.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why pages can remain stale after changing LocalSettings.php
The stale copy is in a CDN or reverse proxy
This is the most important distinction. ParserCache belongs to MediaWiki, while a reverse proxy or CDN is an independent layer. If the proxy already stored an old response, changing $wgParserCacheType or $wgCachePages does not remove that object. Purge the affected URL or change the proxy’s policy using the controls supplied by that infrastructure.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
The request is an API GET with its own cache lifetime
Inspect the API request’s maxage and smaxage parameters. maxage specifies freshness for browsers; smaxage specifies freshness for shared proxies. These controls apply to GET responses and can produce behavior different from a normal page view.
The request is made in a logged-in context
Responses tied to a logged-in user’s context are marked Cache-Control: private for shared caches. A shared proxy should not reuse those responses for other users. This privacy behavior is separate from whether an anonymous page response is cached.
The client changed cache parameters
An API request with different cache parameters has a different URL. Because the URL differs, it may not reuse an earlier cached response. When diagnosing an apparent inconsistency, compare the complete request URL, not only the endpoint path.
The response is an error
API errors are never cached. If an error response appears repeatedly, its cause is not an API cache entry; investigate the request, authentication, permissions, or the upstream system returning the error.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use cache invalidation instead of disabling caching permanently
If the immediate need is to make a configuration or content change visible, but you still want ParserCache’s performance benefit afterward, use $wgCacheEpoch. Set the epoch to a chosen timestamp so entries older than that point expire. This invalidates older entries without turning off every cache layer.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
$wgCacheEpoch is not equivalent to $wgParserCacheType = CACHE_NONE. It changes which existing entries are considered usable; it does not remove browser caching, API caching, or a separate CDN policy. Those layers still require their own controls.
Performance and operational trade-offs
Rendering cost
Parser rendering is more expensive than serving an already-rendered result. With ParserCache disabled, page views must perform that work repeatedly. On a busy wiki, this can increase CPU use and response time, which is why the ParserCache documentation emphasizes retaining cache hits when a full shutdown is not necessary.
Outdated 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 matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallBroader blast radius
The two-line recipe affects the whole wiki’s built-in page-view and client-cache behavior. A special-page or parser-tag setting limits the change to the dynamic output that needs it. A namespace filter limits it further, but requires MediaWiki 1.42 or later according to the documented version boundary.
Cache layers can disagree
Disabling one layer does not guarantee that every request reaches the origin. A CDN can still serve an object, a browser can still have a response, and an API request can carry its own freshness parameters. Treat cache troubleshooting as a layer-by-layer diagnosis rather than repeatedly changing the same LocalSettings value.
Version checks before applying a recipe
- MediaWiki 1.35 and later: do not use the removed
$parser->disableCache()method. - MediaWiki 1.42 and later: the documented
$wgParserCacheFilterConfignamespace filter is available. - Any version: verify the target wiki’s supported configuration variables and extension APIs before deploying a setting copied from another release.
The version boundaries matter most for extension code and namespace-specific controls. The complete site-wide recipe remains the pair of settings shown at the start, provided they are supported by the version you run.
Quick Recap
A practical decision path
- Decide whether the stale output is a normal page, an API response, or extension-generated output. Each has different controls.
- Check for an external proxy or CDN. If one exists, include its cache and purge policy in the diagnosis.
- For a whole-wiki test, set
$wgParserCacheType = CACHE_NONEand$wgCachePages = false. - For one extension special page, call
$wgOut->enableClientCache(false)in that response path. - For parser-tag output, call
$parser->getOutput()->updateCacheExpiry(0)and avoid the removed$parser->disableCache()method. - For one namespace on MediaWiki 1.42 or later, configure its parser-cache filter with
minCpuTimeset toPHP_INT_MAX. - If freshness is temporary, use
$wgCacheEpochto invalidate older entries while retaining normal caching. - Retest each layer separately. A fresh origin response does not prove that a browser or shared proxy has discarded its older copy.
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.
