[00:43:06] great morning here aint it! [00:44:06] hopefully so pineappleskyes [00:44:41] about to try to write my very first template ever. this will test how well the docs about this are written :-P and how well i can understand them [00:45:45] well, good luck! [00:45:55] and have fun while you're at it :) [00:46:13] thanks. luckily what i want to do is pretty simple [00:46:28] for now. till i get the bright idea "hey, let's add dates to this template" [00:47:05] can't wait :) [00:47:34] well, the current template may be simple, but it's wrong rofl. time to reread :-) [00:59:40] well, the talk page on the subject at least showed me that i wasn't the first person to run into this specific issue :-) [01:32:56] Hi! Please comment at https://meta.wikimedia.org/?curid=140676#BiDi about BiDi editing for global accounts via the meta BiDi gadget cc:brion [01:51:54] how's it going greeter? [01:52:08] pineappleskyes: well i ran into a snag, so now i'm looking for a work around [01:52:33] all the best! i'm going offline now :) [01:52:41] alright then, take care [01:52:56] you too, nice knowing you [02:13:01] aha, i think i finally cracked the issue. i don't need a template at all, just a new extension [02:14:31] ok i still do need a template, but at least now the template will work properly. thanks for the help everyone :-D [02:22:16] legoktm[NE]: there? [02:22:48] Not really, I'm on my phone right now. [02:23:21] legoktm[NE]: uh, okay. Whenever you come online from your computer please approve my task :) [02:26:44] I left a comment [02:32:17] what does "[NE]" stand for? [03:18:16] legoktm[NE]: Fixed! I've submitted the task on GCI too [04:32:55] NE for New England Patriots. [04:33:08] what is this NE that people keep making reference to anyway? [04:33:25] NE is shorthand for a football team. [04:33:55] ah i see. american football or what americans would call soccer? [04:34:04] American football. [04:34:07] cool [04:52:40] Hello [04:53:22] greetings Randy___ [04:53:49] I've been looking for a site to get a little help with MediaWiki [04:54:25] Randy___: https://www.mediawiki.org/wiki/MediaWiki is a good palce to start [04:54:54] Are you looking for help about installing or developing for MediaWiki? [04:54:54] I'm a little past that piece [04:55:18] I'm having a few issues with project management [04:56:11] I've been looking for a way to list out tasks that everyone is working on and put a progressbar next to it [04:56:49] Randy___: i don't know about the progress bar bit, but i find creating a page for a todo list helps with that. it usually tracks what tasks are complete, incomplete, or not started [04:57:57] We use some image templates to make status stand out in various reports on mediawiki.org -- https://www.mediawiki.org/wiki/Template:Done [04:58:18] I would agree management likes the pretty pictures, thats why I've been looking for a progress bar, or a ToDo extension that handles these things for me. [04:59:13] There's similar one that uses a single template at -- https://www.mediawiki.org/wiki/Template:Status [05:00:09] Yeah thats what I'm currently doing with color coding [05:00:38] I just found this one as well -- https://www.mediawiki.org/wiki/Template:Backlog_progress_bar [05:00:44] I've never used it [05:01:50] I've been having a lot of issues with templates even working, I keep getting template loop. [05:02:06] and I'm not finding the issue [05:02:51] I'll get back on here tomorrow at work and hope I can get a little help form here [05:03:09] This might be a great find for me finding this site. [05:03:09] enwiki has a whole category full of progress templates too -- https://en.wikipedia.org/wiki/Category:Wikipedia_progress_templates [05:05:31] Thanks for your help. [05:09:47] Hey hi, [05:10:47] greetings FuturisticGroup [05:11:49] Hi, [05:11:57] I'm here for the GCI [05:12:10] GCI? [05:12:25] google code in [05:13:36] FuturisticGroup: have you setup your development environment yet? [05:13:44] ah i see [05:14:02] That might be a good way to keep busy as you hang out to get your irc task done [05:14:23] Things are pretty quiet in this channel right now [05:15:07] Yes... Let's rock it [05:20:05] * legoktm waves [05:20:37] be warned...this channel is guarded by the fearsome wm-bot [05:20:47] * greeter waves back [05:20:57] greeter: nice IP you got there [05:21:11] thanks Hydronium lol [05:21:41] i was really hoping freenode would resolve that after the staff decloaked me, but i can understand why it doesn't [05:23:27] !botdb [05:23:34] bleh [05:23:58] is something wrong? [05:24:19] !botbrain [05:24:19] Hello, I'm wm-bot. The database for this channel is published at http://bots.wmflabs.org/~wm-bot/db/%23mediawiki.htm More about WM-Bot: https://meta.wikimedia.org/wiki/wm-bot [05:25:45] Hello everyone! [05:26:27] * bd808 realizes it mush be getting late because Niharika is active now ;) [05:26:43] greetings Niharika [05:26:48] :P [05:26:57] Hi greeter. Are you a GCI participant too? [05:27:01] it's only 1:30 in the morning here, not late [05:27:19] Niharika: no. in fact i only heard of it a few minutes ago. i was here to get help with a template. it works beautifully now :-D [05:27:43] greeter: Awesome! A feat I am yet to manage. [05:28:12] Niharika: i'm sure my template has extraneous stuff in it, but i'm too lazy to pick it apart and risk breaking things again lol [05:29:25] !bribe [05:29:25] Stroopwafels for everyone!!! [05:29:39] lol, who added that [05:30:17] those sound delicious, but i'm sure they aren't actual waffles :-S [05:30:42] legoktm: I've fixed my issues. Please review. Thanks! [05:31:29] Guys.. Is there any one here working for Wikipedia or Wikimedia ? [05:31:39] maybe [05:32:13] ananayarora: you don't need to ask for reviews, legoktm will not forget about it :) [05:32:24] Hydronium: Okay! [05:34:22] FuturisticGroup: Wikimedia is the organization, Wikipedia is the website. [05:34:29] !wiki [05:34:29] A wiki is a collaborative website which can be directly edited by anyone with access to it. Ward Cunningham, developer of the first wiki WikiWikiWeb, originally described it as "the simplest online database that could possibly work". Wikipedia is one of the best known wikis. [05:34:41] Nah, there was a disambiguation key. [05:34:56] !wikipmediawiki [05:34:56] Confused about the differences between MediaWiki, Wikimedia, Wikipedia and wiki? See https://www.mediawiki.org/wiki/Wikipmediawiki [05:34:59] Can't we people join there as official members ? [05:36:03] FuturisticGroup: Where? [05:36:17] Yup, thanks Hydronium. [05:36:23] In Wiki ? [05:36:31] Or moderators ? [05:39:52] FuturisticGroup: Sure, anyone can become a moderator or admin when they have made sufficient contributions to the wiki. https://en.wikipedia.org/wiki/Wikipedia:Administrators [05:42:08] Niharika, Okay I'll see it .. And read it.. I'd like to contribute for the dearest wiki which always helped me.. [05:42:34] FuturisticGroup: Become an active editor to start with. :) [05:43:13] Okay.. There are lots of mistakes in articles about Nalanda College which they have created.. [05:43:26] i always thought adminship there was overrated. course, i made a horrible editor so it'd have been nuts to seriously consider vying for adminship [05:44:05] I'm building PHP7 right now, this'll be fun [05:44:09] As I'm a student for 9 years and I can help you guys to make it correct .. Is it okay to change few things in the content ? [05:44:29] legoktm, Php won't help for wiki.. [05:44:43] legoktm: I've built it a bunch of times, it shouldn't be hard [05:44:46] You need to edit them in a editor ? I'm I right ? Neharika ? [05:44:49] FuturisticGroup: you'll want to be careful if you're close to a subject. wikipedia has rules against original research. you must be able to site sources for what you add [05:45:01] *cite sources [05:45:10] bd808: yeah, I think it built, I'm running the tests now [05:45:54] Sure.. I have all the things and www.nalanda.sch.lk also can help with it which is the official web site of Nalanda College and www.nalandacollege. also can [05:46:42] for that matter, wikipedia also has its own freenode channels, like #wikipedia-en for the english wikipedia, if you haven't already checked those out [05:47:28] Also who is the actual owner of Wiki and where is it located ? [05:48:41] !irctab | FuturisticGroup [05:48:41] FuturisticGroup: While talking to someone on IRC, if you include their name in your comment, it sends them a ping which is helpful in case they navigate away from the tab. You can type the first few characters of someone's name and press Tab key to auto-complete it. [05:48:42] FuturisticGroup: https://wikimediafoundation.org/wiki/FAQ/en might answer some questions [05:50:10] bd808, Thanks [05:50:15] FuturisticGroup: Anyone can click "Edit" to edit articles on Wikipedia. If you're adding new facts, you need to cite sources. [05:50:53] Yes, I have edited few and no harm happen than making them correct information :-) [05:53:27] Well for example https://en.wikipedia.org/wiki/List_of_government_space_agencies this showes that SLSA is proposed.. [05:53:59] But we guys already launched a satellite called SupremeSAT- I to space in November,2012 [05:54:05] bd808: uh, silly question. where would `make` have put the php-cli binary? :P [05:54:44] ah, found it [05:54:51] ./sapi/cli/php [05:55:15] !php7 is https://www.digitalocean.com/company/blog/getting-ready-for-php-7/get_ready-03a8c363.jpg [05:55:16] Key was added [05:56:10] Elephants crossed with Star Wars? o.O [05:56:11] uh oh, something else i gotta worry about? [05:56:13] I wonder if anyone is planning to try porting scrubunto to php7 [05:56:43] hang on is php 7 actually a thing that's planned for some point soon? [05:56:44] Heh heh, Scrubunto. XD [05:57:19] greeter: PHP7 is the latest PHP stable version (as of a week or two ago) [05:57:39] greeter: Hopefully. Mediawiki on PHP 7 is basically broken right now. MW's exception handler does not work with new fatal exceptions. [05:57:54] Trela: really? [05:57:57] oh, so i shouldn't upgrade my site to it yet in other words [05:58:17] Trela: it's fixed in 1.27 alpha, 1.26 is broken [05:58:38] legoktm: Ah. :D Nice. I was working on a patch to submit, but I guess I can wait. [05:58:55] i should probably think about upgrading my mediawiki installation at some point soon though [05:58:58] Oh was that from the new base class they added? [05:59:04] yeah, `Error` [05:59:11] Trela: there are a few things left though: https://phabricator.wikimedia.org/maniphest/?statuses=open%28%29&projects=PHID-PROJ-uvzjhw46mbirlh2cho4z#R [06:00:44] legoktm: I wrote a utility that identifies all those code issues and suggests corrections. [06:02:00] I will go work on those right now actually. [06:02:23] Bye. Guys.. Good Luck and gotta take the lunch in here.. All the best for all GCI students [06:38:16] ooh, i found a question. i'm reading https://www.mediawiki.org/wiki/Manual:Custom_edit_buttons#Classic_edit_toolbar and i see the example code, think it'll be easy for me to use it and what not, but where do i put it? [06:49:59] scratch my last question, i found it. thanks :-) [06:53:48] hey myself rohit,i am from india and i claimed this task for google code-in [06:54:12] anyone there [06:54:47] Hi Rohytx. Welcome! [06:55:09] Niharika: thanks, [06:55:35] msg /nickserv help register [06:55:38] Rohytx: Did you setup your MediaWiki yet? [06:55:49] The / comes before 'msg' [06:56:36] Niharika: ok, i am just testing it [07:00:49] hmm, is this a contest involving mediawiki? [07:03:17] Pretty much. Codein.withgoogle.com [07:03:58] * greeter clicks [07:04:51] fascinating. this almost makes me want to be a programmer [07:09:29] hey [07:10:36] greetings Rohytx [07:10:52] Rohytx: thanks [07:10:57] greeter: thanks [07:11:33] you're welcome [07:16:22] Nemo_bis: hey mentor , i joined your #wikimedia IRC , my self rohit and i have submitted the task for review too. at https://codein.withgoogle.com/dashboard/task-instances/6564820618838016/ [07:17:37] hi Rohytx, welcome [07:18:41] Nemo_bis: thanks .. [07:23:46] Nemo_bis: i am beginner programmer , i know python can you please suggest me what other tasks i can do [07:27:19] how do I prevent myself from disconnecting? [07:28:58] shiftsayan: from irc? it depends on what is causing your disconnects. a proxy or a bouncer can allow you to appear connected to irc at all times, and not miss any of the conversation [07:29:29] i automatically left the IRC because my laptop was idle for a while [07:30:11] shiftsayan: What client is this? [07:30:21] limechat (mac( [07:30:29] my ubuntu crashed, urrgh [07:31:10] shiftsayan: you might benefit from using a bouncer in cases like that [07:31:21] okay [07:31:24] thanks for helping! [07:34:18] who are here are via GCI? [07:35:07] i am not, just to be clear [07:35:27] i am, but now I feel like staying here :P [07:35:41] shiftsayan: you can learn a lot about mediawiki here [07:35:59] i'm here because my website uses mediawiki. i get a great looking website that's up to date, and i don't have to do much work :-P [07:36:10] yes, I am really enjoying it [07:36:51] i've tried numerous times to get wiki software installed on my website. mediawiki is the only one i've found that made the process painless [07:37:41] which website btw? [07:38:48] well it's a website for a separate irc network. if you still want the link i'll notice it your way [07:39:40] i would love to check it out! [07:40:28] in fact if you want to discuss that more, we should probably pm instead to keep the main channel free for support :-) [07:48:10] Good call, greeter. [07:52:59] how do we go about fixing https://doc.wikimedia.org/mediawiki-core/master/php/todo.html [07:53:06] ^ stuff on the todo list? [07:54:15] that one i'm afraid i don't have an answer to. i'm sure one of the devs can answer it though [07:54:35] let me ask on the dev channel [08:05:00] Rohytx: nice, we have plenty of Python stuff. The main one is https://www.mediawiki.org/wiki/Manual:Pywikibot [08:05:15] You can search for one of the several tasks with pywikibot in title [08:18:35] Hey Guys.. Anyone familiar with Parsoid? [08:26:44] Hey somone tell me how to register my nickname in freenode ? [08:28:17] .seen tgr [08:28:21] FuturisticGroup: use this command: /quote nickserv register [08:28:39] In here ? [08:29:04] tgr: can you please what i really have to do at task Remove uploader's name from MediaViewer at https://codein.withgoogle.com/tasks/5766197941370880/?sp-organization=5505623550590976 [08:29:12] FuturisticGroup: if you run that command in here, then it should work. however you should run it in your server window just to be safe [08:29:36] Okay done... [08:30:03] don't forget to verify your e-mail address, or the registration will be deleted in 24 hours [08:30:43] Rohytx: Did you setup your dev environment yet? [08:31:02] Niharika: nope, how can i setup that? [08:31:15] !hacker | Rohytx [08:31:15] Rohytx: http://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker [08:31:23] Choose 'vagrant insallation' [08:31:26] Niharika: your name seems to be Indian, are you from India [08:31:28] installation* [08:31:37] Rohytx: Yes, I am. [08:31:53] Niharika: me too [08:32:26] :) A lot more indian GCI students than I anticipated. [08:58:04] Bye guys.. Bye for now.. [11:57:53] Hello. Could anyone help me, please? I am facing some problems with latest MW. It works fine some time and falls with the "Sorry! This site is experiencing technical difficulties." message. After creating a new page, for example. What help: opening the user in the ISP manager (yes, this one...) and clicking the 'OK' button. The site is back to normal state then. Some FAQ from Web are too old and not so actual. Why does the problem [12:03:59] Hello! Why does [[File:2015 Gi FW.vsd|GiFW diagram]] display the full file name instead of the alternate text? [12:08:48] !debug | mw_fmt [12:08:48] mw_fmt: 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 [12:08:56] Could be many potential issues [12:11:51] Thx. Will try to figure out the problem [12:12:35] Hi pals. [12:12:41] I had categories with pages. Then I renamed categories and changed them in pages. Now some cat's contain pages, so they have updated, and some -- do not. In some cases the pages are in old-named cat's (already renamed). How can I re-index the pages and categories? [12:14:07] I mean, there were categories that are renamed now. And their inclusions in pages are changed already. But some old-names categories (that stay as deleted now) still have some pages. [12:14:23] Looks like something must be re-indexed in mediawiki site? [12:15:17] You can null edit/purge the pages [12:25:06] Tried to purge some pages. No result. [12:25:49] Null edit helps. [12:26:33] Well, null edit for 300 pages does not add happiness. Maybe there is some extension? [12:40:12] Hi. How can I use the 'echo' or 'notification' feature in my mediawiki installation? [12:40:31] install the extension :) [12:40:45] There is no extension page. [12:41:22] My bad! there is... :) [12:41:22] Yes there is [12:41:22] https://www.mediawiki.org/wiki/Extension:Echo [12:41:36] Is that the official one used in wikipedia? [12:43:47] Yes [12:44:02] Thank you Reedy :) [12:53:05] Help! extensions/Echo/extension.json does not exist!' :/ I used the new way to register it! Is this correct -> wfLoadExtension( 'Echo' ); [12:53:22] Or should I use -> require_once "$IP/extensions/Echo/Echo.php"; [12:54:11] Yeah, you need to use the require_once version [12:54:58] May I know the difference between the two methods? [12:55:37] The first version is for extensions that have been migrated/updated to use the newer loader methods [12:55:41] In this case, Echo hasn't [12:56:14] Now I get this -> MediaWiki internal error. [12:56:14] Exception caught inside exception handler. [12:56:14] Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information. [12:56:52] Did you run the updater after you enabled the extension? [12:57:12] From special pages? [12:57:32] There's no special page for it, unless you're running the maintenance extension or similar [12:57:34] !update [12:57:34] 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 [12:59:53] I don't have SSH access. I tried the web browser method. Still same error! http://site.com/wiki/Mw-config/ [13:02:56] Add $wgShowExceptionDetails = true; then [13:03:00] see what's wrong with it [13:03:57] I saw a lot of things (newb here). I removed the extension, now everything is fine. [13:05:01] !pastebin [13:05:01] To avoid overflowing the channel with inane amounts of text, use https://phabricator.wikimedia.org/paste/create/ or other awesome pastebin sites to share code, errors, and other large texts. [13:07:46] Reedy, http://pastebin.com/6ba3J3Xf [13:07:59] Error: 1146 Table 'josh2_mdwk1.echo_notification' doesn't exist (localhost) [13:08:16] You need to run update.php, or re-run the installer as appropriate [13:09:07] My only way to run the db update is via web. It's not working. :/ it's site.com/wiki/mw-config/ right? [13:09:24] Something like that, depends on your config [13:09:27] it could be /w/mw-config [13:09:53] I did not change that! it's /wiki. I see the same error on that page too. [13:15:24] i will re-install the extension once I get SSH :) thanks reedy anyway... One more question. What extension does this page -https://www.mediawiki.org/wiki/Extension_talk:Echo use for discussion? [13:16:38] https://www.mediawiki.org/wiki/Extension:Flow [13:16:58] Cool... [14:02:34] Warning: OutputPage::getModuleStyles: style module should define its position explicitly: skins.mediawikibootstrap [14:02:46] is this a problem with the skin or with mediawiki [14:03:24] The skin [14:03:44] Template loop detected: Template:Progressbar [14:04:14] I'm having a few issues with templates, anyone able to help? [14:04:48] I have tried deleting the page but I still get the same error. [14:12:55] here is my code Printing:{{progressbar | 40}} on my page and here is the code on my template {{progressbar|percentage|height}} [14:13:08] can we find the devs of these skins and let them know of these errors [14:14:54] Yeah, feel free [14:15:15] It's not a skin WMF host etc [14:15:39] I presume it's http://www.mediawikibootstrapskin.co.uk/index.php/Main_Page [14:15:49] "This is the latest version, released August 21st 2014," [14:15:54] Bit out of date [14:16:12] Hello Everyone.. Does someone know if can migrate an existing MediaWiki to MediaWiki-Vagrant [14:16:28] !backup [14:16:28] See http://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki for information about backing up your wiki. For restoring your wiki, see http://www.mediawiki.org/wiki/Manual:Moving_a_wiki#Import_the_database_backup for more. If you don't have database access, try !grabber. [14:16:29] !movewiki [14:16:30] For help about moving pages, see . For help about moving wikis, see . [14:17:02] Thank you Reedy :) [14:17:02] retrojeff: There seems to be multiple bootstrap skins [14:17:02] https://github.com/nasirkhan/mediawiki-bootstrap [14:18:21] is there a github repo with all the default skins? [14:18:28] or official skins [14:19:33] "official" [14:19:45] https://github.com/wikimedia/mediawiki-skins [14:19:53] There's few official skins [14:46:59] what's the easiest way to disable revision history access to public users? [14:47:07] and instead reserve that right only to registered users [14:47:42] i don't think there's any way to allow viewing of most recent revision, but not any older ones. [14:48:17] (you can do a few things to make it more difficult, i guess, but there's no dedicated permission for it) [14:48:28] Or do you mean viewing teh history page [14:48:40] history page as a whole is fine [14:48:46] if i can restrict that for public users [14:49:14] i probably mean history page, so that public users is not able to see any of the changes made to the article [14:49:21] all they can see is the article itself [14:50:10] you could try setting $wgActions['history']=false. i wonder how many things that would break :D [14:50:31] but this still leaves the history accessible, via the API, via special:export, and probably a few other ways i haven't thought of yet [14:50:32] id like history access for super user though : ] [14:50:45] that there seems to disable history completely [14:51:10] mqds: or you could just proactively delete older revisions. mediawiki doesn't delete them for real, sysops can still view them. [14:51:20] so there isnt a way to simply restrict history access for those who havent registered? [14:51:28] not that i know of [14:51:36] wow [14:51:40] alright [14:51:44] thank you [14:52:51] mediawiki was made with transparency and openness in mind, and the permissions for viewing things aren't very granular :) [15:08:08] I still don't have any clue at all where to start looking for why I get "Fatal exception of type "MWException"" when opening the recent changes page. Any suggestions for where I could find logs or raise logging level? [15:08:19] !debug [15:08:20] 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:08:37] Reedy, thanks! [15:08:50] You really just want $wgShowExceptionDetails = true; [15:19:14] Reedy, any idea what could have caused this? https://maschinenpad.derpy.ws/p/MWexception (error log in etherpad) [15:19:24] I want to Migrate my MediaWiki to a vSphere.. Is the MediaWiki-Vagrant a thing for productiv use? [15:19:48] Not really [15:19:55] basisbit: Did you upgrade something? [15:23:04] PHP/MW/extesion? [15:24:14] Hello everybody. Can anybody help me with git and gerrit? I installed gerrit but i don't know how to get a file in order to edit it [15:24:17] I installed mediawiki 1.25.2, then universial language selector and then visual editor - everything fine until then. a few days later I installed the mediawiki language extension bundle and I get the error since after running the update script as described during the mleb setup [15:24:35] Reedy, I added information from the special:version page to the pad [15:24:49] I think CC is the Clean Changes extension [15:27:07] And I think that's a stupid PHP bug [15:28:18] any idea if I could just disable the clean changes plugin and/or run it manually [15:28:58] What was that command in LocalSettings.php? [15:29:10] The variable which was used to display errors. [15:29:17] of the Fatal Error [15:30:09] MatmaRex, legoktm, Reedy, andre__afk anyone here? [15:30:23] $wgShowExceptionDetails = true; ? [15:30:37] Reedy: Thanks ^_^ [15:31:41] basisbit: https://github.com/wikimedia/mediawiki/commit/cdc50e9029f9781958bec0318ca743265f6a11d7 [15:31:48] I *think* that was the fix for it on master [15:32:34] Yup [15:32:35] https://phabricator.wikimedia.org/T117553 [15:32:38] for another extension [15:33:21] oh, great! thanks! [15:33:43] Let me see about backporting that... [15:35:21] hmm? [15:40:48] Reedy, yes, applying that patch fixed it [15:41:02] That applied for you o_0 [15:41:14] It needed a bit of coercing to apply on 1.25 :) [15:41:21] https://gerrit.wikimedia.org/r/258987 [15:41:32] well, I made it work [15:41:45] being a software developer, that is not difficult for me [15:42:00] heh [15:42:13] Feel free to test my patch, and comment that it fixes it for you [15:42:20] Always good to get support for backporting :) [15:42:40] it is just that I usually do TomEE or other java based framework stuff *hide and run* [15:45:24] heh [15:47:33] basisbit: Either way, a +1 on the changeset on gerrit is useful for ammunition to merge a backport :D [15:47:35] reverted my manual changes, applied your patch and it worked. Special:last_changes it still quite slow - don't know if that is to be expected (small wiki in a kvm on decent hardware owned by me) [15:47:56] No idea about that one, sorry [15:48:08] Might be worth filing a task so someone who knows about it looks at it [15:48:47] would have to register on that page for a +1. why don't you use github pull requests for that kind of stuff? oO [15:49:03] Nope, we don't use github for that [15:49:18] github is just mirrors [15:50:56] could you just add a comment "+1 by basisbit; required for mediawiki 1.25.2 with MLEB installed as described in wiki." [15:50:57] :D [15:51:21] done ;) [15:52:28] thx [15:53:47] Are you on phabricator? [15:58:07] basisbit: Do you mean Special:RecentChanges? [16:04:56] Reedy, yes [16:36:21] hey, to adapt the user registration page, is the Extension:CustomUserCreateForm the correct plugin for that? [16:37:30] To adapt it? [16:37:40] User registration is in core :P [16:38:07] CustomUserCreateForm looks pretty dead [16:38:41] https://github.com/wikimedia/mediawiki/blob/master/includes/specials/SpecialUserlogin.php [16:40:02] I need the user to enter his own email address, confirm the address by clicking on the link, then automatically send an email to the users organisation email address, have an organisation official register the email and then have a wiki administrator manually active the account after that [16:40:23] o_0 [16:40:35] the wiki will be a target of certain political groups who don't like refugees at all [16:40:41] https://www.mediawiki.org/wiki/Extension:ConfirmAccount is partially that [16:41:05] Don't know if it makes you confirm an email address before allowing registration [16:41:20] It's certainy does the gating from allowing open registration [16:53:27] I think most of this can be accomplished with ConfirmAccount + revocation of editing rights from non-emailconfirmed accounts [16:54:17] basisbit: ^^ [16:56:57] MaxSem, we want only members of registered associations to be able to edit the wiki. (thus confirmation over official association email address) [16:57:16] You can probably use a hook to do email validation [16:57:47] and we want almost no work on out side as in checking garbage account registrations [16:58:20] Hooks::run( 'AddNewAccount', array( $u, true ) ); [16:58:54] regex validate $u->getEmail() and abort [16:59:01] Though, that'd be after confirmaccount [16:59:31] Reedy, yes, I think we will set up Extension:ConfirmAccount and then modify the confirm page to send the second email to the official association email address [17:00:08] I really like how much help I get in this channel. You rock! [17:01:21] we try [17:03:07] basisbit: and sometimes, we know what we're on about [17:03:48] :D [17:07:45] does someone know why my wikieditor displays and so on.. and not "Wikitext" [17:08:57] localisation cache out of date/not rebuilt? [17:10:01] how can i fix it? [17:10:51] Run the rebuildLocalisationCache.php maintenance script probably [17:11:09] already did.. didnt fix [17:12:23] with --force too? [17:13:34] ah k.. -f fixed it.. thx [17:16:32] Upgrade 101 query: Attempting to upgrade 1.25.2 to 1.26. Following https://www.mediawiki.org/wiki/Download_from_Git#Keeping_up_to_date. Maybe I misunderstand what is my "MediaWiki clone directory", because from /var/lib/mediawiki/, the command "git pull" yields the error: "fatal: No remote repository specified. Please, specify either a URL or a remote name from which new revisions should be fetched." I'm also unclear on what is my [17:19:06] You installed it from an OS package? [17:21:26] One second Reedy, checking to see if I took notes on install process. It would have been right after installing Trisquel (Ubuntu variant), so I may well have installed it from apt or synaptec package manager. Back in 60 seconds. [17:25:29] My notes aren't great but I suspect it was installed from apt, which I think would fit within what you mean by OS package. Do I simply need to run $ git clone https://gerrit.wikimedia.org/r/p/mediawiki/core.git ? If so, from what directory? I was worried this might overwrite existing materials, and https://www.mediawiki.org/wiki/Download_from_Git#Keeping_up_to_date just says "from a terminal window" without specifying cd location. T [17:25:43] dpkg -l | grep mediawiki [17:25:48] that should confirm if it's from apt [17:26:39] Reedy: dpkg executes silently, no output. I'm not proficient enough to know what that means. [17:27:22] I presume that means you didn't install it from apt or similar [17:28:46] Correction: My notes suggest I intalled from tarball, as per: https://www.mediawiki.org/wiki/Manual:Running_MediaWiki_on_Ubuntu#Configure_MediaWiki [17:29:39] That's better than a debian package then :) [17:31:22] Good to hear! So, how much of a mess am I in? As much as anything, I'm simply confused by "clone directory" "and "core directory," which if I understand maybe is the same thing, the local clone of the git core? In any event, thoughts on where to start? Feel free to rtfm, I just was unclear if it was appropriate to jump in with $ git clone https://gerrit.wikimedia.org/r/p/mediawiki/core.git, and, if so, from what directory... [17:32:38] You could switch to git, but I don't know if it's worth the effort [17:33:01] Grab hte 1.26 tarball, extract it, copy in uploads, LocalSettings [17:33:06] Get any extra extensions... [17:33:10] !upgrade [17:33:10] http://www.mediawiki.org/wiki/Manual:Upgrading [17:36:17] How much effort? Git seems like it might be necessary for WikiBase installation (https://www.mediawiki.org/wiki/Wikibase/Installation), which is what inspired me to drag myself through the upgrade process. Git seems like it may be easier for upgrading longterm, just not sure how to safely start. [17:37:44] you can essentially do the same thing with git [17:38:20] you can install extensions via git, but not MW core etc [17:41:13] Okay, I think I see how to do this from "Other files" and "Using git" in the link you provided (https://www.mediawiki.org/wiki/Manual:Upgrading#Using_Git). There is just one step (#2) I don't understand: 1. Create a new clean folder. 2. If using Git, export the files into a clean location (does this mean $ git clone https://gerrit.wikimedia.org/r/p/mediawiki/core.git ?) 3. then copy the old customized files into the new location as [17:47:42] It's saying to backup https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files [17:47:51] You can git clone into a new folder [17:48:07] I'd probably use /var/lib/mediawiki-new or something to begin with [17:48:18] obviously you need to checkout the branch, not master too [17:48:45] exactly what I was thinking, which I'd then rename /mediawiki and rename the old one /mediawiki-old later, and yes i copy that re: checkout the branch [17:49:03] git clone -b REL1_26 .... [17:49:08] and yes, copy that, backed up already and confirmed it recovering on another computer [17:50:02] If you wanted, you could clone 1.25, so you keep it almost the same, move stuff over, confirm it's working, backup again, and then upgrade ot 1.26 via git [17:50:38] on the last one: did you mean $ git checkout -b REL1_26 (checkout rather than clone), and the ...., presumably origin/REL1_26? [17:50:48] it's the same thing, effectively [17:51:02] you can do a checkout after, it doesn't make much difference [17:52:06] okay, I'm just learning the git commands. thank you for such a helpful back-and-forth explanation. I think I feel safe starting from here. [17:53:03] Sending you an imaginary thank-you cup of coffee from the snowy high desert of northern AZ. [17:53:30] If you get stuck a little further on, chances are someone else in here can help if I'm not about [17:53:57] (thumbs up) [17:57:22] Make sure you check out extensions at the same version as you MW ;) [18:01:39] One last q: working from /mediawiki-new/, $ git clone -b REL1_25 needs a repository specified. "You must specify a repository to clone." Do I simply need to first clone the core repo ($ git clone https://gerrit.wikimedia.org/r/p/mediawiki/core.git) ? [18:01:55] sorry, me being lazy [18:02:04] git clone -b REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/core.git [18:02:08] should be one fell swoop [18:02:29] if you're already in mediawiki-new... [18:02:36] it'll create a folder in there called core [18:02:38] cd .. [18:03:00] anything but lazy - just unclear on how elementary my skill level is. thanks for working with me through it. [18:03:01] rm mediawiki-new [18:03:06] git clone -b REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/core.git mediawki-new [18:03:20] uh, rmdir mediawiki-new I guess [18:03:26] or rm -rf mediawki-new [18:07:25] (only part I didn't follow was the rmdir. What's the reason for that? I just ran $ sudo git clone -b REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/core.git from within the clean /var/lib/mediawiki-new folder, which is still running. I don't follow why I would immediately $ .. and $ rmdir it? [18:08:12] because you're going to end up with a dir called core under mediawiki-new [18:08:30] though, depending on your rewrites... [18:08:35] you might want to just mv core w [18:23:33] *reads up* [18:31:09] Reedy (if still there): process just finished (/var/lib/mediawiki-new/$ sudo git clone -b REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/core.git). If I understand correctly, I can 1. $ cd /var/lib/ 2. $ mv mediawiki mediawiki-old (saving copy of old install) 3. $ mv mediawiki-new/core mediawiki (making the git-installed core folder the main mediawiki folder) and then 4. move on to checking on extensions and 5. using git to upgr [18:31:40] Yeah, you need to copy your LocalSettings.php and uploads etc into mediawiki-new [18:31:56] I'd probably suggest cloning all the extensions before moving it to the canonical mediawki [18:32:45] I follow copying the config files like LS.php and custom stuff like uploads folder. I don't follow what you mean by "cloning all the extensions before moving" [18:33:19] Any extensions you've got in the "old version", clone them into your "new version" before testing it [18:35:59] by clone you simply mean copy? for example renaming the new version's extensions folder extensions-old and copying the previous install's extensions (/var/lib/mediawiki-old/extensions) to the new version I've just installed (/var/lib/mediawiki/extensions) ? or do you mean clone in the sense of some specific command? [18:36:17] No, clone from git [18:36:30] You'll need to update the extensions when you update core [18:40:29] Okay, so this would mean looking up what extensions I had in my previous install, and then one by one running /var/lib/mediawiki-new/core/extensions$ git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/.git ? And then after that moving it to the canonical mediawiki folder? [18:40:55] This is no big deal, it was a fairly simple local installation, just making sure I understand. [18:40:57] you need the -b REL1_26 too [18:41:15] uh, 1.25 in this case [18:41:30] but you shouldn't need to move them, as moving the core folder will move those tooo [18:42:28] Right, so: /var/lib/mediawiki-new/core/extensions$ git clone -b REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/extensions/.git ? (just making sure I have the syntax right) [18:42:36] Yup [18:42:46] whew... thanks, getting started on it [18:42:54] If you used the tarball, you might have extensions in your old one that you're not using [19:31:04] Hello [19:45:37] hi Randy___ [19:52:34] Hi Nikerabbit! Can you please give me a hand? see https://meta.wikimedia.org/?curid=140676#BiDi its a five minute work [19:52:57] Reedy (or others), I've just finished cloning all my extensions, copied images folder and LocalSettings.php to the mediawiki-new/core/, and then renamed my old installation /var/lib/mediawiki to /var/lib/mediawiki-old and moved /var/lib/mediawiki-new/core to the canonical folder /var/lib/mediawiki. (1/2) [19:53:28] Attempting to use the wiki now gives the following error about needing to update PHP, though the PHP is an updated version as the error message itself states: "MediaWiki 1.25 internal error MediaWiki 1.25 requires at least PHP version 5.3.3, you are using PHP 5.5.9-1ubuntu4.11. Installing some external dependencies (e.g. via composer) is also required." Suggestions? [19:57:34] iscutwo: composer :) [19:57:42] You need to clone the vendor repo, or run composer [19:57:44] !composer [19:57:45] Composer is a dependency manager for PHP. MediaWiki uses it to include certain external libraries. See https://www.mediawiki.org/wiki/Composer for more details. For information on how to install MediaWiki dependencies with composer see https://www.mediawiki.org/wiki/Download_from_Git#Fetch_external_libraries [19:58:08] In 1.25 the error messages got mangled and confused whether there were missing libraries, or old php [20:03:36] Okay, I read that I need to "run composer install --no-dev. Note that if you have an existing composer.lock file (I don't, though I see a composer.json, fwiw) you will need to run composer update --no-dev instead." I also read that I need to "Make sure you use the right branch for your MediaWiki version (e.g. REL1_25 for 1.25)." (1/2) [20:04:31] If I understand correctly, I need to run (I've already moved core to the canonical folder) /var/lib/mediawiki $ run composer install REL1_25 --no-dev (is that the correct command and syntax?) [20:08:19] (without "run" after the $, obviously) [20:09:46] hm [20:10:16] iscutwo: if you're using composer (and not cloning medawiki/vendor), then the part about branches shouldn't be applicable [20:10:31] iscutwo: so, just `composer install --no-dev` should be fine. [20:13:16] I'm getting "command not found," though my previous installation was 1.25 and I thought that meant I had composer, but I must be mistaken (low proficiency level, I take good notes on what I do but I don't understand a number of commands). So, from here, if I do need to install composer first before using that command, best to get it with wget? I.e. $ wget https://getcomposer.org/composer.phar ? [20:15:38] (To save you scrolling up, I am trying to transition from an existing working install of 1.25 to 1.26 and with git to manage installation and future updates of wikibase, all on a pretty simple local host installation; I just used git to clone a core repo to /var/lib/mediawiki-new/core, I cloned all my old extensions to core/extentions, copied my LocalSettings.php to the core folder, then renamed my old install from /var/lib/mediawik [20:16:22] (2/2) and then moved the /var/lib/mediawiki-new/core to the canonical /var/lib/mediawiki folder. (I think this pulls you up to speed with the present php error) [20:18:56] MatmaRex: one more clarification, which is that I used git to clone a new version of 1.25, which I plan to then upgrade to 1.26 with git once my git-installed new 1.25 is working. So, where I'm at right now is the php error which I need to use composer to fix, and running composer as instructed says I don't have the command composer, so if I understand correctly I need first to install composer. Is my next step then $ wget https://g [20:26:33] iscutwo: If you're not using any fancy extensions... [20:26:48] Just clone mediawiki-vendor [20:28:09] Is Scribunto fancy? I imagine wikibase is, which I just cloned in earlier. [20:28:25] Well, WMF use both, so it's not an issue [20:30:42] Okay, I see that in the instructions (https://www.mediawiki.org/wiki/Download_from_Git#Fetch_external_libraries): " if you want to use the same set of vendor libraries as used on the WMF production cluster, you can instead git clone https://gerrit.wikimedia.org/r/p/mediawiki/vendor.git to create a vendor/ directory inside the core folder of your MediaWiki installation. Make sure you use the right branch for your MediaWiki versio [20:31:21] (2/2) So, if I understand correctly: /var/lib/mediawiki $ git clone REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/vendor.git ? [20:31:37] (the canonical folder was copied from the core folder already) [20:31:44] -b [20:32:25] ahhh right thank you: /var/lib/mediawiki $ git clone -b REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/vendor.git ? [20:32:50] yeah [20:33:04] you'll need to remove the old one first [20:33:06] /rename it [20:34:09] sorry, remove old... what? the canonical folder? If I understand, rename it to something like mediawiki-somethingelse and then run from a new empty /var/lib/mediawiki folder the command $ git clone -b REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/vendor.git ? [20:34:32] the old vendor folder [20:35:13] Okay, sorry, vendor folder is a term I don't understand. I don't see a folder named vendor in /var/lib/mediawiki, for example. Manual? [20:35:26] eh? [20:35:28] you should [20:36:16] how is your mediawiki working? :) [20:38:44] lol... it's not. but I'm getting closer. Current error is "MediaWiki 1.25 requires at least PHP version 5.3.3, you are using PHP 5.5.9-1ubuntu4.11. Installing some external dependencies (e.g. via composer) is also required." But back to vendor folder, if there is no folder named "vendor" in /var/lib/mediawiki (which I copied from the "core" folder after renaming the previous canonical folder), am I okay to run the command (1/2) [20:38:45] $ git clone -b REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/vendor.git ? [20:38:53] Oh [20:38:57] You've already moved "new" to old? [20:39:03] Yes, just run that then [20:39:36] yes, that's correct. previous canonical is mediawiki-old, previous mediawiki-new/core is presently /var/lib/mediawiki, and does not contain a "vendor" folder [20:39:39] okay, running... [20:39:56] should be relatively quick [20:45:44] Reedy: Okay, it ran successfully, now I've got a /vendor folder with all sorts of exciting things in it, including composer, but I can't find my place in the instructions (https://www.mediawiki.org/wiki/Download_from_Git#Fetch_external_libraries) for my next step (attempting to use the wiki now yields a blank web page, no errors). (1/2) [20:46:05] Am I at the point where I'm supposed to be doing git checkout of 1_25? [20:46:16] You're already on 1_25 [20:46:36] !debug [20:46:36] 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 [20:46:58] Okay, off to rtm the debug links. Thank you again for all the help up thus far. [20:47:13] iscutwo: shortcut [20:47:15] error_reporting( E_ALL | E_STRICT ); [20:47:15] ini_set( "display_errors", 1 ); [20:47:22] Just add those to the top of your LocalSettings.php [20:47:24] below Done. The error I get when attempting to view a wiki page is "Fatal error: Uncaught exception 'Exception' with message '/var/lib/mediawiki/skins/CologneBlue/skin.json does not exist!' in /var/lib/mediawiki/includes/registration/ExtensionRegistry.php:101 Stack trace: #0 /var/lib/mediawiki/includes/GlobalFunctions.php(216): ExtensionRegistry->queue('/var/lib/mediaw...') #1 /var/lib/mediawiki/LocalSettings.php(130): wfLoadSkin('Cologne [20:51:44] des/WebStart.php(124): require_once('/var/lib/mediaw...') #3 /var/lib/mediawiki/index.php(38): require('/var/lib/mediaw...') #4 {main} thrown in /var/lib/mediawiki/includes/registration/ExtensionRegistry.php on line 101 [20:51:55] Haha [20:52:02] You need to clone your skins that you're using too :) [20:52:21] okay to copy from old version, or is this another git step? [20:52:36] Best to just git clone [20:52:46] Only half doing it is pointless :) [20:53:08] Gotcha. I see this under https://www.mediawiki.org/wiki/Download_from_Git#Keeping_up_to_date. Sort of like what I had to do with extensions. [20:54:43] I read: "The new version of core may require newer versions of extensions and skins, so you must go into each extension and skin directory and update it with a command like git pull --recurse-submodules." My new skins folder is empty, though, so not sure what my first step is to be. [20:55:35] Well, the error is for cologneblue [20:55:50] git clone -b REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/skins/CologneBlue.git [20:56:52] into the skins folder [20:57:03] Actually, I see in my mediawiki-old/skins the skins I head. So I presume I go ahead as I did with extensions: /var/lib/mediawiki/skins/extensions$ git clone -b REL1_25 https://gerrit.wikimedia.org/r/p/mediawiki/skins/.git ? [20:57:18] Yup, exacty [20:57:25] (sorry, was scrolling up to copy-paste and didn't see you already wrote that - thanks!) [20:57:53] Most of it is very much of a pattern [20:58:28] (and I realize I mistyped "skins/extensions" in the location, obviously I do this in the currently empty skins folder) [20:58:32] cool - off to try [21:13:02] iscutwo: had any luck? [21:16:13] Wow, I gitted (got?) the four skins I had with my old install, and now the wiki at least works with this new git-installed version. So where I'm at now in the instructions (https://www.mediawiki.org/wiki/Wikibase/Installation#Installation_using_Composer) is that I need to run /var/lib/mediawiki/extensions/Wikibase $ php composer.phar install (1/2) [21:16:34] You shouldn't need to [21:17:04] You'd probably want to do the 1.26 upgrade before you install Wikibase [21:17:55] I think using https://github.com/wikimedia/mediawiki-extensions-Wikidata/tree/REL1_26 would be easier [21:18:04] It's a repo that brings everything into one deployable place [21:18:15] I did git-install the 1_25 wikibase when I was doing (clone-ing?) the extensions before I moved the mediawiki-new/core to mediawiki canonical. [21:18:24] "Wikidata is using a build with Wikibase and its dependencies packaged into one git repo." [21:18:34] I mean, upgrade everything to 1.26 first [21:18:38] ok, looking at it now [21:20:05] Might want to make a backup of your work as is (and your database if you've not done it) [21:20:14] you just need to then do git checkout REL1_26 everywhere [21:20:22] core, vendor, each of the skins and each of the extensions [21:22:23] Backups are done. So, this would mean $ git checkout REL1_26 with no other modifications, just run from the location of the /mediawiki, /mediawiki/vendor, /mediawiki/skins, /mediawiki/extensions ? [21:22:36] yes, yes [21:22:46] you need to go into the subfolders of each skins [21:22:49] and extensions [21:22:55] gotcha [21:22:56] so mediawiki/skins/CologneBlue [21:23:46] is order important? or as long as I go to all the necessary places, $ git checkout REL1_26, I'm on my way? [21:23:55] It isn't important [21:24:06] As long as you don't try to visit your wiki in the middle [21:24:20] most people would do core/vendor, then skins/extensions through [21:24:51] Ok. The only thing I think I didn't follow was when you said "using https://github.com/wikimedia/mediawiki-extensions-Wikidata/tree/REL1_26 would be easier", what does it mean to "use" that in the sense of running this update? [21:25:11] nothing [21:25:15] (And copy that re: not visiting the wiki in the middle. How, though, do I check to make sure I've done everything, without trying to load a page from the wiki, in the event I forget and miss something?) [21:25:18] I'd suggest using that repo, rather than Wikibase [21:25:21] Okay, thanks. [21:25:29] As it's compiled all the dependancies [21:25:40] Just do it sytematically, you shouldn't miss anything [21:26:30] Okay. And when you say using that repo, do you mean I need to append it to the checkout command, i.e. $ git checkout REL1_26 https://github.com/wikimedia/mediawiki-extensions-Wikidata/tree/REL1_26 ? Or, in what command would I use it to make that the repo? [21:27:05] Ignore that for the moment [21:27:23] Did you already enable that extension in LocalSettings.php [21:27:24] ? [21:28:34] If not, just delete it [21:28:35] Okay, ignoring for the moment. And I had enabled it yesterday but have had it commented out since then. [21:28:42] Ok, good [21:29:19] So, for now, just going through the necessary locations: main, vendor, skins, extensions, running $ git checkout REL1_26 (with no modifications to that command) ? [21:29:23] In all the repos you've cloned, run: git checkout REL1_26 [21:29:23] Yup [21:30:57] In vendor, it's just at the vendor level, not subfolders (as I'll need to do in extensions and skins), correct? [21:31:08] yup [21:32:07] Also at the level of /skins and /extensions folders, or just /skins/skin1, /skins/skin2, etc ? [21:32:17] the latter [21:32:26] and extensions/extension1, extension2 etc [21:32:36] There's probably a way to script this... [21:32:38] That's what I thought. Thanks. I'll check back in in 5ish. [21:32:46] As they're not proper submodules [21:32:50] I was thinking the same, but I'm on a (very slow, but steady) roll. [21:33:05] ah [21:33:47] 4 skins done, on to extensions [21:34:12] find -name .git -execdir git "checkout REL1_26" \; [21:34:17] that looks stupid [21:34:22] find -name .git -execdir git checkout REL1_26 \; [21:34:28] something like that should work in theory [21:35:05] but yeah [21:35:08] if you're nearly done ;) [21:37:19] okay, skins and extensions done (main and vendor already done) [21:38:02] cool [21:38:09] 1 last thing to do before you test your wiki [21:38:14] php maintenance/update.php [21:38:21] to do any database updates etc [21:39:03] Run from canonical /var/lib/mediawiki $ ? [21:39:13] yup [21:40:31] ok, done in 40s. Testing wiki... [21:44:13] So it all seems to be running okay, version reports as 1.26.0 (0b709c1), though I don't seen Wikibase in the list of extensions on the version page (Scribunto and others are there), though I know I have a /mediawiki/extensions/Wikibase folder. Presumably because the lines are still commented out in LocalSettings. Okay to uncomment and test? [21:45:09] No [21:45:20] I'd remove that Wikibase directory [21:45:36] git clone -b REL1_26 https://gerrit.wikimedia.org/r/p/mediawiki/extensions/Wikidata.git [21:45:46] Hang on [21:45:49] Let me confirm this is a good idea :P [21:45:52] addshore: About? [21:45:57] k thanks [21:46:04] =o [21:46:21] Is using the Wikidata meta/combined repo rather than extensions/Wikibase and composer a good idea? [21:47:07] mhhhm, for development using composer is defiantly best [21:47:18] for deployment, they are equalish [21:47:35] iscutwo: so yeah, rm -rf extensions/Wikibase [21:47:42] then in extensions [21:47:42] git clone -b REL1_26 https://gerrit.wikimedia.org/r/p/mediawiki/extensions/Wikidata.git [21:48:04] (after renaming/deleting /extensions/Wikibase ?) [21:48:18] Yeah, just delete Wikibase [21:48:19] https://github.com/wikimedia/mediawiki-extensions-Wikidata#to-enable-client-add-the-following [21:52:02] (running) [21:52:33] Hi. I'm admin for http://wiki.openstreetmap.org/wiki/Special:RecentChanges any suggestions on best way to stop mechanical turk spam? and similar. [21:52:47] in room or off ;-) [21:53:00] !spam [21:53:00] For information about combating and handling spam in MediaWiki, see . [21:53:26] RTFM! ;-) [21:53:28] Only question about the link to instructions on enabling the client, if I understand correctly I need Wikibase-repo, not client, so my instructions would be those just above at https://github.com/wikimedia/mediawiki-extensions-Wikidata#to-enable-repo-add-the-following, correct? [21:53:44] iscutwo: Oh, you're trying to create a repo, not a client? [21:54:04] Firefishy: Unfortunately, its mostly a manual process [21:55:52] Spammers moved a bunch of key pages and quickly jacked up changes. Going to be a pain to un-foobar. [21:56:23] I'd suggest using like autoconfirmed and such then [21:56:28] Remove move rights from "newbies" [21:58:49] Will do. [22:00:04] Firefishy: extension:nuke will kill all the page creations by spammers [22:01:31] Reedy: I have been confused by the different (repo vs client). This isn't for interlanguage links but rather to create my own database of items, which seemed closer to the description of repo (https://www.mediawiki.org/wiki/Extension:Wikibase_Repository#Feature_overview) than client (https://www.mediawiki.org/wiki/Extension:Wikibase_Client#Usage) if I understand them. Client appears to be either for external data or interlanguage li [22:01:38] my own created and structured data items.... [22:01:52] Yeah [22:01:57] Client is mostly for accesssing wikidata.org [22:03:02] Ok, that's what I thought. So, having git'ted wikidata new, I'll add the repo-appropriate lines to LocalSettings.php as per (https://github.com/wikimedia/mediawiki-extensions-Wikidata#to-enable-repo-add-the-following), and test? [22:03:20] Yeah [22:05:57] iscutwo: You'll presumably need to run update.php again [22:06:07] !!! So, at least from the Version page, things look great: a giant table of information on the apparently working wikibase installation [22:06:07] There is no such key, you probably want to try: !bribe, !tss, [22:07:13] !bribe ? [22:07:13] Stroopwafels for everyone!!! [22:07:27] lol [22:07:41] but if you bribe all at the same time, does it still work [22:10:14] Reedy: having run /var/lib/mediawiki $ php maintenance/update.php actually gives some errors, probably too long to paste into chat. Gave a php warning, then a warning, then a fatal error, I'll just paste the fatal error part to avoid spamming: [22:10:18] Fatal error: require_once(): Failed opening required '/var/lib/mediawiki/extensions/Wikidata/extensions/Wikibase/repo/maintenance/../../../../maintenance/Maintenance.php' (include_path='.:/usr/share/php:/usr/share/pear') in /var/lib/mediawiki/extensions/Wikidata/extensions/Wikibase/repo/maintenance/rebuildEntityPerPage.php on line 12 [22:10:24] !pastebin [22:10:24] To avoid overflowing the channel with inane amounts of text, use https://phabricator.wikimedia.org/paste/create/ or other awesome pastebin sites to share code, errors, and other large texts. [22:10:41] Got it thank you. [22:15:45] * andre__ wonders who "maintains" /resources/src/mediawiki.special/mediawiki.special.search.css in MediaWiki core [22:16:43] https://github.com/wikimedia/mediawiki/commits/master/resources/src/mediawiki.special/mediawiki.special.search.css [22:16:55] andre__: Why? [22:17:00] No one in particular, it seems :P [22:18:36] Reedy: any thoughts on that error ? [22:19:06] because it might have boogs. Yeah, guessed so. :) [22:19:42] iscutwo: I wonder if it's just sparsely tested [22:19:51] (15minute timeout sorry) [22:19:55] I could tell you how to fix it, but that doesn't help greatly [22:21:14] aude: about? :) [22:25:05] iscutwo: [22:25:07] php extensions/Wikidata/extensions/Wikibase/repo/maintenance/rebuildEntityPerPage.php--help [22:25:08] Does that work? [22:31:12] space before --help [22:46:03] Reedy: back. Running that command gives basically the same error I reported above about line 12: PHP Fatal error: require_once(): Failed opening required '/var/lib/mediawiki/extensions/Wikidata/extensions/Wikibase/repo/maintenance/../../../../maintenance/Maintenance.php' (include_path='.:/usr/share/php:/usr/share/pear') in /var/lib/mediawiki/extensions/Wikidata/extensions/Wikibase/repo/maintenance/rebuildEntityPerPage.php on line 1 [22:46:15] hm [22:46:20] (and yes, I also noticed the missing space and added it) [22:48:49] Ah [22:49:12] putenv( "MW_INSTALL_PATH=$IP" ); [22:49:20] Something like that in your LocalSettings.php should fix it [22:50:47] iscutwo: putenv( "MW_INSTALL_PATH=$IP" ); [22:53:02] Reedy: we run the script in a cronjob on terbium [22:53:19] so, yes, i say i works [22:53:27] aude: Yeah, I presume the require only works in WMF because of putenv( "MW_INSTALL_PATH=$IP" ); in Multiversion [22:53:44] Which stops it using ../../../../ etc [22:53:48] you need $IP set [22:54:23] Which IIRC tim moved out of LS a while ago [22:54:45] yeah, it's in WebStart [22:54:54] hmm, does it work for maintenacne [22:55:21] Reedy: so just add putenv( "MW_INSTALL_PATH=$IP" ); to LS.php? I also noticed the new code I had added most recently used the format require_once __DIR__ . "/extensions/Wikidata/Wikidata.php"; while the code I had pulled from elsewhere was require_once "$IP/extensions/... [22:55:37] (one sec, catching up reading the last few lines) [22:56:02] $IP = strval( getenv( 'MW_INSTALL_PATH' ) ) !== '' [22:56:03] ? getenv( 'MW_INSTALL_PATH' ) [22:56:03] : realpath( __DIR__ . '/..' ); [22:56:08] iscutwo: Yup [22:56:31] the $IP/__DIR__ shouldn't make much difference [22:56:40] Not quite sure why the docs say __DIR__, as that's not usual practice [22:57:44] Presumably hte putenv will fix update.php, but not standalone script running due to WMF using multiversion to host things [22:57:58] one step at a time anyway [22:58:26] Added line and saved. Now I re-run /var/lib/mediawiki$ php extensions/Wikidata/extensions/Wikibase/repo/maintenance/rebuildEntityPerPage.php --help ? [22:58:32] nope [22:58:41] re-run php maintenance/update.php [22:58:55] Right - got it. Running. [22:59:54] Run in 0.2s with no apparent errors, though one note about "Failed to set the local repo temp zone container to be private." if that matters [23:00:14] that's just a permissions error for upload [23:00:27] k [23:03:59] Sorry I'm a little lost at where I am in troubleshooting steps right now. Having updated LocalSettings.php and re-run php maintenance/update.php, do I now return to run $php extensions/Wikidata/extensions/Wikibase/repo/maintenance/rebuildEntityPerPage.php --help ? [23:04:23] Nope [23:04:32] That was just some debugging [23:05:21] You should be good to just setup wikibase repo as you need to [23:06:20] Right, that step was in response to the line 12 error I got from running $ php maintenance/update.php earlier. Thanks. [23:07:35] Now this is the last and most kindergarten question of the day: I couldn't find any wikibase/data documentation on how to actually begin tinkering with it. I work on Wikidata (the real one), but don't know where on my localhost installation to begin working, and can't find it in the documentation. I don't know the equivalent of the "Main Page" [23:09:02] iscutwo: maybe start with Special:NewItem [23:10:11] aude: Got it! Just found the wikibase documentation in my special pages. Thank you, and also and especially 6 hours of help from Reedy, so much! [23:11:22] if you have items in the main namespace, then you can make the main page in your project namespace (like we have Wikidata:Main page on wikidata) [23:12:11] then we set https://www.wikidata.org/wiki/MediaWiki:Mainpage so that clicking on the logo on wikiata goes there [23:26:05] Reedy: yes, it looks great! [23:26:49] Reedy: (oops, sorry, that was in response to a query of yours from a while ago, which I saw again when I left the screen scrolled up. All seems good from here. Thank you again very very much.) [23:27:00] iscutwo: for your records... [23:27:18] Next time you want to upgrade your wiki; to a major release [23:27:23] git fetch --all [23:27:29] git checkout REL1_NEWVERSION [23:27:46] For any point release updates, you just need to run git pull [23:28:03] in each folder, and it'll bring in any commits to that release branch [23:28:45] Got it. Major release fetch & checkout in each folder as well? Or just for point releases? [23:29:41] pull for point [23:29:45] fetch and checkout for major [23:29:46] in each folder [23:29:59] For the point releases, chances are, most extensions/skin won't change [23:30:01] but they do sometimes [23:31:04] find -name .git -execdir git fetch --all \; [23:31:11] That should work as a shortcut [23:31:13] Let me try [23:31:31] yeah, it does [23:31:42] so you can just do [23:31:47] find -name .git -execdir git pull \; [23:31:50] or [23:31:54] find -name .git -execdir git fetch --all \; [23:32:07] find -name .git -execdir git checkout REL1_NEWVERSION \; [23:32:22] Got it - thank you again. [23:32:28] Np :) [23:33:37] I've saved all of this to a lengthy note, and highlighted the important steps and notes for the future. This was like 6 hours of guidance and saved me a ton of stress. If I can send you a book or a movie for the holidays as a thank-you, drop me a line at isaac@isaaccurtis.com. In any event, you have my thanks! [23:34:54] iscutwo, Reedy: see this little script https://tools.wmflabs.org/paste/view/d184736e [23:34:57] I've got a few things on my (UK) amazon watchlist if you're so inclinded [23:35:22] Platonides: yeah, that's where I got the find -name from above... I couldn't remember where the source script came from though ;) [23:36:05] wow, did you have a copy of that? [23:36:27] reedy@ubuntu64-web-esxi:/var/www/wiki/mediawiki$ ls -al subgits [23:36:27] -rwxrwxr-x 1 reedy reedy 540 May 3 2012 subgits [23:36:30] It's been there a while :) [23:36:49] indeed -rwxr-xr-x 1 root root 541 mar 27 2012 /usr/local/bin/subgits [23:37:04] Platonides: also, nice to see you back around :) [23:37:38] it's glad to find out people is still using those little tools [23:37:58] Did you write clone-all.php too? [23:39:11] maybe [23:39:15] let me see [23:40:08] is it on the repository? [23:40:36] I've no idea [23:40:47] https://github.com/wikimedia/mediawiki-tools-code-utils/blob/master/clone-all.php [23:40:49] several people did a few similar tools [23:40:57] Yup, you did :) [23:41:03] yep, it's mine [23:51:02] Reedy: link to amazon watchlist? After that, I'm out of here to go play in my functioning install! [23:51:39] "Working with MediaWiki" by Yaron Koren [23:52:06] That's actually on my amazon wishlist [23:52:07] hahah [23:52:10] lol [23:52:15] Just as a "this seems interesting"