Last modified: 2012-12-05 01:52:39 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 T44695, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42695 - Reply doesn't work anymore
Reply doesn't work anymore
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
wmf-deployment
All All
: Highest normal (vote)
: ---
Assigned To: Andre Klapper
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-04 20:51 UTC by Lupo
Modified: 2012-12-05 01:52 UTC (History)
5 users (show)

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


Attachments
Patch (550 bytes, patch)
2012-12-04 22:56 UTC, Andre Klapper
Details

Description Lupo 2012-12-04 20:51:22 UTC
Since the upgrade on 2012-12-04.

Javascript error:

Timestamp: 12/4/12 21:49:21 
Error: TypeError: BUGZILLA.constant is undefined
Line: 80

FF 16.0.2
Comment 1 Valerie Juarez 2012-12-04 21:04:08 UTC
This error occurs for me in FF17, Chrome, and IE9.
Comment 2 Andre Klapper 2012-12-04 22:40:39 UTC
Confirming. I'm working on a fix.
Comment 3 Andre Klapper 2012-12-04 22:56:07 UTC
Created attachment 11464 [details]
Patch
Comment 4 Daniel Zahn 2012-12-04 23:00:19 UTC
patch applied

 patch -p0 < bz11464.diff patching file template/en/custom/global/header.html.tmpl
Comment 5 Andre Klapper 2012-12-04 23:02:11 UTC
Works here. Thanks a bunch to reporters and Daniel, as usual. :)
Comment 6 MZMcBride 2012-12-05 01:50:36 UTC
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Vestibulum iaculis lectus. Aenean cursus tempor sem. Quisque suscipit nisi quis metus. Nam eget dolor a diam egestas gravida. In egestas elit a augue. Quisque pellentesque interdum arcu. Duis hendrerit congue lectus. Etiam sit amet odio id tellus elementum feugiat. Aliquam sit amet justo. Proin quis nisl. Vivamus facilisis scelerisque velit. Aliquam erat volutpat. Cras risus lea, venenatis quis, pulvinar sed, interdum id, nisi. Donec interdum ullamcorper quam. Vivamus ultrices dignissim pede. In ut nisi nec mauris ornare tempor. Pellentesque  abitant morbi tristique senectus et netus et malesuada fames ac turpis egestas.
Comment 7 MZMcBride 2012-12-05 01:52:39 UTC
(In reply to comment #6)
> Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Vestibulum iaculis
> lectus. Aenean cursus tempor sem. Quisque suscipit nisi quis metus. Nam eget
> dolor a diam egestas gravida. In egestas elit a augue. Quisque pellentesque
> interdum arcu. Duis hendrerit congue lectus. Etiam sit amet odio id tellus
> elementum feugiat. Aliquam sit amet justo. Proin quis nisl. Vivamus facilisis
> scelerisque velit. Aliquam erat volutpat. Cras risus lea, venenatis quis,
> pulvinar sed, interdum id, nisi. Donec interdum ullamcorper quam. Vivamus
> ultrices dignissim pede. In ut nisi nec mauris ornare tempor. Pellentesque 
> abitant morbi tristique senectus et netus et malesuada fames ac turpis
> egestas.

Hmm. I could swear I'm getting weird line wrapping with other comments. Might just be me, though. The quoted text above looks fine, but for me, when I click "reply" at (for example) bug 30413 comment 0, I get:

---
(In reply to comment #0)
> Status information for bug 29550 is apparently hiding on an RT ticket, which
> can't be seen by volunteers, staff, or anybody else who doesn't have a login
> on
> the private RT system.
> 
> This makes it harder to find out what's going on or get feedback; if ops
> people
> are updating the RT ticket we have no way of knowing, and then they get
> annoyed
> when we ask them for updates. :)
---

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


Navigation
Links