Last modified: 2014-07-16 10:27:58 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 T67375, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 65375 - Pages lose their required ResourceLoader modules after being purged on 1.24wmf5
Pages lose their required ResourceLoader modules after being purged on 1.24wmf5
Status: VERIFIED FIXED
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
All All
: Highest major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: wmf-deployment
  Show dependency treegraph
 
Reported: 2014-05-15 22:38 UTC by Aude
Modified: 2014-07-16 10:27 UTC (History)
9 users (show)

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


Attachments
test wikidata with broken formatting (66.04 KB, image/png)
2014-05-15 22:38 UTC, Aude
Details

Description Aude 2014-05-15 22:38:22 UTC
Created attachment 15401 [details]
test wikidata with broken formatting

Item pages are appearing unformatted on test.wikidata, especially with no javascript.

With javascript, the TOC does not have wikibase formatting.

I experienced the same issue on my dev wiki. Restarting memcached (clearing resource loader cache) fixed the issue for me.

I assume the issue is related to some change in core, as new core code was deployed to test.wikidata and no changes in Wikibase.
Comment 1 Aude 2014-05-16 00:05:40 UTC
there also is an issue with missing / wrong styling for pages with Geshi syntax highlighting

http://snag.gy/vhfGe.jpg

seems extension resources are sometimes not being loaded or something
Comment 2 Bartosz Dziewoński 2014-05-16 00:09:21 UTC
To reproduce this bug locally:

1. Have SyntaxHighlight_GeSHi installed ('master' version will do)
2. Checkout mediawiki/core branch origin/wmf/1.24wmf4
3. Save a page with <syntaxhighlight> tag
4. Checkout mediawiki/core branch origin/wmf/1.24wmf5
5. Refresh the saved page. Observe that the styles are still correct.
6. Purge the saved page. STYLES BREAK.
7. Null-edit the saved page. Styles fix themselves.

Trying these steps and bisecting pointed me to f359cdf61462782743a87943938ef4cce78b2647. I'd appreciate if someone could verify the reproduction steps, because that's just too weird.
Comment 3 Bartosz Dziewoński 2014-05-16 00:22:33 UTC
To clarify, the module loading process – load.php and friends, mw.loader.load() calls in JS – works correctly: it's just that the pages do not load these modules (load.php invocations are missing from HTML source).
Comment 4 Kevin Israel (PleaseStand) 2014-05-16 00:43:02 UTC
(In reply to Bartosz Dziewoński from comment #2)
> Trying these steps and bisecting pointed me to
> f359cdf61462782743a87943938ef4cce78b2647. I'd appreciate if someone could
> verify the reproduction steps, because that's just too weird.

Explanation: bug 56911 comment 6.

Do not change visibility modifiers (other than "var" to "public") on classes that are serialized for storage in the DB or a cache (unless, of course, the cached objects are invalidated and any performance implications are addressed).

This includes ParserOutput::$mHeadItems.
Comment 5 Bartosz Dziewoński 2014-05-16 00:56:03 UTC
Reverted in I12a60b5cc52a07a6deabcbf47c7c99cd2faac3c3.
Comment 6 Lydia Pintscher 2014-05-16 15:01:20 UTC
Seems fine now on test.wikidata.org

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


Navigation
Links