Last modified: 2014-06-19 11:55:56 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T68777, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66777 - No way to back-fill log_search with protection information (causing missing data in Special:ProtectedPages)
No way to back-fill log_search with protection information (causing missing d...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.24rc
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 9361
  Show dependency treegraph
 
Reported: 2014-06-18 11:59 UTC by This, that and the other (TTO)
Modified: 2014-06-19 11:55 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description This, that and the other (TTO) 2014-06-18 11:59:49 UTC
The log_search table began to be populated with protection-related information in Gerrit change #105443. Older protection events (prior to deploy of 1.23wmf15) lack the required log_search records, meaning Special:ProtectedPages is full of "unknown" timestamps etc. on big wikis like enwiki.

It should be possible to write a maintenance script to back-populate log_search with the relevant protection data. Requires matching up log entries with records in page_restrictions.
Comment 1 Umherirrender 2014-06-18 16:21:58 UTC
Look at the last page to have it all filled ;-)

https://en.wikipedia.org/w/index.php?title=Special:ProtectedPages&dir=prev

I am not sure, if it is possible to always find the correct or related log entry. Page moves and reprotection can cause a problem here.

On dewiki we also have protected pages without a log entry (see bug 24511), because the logging system does not exists at that point. So you would still have unknown rows on enwiki.

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


Navigation
Links