[02:20:43] hi [04:08:53] Anyone have a favorite blog post, script or extension they use to move a wiki from one host to another? old centos 6 php 5.3.3 mw 1.21.1 new Centos 7 php 5.6 mw 1.3.0 with short URLs implemented. [04:10:12] For wordpress I just discovered wp-cli a command line interface fpr wp. It's very cool. Be nice to have a similar tool for MediaWiki. [14:19:38] Hi GumShoe. [14:19:45] You could write one. :-) [14:19:54] MediaWiki has a pretty robust API. [14:20:09] There are also some existing command-line tools for MediaWiki. [14:44:31] hi all! I'm looking for a way to list all existing templates on my wiki, does such a special page exist or will I need a plugin for that? [14:46:03] Raazeer: Special:AllPages [14:46:13] Filter to the "Template" namespace. [14:46:28] There's API access to the same information if you need JSON output or something. [14:46:43] Special:SpecialPages has a listing of all Special pages on your wiki. [14:55:40] Ivy, thanks that helps [14:55:57] Hello, I'm asked to help migrate an old install (mediawiki 1.17) to a (recent|decent) one (v1.30). Do you see anything I should be aware of ? [14:56:28] I know I will have to update the os, php version and mysql [14:59:22] 1.17 doesn't support PHP 7, so you may have to upgrade to 1.30 while still on PHP 5, and the upgrade to PHP 7 after that [15:19:57] OK I just did a mysqldump on my old 1.21.1 in preparation for import to 1.30.0. Queasy feeling dowing it with sql statements. Would rather some type of dump the page, them import the page by way of an api call to create page. I think I'll go reread the move and upgrade pages again. [15:21:20] Any one with specific knowledge and/or experience move&upgrading from 1.2 to 1.3... "I'm listening" [15:29:29] GumShoe: mysqldump is the best way of going about making a backup/restoring a backup of the database [15:29:37] page export is really not meant for backup purposes [15:29:46] Skizzerz: thx [15:31:07] GumShoe: for one, page export won't capture things like your recent changes and log entries, users and group membership, and anything else that doesn't directly deal with the storing of page content itself [15:31:30] I'm reading in https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script "Upgrading from 1.4 or earlier is potentially complicated because support for character sets other than UTF-8 was dropped..." [15:31:47] GumShoe: otherwise, upgrade process from 1.21 to 1.30 (think of the . as a separator, not a decimal point; 1.20 is 18 versions newer than 1.2) [15:31:53] is pretty straightforward [15:32:04] Not understandingn the use of 1.4 in that sentence. The current release is 1.3 ??? [15:32:10] current release is 1.30 [15:32:16] which is 26 versions newer than 1.4 [15:32:24] again, the . is a separator [15:32:27] not a decimal [15:32:42] it is like that in every software versioning scheme that uses periods, not just mediawiki [15:34:20] so just follow normal upgrade procedure: make a db backup, extract tarball to new (clean, empty) directory, copy over LocalSettings and images, grab updated versions of any extensions, then run the update.php maintenance script [15:34:45] uhh... hoping for a light bulb or similar ahha moment on the versioning... [15:34:47] if you extract the tarball over your existing files, you could create issues, hence why the recommendation is to put it in a new place [15:35:07] GumShoe: pretend the 1. doesn't exist [15:35:20] think of it as saying "Upgrading from 4 or earlier..." [15:35:38] and you have version "21" with subversion "1", and upgrading to "30" with subversion "0" [15:36:20] Do I need to patch "Use patch -p1 --dry-run to check what will be changed (e.g., patch -p1 --dry-run -i mediawiki-x.xx.x.patch)" [15:37:21] if you're using the patch files, I'd suggest that just to make sure that it applies cleanly [15:37:42] you can mostly ignore the output, unless you've modified your core files [15:38:00] patch files will be kinda a nightmare for this upgrade though [15:38:57] I do not recommend them [15:39:17] FWIW and FYI I brought up a new 1.3 mw on a new centos 7.4 vm the old 1.21.1 is on a different vm on centos 6.... I'm not doing an in place upgrade... [15:39:22] again [15:39:27] 1.3 IS NOT THE SAME AS 1.30 [15:39:31] 3 < 30 [15:39:34] 30 - 3 = 27 [15:40:51] the version numbers (in order of release) go 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12, ..., 1.29, 1.30, 1.31, ... [15:41:24] if you're looking at things that talk about 1.3 or 1.4, ignore those things, they're talking about super ancient versions [15:41:42] process for upgrade into new vm: [15:42:38] 1) mysqldump database off old box (call it dump.sql or whatever), 2) restore into new box via mysql < dump.sql, 3) unpack the .tar.gz for 1.30, 4) identify what extensions you had installed on the old wiki and download updated versions of those too, 5) copy over LocalSettings.php and any images from the old server, 6) run the upgrade.php script [15:43:24] the new mw is up and running. I've got VisualEditor worling on it. I also implemented short urls. [15:43:29] cool [15:43:47] so what was the question then? I'm a bit confused if you are saying you already upgraded [15:44:33] I haven't moved the sql data yet.... or the files. old was in /wiki new in /w [15:44:49] ok [15:45:06] for files, only move your images directory over. Do not move any other files [15:45:24] for sql data, do steps 1 and 2 I mentioned above (mysqldump on old server, restore on new server) [15:45:41] make sure the restore is to a different database than the one you created during the install of the new mw [15:46:02] I'm thinking restore the db, then check the logs to see where the new server is looking for the images before I do the rsync [15:46:11] then, edit your new LocalSettings.php file to point to the restored database name [15:46:19] then run the update.php maintenance script [15:47:10] the images directory location hasn't changed, it's still in the same place and same format as 1.21 :) [15:47:35] I guess I better save this page on the new wiki documenting the entire vm move https://wiki.rodaw.com/wiki/CentOS_Upgrade [15:48:04] after you follow my steps, your old wiki's pages will be live and anything you created on the new wiki up to that point will go away [15:48:44] (you're replacing the database you just installed with the one from the old server and upgrading it) [15:48:53] I'll stick it in the old wiki and re dump the db [15:53:35] Skizzerz: so you do first a fresh install on empty database, then change settings to use restored db ?, nice tips [15:53:49] no, the fresh install is an unnecessary step [15:54:10] Skizzerz: so why an empty db ? [15:54:22] not sure I understand the question [15:54:44] Skizzerz: < Skizzerz> make sure the restore is to a different database than the one you created during the install of the new mw [15:55:13] in the case above, they already did a fresh install, so I want to ensure that the restored db doesn't try to merge/collide with the freshly-created one, or else there would be major problems [15:55:24] so the restored one needs to go into a different db [15:55:31] ho, ok [15:56:04] that's very clear, many thx, Skizzerz ! [15:56:46] armage: your upgrade process is going to be a bit more involved though due to the PHP versioning issues [15:57:20] see what I wrote above for you :) [15:57:32] Skizzerz: yes, I remember this point [15:58:31] er... why *did* I write that actually [15:58:46] it doesn't make any sense now that I go back and look at it :( [15:59:06] what 1.17 supports doesn't matter after you've extracted all the 1.30 files [15:59:26] since the upgrade process uses the 1.30 files, not the 1.17 files [15:59:44] so ignore what I said above, you can use whichever version of PHP you want :) [16:01:11] Skizzerz: so the update script in v1.30 will know how to update from v1.17 ? [16:01:29] yes [16:01:44] that's mucho great \o/ [17:09:41] :-) https://wiki.rodaw.com/wiki/Main_Page [17:11:06] compare to the old site url http://dediserve0.rodaw.com/wiki/index.php/Main_Page [17:55:11] i am trying to install and i can type in my localhost/mediawiki and I get page cannot be displayed... [17:59:01] Hi! I'm a free Shell Provider and Web Host. I've never used MediaWiki before so I don't know how it works. But can I install MediaWiki so that many different users can use it? [17:59:53] Or it works with only one copy for all? [18:01:21] Depends what you mean by "use" [18:01:45] Reedy: so that every user has it's own personal MediaWiki. [18:02:09] Each person needs its own db (or to use different db prefix) [18:02:36] you can share the MediaWiki php code if you want, as long as LocalSettings.php and database (and maybe image upload directory) is separate [18:02:56] !wikifarm [18:02:56] To run multiple wikis, you can simply install MediaWiki in different folders, with different databases or in one with database prefixes. You can also have multiple wikis using a single installation: If you run a farm or want to, join the mailing list: [18:14:25] hexhaxtron: mediawiki operates on free hosts, so you can offer it in your panel as an option (if you have an autoinstaller sort of thing). Each wiki would need its own copy of the files and its own database (you'd dump the files in the user's public_html and give each user their own db so that mysql permissions can be set up sanely) [18:19:34] I've got a long code block between block. Can I put scroll bars on it so as to still have the entire code block but limit it's display size on the page? For instance https://wiki.rodaw.com/wiki/CentOS_Upgrade#current_soon_to_be_old_wiki_version_info [18:23:39] depends with syntaxhighlight ext you are used, but try adding style="max-height:30em; overflow:auto" [18:29:32] SyntaxHighlight_GeSHi [18:34:30] Nice! Just what the doctor ordered. Than you @bawolff [18:35:48] And thank you too @Skizzerz the moved wiki https://wiki.rodaw.com/wiki/Main_Page [18:36:05] nice :) [21:08:27] Hi I'm trying to install the CategoryTree extension onto my mediawiki but as simple as it is, it's not working. I put the files in the correct folders, add wfLoadExtension( 'CategoryTree' ); to my LocalSettings.php file, but it doesn't show it as being installed on my Special:Version page [21:08:54] I've tried searching the internet for some help, but nobody else seems to be having issues with the installation process [21:09:03] I have MediaWiki 1.30 [21:09:47] If it's not being displayed in Special:Version despite having the wfLoadExtension, you're editing the wrong LocalSettings.php file (maybe you have several installations in different folders?) [21:11:51] It seems to be the correct file, and I only have the one installation in extensions/CategoryTree [21:12:18] OH WAIT [21:12:23] Maybe I'm being an idiot... [21:14:02] YES, hahaha, wow.... I accidentally added an extra LocalSettings.php file on the top-level of my root folder and forgot that's not where it's supposed to go [21:14:07] Thank you very much [21:14:19] yw :) [21:14:32] sometimes the obvious get overlooked [21:15:05] Yes... hard to look past your own certainty until someone else asks a proper quesiton