Last modified: 2012-08-04 21:10:52 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 T36283, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34283 - enabling aftv5 on the beta cluster broke gadgets
enabling aftv5 on the beta cluster broke gadgets
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
ArticleFeedbackv5 (Other open bugs)
unspecified
All All
: Highest critical (vote)
: ---
Assigned To: Yoni Shostak
:
Depends on:
Blocks: 39043
  Show dependency treegraph
 
Reported: 2012-02-08 21:53 UTC by Mark A. Hershberger
Modified: 2012-08-04 21:10 UTC (History)
4 users (show)

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


Attachments

Description Mark A. Hershberger 2012-02-08 21:53:00 UTC
I had to disable aftv5 on enwiki.beta because js stopped loading after it and so gadgets weren't loaded.  No errors were shown in the firebug console.
Comment 1 Fabrice Florin 2012-02-08 23:44:03 UTC
Hi Mark, could you please provide more details about this issue? How can we help address your concerns? We'd like to do what needs to be done to make sure we don't stop other gadgets to be loaded. Also, can you please confirm that this only affects beta, not the live production site on en-wiki? We definitely don't want aft5 to be disabled on production, if possible. Thanks!
Comment 2 Roan Kattouw 2012-02-08 23:44:55 UTC
Mark, I think this is a non-issue now, because re-enabling AFTv5 didn't reintroduce the issue, right?
Comment 3 Yoni Shostak 2012-02-08 23:58:41 UTC
keeping this open for verification
Comment 4 Mark A. Hershberger 2012-02-09 01:02:43 UTC
(In reply to comment #2)
> Mark, I think this is a non-issue now, because re-enabling AFTv5 didn't
> reintroduce the issue, right?

Right.  This is most likely something with RL/Beta cluster wonkiness.

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


Navigation
Links