[00:00:10] there's lots to learn and lots to do, before we really go live [00:00:11] super [00:00:21] ok 1) let's stick a list of what needs to be done on a wiki page [00:00:27] 2) let's have someone say "i'm gonna do it" [00:00:32] 3) then let's make sure they have access [00:00:42] brion: it's not that easy [00:00:49] current architecture is a bit in flux [00:01:00] for osm, i'm not sure who has access to the osm production db server, who is doing what with the tile server, etc. [00:01:01] So are wiki pages! [00:01:16] saper: then identify first steps to perform [00:01:18] getting to #1 will be a success [00:01:33] brion: first is to mirror production osm on a wmf box [00:01:57] there needs to be a one sacred postgres instance [00:02:04] excellent [00:02:08] write this down man :) [00:02:46] http://meta.wikimedia.org/wiki/Maps_server_setup_tasks <- starting here [00:02:51] feelf ree to rename it appropriately [00:03:54] let's also make sure we have here listed how many boxes there are, exactly :) [00:04:35] brion: can we move this to toolserver wiki? [00:04:42] by all means [00:04:42] and the whole project? [00:04:47] anywhere you guys like :) [00:06:02] good [00:08:04] so you agree to run the project, cool :) [00:08:42] haha sounds like ;) [00:09:26] brion: http://wiki.openstreetmap.org/wiki/Image:OSM_Components.png [00:09:33] this is the OSM architecture now [00:09:57] <^demon> Whee Kill Bill on TV :) [00:10:09] we can work probably using one renderer (say Mapnik) but more or less rendering and serving tiles _fast_ are the main problems [00:10:37] we only need the database, mapnik rendering and slippymap part of that, and possibly the api for toolserver purposes [00:11:09] that's not "only" :) [00:12:42] ok tossed a quick note to maps-l with link :D [00:14:19] step one is get something working, step two is get it working well ;) [00:14:26] it's not about bashing people [00:14:31] haha [00:14:41] i mean making sure my guys are setting up access as necessary [00:15:41] maybe access is not imporant as long as it is non-production stuff, I don't know [00:15:59] off to a wiki [00:16:01] well, the important part is that _someone_ has to set up the software :) [00:16:23] so either that means one of my techs does it or one of my techs gives someone access to those boxes to do it [00:16:31] brion: where are the hardware specs of those two wmf boxes, ptolemy and wiheisster? [00:16:37] no clue :) [00:17:28] i haven't been in the thick of it as i thought other folks were handling it :( [00:19:47] i now have lots more spare time, so can do setup work, but don't have access to anything [00:20:07] oh, here it is http://meta.wikimedia.org/wiki/OpenStreetMap [00:20:35] was just to give the same link http://meta.wikimedia.org/wiki/OpenStreetMap [00:21:30] :D [00:22:31] I think we need architecture piece [00:26:18] architecture documentation would be good [00:26:28] excellent, page looking fuller :D [00:26:41] yeah :) i lnked that graphic you showed me for now [00:27:48] aude: would you agree with that? [00:27:51] http://meta.wikimedia.org/wiki/OpenStreetMap#Project_goals [00:28:04] so does cassini basically have test installs of the bits we need to grab plus some misc stuff? [00:28:40] brion: partially yes [00:28:57] but I think we should do more work on that [00:29:08] I don't think that renderd with mod_tile will be scalable [00:29:27] who has geohack/wma tile server stats? [00:30:05] saper: dschwen i guess. [00:30:46] ok, well we can start there in the near term :) but definitely more info will be helpful if we think we need to change [00:30:55] there was some talk of putting it behind a squid caching proxy? [00:31:10] what about thttpd or something like that [00:31:28] I think we should measure what will be faster [00:31:33] the goals are good [00:32:01] aude: I forgot "develop innovative map applications" maybe but that's priority 2 [00:32:09] we definitely need to try out different approaches and test performance [00:32:24] I don't know why we can't have one rendering architecture for toolserver and production [00:32:37] let's just get the basics implemented [00:32:51] first let's get damn osm onboard [00:33:29] yeah :D [00:33:32] does wiki.openstreetmap.org have an interwiki entry? [00:33:35] anybody mess with ProtectPagePlus - encryption extension ? [00:33:42] then we can measure imports and stuff [00:33:51] replication will be tricky as usual [00:34:17] ok guys i gotta run; poke me tomorrow and feel free to flood my inbox :D i'll keep an eye on maps-l and the wiki page [00:34:26] aude: I think that maybe we should try to live with one postgres instance, not two [00:35:35] or is there maybe another channel where noob/user types can ask questions [00:36:21] Heh, JeroenDeDauw: don't you think you're getting a little ahead of yoursef? :D [00:36:41] hotchip: this is the place, but I don't see any extension by that name on MW.org [00:37:38] http://www.mediawiki.org/wiki/Extension:PageProtectionPlus [00:37:55] i'm pretty close to having it working, but i'm experiencing some php gmp extension weirdness [00:38:04] Doesn't look well-maintained [00:38:25] doesnt mean it doesnt work right? ;) [00:38:36] It might or it might not [00:39:02] is there another extension that implements strong encryption of pages i should be looking at [00:39:37] Hmm, http://www.mediawiki.org/w/index.php?title=Special%3ASearch&search=encrypt&go=Go [00:40:14] Emufarmers: :d I'm first though! [00:40:37] First is the worst; second is the best; third is the one with a hairy chest [00:41:53] i'm not sure how many postgres instances... but we could start with one [00:43:39] is it possible to change the width of the border on images? [00:44:43] div.thumbinner { [00:44:43] border: 1px solid #ccc; [00:44:45] is the default [00:44:57] in monobook anyway... [00:45:13] so just redefine that in MediaWiki:Monobook.css [00:45:19] ok, so it can be changed in the css file for the style? [00:45:50] i typed that before i saw the last post... lol [00:45:51] not a file, on the page called [[MediaWiki:Monobook.css]] [00:45:56] <^demon> Emufarmers: I haven't heard that since like 2nd grade. [00:47:40] ^demon: me either, but it popped into my head [00:47:58] *Emufarmers thinks Splarka has cooties [00:49:53] <^demon> Emufarmers: I am rubber and you are glue.... [00:55:56] Five minutes to get rid of it! :O [01:33:40] So what would breaking math support into an extension actually look like? How would we maintain backward compatibility? [01:54:56] Emufarmers: dunno, you might just be able to do it as a normal tag extension [02:02:46] 03(NEW) Need default values for accesskey-n-mainpage-description and tooltip-n-mainpage-description - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=20317 normal; Normal; MediaWiki: Internationalization; (rockmfr) [02:02:54] 03(mod) Separate main page url and name - create MediaWiki:Mainpage-url - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=8617 (10rockmfr) [02:04:03] MrZ-man: well, I mean, would there be any way to do it that wouldn't require people who upgraded and already had math to redo it? [02:04:25] Though I suppose installing an extension is easy compared to the existing process of setting up tex anyway... [02:06:37] well, if the binary is the same, converting should be easy, maybe? [02:07:02] yeah [02:08:13] though on a linux system, its not particularly hard to set up [02:08:50] Not on a proper one, but if you're on crippled shared hosting, I understand it's rather unpleasant (or impossible) [02:09:01] why those people want tex, though, I don't know :D [02:10:00] yes, you need to be able to install the dependencies [02:11:43] but I'm sure every shared hosting server has ocaml installed 9_9 [03:34:42] 03shinjiman * r55363 10/trunk/extensions/UsabilityInitiative/ (2 files in 2 dirs): Localisation updates Cantonese and Chinese for extension messages [03:55:59] HAHAH, on the local digital weather feed, & is showing in the news ticker... fail [03:58:04] Splarka: you'd like http://revealingerrors.com/ [03:58:15] Scroll down past the last few [04:03:48] Can someone explain to me why Special:LinkSearch is listed under "Redirecting special pages" [04:04:38] does anyone know why the pbody attribute messes up in the navigation bar of monobook if the content column is long vertically [04:05:40] Charitwo: where? [04:05:55] Oh, I see what you mean [04:06:37] seems like an "incorrect" place to put it, but then again nowhere else seems appropriate either [04:07:08] Tyson Homosexual. Haha [04:07:17] :) [04:07:48] It'd probably fit under Page tools [04:08:04] Or Wiki data and tools [04:10:08] charitwo: http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/includes/SpecialPage.php?view=diff&r1=48044&r2=48045 stab ^demon? [04:11:20] :o [04:26:37] i need to move my wiki(1.9) to a new server and upgrade it to the newest version....my plan is to do a db dump, restore it on the new server with the newest mw installed and run the upgrade scripts....will this work? [04:27:23] Should do. [04:27:31] Follow the UPGRADE instructions carefully. [04:28:04] The update.php script should handle the main database issues. [04:28:06] GreenReaper: ok...great, I'll do tht...thx [04:28:19] If you are putting in extensions, make sure they are updated too, to the stated revision. [04:28:30] Some may have to come out, if they are now redundant. [04:28:41] but there's not too many in that situation. [04:28:59] Put them in place in your config before you run update so that they have the chance to run their own DB update. [04:29:05] 03dale * r55364 10/trunk/phase3/js2/mwEmbed/skins/mvpcf/styles.css: * broken kskin integration mvpcf bootstrapping [04:29:35] ok...I'll just have a clean installation with all the extensions and then restore the old Db..and run the update script... [04:29:47] Good luck. But you shouldn't need it. [04:30:36] GreenReaper: I suppose it would be easiter to upgrade first and then migrate...but I don't want to mess with the old system [04:30:48] I'd just move the DB and do it in place. [04:30:50] can someone tell me why my nav bar css is messing up? compare: http://www.starcraftmethod.com/wiki/index.php?title=Main_Page to http://www.starcraftmethod.com/wiki/index.php?title=Zealot to see what i mean.. the left nav bar [04:30:55] If it all goes horribly wrong at least you still have a working setup. :-) [04:31:15] Yeah...exactly... [04:32:29] Looks like you have an issue with those boxes but it's only shown when the page is tall enough to mess it up. [04:32:34] The wiki moving guide though explictly says "You should avoid moving the database from an older version of the software into a newer version; this will not work."...that is why I was a bit aprehensive [04:32:36] The main page isn't so you don't see it. [04:32:54] Well, without an update it won't wokr. [04:33:02] *work [04:33:15] "an older version" might refer to older than a certain revision. [04:33:41] e.g. phase2 to phase3 which was about six (?) years ago. [04:34:01] ah...yeah..just moving the Db will not work...k...got it. [04:39:19] ty got it fixed [04:39:29] Hmm, "Ensure, prior to moving, that any upgrading of the software and database schema is done. You should avoid moving the database from an older version of the software into a newer version; this will not work." <-- that's wrong (or at least out-of-date). [04:40:52] So fixit! [04:40:57] no u. [04:41:01] No wai. [04:44:18] what's wrong about it? there's typically some schema change with every new version [04:44:51] Right: and what's wrong with that? [04:44:58] You move and then you run the update script [04:45:22] I think it could be clarified. You *can* do it after moving, but you must do so before using. [04:45:40] The issue is that many people do not want to touch the old "working" version but instead set up a new version somewhere else. [04:46:33] We should ideally encourage them to do that rather than make them think they have to either upgrade the existing one first (if they can), or load the original version of the software on the new location, copy the database, then upgrade the software to the new version. [04:50:06] we should encourage people to just follow the directions, then we won't have to explain how to fix everything when they come here saying "I decided to do it this way instead and now everything is broke" [04:50:51] FOLLOW THE DIRECTIONS EXACTLY OR YOUR WIKI WILL BREAK. [04:51:22] Something like "You MUST run the database update script when moving between versions, or things will break. Maybe not today, maybe not tomorrow, but soon." [04:52:08] Uh, why would you say that when you could say that they will break? [04:52:47] Special pages. Editing. Some random feature that other people rely on that you don't know about until the day your new site goes live. [04:53:46] I'm not sure why you would use vague hypotheses about what might go wrong rather than simply saying that it will break. [04:54:22] I'm sorry, I misread that as "what would you say they could break", for no apparent reason. [04:54:29] Okay. ^__^ [04:54:36] But to answer your question: because people fear the unknown. [04:54:49] They also get confused by the unknown [04:54:57] If you tell them something might break, but even *you* don't know what it is, they're scared. [04:55:13] But when you tell them something won't work and it does that just makes them less willing to respect your authority. [04:55:22] Which is why the current text is wrong. [04:55:28] Probably no reason to even say "if you're moving between versions"; they won't know whether they are, and it does no harm to run the update script if they're not, so the instructions should always direct them to run it [04:55:59] Yeah. It's not like it's particularly slow if they are, and there might always be a new extension. [04:59:02] So should we recommend that people only transfer customizations and use a fresh tarball? [04:59:51] Well, it doesn't have to be fresh, just not past its sell-by date. [04:59:52] Well, when I read the guide I was under the impression that I had to update the current wiki before moving...since that not the case, maybe that should be changed [05:01:05] GreenReaper: could you actually answer my question, rather than responding with a metaphor? :-D [05:01:51] I'm not really sure where you got that idea, actually. [05:02:05] What idea? [05:02:41] "(GreenReaper): Yeah. It's not like it's particularly slow if they are, and there might always be a new extension." --> this was meant to imply that it was fine and a good idea to always run the database update script. [05:02:55] Yes, we agreed on that [05:03:11] and then I asked So should we recommend that people only transfer customizations and use a fresh tarball? [05:03:13] I don't know where that results in a "so" for the statements you subsequently made. [05:03:19] s/where/how/ [05:03:53] It...doesn't? The "so" was just "so, in terms of what I should actually write in the article..." [05:04:08] OK. So usually means "implies". X, so Y. :-) [05:04:17] So it does. [05:05:18] It's 1AM, so I'm not really up to making good documentation. [05:05:53] I think in the end we just need to be sure they run the update for whatever version it is they do have. [05:06:02] If it's not the right one, they'll probably figure that out soon enough. [05:06:06] Uh [05:06:23] Don't see how a fresh tarball is anything to do with it. [05:06:30] If they want a new version they'll get it one way or another. [05:06:37] SVN is fine. [05:06:50] You don't want to discourage people from using that. [05:07:00] The instructions have to say either "copy all the files from your MediaWiki installation over" or "download a fresh copy of MediaWiki and bring over your configuration files, images, and extensions" [05:07:36] And they shouldn't say both or neither [05:07:42] Both is fine. [05:07:49] Or rather, either. [05:08:00] :| [05:08:03] Since Either will work. [05:08:13] Lots of things will work [05:08:20] But *if* they download a new copy, they *must* run the update script. [05:08:23] That's how it works. [05:09:03] Transfering everything over via carrier pidgeon will also work. The guide is supposed to instruct users on what they should (or must) do, not what they could do. [05:10:07] I disagree. If it wants to say the best way to do something, that's fine. But maybe, for some reason, they don't want to update. [05:10:39] We don't want to say "you can't just copy the files and database over" if they can, in fact, do that. [05:10:45] Then they don't have to follow the directions [05:10:57] But whatever, I'm going to bed [05:11:14] The point is the directions should not forbid something that is possible, which was the problem to start with. :-) [05:11:15] Night. [05:11:27] it wouldn't say "you can't just copy the file and database over": it would simply never mention that option [05:11:56] And that's wrong. Options are good. [05:12:19] Believe me, I know corporate people. If they can avoid an upgrade they will. It is not our job to tell them their jobs. [05:12:22] *Splarka adds "When upgrading, be sure not to put beans in your nose" [05:12:43] We can strongly recommend it, pointing out the security implications of being unpatched. [05:13:01] Like a good article, it's better to show rather than just tell. [05:13:24] "We recommend you upgrade *because* if you don't, Splarka will bite you." [05:13:36] s/will/won't/ for the vores [05:22:00] where is $wgLogo located [05:26:57] in your localsettings.php file, you need to define it though [05:26:57] the var is in localsettings, the file is wherever you put it [05:28:12] where should i type it in [05:28:13] anywhere? [05:31:10] got it workin, thanks [05:31:12] :-) [05:33:52] Hi there. Can anyone help me using the usability enhancements and the vector skin in mediawiki 1.15? Is that even possible? If not, how can wikipedia run it? [05:34:13] Wikipedia is running a special branched copy of the pre-1.16 version. [05:34:36] It commonly runs pre-release but still relatively stable revisions. [05:34:49] Oh. So Vector is not supported in 1.15? [05:35:03] Not really. [05:35:05] Which branch does it run on, and how could I download it? [05:35:06] I don't think so, but you'd need to talk to a vector specialist. [05:35:33] All I'm getting is 'Override this function.' when I try to enable it. [05:35:38] It *should* run on trunk, if nothing else. That's always a little dicey, though. [05:35:56] http://svn.wikimedia.org/viewvc/mediawiki/branches/wmf-deployment/ [05:37:11] Oh, thank you Annemarie and GreenReaper. I'll try to install it from that? [05:37:22] Is that any different than installing from a tarball? [05:37:36] A tarbell is usually a branched release. [05:37:46] wmf-deployment/ has Wikimedia-specific hacks in it. [05:37:50] So you probably don't want it. [05:38:11] Oh. So I should really try it from trunk? [05:38:24] trunk is generally broken [05:38:32] *GreenReaper would personally try trunk first with the understanding that it may be broken in interesting ways. [05:38:37] since wmf's last fork/scap (or whatever the new term will be), there have been 3 branch merges [05:38:58] so right now it is rather unstable, though brion has been doing code review this week, a bit [05:39:01] What's your opinion to a guy trying to deploy the Vector skin cause he liked it *a lot* [05:39:03] ? [05:39:08] wait ^_^ [05:39:11] ¬¬ [05:39:24] Is there a timeline for 1.16? [05:39:38] "quarterly" which can mean 3-6 months (since 1.15) [05:39:38] Sometime this year, I would hope. [05:40:02] It's been about two and a half months [05:40:11] but as Splarka notes, probably best to estimate longer for this one. [05:40:14] you can't really go for the branch in trunk wmf-deployment went off of, because a lot of vector-specific hacks are on top of that, you shouldn't go for live trunk because it is a bit broken, and you shouldn't use the wmf-deployment branch because it has loads of wmf hacks as stated [05:40:43] it is a lose-lose-lose situation for vector fans, though probably trunk is the least crazy option [05:41:25] Well, I love lose-lose-lose situations. Can't get enough of them. :( [05:42:03] well if you pull wmf-deployment branch it should work ;) [05:42:32] 'course, he could have been wrong (blasphemy!) [05:43:04] Well, Emufarmers, they are telling me that I really shoudn't cause of all the wmf hacks. [05:43:09] he's known to have been sarcastic before [05:43:31] http://sarcasmdetector.ytmnd.com/ [05:43:38] readings are unclear; proceed with caution [05:43:41] http://translatewiki.net/w/i.php?title=Special:Version [05:44:11] 03dale * r55365 10/trunk/extensions/OggHandler/OggHandler.php: * moved $wgEnableTemporalOggUrls configuration var from default settings to oggHandler [05:44:18] translatewiki is probably the one of most popular public wikis that run (or tries to) daily trunk [05:44:23] 03dale * r55366 10/trunk/phase3/includes/DefaultSettings.php: * moved $wgEnableTemporalOggUrls configuration var from default settings to oggHandler [05:44:26] Just running trunk up to the point that's been reviewed might be a good compromise [05:45:41] And how can I tell that point? [05:45:52] http://www.mediawiki.org/wiki/Special:Code/MediaWiki?path=/branches/wmf-deployment/&limit=100 [05:45:54] Is there a review log? [05:46:02] here are the "hacks" applied to wmf-deployment since it was forked [05:46:21] as well as live hacks from trunk for the usability team's tests [05:46:35] edufelipe: http://www.mediawiki.org/wiki/Special:Code/MediaWiki [05:46:56] Is having the "this page added to your watchlist" banner dismiss by itself an accessibility issue? [05:47:00] Seems like it'd be handy. [05:47:19] http://www.mediawiki.org/wiki/Special:Code/MediaWiki?path=/trunk/phase3/&limit=2000 [05:47:43] Splarka: should be a more elegant way to see... [05:48:02] Does encoding work on that URL? [05:48:40] what are ya bitching about now? [05:48:49] are the slashes breaking your precious IRC client? [05:48:53] I'm just curious by nature. [05:48:57] No, the link works fine. [05:49:06] heh [05:49:10] And, I was more curious about dismissability. [05:49:11] Thank you guys. So helpful! [05:49:14] Hmm, but there will still be fixmes in between, so that's not really a guarantee of safety [05:49:41] Emufarmers: if you were '''bold''' you could put scapmap into MediaWiki:Common.js [05:49:54] so anonnies could use it [05:50:02] It doesn't work for me, remember? :( [05:50:14] MediaWiki is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [05:50:16] nope, I don't remember, [05:50:21] You get no guarantees, no matter what you do. [05:50:37] 'cept a good time. That's always a constant. [05:50:55] You get no guarantees from the distributor; you can get a guarantee for some things from an individual :) [05:52:20] a cement-masonry friend gives three guarantees about his cement work: it will dry, it will crack, and nobody will steal it [05:53:01] Now, if it were limestone . . . http://dwarf.lendemaindeveille.com/index.php/Planepacked [05:59:17] Emufarmers: Do you get any errors in your error log? [06:01:10] http://www.mediawiki.org/w/index.php?title=Extension:DumpHTML&curid=26391&diff=272236&oldid=271653 Ooh, the spammers are getting good [06:02:06] We have some not-so-smart but very persistent ones on our Czech wiki, of all places. [06:02:26] AbuseFilter is quite effective there. [06:02:31] [06:04:21] *GreenSleeper throws http://en.wikifur.com/wiki/Vixen_jokes at Emufarmers. [06:05:45] Not only are they stereotypical, they're also very bad. Although the 10 cent one has merit. [06:06:26] "Why did the vixen wear condoms on her ears? So she wouldn't get Hearing Aides." <-- Neither AIDS nor "hearing aids" has an e [06:06:31] well, except in "hearing," obviously [06:07:03] But I can't edit it :( [06:07:09] Denied! [06:07:13] STOP PERSECUTING ME [06:07:19] *fursecuting [06:07:50] You can edit it on the new site, http://en.wikifur.com/w/index.php/Vixen_jokes [06:07:55] Though you probably shouldn't. [06:08:23] Because I hope to lead a normal life? [06:09:11] *GreenSleeper finds the relative difference in page size amusing. [06:09:19] Well, it's a little late for that, don't you think? [06:09:31] Besides, who'd want to be normal, anyway? [06:09:49] how do u upload a file? i cant find it like the tutorial or w/e says [06:12:16] found it [06:12:28] how do i unlock uploads? [06:13:17] !uploading | jjiiiiiiilothar [06:13:17] --mwbot-- jjiiiiiiilothar: File uploads are an often-used feature of MediaWiki, but are disabled by default in all current release versions. To enable them, first make the upload directory (default images) writable by PHP, then set $wgEnableUploads to true in LocalSettings.php (i.e. "$wgEnableUploads = true;"). See for more info. [06:17:33] thanks [06:17:59] the php.ini i need to edit is located in wiki folder or somewhere else on server? [06:25:10] nvm ty! [06:47:56] 03siebrand * r55367 10/trunk/extensions/UsabilityInitiative/EditWarning/EditWarning.i18n.php: Fix syntax error in r55363 [07:52:00] 03(mod) Changing SITENAME of ckbWiki - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=20295 (10aso.mehmudi) [08:30:15] 03(NEW) Add distinct class for ISBN special links - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=20318 trivial; Normal; MediaWiki: Page rendering; (mathias.schindler) [08:44:17] *Splarka ponders giving hotchip a +b *chip!*nunya@*.dsl.austtx.sbcglobal.net!##fix_your_connection [08:45:31] 03(ASSIGNED) Add distinct class for ISBN special links - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=20318 (10raimond.spekking) [08:49:08] Hi all, is there a command-line way to setup a MW database if I already have a LocalSettings.php? [08:50:02] Command-line or whatever, as long as it can be automated and non-interactive :-) [08:54:04] you could try the upgrade script, but i'm not sure it will create it [08:54:30] if not just move your localsettings and then re run the installer and then move localsettings bacl [08:54:32] *back [08:55:00] I tried "php maintenance/update.php --conf .../LocalSettings.php", but it gets confused with itself. [08:55:53] It tries to rename the user table to mwuser, but there's no user table yet. [08:56:44] Also, I think it ignores my schema settings, and the sequences it creates are in the "public" schema rather than the one I'd like to confine the wiki to. [09:13:47] 03raymond * r55368 10/trunk/phase3/ (RELEASE-NOTES includes/parser/Parser.php): * (bug 20318) Distinct CSS classes for ISBN/RFC/PMID special links added [09:15:27] 03(FIXED) Add distinct class for ISBN special links - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=20318 +comment (10raimond.spekking) [09:41:36] hmm, hotchip: 62 joins/parts in 10 hours, not really spam unless the chan is quiet otherwise, but plz fix connection ^_^ [09:52:20] Can Mediawiki work with table prefixes rather than schemas, if I want several independent wikis in the same database? [09:55:54] 03dale * r55369 10/trunk/phase3/js2/ (12 files in 8 dirs): [09:55:54] * minor css fixes [09:55:54] * fixes to inline uploads [09:55:54] * stubs for recent uploaded asset import listing [09:58:39] Lo-lan-do: yes, set http://www.mediawiki.org/wiki/Manual:$wgDBprefix in your LocalSettings.php [09:58:59] SPQRobin: Excellent, thanks. [10:04:22] 03(NEW) Rough toolbar display on zhwiki using IE - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=20319 major; Normal; MediaWiki: Vector Skin; (xu.jimmy.wrk) [10:04:58] Except… "This setting is not used if your database is Postgres". [10:05:34] 03(mod) Rough toolbar display on zhwiki using IE - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=20319 (10xu.jimmy.wrk) [10:06:30] Oh well. Food first, database later. [10:29:24] 03dale * r55370 10/trunk/phase3/js2/mwEmbed/ (5 files in 4 dirs): [10:29:24] * slightly better sequencer css layout. [10:29:24] * now to fix the mismatched selectors *****I hate kskin right now**** [10:31:25] i read that as kissing at first =/ [10:31:36] what would cause "printfooter" to have no content ? [10:35:05] thedj: blank retrievedfrom perchance? [10:37:00] Splarka: as in the translation string ? [10:37:23] well, the system message, yah, MediaWiki:retrievedfrom [10:38:36] not blank, but not working either it seems. [10:38:49] $printfooter = "

\n" . $this->printFooter() . "

\n"; [10:38:49] function printFooter() { return "

" . $this->printSource() . "

\n\n

" . $this->pageStats() . "

\n";} [10:38:49] function printSource() {$url = htmlspecialchars( $this->mTitle->getFullURL() ); return wfMsg( 'retrievedfrom', ''.$url.'' ); } [10:39:01] yeash. [10:39:06] what an idiots. [10:39:17] who where? [10:39:23] seriously, nl.wp is the most technically incable bunch of wikipedians. [10:39:37] heh [10:40:07] they speak four languages and smoke pot, whatcha expect in an encyclopedia [10:40:51] thedj: well, it looks blank to ME, heh [10:41:03] *Splarka guesses that yeash was for " " [10:41:56] thedj: do you have editinterface globally yet? [10:42:00] no [10:44:44] thedj: http://translate.google.com/translate?hl=en&sl=nl&tl=en&u=http://nl.wikipedia.org/wiki/Overleg_MediaWiki:Retrievedfrom&prev=hp [10:45:26] > I make the text empty, until a solution. Jeroenvrp August 9, 2004 02:49 (CEST) [10:47:08] Splarka: i posted to their tech VP. [10:47:31] "all prints are copyright violations" :D that should get their attention. [10:49:05] "dude, chill, wait, what?" [11:00:01] 03(mod) Vector adds wikiprintable.css but like monobook does not require it. - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=19801 (10hartman) [11:11:28] 03philip * r55371 10/trunk/phase3/languages/LanguageConverter.php: Save the variant find from HTTP_ACCEPT_LANGUAGE to $mPreferredVariant, so we do not need to do it again. [11:14:16] 03(mod) Rough toolbar display on zhwiki using IE - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=20319 +comment (10liangent) [11:16:34] 03philip * r55372 10/trunk/phase3/languages/messages/MessagesZh_hans.php: Set linkTrail for Chinese language. There is no character should be appended to a titlelink in Chinese wiki. [11:38:05] 03dale * r55373 10/trunk/phase3/js2/mwEmbed/ (5 files in 4 dirs): * kskin final state before revert for presentations [11:40:58] Is there a way to convert HTML to wiki-format? [11:44:09] sounds ugly [11:46:02] 03philip * r55374 10/trunk/phase3/languages/LanguageConverter.php: Fixed some of tests failed caused by r55371. [11:50:49] PupenoG: toolserver.org/~diberri/cgi-bin/html2wiki/ [11:52:20] * http://openfacts2.berlios.de/html2wiki/ [11:52:26] p858snake: thanks! [11:52:51] how can i access the categories of an article? i.e. which class provides access to them so i don't have to parse the wikitext manually [11:57:16] hiya. i'd love to convert a lengthy page from Textile -syntax to MediaWiki -syntax. can anyone think of a tool for this? [11:57:51] 03dale * r55375 10/trunk/phase3/js2/mwEmbed/ (3 files in 2 dirs): * partial revert to 55208 (pre kskin) [12:03:28] 03(NEW) Some pages won't open on Russian Wikinews - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=20320 normal; Normal; Wikimedia: General/Unknown; (Ruslik00) [12:05:34] 03dale * r55376 10/trunk/phase3/js2/mwEmbed/skins/ctrlBuilder.js: * restored control Builder as wel [12:06:27] 03yaron * r55377 10/trunk/extensions/SemanticMaps/SM_Mapper.php: Added necessary getName() function [12:07:15] tekonivel-o: There's something called wikicreole. I never tried it, but it may help. [12:14:26] 03dale * r55378 10/trunk/phase3/js2/mwEmbed/skins/mvpcf/styles.css: * skin revert [12:16:13]