Last modified: 2012-11-05 20:53:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 27592 - Extension:ReaderFeedback failing to create graphs on n:en:Special:RatingHistory
Extension:ReaderFeedback failing to create graphs on n:en:Special:RatingHistory
Status: NEW
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2011-02-20 19:43 UTC by Amgine
Modified: 2012-11-05 20:53 UTC (History)
4 users (show)

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


Description Amgine 2011-02-20 19:43:24 UTC
Problem was not noticed earlier, but existing since at least 18 Feb 2011.

Possible cause: a configuration change to $wgFeedbackSizeThreshhold, which should be 5.
Comment 1 Bawolff (Brian Wolff) 2011-02-24 21:34:23 UTC
Note, the size is currently set to 15. However, its not rendering on pages with over 234 votes, so i don't think that is the issue.

I filed a semi-dupe at bug 27695
Comment 2 Mark A. Hershberger 2011-03-08 22:44:45 UTC
Upgrade to Article Feedback?
Comment 3 Nemo 2012-08-23 22:14:18 UTC
(In reply to comment #2)
> Upgrade to Article Feedback?


(In reply to comment #1)
> I filed a semi-dupe at bug 27695

What makes it a semi-?
Comment 4 Bawolff (Brian Wolff) 2012-11-05 20:53:39 UTC
> What makes it a semi-?

Don't remember. Assumed cause perhaps? (Entirely broken vs just not enough votes)

Anyhow, at this point i think the extension should just be disabled.

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