Last modified: 2014-02-12 23:55:40 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 T43333, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41333 - MobileFrontend extension loads JavaScript twice, has weird errors when database error occurs in job queue
MobileFrontend extension loads JavaScript twice, has weird errors when databa...
Status: RESOLVED INVALID
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
: performance
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-23 21:59 UTC by Brion Vibber
Modified: 2014-02-12 23:55 UTC (History)
10 users (show)

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


Attachments

Description Brion Vibber 2012-10-23 21:59:55 UTC
We had an exciting problem locally when Jon updated his test wiki but forgot to run maintenance/update.php. Things appeared to be working fine until it started failing to open the navigation menu.

On investigation, Jon determined this was due to JS being loaded twice: the toggle thus happened twice and the navigation menu didn't stay open.

On further investigation, we found that going to the wiki straight, without MobileFrontend, was showing a database error.

Running maintenance/update.php resolved the issue.


It looks like errors in the job queue (?) are triggering a second set of output. I seem to remember similar problems outside of MobileFrontend in the past, need to examine how the skins & error reporting manage this case.
Comment 1 Jon 2012-10-30 18:55:39 UTC
Any ideas what caused this Brion or should we close this or how someone could investigate this further? I'm not sure how we can investigate this further...

I don't want this to sit in bugzilla for several months with nothing going on :)
Comment 2 Jon 2012-11-29 23:14:12 UTC
Closing as invalid due to lack of activity and not knowing what to do about it.

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


Navigation
Links