[00:02:27] Any ideas on which files to copy from my old wiki to the new one in order to get all my pages back? [00:04:57] PelicanGaming: It's not "files", it's a database. Did you use Mysql for the database setup? [00:05:01] PelicanGaming: most of the data you want is stored in your database, not the files [00:05:21] when you reinstall you need to point to your old db [00:05:27] bugger....I accidentally deleted the db.... [00:05:35] and then if they were running differnt versions run the update script [00:07:11] so I'm basically out of luck..... [08:47:36] hi im trying to move a quite old mediawiki to a new host and upgrade it. It have a lot of old extentions so my plan is to install it with the old version of mediawiki on the new host and then upgrade from there. It is currently running mediawiki 1.24.6 [08:52:49] I have installed mediawiki1.26.6 on the new host, moved all the pictures etc and dumped the db og reimported it on the new host with the process described here: https://www.mediawiki.org/wiki/Manual:Moving_a_wiki#Versions_and_upgrading [08:57:43] after importing the db on the new host I run maintenance/update.php but it i get a "Error: 1054 Unknown column 'page_counter' in 'field list' (localhost) " error and i dont know how to attack that problem. As everyting i find on google is to run the update.php as i have allready done. [09:20:01] sptz: https://www.mediawiki.org/wiki/Manual:Hitcounter_table [09:20:54] https://www.mediawiki.org/wiki/Manual:Page_table#page_counter [10:32:33] Guest39600: thanks! [17:23:59] Hi! Does anyone know if I can call the SpecialRunJobs.php remotely? I'm looking to trigger a job queue run without command line access [17:25:59] Can't you just POST to it? [17:26:07] Or setup a cronjob to run runJobs.php? [17:39:14] no, it needs an hmac so you can't just post [17:39:42] JosefAssad: In the default config, job queue will run without command line access [17:40:25] JosefAssad: $wgJobRunRate will control how fast. [17:42:12] although it's too buggy until the recent fixes land on a new MediaWiki release. See T100085 and related... [17:42:12] T100085: PHP Notice: JobQueueGroup::__destruct: 1 buffered job(s) never inserted - https://phabricator.wikimedia.org/T100085 [18:54:32] Reedy: oh. That works? [18:54:49] POSTing directly to SpecialRunJobs.php? [18:55:21] Apparently not [18:56:41] ah yeah bugger, just tried it [19:57:04] Hi y'all. SysAdmin here. Love MediaWiki, and have worked with it as an admin and WP editor for a long, long time. [19:58:31] However, I'm coming back to it after a haitus. I have a progressive (Bernie) group I'm demoing a MediaWiki instance for a medium-sized group to facilitate inter-regional coordination. ("Hey, how do I phonebank?") [19:58:33] Woo! [19:58:48] I'm looking to be suuuuupper lazy as an admin. [19:59:26] Are there a "common set" of MW extensions now preferred for non-Wikipedia use to make admining for smart but non technical users easier? [20:00:13] hmm not really. different people like different things. The one's included with the tarball are a good start though [20:00:15] And perhaps "best practice" guidelines for backups, security, etc? [20:00:27] VisualEditor is very popular with users, but a pita to setup [20:00:43] Backup is fairly easy [20:00:52] Dump the mysql database, copy/tar up the files [20:00:57] bawolff: I like WikiEd for WP, and I'm not afraid to do more work to make sure they don't just give up and not share info. [20:01:36] I'm looking to make as "frictionless" a data-exchange as I possibly can, while still balancing against obvvious security concerns. [20:01:39] VisualEditor works wonders for making non-technical users contribute to a wiki [20:02:43] bawolff: Cool! I'm reading over the Extension page now. Does it make "good" mediawiki markup code, or a horroshow? :) [20:03:20] Oh, jeez. Parsoid is a new thing to me. Interesting. [20:03:46] Oh, wow, *vagrant instances of MediaWiki*. wow. [20:03:53] NightMonkey: Yeah, it has to appease the wikipedians, and they are very picky [20:04:13] I love VE. it's been great for getting people to use headers properly instead of just making things bigger and bolder. and it's almost entirely killed our usage of bold red text [20:05:36] shauno: Ah, awesome! [20:06:00] I'm getting the sense from the docs that Parsoid is the PITA part of the setup of VE. [20:06:08] yep [20:06:17] We previously had users who had no desire at all to learn markup. They'd find something someone else had done elsewhere, and paste it in. So some really bad habits were hard to kill. [20:06:26] Now creating valid markup is easier than cheating [20:07:34] As a secondary concern, I'm also looking to set them up so that if I get hit by a bus, they aren't DOA in terms of basic mainteance, and can tread water until they find a new "techie"> [20:07:37] . [20:08:06] shauno: Awesome, II. [20:09:13] Is there a lot of grief with Parsoid failing? Does Parsoid failing disable all editing features? [20:10:08] If parsoid doesn't return properly, VE gives them nothing useful at all (but other editing methods are unaffected) [20:10:17] But you can still use the old wikitext editor too [20:10:26] Ah, great. [20:10:36] I would hate for them to lose edits in-progress. [20:11:50] We haven't hit that yet (~20,000 users, maybe ~50 editors, one machine running everything out of docker). Parsoid's been very fire and forget. The fire part is the sticking point, forget is working flawlessly [20:14:12] shauno: Great to know - thanks for the background on your setup. [20:14:30] shauno: Do you generally have a rapid upgrade process? [20:16:05] very much the opposite. it's an internal corporate wiki, and the person who used to handle it left 6 years before I was given the task of moving it off win2k3 [20:16:17] shauno: Oh, my condolences. [20:20:55] Hmm. I'm wondering if WikiEd might be reasonable to use. But, it sure is more fiddly for users. [20:22:36] * NightMonkey realizes he smoked crack when he wrote that last statement. [20:24:35] WikiEd?} [20:24:40] As in, WikiEditor? [20:24:48] Or the ooold WikiEd? Which was based on something else? [20:28:22] https://en.wikipedia.org/wiki/User:Cacycle/wikEd [20:28:50] But that is completely different than VE. [20:29:23] I don't think that is maintained... Or works on modern MW [20:30:43] I'm now playing with VE on WP. Slick. [20:32:27] Reedy: It was updated in March. It works - but is inappropriate for non-technical users I'm going to be helping. [20:32:47] VE is muuuch better. Does it work okay on Mobile browsers? [20:49:03] I think so, I think it can be integrated into mobile frontend [22:49:12] Hello. A day before I enquired about implementing automatic Cyrillic converter to sh.wikipedia.org and announced that I was working on it. I haven't found a corresponding enhancement request or a bug filed on phabricator, and IIUC MatmaRex mentioned that he hadn't noticed such a thing on https://phabricator.wikimedia.org/T32759 [22:51:07] So what I'm asking is what's the correct path now: should I ask for consensus for such an enhancement on sh.wikipedia.org for example or file a bug myself... or sth else? [22:51:58] Filing a bug is probably a good idea whatever [22:52:27] Even myself? [22:52:38] Yeah, anyone can file them. That's not an issue [22:52:45] I mean this is not a bug per se IMHO [22:52:53] Bug, feature request [22:52:58] It's all vaguely the same thing [23:01:12] file a task in Phabricator. [23:01:22] Make T32759 a parent task of your task. [23:01:22] T32759: Languages that need a LanguageConverter implementation (tracking) - https://phabricator.wikimedia.org/T32759 [23:01:29] https://www.mediawiki.org/wiki/Phabricator/Help