[01:45:13] javascript hasnt been working properly for me since a few days ago [01:45:21] i use an old browser, Firefox 3.6 [01:45:29] did something happen that suddenly made FF3.6 incompatible? [01:45:33] it works fine on Chrome [01:46:01] e.g. the clock works fine for teh few seconds it takes to load a page, then stops [01:46:05] wiked doesnt work [01:46:33] it just creates an entirely blank edit window [01:46:49] it happened on or about December 14 [02:30:21] i have no twinkle now apparerntly [02:31:56] Swob: I'm sorry to hear that. On which wiki? [02:33:18] i was here earlier [02:33:24] javascript stopped working about 2 days ago [02:33:28] did something change? [02:33:50] editing with no javaxcript or twinkle makes me look like a clueless newbie [02:34:08] Swob: Can you check your browser's error console? [02:34:28] Swob: You can also try a different browser to isolate the problem. Firefox 3.6 is ancient and unsupported, I believe. [02:34:40] yeah theres a bumnchj of warnings [02:34:45] Ah, never mind, I see it works on Chrome. [02:34:49] Just use Chrome? :-) [02:34:52] did something suddenly change recently that would make it work bnadly on firefox 3.,6? [02:35:05] Well, the world changed. Firefox 3.6 isn't really supported. [02:35:13] did something change recvently though? [02:35:22] did they upgrade to a new version of mediawiki 2 days ago? [02:35:25] That's not really a valid question. [02:35:35] Two days ago would be Saturday. [02:35:43] No deployments happen on Fridays or Saturdays, generally. [02:35:51] ok then there must be another problem [02:35:56] There's a log at https://wikitech.wikimedia.org/wiki/SAL [02:36:07] Twinkle could've been updated. [02:36:16] I assume you use the JavaScript gadget? [02:36:17] Which wiki? [02:36:25] You can check the page history to see if it's been changed. [02:36:26] i need FF3.6 because of some plugins that dont work with newer versions of FF yet [02:36:36] i could use chrome yes but then there'd be no bookmarks [02:36:41] Yet? Heh. [02:36:49] You can import bookmarks into Chrome. [02:36:51] Surely. [02:37:02] yeah but Chrome doesnt support Firefox-style bookmarks [02:37:11] I imagine it has a plugin. [02:37:13] keywords, i mean [02:37:17] Or extension, whatever it's called. [02:37:17] it doesnt support ketywords [02:37:43] https://encrypted.google.com/search?hl=en&q=bookmark%20keywords%20google%20chrome [02:37:48] like i could just type "ah Longisquama" and get the article history of longiquama [02:37:51] > How to Set Keyword Bookmarks in Google Chrome - Lifehacker [02:37:58] > Chrome Web Store - Quickmarks - Google [02:38:13] I think you have some options. :-) [02:38:24] Firefox 3.6 was released in January 2010, BTW. [02:38:45] So it's nearly four years old, which is... really old in Internet time. [02:38:57] If you're waiting on plugins to be updated, you're probably out of luck. [02:39:37] if youve decided you dont want to help me, then OK. I'm not here to argue about what browsers i should use [02:39:57] i know something happened 2 days ago and if it wasnt a mediawiki upgrade then something is wrong on my end [02:40:23] I'm trying to explain to you why you'll have difficulty getting help. [02:41:06] Browsers are free (as in beer). If you tie yourself to a particular one and wait a few years, things will break... [02:48:39] also i know osmeone else said he had the problem and he wasnt on FF3.6 [02:49:18] i seem to have fixed it for the most part by disabling Greasemonkey [05:03:02] hola [05:03:21] hhaah [05:03:28] que tal [05:03:29] !asl [05:03:34] eh:) [05:03:36] !ask [05:03:49] hola mutante que cuntas :) [05:04:01] xD CUENTAS * [05:04:35] jesus_MAncini: the site, i hope. i dont really speak Spanish:) [05:04:44] any issues? [05:04:59] e.e que'? [05:05:08] no te entiendo [05:06:19] jesus_MAncini: [05:06:20] Realmente no hablo español, si usted tiene algún problema con el sitio, Wikipedia, por favor háganoslo saber en Inglés o utilizamos Google Translate. Gracias. [05:07:19] e [10:22:10] hey, all, I'm looking for some help with an API call [10:24:36] Writ_Keeper: I can probably help if you tell me what you need [10:25:01] so, I'm trying to use the query api to get a diff [10:25:15] by sending in text via the difftotext parameter [10:25:38] the question is: does the difftotext parameter have some sort of maximum limit on size? [10:25:49] Not really [10:26:10] If you specify it in the query string (as a GET request), then in practice there will be some sort of limit [10:26:12] Probably in the 8K-16K range [10:26:57] If you make a POST request, rvdifftotext can be as long as you want [10:27:06] hmm okay [10:27:08] thanks [13:29:26] is https://donate.wikimedia.org down for anyone else? [13:31:08] down for me in europe. [13:41:55] the-wub: doesn't work for me via esams and no ping, can ping via eqiad but doesn't actually bring up the site [14:31:40] Someone to confirm that this picture does display at all on Android native browser? https://fr.wikipedia.org/wiki/Fichier:Logo_de_Institut_Bergoni%C3%A9.jpg [14:31:47] Nemo_bis: ? [14:32:18] There is probably a bug there... but on which side... browser? Mediawiki? [14:33:45] I don't have android [14:34:19] Nemo_bis: :( [14:34:33] apart from beine an obvious copyvio, looks like a standard file page [14:35:05] Nemo_bis: this is not a copyvio, this is a logo, with dedicated laws and rules [14:36:12] it's obviously not pd-ineligible [14:37:58] ok, now it might be respecting the local EDP, can't tell [16:06:11] hi, does the host wikimedia3.typhon.net belong to the wmf? [16:26:17] No [16:26:42] * Reedy follows [16:27:18] http://www.typhon.com [16:31:22] "We also host: [...] wikimedia.fr" [16:32:26] ah, that makes sense. thanks. [18:28:41] hmm, https://www.mediawiki.org/wiki/Extension:Bugzilla_Reports looks like it has funny CSS issues with mw-head and mw-panel covering site content, plus I can reproduce in Firefox and Chrome. Wondering if that's just me and an isolated issue [18:30:30] Whoa, weird [18:30:33] andre3003: Confirmed [18:34:58] marktraceur, it's also on the first diff. But I don't get what's wrong here... [18:35:49] Huh. [18:36:03] Maybe it's an issue with one or more of the templates or extensions or something [18:43:29] andre3003: looks like a typical example of unbalanced div [18:45:32] though I can't find it quickly [18:50:25] * andre3003 gives it a shot [18:50:47] looks like https://www.mediawiki.org/w/index.php?title=Extension%3ABugzilla_Reports&diff=844734&oldid=773425 fixes it for me [18:50:53] interesting [22:41:02] Reedy: mind clarifying https://bugzilla.wikimedia.org/show_bug.cgi?id=58598 a bit? [22:41:18] kaldari just filled https://bugzilla.wikimedia.org/show_bug.cgi?id=58602 too [22:42:15] twkozlowski: Yeah. Crap error message on the special landing page [22:42:25] message/handling [22:42:30] so it's just about the crap message? good :) [22:42:41] twkozlowski: yeah, those are basically the same bug [22:42:57] kaldari: if Reedy's about the crap message, then I think not [22:43:02] It is [22:43:04] well at least the underlying issue is the same [22:43:05] Without reading the code, I don't know if it's actually buggy [22:43:07] Yours is about the user right/user group difference [22:43:22] Right [22:43:23] See https://bugzilla.wikimedia.org/show_bug.cgi?id=58598#c1 [22:43:24] if you fix my bug, Reedy's bug gets fixed for free :) [22:44:46] Reedy: apparently the special page is actually checking of the group, not the right, so it's all backwards :) [22:45:14] really? :/ [22:47:22] so technically the error message is (mostly) correct, but just very confusing and non-standard behavior [22:47:30] * @param string $restriction User right required, e.g. "block" or "delete" [22:47:46] That's from SpecialPage.php __construct() docs [22:48:16] It sort of loooked like wheel reinvention to me from the outside [22:48:51] I haven't looked at the code, but I get the error message if I belong to the admin group, but not if I belong to the gwtoolset group, both of which have the gwtoolset right [22:49:19] lol [22:49:21] Right [22:49:29] I just added myself to the toolset group [22:49:41] But that seems even more like re-inventing the wheel for special pags [22:50:02] yeah, should be easy enough to fix though [22:50:31] yup [22:50:49] or it isn't, some code reviewers need poking with big sticks