Apr 14 2016
I am also observing this behavior in Chrome (on Ubuntu,
Feb 24 2016
Just wondering - did you try what I suggested - making a page with 200 copies of <source lang="xml" enclose="none"><Test></source>
"We" is the organization I work for.
Feb 3 2016
BTW, maybe it would be a good idea to add something to the release notes for 1.26 (https://www.mediawiki.org/wiki/Release_notes/1.26) about this. Although I read the release notes all the way back to 1.24 before upgrading, it was not apparent to me from "Removed hitcounters and associated code." in https://www.mediawiki.org/wiki/Release_notes/1.25 that this would result in loss of data. It isn't even labelled as a BREAKING CHANGE.
Hi, I just got whacked by this. We upgrade only from LTS to LTS (maybe this is a bad idea?). So I just went from 1.23 to 1.26. We didn't notice that the hit counts were missing for 1 month, with extensive edits in the mean time. It appears that the only way to recover our hit counts without losing our page edits is to extract the hit count tables from the pre-upgrade backup (I guess after upgrading that to 1.25?) and manually (scary) add them to the 1.26 database?
Jan 7 2016
Jan 4 2016
We are now experiencing a much more serious problem. We have a page with 811 distinct usages of syntax highlighting, mostly as inline fragments. It will not render - instead we get a timeout.