From d49ae175ca53eb19f4bb870ed5df68ad7d378fd5 Mon Sep 17 00:00:00 2001 From: Morne Alberts Date: Fri, 17 Jul 2026 09:08:27 +0200 Subject: [PATCH] Show a runnable purgeParserCache invocation Run bare, purgeParserCache exits with "Must specify either --expiredate or --age" on every MediaWiki version the extension supports. Spell out an invocation that works: --age 0 deletes every parser cache entry saved before the run, since entry expiry is capped at $wgParserCacheExpireTime. Also say the script clears the whole parser cache, not only the affected pages. Co-Authored-By: Claude Fable 5 --- docs/migration-guide-bs5.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/migration-guide-bs5.md b/docs/migration-guide-bs5.md index eaf5ad0..812992d 100644 --- a/docs/migration-guide-bs5.md +++ b/docs/migration-guide-bs5.md @@ -72,7 +72,12 @@ Pages rendered before the upgrade still carry Bootstrap 4 markup in the parser cache while the wiki already serves Bootstrap 5 CSS and JavaScript, so components on cached pages can look broken. This resolves as pages re-render; to force it, purge the affected pages or -run the `purgeParserCache` maintenance script. +clear the whole parser cache with the `purgeParserCache` maintenance +script: + +``` +php maintenance/run.php purgeParserCache --age 0 +``` [BS5-jumbotron]: https://getbootstrap.com/docs/5.3/examples/jumbotron/ [BS5-migration]: https://getbootstrap.com/docs/5.3/migration/