[01:03:30] heya guys... i upgraded my mediawiki install to the current version, and now i have an odd error... i'm not sure what to make of it: http://starfoxwiki.info/wiki/Lylat_Wiki [01:52:22] helo? [01:57:39] hi [02:45:50] i've been getting odd errors on my mediawiki install: http://starfoxwiki.info/wiki/Lylat_Wiki [02:47:30] what are the errors? [02:52:23] i have no idea... that's why i cae here [02:52:24] *came [02:53:08] what is the actual thing that you are seeing on that page? [02:53:24] is it a picture of a camel? [02:54:18] no, supposed to be a starfox-themed wiki [02:55:16] because it looked to me like it actually was a starfox-themed wiki [02:55:53] that's why I'm asking you for the exact text of the error messages that are troubling you [02:57:12] Strict Standards: Declaration of GadgetResourceLoaderModule::getDependencies() should be compatible with ResourceLoaderModule::getDependencies(ResourceLoaderContext $context = NULL) in /home/starfoxw/public_html/w/extensions/Gadgets/Gadgets_body.php on line 421 [02:57:13] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: ext.echo.badge ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /home/starfoxw/public_html/w/includes/OutputPage.php at line 623] in /home/starfoxw/public_html/w/includes/debug/MWDebug.php on line 300 [02:57:13] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: ext.gadget.ReferenceTooltips GadgetResourceLoaderModule [Called from OutputPage::getModuleStyles in /home/starfoxw/public_html/w/includes/OutputPage.php at line 623] in /home/starfoxw/public_html/w/includes/debug/MWDebug.php on line 300 [02:57:19] that's the stuff that pours out... not sure why [03:00:17] you can't load the CSS extension via wfLoadExtension('CSS'), because it has not been updated for the new extension registration / loading mechanism. You need to replace that line (line 155 in /home/starfoxw/public_html/w/LocalSettings.php) with: require_once "$IP/extensions/CSS/CSS.php"; [03:01:27] ditto for the Variables extension [03:01:38] ...and PatrolledEdits :) [03:02:34] legoktm: have you considered making wfLoadExtension( 'foo' ) default to loading $IP/extensions/foo/foo.php, if extension.json is missing? [03:03:14] i tried switching everything to wfloadextension thinking that woudl fix it [03:03:18] well,t aht was a failure [03:03:19] so i'm reverting the cahnges [03:03:23] not sure why the wiki is acting up [03:03:28] upgraded fro 1.25.3 to 1.26.1 [03:03:45] what is "it", that you were hoping the change would fix? the warnings? [03:04:00] yes [03:05:14] therew e go. back to normal [03:05:16] well, the new normal [03:05:37] add $wgShowExceptionDetails = true; to LocalSettings.php [03:05:59] ok [03:06:01] http://starfoxwiki.info/wiki/Special:Version [03:07:05] that's another extension you can't load via wfLoadExtension [03:07:26] oh for fuck's sake [03:07:37] ..and another [03:07:40] yeah [03:07:52] let me fix this [03:09:02] the warnings are included in the HTML because of the value you set for PHP's error reporting level [03:10:51] there are several places where you may be setting it. do you see calls to error_reporting( ) or ini_set( 'display_errors', ); in LocalSettings.php? [03:11:35] hold on, winscp is locking pu [03:11:36] *up [03:12:03] there may also be an .htaccess file in /home/starfoxw/public_html with "php_value error_reporting " [03:12:32] ok [03:12:42] there's also php.ini, but i'm guessing you don't have access to that [03:12:48] no htaccess [03:12:50] oh i have root access [03:13:13] # Display detailed information about server errors [03:13:13] error_reporting( E_ALL | E_STRICT ); [03:13:13] ini_set( 'display_errors', 1 ); [03:13:14] ini_set( 'display_startup_errors', 1 ); [03:13:18] taht's in LocalSettings.php [03:14:47] comment out the error_reporting line [03:15:22] (that is, prefix it with '#') [03:15:55] i' rather fix errors than ignore them :) [03:16:42] I'm not entirely sure what problem you are trying to fix, then [03:17:05] hmm [03:17:36] yeah, commenting it out does nothign [03:18:33] you need to undo the breakage you introduced by trying to use wfLoadExtension() with legacy extensions [03:19:00] already did [03:19:05] http://starfoxwiki.info/wiki/Special:Version gives an error too [03:19:32] but you took out $wgShowExceptionDetails = true; [03:19:51] [ac3be432] 2016-05-06 03:19:42: Fatal exception of type "MWException" [03:19:53] yes [03:20:38] add it back, so we know what the exception is [03:20:44] already did [03:20:48] removnig it changed nothing [03:21:04] [77b0991d] 2016-05-06 03:20:52: Fatal exception of type "MWException" [03:21:13] add it to the top of LocalSettings.php [03:21:18] if you added it to the bottom, move it up [03:21:41] now at the top, just below the [0e6f82b7] /wiki/Special:Version MWException from line 40 of /home/starfoxw/public_html/w/extensions/TrustedXFF/TrustedXFF.body.php: TrustedXFF: hosts file missing. You need to download it. [03:22:00] hmm, trustedXFF [03:22:01] yeah [03:22:25] copying [03:23:02] that file's there [03:23:05] not sure why it's bitching [03:23:35] run: [03:23:49] cd /home/starfoxw/public_html/w ; php extensions/TrustedXFF/generate.php --conf LocalSettings.php [03:25:00] cannot find generate.php [03:25:07] *cannot open generate.php [03:25:19] ok, remain in the same directory, but run: [03:25:28] i'm in trustsedxff's directory [03:25:49] just run this, from whereever: curl https://noc.wikimedia.org/conf/trusted-xff.cdb -o /home/starfoxw/public_html/w/cache/trusted-xff.cdb [03:26:28] oy, that'sway more painful than it needs to be [03:26:29] yay [03:27:34] yes [03:28:04] the version of the Gadgets you are using is out of date, I think [03:28:34] if you update it to the latest version, those warnings should go away [03:28:38] i'm just using the version that came bundled with 1.26.2 [03:28:39] ditto the monobook skin [03:28:48] i'll try to update the [03:28:50] *them [03:28:50] hrm [03:29:55] you should probably remove $wgShowExceptionDetails = true; now [03:30:22] we enabled it so we could figure out why mediawiki was throwing an exception [03:30:40] now that it's loading, you should take it out. it's off by default because exception details are liable to contain sensitive information. [03:30:43] loading now [03:30:53] most of the errors are gone! [03:31:07] yeah, just the monobook ones remain [03:31:57] down to just two errors now [03:32:09] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: ext.echo.badge ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /home/starfoxw/public_html/w/includes/OutputPage.php at line 623] in /home/starfoxw/public_html/w/includes/debug/MWDebug.php on line 300 [03:32:09] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: ext.echo.badge ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /home/starfoxw/public_html/w/includes/OutputPage.php at line 623] in /home/starfoxw/public_html/w/includes/debug/MWDebug.php on line 300 [03:32:53] you may be able to make that go away by upgrading Echo, but I really wouldn't, because [03:33:23] that warning is there to nag developers into fixing their code so that it's compatible with future changes [03:33:42] echo? [03:33:43] mediawiki will do the right thing in this case, the warning is of no consequence to you [03:33:57] yes, ext.echo.badge is part of the Echo extension [03:35:14] you could upgrade Echo, or you could change the error reporting line in your LocalSettings.php so it suppresses warnings [03:35:21] by changing it to error_reporting( E_ERROR ); [03:35:36] i'd recommend suppressing the warning rather than trying to upgrade the Echo extension [03:35:50] THERE we go [03:35:59] wait, i upgraded echo... [03:36:01] why is that a bad thing? [03:36:16] it's fine if you did and it works [03:36:24] I was just worried you'd run into another set of compatibility issues [03:36:32] it looks like you haven't, so good [03:37:22] still, thank you so uch for helping me with these issues [03:37:44] you're welcome! I have to get going, bye [03:39:24] be safe [06:25:21] ori: unfortunately that wouldn't work because the PHP entry points expect to run in global scope and that would put them in function scope [06:45:51] legoktm: there has to be some way around that. For example, wfLoadExtension() could add "$IP/extensions/foo/foo.php" to some global array, and file-scope code in Setup.php could iterate on that and load each file [06:46:24] hmm, that's actually a really good idea. [06:47:39] Hi all. I am editing a wiki right now (own mw installation). One of my entries after a h3 tag wont be rendered inside a paragraph. Is this a bug? [06:47:47] if you want to preserve load-order for both new (extension.json) and old extensions you would have to load all extensions in that Setup.php code [06:48:20] so in both cases (old and new) wfLoadExtension() should add an item to a load queue, rather than actually load [06:48:46] that probably won't work [06:49:07] ori: we'd run into the issue that ExtensionRegistry has code designed that config is loaded before the extension info is, while PHP entry points rely on them being loaded before config [06:49:14] yep [06:49:25] yeah, that's a fatal flaw [06:49:25] sucks [06:50:06] TridenRake: hi, I'm not really sure what you mean. Can you pastebin the wikitext that's not working? [06:50:59] legoktm, I'll annotate the issue and paste a imgur link, so that you cud get a better idea. :) Be back in a moment! [06:53:48] legoktm, http://i.imgur.com/wMqwjC7.png [06:54:30] hm, does your wiki have tidy enabled? [06:54:35] and can I see the source wikitext? [06:56:07] legoktm, http://pastebin.com/gwKn3v9g [06:56:24] legoktm, Tidy? Is that an extension? [06:57:23] !tidy [06:57:23] HTML Tidy is an external application that cleans up HTML for XHTML compliance (such as bad user input like
). Prior to the new preprocessor in 1.12 it was also needed for distributed, transcluded, or conditional HTML, or mixed HTML and wikitables, but newer versions allow it without Tidy. See [06:57:52] legoktm, I will enable tidy and let you know if this changes. :) [06:58:18] after you enable tidy, make sure to null edit the page so it reparses [07:00:28] legoktm, I am not sure how to use $wgTidyConfig. Sorry, I am not that good with MediaWiki. [07:00:57] Following this - https://www.mediawiki.org/wiki/Manual:$wgTidyConfig [07:00:59] what version of MW are you using? [07:01:10] 1.26. The latest build. [07:01:39] just add $wgUseTidy = true; to your LocalSettings.php for now [07:01:43] that should be good enough [07:02:35] (I'm not actually sure this will solve your problem, so I don't want you to spend too much time trying it out...) [07:03:06] Yeah. In a minute.. :) Will check it in a flash! [07:04:24] legoktm, it's fixed now. But I see that this is deprecated. Is that okay? [07:04:25] Hello people. [07:05:09] I have a little question: how to print error message with $status->fatal() in Hook? [07:06:19] Im using $status->fatal($message) but it just prints the raw text outside of

MESSAGE [08:27:13]

" -- is what i have [08:27:45] why do you need that structure? [08:28:59] I need

MESSAGE

, but i have

MESSAGE

[08:32:57] yes but *why* do you need that? [08:35:24] I just need to show error message ;P If you know another way please give it to me. [08:35:47] I don't, sorry. [08:35:58] if I understood your usecase better, I might be able to suggest something else [08:36:12] But I have to go sleep now anyways, bye o/ [08:37:55] okay. Im coding extension. So in Hook I have to check special permission and if it FALSE i have to cancel operation (with given $status) & display error message [08:38:12] legoktm, ciao! [08:38:22] thanks 4 trying ) [09:22:53] Hello people. Does anyone khow why $status->fatal(wfMessage("message")) produces

MESSAGE

instead of plain text? [09:35:06] So far, OutputPage::getHTML(), nor $mBodytext actually returns the body of the page with the onBeforePageDisplay hook [09:35:48] Just returns the article, but the documentation on it is misleading saying it return all inside the tag [11:30:14] Ah, it seems that the skin is the last handler of outputting data to the request, I don't think its possible to hoot into the entire output of a page, has to be an API request, but that doesn't work for my use case :\ [12:03:04] Hello people. Does anyone khow why $status->fatal(wfMessage("message")) produces

MESSAGE

instead of plain text? [12:04:36] Serge: wfMessage( 'message' ) gets cast to a string, and that calls ->parse() [12:04:44] you should always specify the output format [12:05:43] ->plain() produces

..

too :-( [12:35:53] Serge: well it could be that whatever formats the Status output outputs html [13:37:42] The AJAX example given on this page https://www.mediawiki.org/wiki/Manual:CORS doesn't work. https://jsbin.com/surele/edit?js,output What am I missing ?? [13:56:51] morning [13:56:59] evening [13:59:57] howdy Nikerabbit [14:00:24] going out to enjoy the weather [14:09:49] wish i could say the same [14:58:20] is the mwf meeting happening on IRC or somewhere else? [18:17:16] Hello. Does anyone know how you can obtain page view statistics in 1.26.2? [18:21:09] spelledgeary, https://www.mediawiki.org/wiki/Extension:Google_Analytics_Integration or https://www.mediawiki.org/wiki/User:Dantman/Analytics_integration [18:22:34] You can use Google Analytics to query most popular pages, like you could previously with Mediawiki? [18:23:54] spelledgeary, maybe https://www.mediawiki.org/wiki/Extension:HitCounters ? [18:25:42] thanks for the suggestions, HitCounters has major issues with 1.26 [18:26:00] andre__, "A fresh install in MW 1.26 and higher is not possible!" [18:26:16] argh [18:28:20] We didn't realize the stats had been removed until after the install. I assume you could run mySQL queries to obtain the info though? [20:19:09] Hi guys, I need help setting up MW on my omeka site, anyone has some exp with that?? [20:20:33] ANYONE CAN ASSIST WITH THAT? [20:24:14] Mario_: what do you need help with? [20:26:18] I have installed MW on a omeka site and gave Apache all the required permissions (same as site permissions) then when I go to xxxx/omeka/site/wiki/ and i get 404 Page not Found [20:27:50] What is the name of the MediaWiki directory - /w ? [20:27:52] Yaron_ let me know what you think [20:28:37] var/www/html/omeka/sitename/wiki/I unpcket everything here [20:28:46] you have all the installation under wiki/ [20:30:07] What happens if you go to "xxxx/omeka/site" - do you see the right thing there? [20:30:28] that is my site and it works fine [20:31:06] Alright.... what if you go to xxxx/omeka/site/wiki/index.php - also a 404? [20:31:13] I want to install WM for in my omeka site that uses SCRIPTO (a pluging that requires MW) [20:31:31] Yes I tried .index.php and same thing [20:32:23] Alright - that's strange. I don't know what's causing that; maybe someone else does. [20:32:26] 404 Page Not Found /omeka/sitename/wiki/index.php is not a valid URL. [20:35:00] Thanks[YARON] [20:35:05] Any one else [20:35:06] ?? [22:29:16] heya guys.... having more issues with mediawiki 1.26.2.... the skins stopped working and now throw errors: http://www.starfoxwiki.info [22:30:55] if you're using git as oposed to the tarball, the skins are in their own repos and need to be updated separately [22:30:56] is your monobook up to date with 1.26 brnch? [22:31:49] yes [22:31:56] i'm using the tarballs [22:32:04] 1.26 seems incredibly buggy for a final release [22:32:46] if it was, WP/WM wouldn't use it - something must be wrong somewher [22:33:45] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: skins.monobook.styles ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /home/starfoxw/public_html/w/includes/OutputPage.php at line 623] in /home/starfoxw/public_html/w/includes/debug/MWDebug.php on line 300 [22:33:45] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: skins.monobook.styles ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /home/starfoxw/public_html/w/includes/OutputPage.php at line 623] in /home/starfoxw/public_html/w/includes/debug/MWDebug.php on line 300 [22:33:46] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: skins.monobook.styles ResourceLoaderFileModule [Called from OutputPage::getModuleStyles in /home/starfoxw/public_html/w/includes/OutputPage.php at line 623] in /home/starfoxw/public_html/w/includes/debug/MWDebug.php on line 300 [22:33:47] have you edited the monobook skin at all? [22:33:51] no [22:33:58] WMF uses master snapshots, which means that precisely the tarball code was never run in our prod [22:34:12] what is on line 300 of that file? [22:34:39] ilera, a trigger_error() call :P [22:34:56] $msg .= ' [Called from ' . $caller['func'] . ' in ' . $caller['file'] . ']'; [22:34:59] that's line 300 [22:35:12] so you guys put out one code for everyone else and use another? [22:36:10] we deploy weekly, so release versions aren't used because by the time of release servers are already running a next version alpha [22:36:55] hmm. i put the newest skin skins folder in over the old one and the errors go away [22:37:01] but.. so do my logo, background, and text colours [22:38:39] so it sounds like you customized the skin by editing the source code rather than using on-wiki css [22:38:45] which is a horrible idea [22:38:52] oh thatwasn't me. that was the project head [22:39:00] in which case, i'll tell him to edit the on-wiki CSS stuff [22:39:01] because it means you can't update properly [22:39:22] i know [22:40:09] Mediawiki:Common.css, if i recall, right? [22:40:13] note that vanilla REL1_26 monobook shouldn't have this error [22:41:34] yes [22:42:03] hence my "[15:30:56] is your monobook up to date with 1.26 brnch?" [22:42:34] great now it's bitching about cookies [22:42:38] can't log in [22:43:32] Login error [22:43:32] Lylat Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again. [22:45:29] check if wherever you store cookies works [22:45:37] i don't know where that is [22:45:45] ie if in memcached, it should be up and configured [22:45:58] if in tmpfs somewhere, check file perms [22:46:21] tmp is 777 [22:46:26] i mean /tmp [22:49:37] well, fuck i have no idea what's going on [22:49:57] 1.26 is buggy as shit and even wikipedia.org throws errors half the time... you guys really did NOT think this version through.. [22:50:36] wp is running 1.27 and will have 1.28 next week ;) [22:50:40] I've been running it without issue [22:50:44] so, *shrug* [22:50:46] and i will not be upgrading to those [22:51:13] well, good luck with Confluence :P [22:51:13] i need to be able to log in again [22:51:17] what's that? [22:51:21] a different wiki [22:51:31] it sucks [22:51:36] so does Dokuwiki [22:51:44] starting to think movnig from wikia was a bad idea [22:52:09] can you guys help me log back in to my wiki? [22:52:25] anyway, I see you're on NIWA, so if hosting the wiki is difficult, I'd recommend hitting up other members to see if they'd be willing to host it for you [22:52:31] what di you do to make this happen? [22:52:51] i upgraded from 1.25.3 to 1.26.2 and i was in the process of upgrading the extensions to the latest version since theyw ere all relatively out of date [22:53:03] we're all on the same server running 1.25.3 (except for the lylat wiki) [22:54:08] anyway [22:54:19] did you run the update script? [22:54:21] it was woring for a half hour after iupdated the first three extensions, then started fraeking out [22:54:23] php update.php? [22:54:26] yep [22:54:28] after i ugraded the wiki, yes [22:54:30] should i do so again? [22:54:42] yeah, som extensions you had may need updates too [22:54:52] i was in the process of updating them in threes [22:54:58] stopped to eat dinner... [22:55:01] came back, they were fine... [22:55:08] update.php updates both the base wiki as well as any extensions [22:55:11] re-freshed a few more times, thigns started fucking up [22:55:30] running now [22:56:03] nope, logo and text colours are missing and i still can't log in [22:56:11] clarification: update.php updates the DB schema [22:56:20] it doesn't update extension code :) [22:56:27] i know. that's what i was doing [22:57:17] I'm getting a 404 for the background and logo [22:57:24] it seems you may have deleted the files [22:57:45] what is the link for the 404 error? [22:57:57] i deleted nothing [22:58:16] check your browser console [22:58:38] i am [22:58:40] i'm not seeing anything [22:58:44] post for me please? [22:59:19] do you mean /w/LWLogo.png ? that's there! [22:59:22] http://starfoxwiki.info/wiki/W/Starfield.png [22:59:23] it has not changed its spot [22:59:37] is the address it's trying to load [22:59:48] if that doesn't look right (it doesn't to me), check your paths in LocalSettings.php [22:59:49] i swear to fuckign god if the project head deleted them, i'm fucking done [23:01:04] yeah /home/starfoxw/www/w/LWLogo.png is present and accounted for [23:01:07] not sure where Starfield.png went [23:02:10] copied starfield from a backup [23:02:21] well [23:02:25] it's trying to load the wrong URL [23:02:27] yet it still won't load [23:02:31] what url is it trying to load? [23:02:47] I just pasted it [23:02:49] $wgLogo = "$wgScriptPath/LWLogo.png"; [23:02:53] that's what LocalSettings.php has [23:02:55] note how it has /wiki/ in it [23:02:57] ok [23:03:03] so it sounds like your rewriterules are messed up [23:03:19] wait, now it's working [23:03:20] hmm [23:03:25] schizophrenic software? [23:03:38] congrats, mediawiki.. you made the first sentient AI... and it needs lithium :P [23:03:39] I think you restoring the files fixed it [23:03:57] I now get the background and logo [23:04:03] although monobook itself is still very white [23:04:04] same here now [23:04:11] idk if that's intended or not [23:04:18] fuck.. still gotta log in [23:04:27] also the main page keeps giving me Slippy every other load [23:04:32] yeah, it happens [23:04:55] why is it so weighted towards Slippy though? :P [23:04:58] i wish i knew [23:05:02] i hate that annoying little fuck [23:05:04] prefer falco, myself [23:05:39] still can't log in [23:05:41] no cookies [23:06:39] i don't know what to check or where to fix this [23:08:43] php's session.save_path [23:08:47] probably [23:09:23] how would i figure out where THAT is? [23:15:56] ok [23:16:00] so, the session ssave path is /tmp [23:16:02] i just cleared that out [23:16:12] it's writable to everyone to store their temp files in [23:16:15] so what is going on? [23:31:12] well fuck it [23:37:38] is this your way of tryign to get people to stop using mediawiki software?