Bug 25516 - Wiki: Recentchanges doesnt get updated since maintenance
Summary: Wiki: Recentchanges doesnt get updated since maintenance
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: wiki.mageia.org (show other bugs)
Version: trunk
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL: https://wiki.mageia.org/en/Special:Re...
Whiteboard:
Keywords:
: 26245 (view as bug list)
Depends on:
Blocks: 26245
  Show dependency treegraph
 
Reported: 2019-10-02 20:49 CEST by psyca
Modified: 2022-09-11 11:27 CEST (History)
6 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description psyca 2019-10-02 20:49:31 CEST
Description of problem:
Since the maintenance on 30.09, the page https://wiki.mageia.org/en/Special:RecentChanges doest get updated if an page in the wiki got changed or newly created.

This page is important for translators to see the latest changes.
psyca 2019-10-02 20:49:43 CEST

Summary: Wiki; Recentchanges doesnt get updated since maintenance => Wiki: Recentchanges doesnt get updated since maintenance

Comment 1 Thomas Backlund 2019-10-03 10:03:31 CEST
Indeed, running the cron job manually shows some problems...

I will look into it

Assignee: atelier-bugs => tmb
CC: (none) => tmb

Marja Van Waes 2019-10-13 18:15:56 CEST

CC: (none) => doc-bugs, marja11

Comment 2 psyca 2019-10-29 00:47:52 CET
Is it possible to make a dump of the wiki and try the latest (non lts) version, to check if the error still occurs?
Comment 3 psyca 2019-10-29 00:52:02 CET
Or try a Database Check via the current wiki? https://www.mediawiki.org/wiki/Manual:Update.php
Comment 4 Thomas Backlund 2020-01-05 21:27:31 CET

Turns out I had to run maintenance/rebuildrecentchanges.php to fix up the changes database.

now fixed.

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 5 Thomas Backlund 2020-01-05 21:31:50 CET
btw, the de wiki should be working since the infra upgrade to mga7
Comment 6 psyca 2020-01-05 21:39:54 CET
#Comment 4
Many thanks for this.

#Comment 5
Yea i already saw it and it works again. Thanks for this.
But before the release of MGA7 (date: march 2019) i ported the pages to en.wiki, thats why de.wiki is (now) deprecated/not up-to-date since then and all links (in the MGA7 distro, wiki, manual) are directed to the german pages in the en.wiki.
Comment 7 papoteur 2020-01-05 22:23:35 CET
(In reply to Thomas Backlund from comment #4)
> 
> Turns out I had to run maintenance/rebuildrecentchanges.php to fix up the
> changes database.
> 
> now fixed.

Oh, thanks a lot, Thomas !

CC: (none) => yves.brungard_mageia

Comment 8 psyca 2020-01-06 12:52:22 CET
Hi.
I have to reopen it.

Its true, that the RecentChanges got updated yesterday, but after that i updated an wiki page, my change is not listed in RecentChanges.
I think if you ran the script, it updated the RecentChanges page, but it dont do this automatically (only manual).

This also (not updating) affects the special pages (like https://wiki.mageia.org/mw-en/index.php?title=Special:WantedPages&limit=500&offset=0 ). They dont get updated.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 9 papoteur 2020-02-24 10:57:37 CET
Hello,
Is $wgJobRunRate [1] set?
Do we need a cron job with RunJobs.php [2]?

[1] https://www.mediawiki.org/wiki/Manual:$wgJobRunRate
[2] https://www.mediawiki.org/wiki/Manual:RunJobs.php
Jybz 2020-02-24 14:00:40 CET

Blocks: (none) => 26245

Comment 10 Jybz 2020-03-04 13:32:37 CET
*** Bug 26245 has been marked as a duplicate of this bug. ***

CC: (none) => j.biernacki

Comment 11 psyca 2020-03-05 22:03:54 CET
Seems, that it works now.
Can you confirm your report has fixed, too @Jybz
Comment 12 Jybz 2020-03-06 08:38:20 CET
Hello !

For few days I warned Maât (one sysadmn) of this bug, he triggered a shot, but it isn't permanently fixed yet. I let the sysadmins answering better than I can do.
Maat 2020-03-06 09:23:42 CET

CC: (none) => maat-ml

Comment 13 psyca 2022-09-11 11:27:26 CEST
Closing. Fixed.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.