[07:39:05] Hi. I am just wondering if there's equivalent extension of "DisableSpeciaPages" for MWv1.26? [07:39:28] I just need an extension to hide special pages [07:39:30] what special pages do you want to disable? [07:39:47] p858snake: several special pages [07:40:16] there may be other ways to do it dependong on what pages you want to disable [07:40:51] such as [07:43:47] this is really works on my MW 1.17 but after I upgraded to 1.26, it doesn't work anymore -- https://www.mediawiki.org/wiki/Extension:DisableSpecialPages [07:45:52] to be honest, unless you really need it for some bizzare reason, there isn't much point in disabling special pages [07:47:48] yeah but the reason is to avoid showing up special pages for anonymous users [07:48:17] why? they don't reveal anything that the anon users don't already have access to [07:48:57] you are just making it harder for people that knowledge in mediawiki to use your wiki [07:49:13] because i want to show only those relevant stuff in the main page [07:49:53] and i don't want non-techy users to reveal those things that makes them confusing :) [08:19:23] anyone, can you review this patch? https://gerrit.wikimedia.org/r/#/c/266943/ [09:25:05] How can I add a Bitcoins button to receive donations in WikiMedia? [10:25:19] How can I display a picture? [10:25:56] I got a picture at /images/behringer.jpg and I'm using [[File:images/behringer.jpg]] but it doesn't show up... [10:40:57] hexhaxtron: Was it uploaded via MediaWiki? [10:41:01] Or just put there manually? [10:41:06] Reedy, manually. [10:41:29] Without importing it to MediaWiki, I don't think there's an easy way to do it [10:41:44] How do I import it? [10:44:14] Well, easiest way is to upload it via the MW interface [10:44:15] !uploads [10:44:15] File uploads are disabled by default, set $wgEnableUploads=true; to enable it. See for configuration details, and for using uploaded images and other files. [10:50:14] Reedy, can you guide me step by step? [10:50:17] I added $wgEnableUploads = true; [10:50:22] But I don't see any button... [10:59:25] Reedy, got it! Thanks! [10:59:39] Reedy, I need another thing. How can I insert a Youtube video? [11:07:17] !queryerror [11:10:26] hexhaxtron: look at widgets for arbitrary HTML [11:10:27] https://www.mediawiki.org/wiki/Extension:Widgets [11:15:47] RobotsOnDrugs, got it! [11:16:08] RobotsOnDrugs, my last question. How can I add a Bitcoins button? [11:17:00] depends on what you want exactly [11:17:22] if you just want an image with a link, that should be pretty easy to add in a footer or something [11:17:23] RobotsOnDrugs, I wanted to receive Bitcoins donations. [11:18:44] there may be an extension specifically for donations, but putting whatever in a footer would work just fine [11:19:14] does your bitcoin processor provide a button you can use? [11:19:48] p858snake, [11:19:50] I'll see. [11:28:05] RobotsOnDrugs, p858snake I got the code for the button. It starts like this: [11:28:14] RobotsOnDrugs, p858snake can I add that code to the sidebar? [11:48:25] RobotsOnDrugs, I wanted to add the Bitcoins button right bellow the Paypal button in the Sidebar http://e-guitar.co.uk [13:02:05] when i install a new version, i get "A database query error has occurred. This may indicate a bug in the software." and i have to visit http://localhost/mywiki/mw-config/index.php?page=DBConnect and i have to "enter the value of $wgUpgradeKey in the box below". why is this needed? is there any way to do it that doesn't involve the browser? (i'm trying to automate the backup/restore process.) [13:03:08] settings go in LocalSettings.php [13:03:36] RobotsOnDrugs: and what should i do in LocalSettings.php? [13:03:49] set $wgUpgradeKey [13:05:47] is was set already... to some "default provided" value. what else should i set it to? [13:08:04] RobotsOnDrugs: it seems you understood my question the other way around [13:09:43] RobotsOnDrugs: as part of my question, i already quoted a part of this message: A LocalSettings.php file has been detected. To upgrade this installation, please enter the value of $wgUpgradeKey in the box below. You will find it in LocalSettings.php. [13:10:14] oh, i thought that setting did something else [13:10:22] https://www.mediawiki.org/wiki/Manual:$wgUpgradeKey [13:10:49] jkale: https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script [13:10:52] it basically locks upgrades via the browser [13:11:26] i've never used the browser to do updates :P [14:11:27] morning [14:23:32] Hi, I'm using 1.26.2 along with the QuestyCaptcha extension and I would like to have the output of a shell command as the answer to a question, but even though I can print it to the registration form it doesn't seem to be accepted as the correct answer - I get the error "Account creation error\nIncorrect or missing CAPTCHA.". This is my code: https://gist.github.com/totte/87cc7585e535d8646e4b, any idea what I'm doing wrong? [14:55:32] I'm trying to add a NoCaptcha do the Wiki but my friend can still add stuff like Viagra, etc. [14:55:47] How can I tell if it's working? [15:21:16] RobotsOnDrugs, you there? [15:56:10] What format are the Wikipedia text dumps? XML? [15:58:49] Why can't I execute composer.phar inside my root of mediawiki? [15:59:12] It doesn't seem to be in there, but the wiki says its installed by default? [16:00:36] Attempting to install this skin: https://www.mediawiki.org/wiki/Skin:Chameleon [17:17:32] I uploaded a picture but how do I delete it? [17:22:07] If you are an admin there should be a tab at the top of the page (by view history) to delete it [17:22:14] may be in a drop down box [17:26:11] Installing chameleon doesn't work [17:26:43] MW Version 1.26 [17:26:55] Can someone help me troubleshoot this [17:26:58] Please [17:27:27] Literally all of the hard stuff works without a hitch. I have no idea why I can't install this stupid skin [17:30:32] I am the principal of a small school. We are teaching our students about online contributions and want more than six to be able to create accounts within 24 hours. Is there a way to do this on the same IP? [17:31:30] Guest21773: https://www.mediawiki.org/wiki/Help:Mass_account_creation [17:31:46] thanks [17:36:43] totte, I'm editing this page: http://e-guitar.96.lt/e-guitar/index.php?title=Beginner_Lessons [17:37:08] totte, but I wanted to change it to: Lesson 01 - Anatomy of a Guitar and Lesson 02 - Scales [17:37:14] How would I do it? [17:40:00] baaas: Hi what is not working in the skin. Do you see any errors. [17:41:13] hexhaxtron: If your logged in then there should be a button to the right that says more and it drops down. Then click move in the dropdown. [17:47:06] paladox, can you help me adding AdSense to the Wiki? [17:48:36] baaas: please elaborate on "doesn't work", otherwise noone will be able to help. [17:48:56] haxhaxtron: Ok. Do you want this extension https://www.mediawiki.org/wiki/Extension:Ads since the AdSense extension was removed because of security problems. [17:49:46] hexhaxtron: Or https://www.mediawiki.org/wiki/Extension:Google_AdSense [17:50:46] andre__: when I install mediawiki it doesn't seem to have composer.phar even though the wiki says it does. [17:51:55] When I install composer separately into my mediawiki root and run the require command to install chameleon, it extracts everything to my home dir. [17:52:01] baas: I doint think you need to have composer.phar to be installed. all you have to do is download Bootstrap extension manualy and add the installation line above the skins and it should work. [17:52:13] baas: https://www.mediawiki.org/wiki/Extension:Bootstrap [17:53:26] Okay but that doesn't work [17:54:03] Wait you told me to download it manually but then link me to the wiki which says to use composer [17:54:55] baas: It should work without composer. [17:55:25] yes that's fine but the wiki page doesn't have a non-composer install section [17:55:30] It requires composer [17:55:42] "The Bootstrap extension requires Composer for installation. " [17:56:19] baas: Ok download from here please https://github.com/wikimedia/mediawiki-extensions-Bootstrap [17:57:17] baas: Doint forget to install bootstrap in the extensions folder so it looks like this extensions/Bootstrap [17:57:45] baas: Add this line require_once "$IP/extensions/Bootstrap/Bootstrap.php"; above the skin in localsettings.php file. [17:59:07] Give me a sec, rebuilding my container. [18:01:41] baas: Ok. if that dosent work ive uploaded a patch here that should fix that issue https://github.com/wikimedia/mediawiki-skins-chameleon/pull/2 and https://github.com/wikimedia/mediawiki-extensions-Bootstrap/pull/1 [18:04:59] Where am I pulling chameleon from? [18:06:12] paladox, it's not working but I can see Google AdSense there. [18:20:25] baaas, see "Download" on https://www.mediawiki.org/wiki/Skin:Chameleon [18:21:55] andre__: got it, thanks [18:27:45] andre__: paladox: Do I need to enable Chameleon? [18:28:21] baas: If you have installed bootstrap extension. And if you want to enable that skin then yes. [18:31:52] Okay, testing now [18:34:08] baas: Ok. [18:35:11] paladox: White screen now [18:35:22] At least it isn't warning me about my skin...? [18:36:12] baas: Hum maybe the skin may not be compatible with mw 1.26 but im not sure. Please try this https://www.mediawiki.org/wiki/Manual:How_to_debug#PHP_errors [18:37:55] paladox: https://dpaste.de/jWtG [18:38:52] Says that skin.json doesn't exist? [18:39:52] baas: Thanks it is this skin.json this file does not exist you need to do this add this require_once "$IP/skins/Chameleon/Chameleon.php"; under bootstrap in localsettings.php remove wfLoadSkin with Chameleon in it. [18:39:57] please [18:40:13] Oh well that's what I was confused with [18:40:14] Lol [18:41:48] baas: Ok. Does it work for you now. [18:42:44] baaas: [18:43:48] paladox: "Exception encountered, of type "RuntimeException" " [18:44:04] baaas: Ok could the full error be shown. [18:44:08] please. [18:44:30] How can I? [18:46:15] baaas: Could i ask how you set your localsettings.php just the two lines concerning that skin and the extension please. [18:46:43] Please hold. Remerging my DB in [18:46:58] I tried to put it in the background last time. Maybe that broke it [18:48:04] paladox: This is code I have at the end of my LocalSettings.php [18:48:06] https://dpaste.de/39Xq [19:15:05] baaas: Try removing $egChameleonExternalStyleModules from localsettings.php to see if that works. [19:16:46] paladox: nothing [19:19:28] paladox: I'm going to rebuild my container... Again [19:19:53] baaas: Ok. [19:21:26] baaas: Does composer work. If it downloads all the required files in what ever your folder is named for the skin then you should try this patch https://github.com/wikimedia/mediawiki-skins-chameleon/pull/2 [19:21:49] It doesn't work unless I install it by itself. [19:22:14] And then it won't extract the downloaded files to the correct directory [19:22:56] It puts everything in /root for some really [19:22:57] *reason [19:27:44] baaas: Hi i found the problem. The problem is with bootstrap and would need a patch to fix it. [19:28:19] *sigh* [19:28:27] Okay what's the patch paladox? [19:28:40] baaas: I will have to upload one. [19:29:01] Okay. What do I do when you've uploaded it? [19:41:45] baaas: Well i have to first create the patch then upload for review. [19:42:15] Okay. [19:42:19] Thanks. [19:42:26] Let me know when that's ready [19:43:21] Ah, concerning the page for CategoryTree: https://www.mediawiki.org/wiki/Extension:CategoryTree. It says "CategoryTree was originally written by Daniel Kinzler as an external tool, but was later integrated into the MediaWiki software". Is it just me that finds that phrasing confusing? It almost reads like CategoryTree was woven into core which it wasn't [20:56:07] Someone here who knows GeShi-Sytnax-Highlight? [20:56:40] Joergi: what's your question? [20:56:43] A new language has been added to Pygments and I would like to know, what to do in order to get it integrated into the official GeShi release. [20:57:00] Precisely: [20:57:25] I am speaking about the language called "TypoScript", which has just today been added to Pygments master branch. [20:58:06] Which branch is being used in the GeShi extension? How/When is it updated? [20:59:04] the extension currently bundles version 2.0.2 [20:59:49] there is a script in the extension's repo (in pygments/create_pygmentize_bundle that queries the PyPI (python package index) for the latest release and updates pygmentize accordingly [21:00:44] how big is the delta from 2.0.2 to the current head of master? [21:00:46] * ori checks [21:02:26] oh, there are a lot of new lexers [21:02:30] we should probably update [21:02:38] * Joerg realizes that it's exactly you Ori, who integrated Pygments in that extension. [21:02:55] Seems it's my lucky day... [21:03:13] Ori, can I help with that somehow? [21:03:52] Nah, should be straightforward. I can prepare a patch. [21:04:24] That would be great! [21:04:29] Joergi: Could you file a task in phabricator (https://phabricator.wikimedia.org/maniphest/task/create/) requesting that Pygments be updated to the latest version? [21:08:19] Done: https://phabricator.wikimedia.org/T125581 [21:09:16] I am really missing TypoScript highlighting for a wiki where I am heavily using it... [21:14:52] Joergi: I'll have a patch in a few [21:24:46] Ori: Having a patch would be amazing! [21:40:55] Joergi: is this a Wikimedia wiki, or a wiki that you administer? [21:41:38] It is a wiki I am running. It uses MediaWiki 1.26.2. [21:42:29] Hey guys. I'm having an issue with a conditional. The first bit of code in http://puu.sh/mTvzD/a68a153a87.png works when it evaluates to true, but it doesn't use the false condition if it evaluates to false. Am I screwing up syntax somewhere? The second bit of code (for comparison) works perfectly. [21:43:06] Gotcha. I think we may want to wait for the TypoScript lexer to be included in an official release. I prepared a patch to update Pygments to 2.1, but I can prepare another one that would update it to the current tip. That one might not get merged, but that doesn't stop you from using it locally in your installation. [21:43:36] When we get the PHP version bumps, we can do the pygments bumps [21:43:50] Reedy: what do you mean? [21:44:22] Oh, I'm thinking of symfony/process [21:45:33] Ori: Yeah, if you could prepare a patch from current tip, that would solve my issue. [21:45:45] That would be really great! [21:48:26] Reedy: https://gerrit.wikimedia.org/r/#/c/267998/ , https://gerrit.wikimedia.org/r/#/c/268001/ [21:50:04] when i install a new version, i get "A database query error has occurred. This may indicate a bug in the software." and i have to visit http://localhost/mywiki/mw-config/index.php?page=DBConnect and i have to "enter the value of $wgUpgradeKey in the box below". why is this needed? is there any way to do it that doesn't involve the browser? (i'm trying to automate the backup/restore process.) [21:50:52] Yeah [21:50:57] run the update.php maintenance script [21:50:58] !update [21:50:58] update.php is a script that updates the database tables. You usually need to run it after upgrading MediaWiki or installing certain extensions. For details, see [21:51:00] i did run php update.php and it seems to be doing all its magic, but nothing changes browser-side [21:51:28] Reedy: sorry for sending the second part later [22:06:00] Joergi: https://gerrit.wikimedia.org/r/#/c/268003/ should be all you need [22:14:32] ori: I'm currently integrating it... [22:17:29] Joergi: cool, let me know how it goes [22:18:06] I was referred here to ask my questions about epub export using the Collections extension. Is this the best place to ask? [22:27:21] Anyone? [22:27:24] :D [22:28:24] jfumitaka: it's certainly a reasonable place to ask. "Best" is hard to judge :) [22:28:26] go ahead and ask [22:28:37] ori: Currently, it does not highlight tags with language typoscript. Does it work for you? [22:29:00] Other languages are fine, but for "typoscript", I do not get highlighting... [22:30:37] ori:When using the book creator, the right side of the page has the drop-down for selecting the output format. Whenever I select "e-book (EPUB)" and click the Download button, I just get an error. The error isn't useful, either. It states, "There was an error while attempting to render your book." [22:30:40] Joergi: are you using the bundled pygmentize, or do you have a $wgPygmentizePath set? [22:30:55] *a different [22:31:17] I use the bundled one and I have replaced the bundled file(s) with the one from your patch set. [22:32:20] Joergi: weird. If you edited the page before you updated pygments, you'd need to trigger a re-parse -- try editing a page with typoscript code? [22:34:11] I have cleared the cache and changed the page content afterwards. Did not help. [22:34:26] Other languages are highlighted, but typoscript isn't. [22:35:05] All I get are 
..... tags around the code.
[22:35:24] 	 But no language code anywhere and no highlighting, just plain text inside the pre tag...
[22:35:42] 	 Joergi: did you update SyntaxHighlight_GeSHi.lexers.php as well?
[22:37:18] 	 can you confirm that 'typoscript' is listed in that file?
[22:38:41] 	 Yes, I updated that file as well.
[22:39:13] 	 It is the file, which you provided - it does not only contain "typoscript, but also typoscriptcssdata and typoscripthtmldata.
[22:39:33] 	 very mysterious; let me try
[22:39:50] 	 jfumitaka: is this on a wikimedia wiki or a different wiki?
[22:42:50] 	 it's using mediawiki, but not one of their wikis.
[22:55:16] 	 Joergi: can confirm, will have a fix shortly
[23:03:32] 	 note that i deleted all mysql file and reinstalled it but reimported (successfully) the database backup (and recreated user etc.). i ran php update.php ran successfully but i still get "A database query error has occurred. This may indicate a bug in the software." (so i have to visit http://localhost/mywiki/mw-config/index.php?page=DBConnect and i have to "enter the value of $wgUpgradeKey in the box below"). why is this needed? is there any way to do it t
[23:03:32] 	 hat doesn't involve the browser? (i'm trying to automate the backup/restore process.)
[23:03:49] 	 *mysql files
[23:07:08] 	 jkale: As Reedy said, you don't need the browser. Just use update.php from the shell.
[23:08:25] 	 jkale: For the error "A database query error has occurred.": At the end of your LocalSettings.php file add 
[23:08:25] 	 jkale: $wgShowSQLErrors = 1;
[23:08:25] 	 jkale: and see, what the exact error is.
[23:08:26] 	 Joergi: this is what i needed!
[23:11:22] 	 Joergi: Error: 1054 Unknown column 'page_counter' in 'field list' (localhost). i guess it's some extension?
[23:11:22] 	 jkale: This column has been removed during your upgrade to MW 1.26. 
[23:11:39] 	 The fact that this column is missing is ok, if(!) you are using MediaWiki 1.26.
[23:11:46] 	 What query is that?
[23:13:21] 	 localhost/mywiki. and i actually downgraded back from latest to lts (1.23).
[23:14:16] 	 Joergi: so, it was my mistake. I thought a zip file of the repository would be equivalent to the zip file of a release from pypi, but it is not -- we actually fetch a wheel from pypi, which is a special zip file that was built by python to be executable. 
[23:14:23] 	 Joergi: so what you need to do is this:
[23:14:24] 	 i'm planning to stick to the lts
[23:14:36] 	 Joergi: run: pip install -e hg+https://bitbucket.org/birkenfeld/pygments-main#egg=pygments
[23:15:10] 	 and then in LocalSettings.php, set $wgPygmentizePath to the path to the pygmentize executable which pip installed
[23:15:41] 	 (which you might be able to discover by running `which pygmentize`)
[23:15:51] 	 Joergi: the latest two messages were for you
[23:16:05] 	 jkale: Note that a downgrade is _not_ supported. You in fact have to use a backup and go to 1.23 from there (if that is an upgrade in your case).
[23:17:36] 	 jkale: If you once did an upgrade to e.g. 1.26 and then went back to an older version, this upgrade will no longer work correctly in the future. You will then have a broken wiki when you upgrade to 1.26 again.
[23:17:38] 	 Joergi: i created it in the latest originally then i decided to use 1.23, so my only choice is to try to downgrade it.
[23:18:27] 	 jkale: If there is not much important content in it, maybe you can just create a new wiki with 1.23 and add your contents there. Otherwise, see above: Downgrades are not supported.
[23:20:20] 	 ori: it's using a mediawiki installation, but it's not a wiki run by WMF
[23:20:24] 	 Joergi: thank you. at least i know my options.
[23:20:32] 	 jfumitaka: sorry, I'm not sure
[23:21:24] 	 ori: Any ideas on where to look to figure out what the actual error is? None of the logs seem to really indicate anything specific
[23:23:22] 	 ori: Thanks for digging into the Pygments install.
[23:23:45] 	 Joergi: np -- I'd love to know that it works, so let me know.
[23:23:53] 	 jfumitaka: not sure, I'm looking at the extension's source
[23:24:10] 	 ori: Okay, thanks.
[23:26:48] 	 jfumitaka: argh, sorry -- it is a bit more complicated than I was expecting. I don't have the time to dig deeper; I'm sorry.
[23:26:59] 	 No problem. 
[23:27:06] 	 ori: If I got you right, then the pygmentize binary eeds to be created differently. Would you mind creating the head binary for me again?
[23:28:23] 	 Joergi: the 'pygmentize' binary installed by pip and the 'pygmentize' binary that ships with the extension are different. The first is just a small script; it loads Pygments from the installation in your Python system path. The one that ships with the extension is a wheel file, meaning the whole package is bundled inside of it
[23:28:56] 	 if you can use pip to install the latest version (pip install -e hg+https://bitbucket.org/birkenfeld/pygments-main#egg=pygments), you can change $wgPygmentizePath to point to the pygmentize script which pip installed, which should do the job.
[23:29:48] 	 Joergi: I can make a bundle for you too, though. Hang on
[23:31:04] 	 ori: Oh, that would be so nice!
[23:36:18] 	 jfumitaka: Have you seen the according topic "Book rendering failed" at: https://www.mediawiki.org/wiki/Extension_talk:Collection ?
[23:36:44] 	 Joergi: try the copy of pygmentize from the patchset i just uploaded, https://gerrit.wikimedia.org/r/#/c/268003/
[23:37:11] 	 jfumitaka: But it doesn't seem like there is a solution for this error message currently. I think you would have to dig into the code in order to understand, where it fails in your case.
[23:39:27] 	 Joergi: Yeah, I saw the discussions there, but they didn't really help with figuring out the problem. 
[23:42:55] 	 ori: Yes! It _is doing_ highlighting now. That is what I need!
[23:43:06] 	 Thank you so much!
[23:43:24] 	 np, glad I could help.
[23:47:09] 	 ori: You certainly could. Thanks for your time and for the help you have been!