[03:00:31] is there a way to hide a page unless a password is known? [03:00:44] http://rdsonline.org/index.php?title=Troubleshooting [03:00:48] i want this hidden heh [03:14:46] guess its late, sorry [03:27:24] what is this? [03:32:25] a channel ;) [03:44:15] Bitgod, https://www.mediawiki.org/wiki/Manual:Preventing_access#Restrict_viewing_of_certain_specific_pages generally not recommended [04:06:31] ty [04:06:37] well its recommended for us [04:06:40] :) [05:58:51] saw the upgrade announcement, after applying the patch, I get: PHP Parse error: syntax error, unexpected '[' in ..../wiki/includes/Title.php on line 2283 [05:59:05] patch from 1.23.15 to 1.23.16 [06:03:18] sounds like a bug Erkan_Yilmaz [06:03:48] yeah, I am just getting the new 1.23.16 tar.gz to see what the diff between this patched file and the new archive is [06:04:36] it's because the backported patch uses short array syntax, and you are using an old version of PHP [06:05:00] 1.23 theoretically supports older versions of PHP, but evidently that was forgotten when the backport was done [06:05:06] oh [06:05:23] Required software: [06:05:23] * Web server with PHP 5.3.2 or higher. [06:05:28] which you presumably have [06:05:47] but MW master requires 5.5.9 [06:06:21] right [06:09:45] do you want a workaround? or should I just file a bug in phabricator? [06:15:32] for me workaround, later you can file a bug ;-) [06:16:58] has been 9h since the announcement, probaly not so many 1.23 users or all are still sleeping [06:19:05] wow, not even any composer.json in 1.23 [06:19:13] the world has changed since then... [06:20:24] and no phpcs.xml [06:22:21] sounds like it will take longer [06:23:02] phpcs has this magic feature where it changes all the short arrays to long arrays, or vice versa [06:26:10] Queen song: "it's a kind of magic" :-) [06:30:10] I did this one by hand, Erkan_Yilmaz: http://paste.tstarling.com/p/hSCDGi.html [06:30:24] can you try applying it with patch -p1 [06:30:31] clicks [06:30:35] yes, I will try [06:31:08] and then if you're feeling charitable, please run this command from the base directory of the installation: find -name \*.php -exec php -l {} \; | grep -v 'No syntax errors' [06:31:27] to save me from figuring out some other way to automatically search for these [06:34:20] wiki loads again, thx [06:34:54] running the find command [06:35:57] - - - [06:35:58] PHP Parse error: syntax error, unexpected T_PRIVATE in ./includes/libs/XmlTypeCheck.php on line 364 [06:35:58] Errors parsing ./includes/libs/XmlTypeCheck.php [06:36:01] still runs [06:36:27] done, those 2 lines are all [06:38:11] thanks [06:38:46] thank you for the dirty hack :-) [06:46:28] I tried running XmlTypeCheck.php on 3v4l.org, couldn't reproduce your error [06:46:53] it seems to work back to PHP 5.0.0 [06:47:25] also on line 364 there should be a comment, not T_PRIVATE [06:47:34] so maybe you have a conflict marker there or something [06:52:36] let me check [06:53:43] line 364: private function DTDHandler( XMLReader $reader ) { [06:53:50] line 363: */ [06:54:50] can you just cat the whole file and pastebin it? [06:56:12] http://paste.tstarling.com/p/QThmkn.html [06:57:44] I doubt it is your fault Erkan_Yilmaz [06:58:11] in git the file does not look like that, but I'm pretty sure the tarballs were made from a local copy, prior to the git merge [06:58:22] so maybe the tarball is wrong [06:58:33] ok [06:58:48] in the previous function, processingInstructionHandler, second nested if() is unclosed [06:59:46] here's the correct file: http://paste.tstarling.com/p/KnAQZq.html [06:59:53] gtg [07:19:33] thx TimStarling [07:19:41] I don't get anymore errors with: "find -name \*.php -exec php -l {} \; | grep -v 'No syntax errors'" [08:07:38] Oh hai [08:08:03] I just cant seem to be able to find any examples of how to do inline linking of external images.... do you know any? [08:35:20] sybariten, what is "inline linking"? [08:35:25] embedding? [08:42:25] andre__: exactly! You're embedding an image that is hosted somewhere else [08:42:28] When i set the format to computer code, it doesnt seem to be surporting computer code that has line breaks, each line has its own computer code box [08:42:40] you never actually upload it uourself, youre only referencing the images URL [08:42:42] Im using latest visual editor, can anyone help? [08:43:21] sybariten: https://www.mediawiki.org/wiki/Help:Images#Files_at_other_websites [08:45:02] andre__: thanks, but "With these syntaxes, the image will not be rendered" ... ? [08:45:37] I assume computer code format should support multiple lines with line breaks? [08:45:57] sybariten, did you read further? [08:46:42] andre__: yes... ? I really cant see it [08:46:58] sybariten: "If it is enabled on your wiki (see Manual:$wgAllowExternalImages), you can also embed external images." [08:48:05] NOW i saw it [08:48:22] Mustve read that part ten times and missed it... sigh [08:50:20] andre__: ok how about something like this then, which is what i really wanted to use... not sure what to call this example, but its what google gives ya https://pastebin.com/v8Z0U25x [08:52:13] some access restricted URL that noone can access without having permissions [08:57:38] andre__: hm? The URL i linked/pasted shouldnt need permissions.... [08:57:43] gotta go a couple of hours! [08:58:41] sybariten, it does not permissions. [08:58:46] errr need, not not [08:59:03] try in your own private browser window and see. [09:06:21] Also under Insert menu, CodeBlock does not appear, anyone know why not [09:09:15] CookieMonster__, what does your error console of your browser's developer tools say? [09:10:56] andre__: What when I go to edit the page and VE doesnt show the CodeBlock option under insert? [09:12:50] oh, looks like extension syntaxhighlighter is required for codeblock [09:18:39] andre__: I have now enabled SyntaxHighlight_GeSHi, and when i save the page with the code block in it, it saves correctly, but when editing in VE, code block does not display correctly [09:53:12] How can I tell is pygments is running on windows? [11:17:23] andre__: im so stupid, i know why .. i used a so called google for business account, i have a couple of other "normal" google accounts, i should use those instead [11:42:54] andre__: hopefully this is a link thats more accessible https://pastebin.com/cxZNd4b3 [13:22:00] is there seriously noone here that can help me [13:42:28] CookieMonster__: depends on the question [13:42:42] what do you need? [13:59:07] MatmaRex: Appologise, having a bit of a stressful day [13:59:44] MatmaRex: I've added wfLoadExtension( 'SyntaxHighlight_GeSHi' ); to localsettings.php, and in visual editor I can now select Code Block, but I dont think its working [14:00:58] MatmaRex: I select my code type, type in the code and click Done button, but then it adds it to the visual editor page as: Select * From Log [14:01:14] I'd presume the bundled pygments wouldn't work on windows [14:01:16] MatmaRex: Would you be able to help? [14:01:53] Reedy: I have installed python27, pip, and installed pygments, confirmed that one runs outside of mediawiki [14:02:06] Did you change the path that MW is using for pygments? [14:02:21] $wgPygmentizePath [14:02:36] Reedy: so I set $wgPygmentizePath = "C:\\Program Files (x86)\\Python27\\Scripts\\pygmentize.exe"; [14:03:03] Reedy: which is where pygmentize.exe is [14:04:08] Reedy: does SyntaxHighlight_GeSHi have any kind of debug log? [14:04:30] Reedy: MediaWiki Debug log isnt telling me anything in regards to this issue [14:04:33] CookieMonster__: hmm. if you save a page with that, does it render correctly after saving? [14:04:51] (do you see the problem in read mode, or only inside VisualEditor?) [14:04:51] MatmaRex: Yes it does, it just doesnt in Visual Editor [14:05:37] CookieMonster__: then it seems that SyntaxHighlight and Pygments both work just fine. but either VisualEditor or Parsoid has problems contacting your wiki's API to render the preview [14:05:46] MatmaRex: Oh sorry I mean yes the text displays in the code box window correctly without the tag start and end, but it doesnt colour the text at all [14:06:04] oh. hm [14:07:33] When in VE I see " Select * From Log " in the code block with no text colouring, when i save changes, on the page I see "Select * From Log" in a code block with no text colouring, and if I do multiple lines, then each line is in its own code block instead of all in one code block [14:07:55] does SyntaxHighlight_GeSHi have any kind of debug log? [14:08:27] no idea :/ [14:08:35] and i get "syntaxhighlight-error-pygments-invocation-failure" [14:09:34] !debug [14:09:34] For information on debugging (including viewing errors), see http://www.mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://www.mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging [14:09:38] When adding code block selecting show line numbers does nothing too [14:09:42] if ( !$process->isSuccessful() ) { [14:09:42] $status->warning( 'syntaxhighlight-error-pygments-invocation-failure' ); [14:09:42] wfWarn( 'Failed to invoke Pygments: ' . $process->getErrorOutput() ); [14:09:50] sounds to me like SyntaxHighlight_GeSHi extenstion isnt running [14:09:55] also [14:09:56] if ( wfShellExecDisabled() !== false ) { [14:09:56] $status->warning( 'syntaxhighlight-error-pygments-invocation-failure' ); [14:09:56] wfWarn( [14:09:57] 'MediaWiki determined that it cannot invoke Pygments. ' . [14:09:59] 'As a result, SyntaxHighlight_GeSHi will not perform any syntax highlighting. ' . [14:10:01] 'See the debug log for details: ' . [14:10:03] 'https://www.mediawiki.org/wiki/Manual:$wgDebugLogFile' [14:10:05] ); [14:10:10] The extension is running [14:10:12] pygments isn't [14:10:25] I have the debug log but isnt telling me anything about this issue [14:10:42] Reedy: so is this the same ready why line numbers wont go on the code block? [14:11:33] I have $wgDebugLogFile = "C:\\inetpub\\wwwroot\\wiki\\log.log" and the log file populates but it doesnt mention Pygmentize [14:15:55] !pastebin | Reedy [14:15:55] Reedy: To avoid overflowing the channel with inane amounts of text, use https://dpaste.org or https://phabricator.wikimedia.org/paste/edit/form/14/ or other awesome pastebin sites to share code, errors, and other large texts. [14:16:02] effort [14:16:35] Reedy: Surly because nothing is going in the log it shows the extension is not running? [14:16:48] [15:08:35] and i get "syntaxhighlight-error-pygments-invocation-failure" [14:16:51] If the extension wasn't running [14:16:53] You wouldn't get that [14:16:56] Check Special:Version [14:17:22] Sorry I got confused, thats on my other server, not this one that I have the problem on [14:17:31] ignroe that line, and il check special:version now [14:18:17] Yes it is in Special:Version : SyntaxHighlight [14:19:02] And when I loaded special:version the log has: Getting VCS info for extension SyntaxHighlight [14:19:05] and two other lines [14:21:18] I think theres something wrong with the extension, I click save changes and it wont save now, the log keeps on and on until i refresh my page [14:36:21] is this: "[session] SessionBackend "8kpsqof6pmh88kuahd19ekhjheqhr620" is unsaved, marking dirty in constructor" bad? [14:36:49] or "[session] SessionBackend "8b1qp2grt0jcfu18e4j7n13vvve3b8dv" data dirty due to addData(): call_user_func_array/MediaWiki\Session\SessionBackend->MediaWiki\Session\{closure}/MediaWiki\Session\SessionBackend->save/MediaWiki\Session\CookieSessionProvider->persistSession/MediaWiki\Session\SessionBackend->addData" [14:41:55] Reedy: Are you there? [14:56:21] Can anyone help with SyntaxHighlight_GeSHi causing an endless hang, mediawiki log constantly looping until user refreshes page or closes browser [15:22:20] Can anyone help with SyntaxHighlight_GeSHi causing an endless hang, mediawiki log constantly looping until user refreshes page or closes browser [15:23:37] Hi ashaman [15:26:40] Hi ikcerog [15:43:20] CookieMonster__, the network tab of your web browser's developer tools might show you if a file fails to load. [15:55:32] andre__: fixed that now, but im getting "Pages with syntax highlighting errors" category going onto the page now? [15:55:44] yeah? [15:56:07] andre__: any idea what might be causing it? I cannot see anything in mediawiki debug log [15:57:11] !debug [15:57:11] For information on debugging (including viewing errors), see http://www.mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://www.mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging [15:57:15] and $wgDevelopmentWarnings [15:57:24] andre__: Oh wait think I have it working... Just going to retest. [15:58:31] andre__: it almost fully works now, the only problem I have now, is that when I edit page that had code block, visual editor shows " Select * from log " instead of "Select * from log" in a code block [16:22:50] Reedy or andree__ ? [16:34:41] CookieMonster__: try instead of [16:35:57] CookieMonster__: hm, on wikipedia, both work for me. maybe your version of VE doesn't support code blocks yet. [18:35:31] I've got a quick question if someone has a moment to help with a wikimedia install? [18:35:57] you mean a mediawiki install ;) [18:36:06] Oh, yes. Indeed [18:36:26] I am attempting to log in with the sysops account. [18:36:30] What sets that password? [18:36:44] Fresh install, something auto created the user [18:36:53] I am trying to edit the logon screen, I have completed a SSO extension, and I need to remove the password help line and the box that say Keep Me logged in, anyone have an idea where I need to look? [18:37:40] Tenakwa, Durring the installation script, you gve it the password [18:38:28] Huh, Okay its been a month. One sec [18:38:46] I am getting the error "There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Go back to the previous page, reload that page and then try again." [18:39:14] During creation the script created the sysop and your account, both should have the same rights [18:40:02] do you have more than one window open to the same site? [18:40:24] it's the lovely session bug again [18:40:28] tenakwa: What version of MediaWiki? [18:42:02] It should be the most recent as of the 4th of Feb [18:42:08] Im trying to look it up [18:42:15] visit Special:Version on your wiki [18:43:06] Thanks, its 1.29.0-alpha [18:45:18] Is this a dev wiki? [18:45:27] update mediawiki or roll back to the latest stable version [18:45:29] Either way, I'd reccommend updating your install [18:46:09] Its a wiki where I have very little idea what I am doing [18:46:24] I see that I accidently pulled in an alpha from git [18:46:41] How do I 'update'? [18:47:15] pull from git again [18:47:27] run the upgrade.php maintenance script just in case there were any db changes since then [18:48:06] update.php [18:50:21] Just to make sure that I understand. In the /var/www/html/ directory I do git clone [18:50:34] No [18:51:15] jhuff05: On older versions of MediaWiki, I think it's the UserLoginForm hook you want. But that says "DEPRECATED! Create an AuthenticationProvider instead." [18:55:24] That is what I have done, but it looks like there are some "Left overs" that don't go away with setting their properties to off... [18:56:38] tenakwa: are you comfortable with using git? If no, using the stable versions may make more sense [18:57:18] the alpha versions benefit from a much more aggressive update cycle, which means you'll need to stay on top of updates more [18:57:31] (and potentially rolling things back if stuff breaks) [18:58:44] if you want to use the alpha versions, updating is easy: change directories to your mediawiki directory and then run 'git pull' [18:58:52] then 'php maintenance/update.php' [19:00:20] if you want to switch to the stable versions, you could either do that with git as well (using 'git checkout' to switch to a stable branch), or you can delete all of the files (save your LocalSettings.php though), download the tarball for 1.28.1, extract it, then put your LocalSettings.php back in there