Page MenuHomePhabricator

Can't see references on historic revisions of items on Wikidata
Closed, ResolvedPublic

Description

You can't expand the revisions on a historic revision of an item on Wikidata like you can on the most current one. This means users can't see how a statement was referenced before.

For example https://www.wikidata.org/w/index.php?title=Q43920918&oldid=599708910

looks like this:

image.png (86×913 px, 6 KB)

compared to the most recent revision:

image.png (111×910 px, 8 KB)

I saw this on Chrome Version 62.0.3202.94 (Official Build) (64-bit) (linux) in incognito mode when not logged in.

Event Timeline

thiemowmde moved this task from incoming to consider for next sprint on the Wikidata board.

I believe this is a fallout from a recent MediaWiki core change that is closely related to T181807. Thanks a lot for reporting this. This indeed needs fixing.

I just realized this is exactly the same as T129836. I assume the issue came back because of an other reason, that's why I suggest to leave this separate ticket open.

We picked this for Wikidata-Sprint-2017-12-20, but only for investigation. If a fix is trivial it will be submitted right away. Otherwise the result of the investigation will go as a task to the next sprint.

I was bold and made a temporary workaround in Common.css.

Thanks! This CSS workaround gives us time to figure out what happened. Thank you especially for leaving this comment here, this is very helpful.

Change 400684 had a related patch set uploaded (by Thiemo Kreuz (WMDE); owner: Thiemo Kreuz (WMDE)):
[mediawiki/extensions/Wikibase@master] Properly load collapsible sitelinks CSS exactly when needed

https://gerrit.wikimedia.org/r/400684

Change 400685 had a related patch set uploaded (by Thiemo Kreuz (WMDE); owner: Thiemo Kreuz (WMDE)):
[mediawiki/extensions/Wikibase@master] Do not collapse references on diffs/old revisions

https://gerrit.wikimedia.org/r/400685

Change 400686 had a related patch set uploaded (by Thiemo Kreuz (WMDE); owner: Thiemo Kreuz (WMDE)):
[mediawiki/extensions/WikibaseMediaInfo@master] Remove default "true" from MissingMediaInfoHandler

https://gerrit.wikimedia.org/r/400686

Change 400684 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Properly load collapsible sitelinks CSS exactly when needed

https://gerrit.wikimedia.org/r/400684

Change 400685 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Do not collapse references on diffs/old revisions

https://gerrit.wikimedia.org/r/400685

Change 400686 merged by jenkins-bot:
[mediawiki/extensions/WikibaseMediaInfo@master] Remove default "true" from MissingMediaInfoHandler

https://gerrit.wikimedia.org/r/400686

@matej_suchanek can you remove the work-around after tomorrow's deployment?

Change 401695 had a related patch set uploaded (by WMDE-leszek; owner: Thiemo Kreuz (WMDE)):
[mediawiki/extensions/Wikibase@master] Show references on the diff page

https://gerrit.wikimedia.org/r/401695

Change 401695 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Show references on the diff page

https://gerrit.wikimedia.org/r/401695

Change 401699 had a related patch set uploaded (by WMDE-leszek; owner: Thiemo Kreuz (WMDE)):
[mediawiki/extensions/Wikibase@master] Remove editable flag in EntityParserOutputGenerator

https://gerrit.wikimedia.org/r/401699

Change 401699 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Remove editable flag in EntityParserOutputGenerator

https://gerrit.wikimedia.org/r/401699

@matej_suchanek can you remove the work-around after tomorrow's deployment?

The fix seems to have been rolled back, disabling the workaround doesn't fix the problem.

Jep you're right. It had to be reverted. So let's keep the hack until the fix is back in :)

Still not working (workaround necessary).

Because it's not live, the train got rollbacked.

thiemowmde removed a project: User-thiemowmde.

Please do not reopen issues that are solved in the code just because the code is not yet rolled out to the live website. I understand that you want to track if you can remove the local workaround. That might need a separate ticket.