[17:59:21] can anyone explain to me what EventLogging extension is used for? [17:59:37] and what the point of requesting event.gif on port 8080 is? [19:12:22] I have a variable (name $post) and I want to figure out the contents of it but simply 'echo'-ing it doesn't display anything becuase it is not a wikitext. How can I figure out the contents of $post? [19:14:49] PHP variable? [19:16:34] yes [19:17:13] var_dump(); [19:20:22] where will the output show up? [19:38:57] Hi, I need help with something. I just updated my local installation of mediawiki after a long time [19:39:06] and I am getting this error [19:39:14] Fatal error: Call to undefined function MediaWiki\suppressWarnings() in /Library/WebServer/Documents/mediawiki/includes/Setup.php on line 435 [19:39:38] Also, when I try to run update.php I get the error [19:39:52] Sorry all, I am very new to PHP and I really appreciate your help. Much thanks for telling me how to display the contents of my $post variable. The only thing I don't understand now is where will I be able to see the contents being printed out in my browser. I can't see it the HTML produced in the Wiki, nor in the MathML. Where would it show up in my browser. Thanks so much. [19:39:54] Fatal error: Call to undefined function MediaWiki\suppressWarnings() in /Library/WebServer/Documents/mediawiki/maintenance/Maintenance.php on line 960 [19:41:03] Both of these lines contains this : [19:41:11] MediaWiki\suppressWarnings(); [19:41:36] Can anyone help me debug this? [19:41:42] ankita-ks: Did you run composer update? [19:41:59] No, I did not. [19:42:14] That should help [19:42:22] a lot of dependencies have been updated [19:53:47] Sorry all, I am very new to PHP and I really appreciate your help. Much thanks for telling me how to display the contents of my $post variable. The only thing I don't understand now is where will I be able to see the contents being printed out in my browser. I can't see it the HTML produced in the Wiki, nor in the MathML. Where would it show up in my browser. Thanks so much. [19:54:03] What the fuck was thinking WMF when ask for developpment of mediawiki to enable graph extension? [19:54:10] There is a great lack of documentation [19:56:21] Akash: What are you trying to do? You've sent an HTTP post request and you want to dump the contents of the $_POST variable? Is this for a particular wiki page? [19:56:39] The_Photographer: if you're trying to start a dialog/ask others for help, that wasn't the best way of starting. Calling into question another (faceless/generalized) organization's intelligence/sanity/whatever you were implying is not productive. [19:58:27] Not the $_POST variable, i have created a $post variable and I woudl like to track what is in it. When I use var_dump() I cannot find where the output is. [19:58:28] greg-g: Its not a falaceless, The documentation is very low, documentation is very little, only the properties of certain objects are listed in no example of actually using the syntax. For example, something basic as the thousands separator is not documented. [19:58:42] "WMF" is faceless in this regard [19:58:51] if you have suggestions for a person, please say so [19:58:56] how I can change the thousands separator? [19:59:27] greg-g: this extension is enabled in wikipedia, and mediawiki is not anymore a community project [19:59:35] The_Photographer: and? [19:59:51] Akash: Where are you writing this code? In general, however, the output will appear on the top left of the page, at least if you're using the default Vector skin [20:00:05] Akash: You can do a view-source and it should be the first piece text in the output [20:00:23] greg-g: We are in a dictatorship, yes, and what's the problem right? [20:00:50] The_Photographer: not what I said, my point is: what do you want? can you express your need in a non-confrontational way? [20:01:29] (unfortunately, I don't know the answer, 99% likely, I'll just deflect to the author of the extension (yuri k) and phabricator for feature requests) [20:02:14] [16:58] greg-g: Its not a falaceless, The documentation is very low, documentation is very little, only the properties of certain objects are listed in no example of actually using the syntax. For example, something basic as the thousands separator is not documented. [20:02:26] polybuildr: It is not in the source either. I am writing this code in MathLaTeXML.php file [20:03:51] The_Photographer: I would suggest to file tasks in Phabricator, the people who know that extension well probably aren't on IRC watching this channel right now. [20:03:51] greg-g: Thanks for express your help in a non-confrontational way [20:08:19] greg-g: https://phabricator.wikimedia.org/T103173 [20:18:31] polybuildr : So I ran a composer update [20:18:42] and it worked? :P [20:18:45] now I have three errors. [20:18:46] :D [20:18:56] but different ones from before. [20:18:57] What are they? [20:19:04] Well, different errors is always good news. :P [20:20:28] Akash: So you're using the Math extension. [20:20:36] A var_dump will always show if that page is getting executed. [20:20:41] polybuildr: Sorry about that my computer crashed for some reason. [20:20:54] Are you sure it is being executed? An easy way to check would be to just call die() in the middle and see what happens. [20:20:56] that's alright :) [20:21:22] polybuilr: Let me check [20:21:32] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: skins.vector.styles ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /Library/WebServer/Documents/mediawiki/includes/OutputPage.php at line 623] in /Library/WebServer/Documents/mediawiki/includes/debug/MWDebug.php on line 300 [20:21:32] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: skins.vector.styles ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /Library/WebServer/Documents/mediawiki/includes/OutputPage.php at line 623] in /Library/WebServer/Documents/mediawiki/includes/debug/MWDebug.php on line 300 [20:21:32] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: skins.vector.styles ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /Library/WebServer/Documents/mediawiki/includes/OutputPage.php at line 623] in /Library/WebServer/Documents/mediawiki/includes/debug/MWDebug.php on line 300 [20:21:33] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: skins.vector.styles ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /Library/WebServer/Documents/mediawiki/includes/OutputPage.php at line 623] in /Library/WebServer/Documents/mediawiki/includes/debug/MWDebug.php on line 300 [20:21:39] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: skins.vector.styles ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /Library/WebServer/Documents/mediawiki/includes/OutputPage.php at line 623] in /Library/WebServer/Documents/mediawiki/includes/debug/MWDebug.php on line 300 [20:21:45] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: skins.vector.styles ResourceLoaderFileModule [20:21:46] whoa. [20:21:48] sorry about that [20:21:57] polybuildr [20:22:14] Read the first one. Don't ask me why I copied it so many times. [20:22:28] ankita-ks: This is because your copy of Vector is outdated. [20:22:31] skins/Vector [20:22:44] Either pull/clone from master or get a new tarball. [20:22:57] oh okay [20:25:28] polybuildr : that doesn't solve it. [20:25:29] Same error still. [20:26:30] Sorry for pursuing the same path (because I got rid of the error this way), but skins/Vector is in the .gitignore of skins/ [20:26:55] so just cding into the directory and git pull won't fix it [20:27:18] ankita-ks: did you clone a new version from master? or did you already have one cloned and you just pulled? [20:27:27] I git pulled into Vector directly [20:27:34] I have one cloned [20:28:14] Hmm, that's odd. Getting the latest version fixed it for me. [20:29:32] ankita-ks: My freshly pulled version has efa073d3c648 as the latest commit, same for you? [20:29:39] checking [20:30:14] polybuildr : yup [20:31:09] polybuildr: When i put the die() function in the same file it changes the function to say "string(718) "format=xhtml&whatsin=math&whatsout=math&..........................." (i cut of the output because it was excessivley long.) [20:31:44] Other extensions can also cause that error [20:31:51] You might have another out-of-date extension sitting around somewhere [20:32:13] RoanKattouw: ankita-ks's error? [20:32:58] RoanKattouw : checking. [20:32:58] Oh, wait [20:33:03] "skins.vector.styles" [20:33:08] It says so right in the error message [20:33:10] yeah. :P [20:33:14] Never mind [20:33:18] * RoanKattouw has not had enough sleep :D [20:33:48] ankita-ks: line 30 of skins/Vector/skin.json has "position: top", right? [20:33:57] If it does, then the error doesn't make any sense and I give up. [20:34:16] Akash: Changes the function to say?... Do you mean the var_dump is working? [20:34:26] polybuildr : yes, it does. [20:34:55] Also, if it helps, there is another error. [20:35:03] * polybuildr shrugs [20:35:07] That's exactly what "style module should define its position explicitly" means. [20:35:10] Oh, go on. [20:35:10] Cannot read property 'addParsedMessages' of undefined TypeError: Cannot read property 'addParsedMessages' of undefined [20:35:12] That might help. [20:35:50] ankita-ks: Not sure about that one. Wild guess: You did run update.php after the composer update right? [20:35:56] And I suppose there's a stack trace? [20:36:22] yes, [20:36:24] and yes [20:36:37] wait. making a gist [20:38:24] polybuildr : https://gist.github.com/ankita-kumari/ee2391caa20021fc2634 [20:38:26] there [20:39:25] ankita-ks: I'm afraid I have no idea what to do next. :/ Sorry. [20:39:43] That's a JS error [20:39:53] Could be in VisualEditor [20:40:16] ankita-ks: Can you use ?debug=true and try again? That should get you a better stack trace [20:40:24] polybuildr: When i put the die() function in the same file it changes the function to say "string(718) "format=xhtml&whatsin=math&whatsout=math&......" (i cut of the output because it was excessivley long.) [20:40:27] RoanKattouw: The stack trace has a lot of modules=jquery%2Cmediawiki&only=scripts&skin=vector [20:40:36] RoanKattouw : trying that [20:40:37] Akash: I replied to that above. [20:40:42] Also, interestingly [20:40:52] when I go to Edit source [20:40:53] Changes the function to say?... Do you mean the var_dump is working? [20:40:58] the errors disappear [20:41:08] Oh, that's cute. [20:41:10] polybuildr: Yup that's because a lot of the stack frames are internal to mw.loader [20:41:23] and reappear when i switch to VisualEditor from there [20:41:30] ankita-ks: Yeah it looks like a VisualEditor error to me [20:41:44] But not the skins.vector.position one [20:41:51] ?debug=true will help narrow down where in VE it is [20:41:51] only the second error reappears. [20:41:55] Pull visualeditor, then maybe? :P [20:42:07] Did that :| [20:42:30] polybuildr: I think the var_dump() is working, I just cannot find where the output is. [20:42:56] Akash: Just echo something else and do a ctrl-F in the source? [20:48:28] polybuildr: whatever I echo does not show up [20:48:38] polybuildr: in the source [20:49:14] Akash: but if you put a `die("pink elephant");` in the code, does 'pink elephant' show up in the source? [20:49:25] hmm..so VisualEditor has some failed dependencies. [20:50:44] echo doesn't work [20:50:52] var_dump will [20:51:03] https://www.mediawiki.org/wiki/Manual:How_to_debug "One of the first things you will notice is that "echo" generally does not work; this is part of the general design." [20:52:43] Okay, did not know that. Sorry. [20:53:55] polypuildr: it shows it on the home page itself, covered up by the rest of the page. Also after one refresh it goes away and doesn't come back. [20:55:39] Akash: Yeah, the covering up is to be expected. I'm not sure why it doesn't come back, though. More importantly, the var_dump is working though, isn't it? [20:56:01] polybuildr: yes [20:56:27] Akash: So... issue resolved? [20:59:23] https://gist.github.com/ankita-kumari/66697ffe097bb6502f55 [21:02:00] ankita-ks: Now this looks like a node/npm error. [21:02:11] yup [21:02:18] I don't know where it's from, but based on general npm experience [21:02:23] npm update? :P [21:04:14] polybuildr : did that. [21:04:24] Seems to have solved the parsoid error [21:04:39] but the previous one doesn't go away [21:04:42] "Cannot read property 'addParsedMessages' of undefined" [21:05:09] ankita-ks: The error you made a gist of right now, was that parsoid or ^ that one? [21:05:31] … Speaking of the wiki; I have a MediaWiki interface for Perl (as of yet unreleased), and one another for Emacs. Would it be appropriate to put their respective documentation under [[mw:Manual:]]? [21:05:58] polybuildr : https://gist.github.com/ankita-kumari/ee2391caa20021fc2634 [21:06:22] this is the one that remains. The parsoid error gist is titled parsoid-error-log [21:07:31] Oh, right. The title. [21:07:50] Okay, so the this one isn't fixed yet. Hmm. [21:08:24] polybuildr : https://gist.github.com/ankita-kumari/04303a09d7911c05f095 [21:08:30] This is where it gets traced. [21:16:39] ankita-ks: Don't know, sorry. :/ [21:16:59] polybuildr : That's okay [21:17:10] Thanks for the help so far :) [21:20:16] hey finding some weird behaviour on mw 1.25.1.. some extensions are suggesting that i use wfLoadExtension() but this seems to give me php errors, while the old method of requiring the extension's php file works :/ [21:20:23] for example, Nuke and PdfHandler [21:31:14] PJosepherum: what PHP errors are you getting? [21:38:40] ankita-ks: I think you have found a bug in VE [21:38:46] legoktm http://hastebin.com/hefalaqiqu.tex [21:38:49] There's an undeclared dependency [21:39:02] Wait, no [21:39:04] It is declared [21:39:06] wtf [21:39:13] RoanKattouw : where? [21:41:06] I'm puzzled [21:41:11] It depends on all the right things [21:41:30] looks like it's calling require_once('/var/www/html/w...') instead of the correct folder [21:42:10] ankita-ks: Can you reproduce this bug in Chrome with the inspector open? That'll cause the debugger to jump to the failure [21:42:22] (oo hastebin is nice) [21:42:33] If you open VE while the inspector is open, the debugger should activate and jump to the line where it goes wrong [21:42:41] Okay [21:42:52] I have the inspector open. [21:43:23] Oh, sorry, I see you're also talking in #mediawiki-visualeditor , let's move there [21:43:43] PJosepherum: umm, is there an "extension.json" file in the PdfHandler folder? [21:43:55] RoanKattouw : okay [21:47:00] no just seen that in the log also [21:47:24] pulled it from git. same issue appeared with nuke [21:47:36] are you sure you got the 1.25 branch? [21:47:57] https://github.com/wikimedia/mediawiki-extensions-Nuke/tree/REL1_25 definitely has a extension.json in it [21:48:15] https://github.com/wikimedia/mediawiki-extensions-PdfHandler/tree/REL1_25 same here [21:51:09] ah yeah, weird. git pull said it was up to date, but missing a ton of files