When the “Recent Changes” page stops working in MediaWiki, it usually stems from database lag, caching issues, or misconfigured background jobs. 🛠️ Common Fixes Clear the Object Cache
Old data can get stuck in your cache and prevent new edits from appearing.
Fix: Add ?action=purge to the end of your Recent Changes URL to force a refresh.
Fix: Clear your server cache (like Memcached or Redis) if you use one. Run the Job Queue
MediaWiki uses a job queue to update pages in the background. If the queue stalls, updates stop.
Fix: Add \(wgJobRunRate = 1;</code> to your <code>LocalSettings.php</code> file to run jobs on every page view.</p> <p><strong>Fix:</strong> Run <code>php maintenance/runJobs.php</code> via terminal for large wikis. Check Database Lag</p> <p>If you use a master-replica database setup, replication lag will delay updates.</p> <p><strong>Fix:</strong> Check your database status to ensure replicas are syncing with the master.</p> <p><strong>Fix:</strong> Temporarily increase <code>\)wgMaxExecutionTime if large edits are timing out. Verify User Permissions
If changes by certain users are missing, they might be marked as hidden “bot” edits. Fix: Click Show bots at the top of the Recent Changes page.
Fix: Check if the edits were inadvertently oversighted or suppressed by an administrator. 💡 Optimization Tips Use Manual Cron Jobs
Relying on page views to clear the job queue slows down user traffic. Tip: Set \(wgJobRunRate = 0;</code> in <code>LocalSettings.php</code>.</p> <p><strong>Tip:</strong> Create a system cron job to run <code>runJobs.php</code> every few minutes instead. Adjust Feed Limits</p> <p>Loading too many results at once can crash the page or cause timeouts.</p> <p><strong>Tip:</strong> Lower <code>\)wgRCMaxAge to keep fewer days of history in the active table.
Tip: Set reasonable defaults for users with $wgQueryPageDefaultLimit. Monitor the recentchanges Table
An oversized or corrupted database table will break the feed.
Tip: Run php maintenance/cleanupTable.php recentchanges to remove orphaned rows.
Tip: Ensure the table has proper database indexes if queries are slow.
To help narrow down the exact issue, could you tell me if you are seeing an error message, a completely blank page, or just delayed updates? Saved time Comprehensive Inappropriate Not working
A copy of this chat, including the images and video, will be included with your feedback A copy of this chat will be included with your feedback
Your feedback will include a copy of this chat and the image from your search
Your feedback will include a copy of this chat, any links you shared, and the image from your search.
Thanks for letting us know
Google may use account and system data to understand your feedback and improve our services, subject to our Privacy Policy and Terms of Service. For legal issues, make a legal removal request.
Leave a Reply