..." basically the

break

block has been moved outside of the preview area [05:40:42] That ok, or would that be a regression? [05:41:17] sounds fine to me [05:41:40] mkay... that was the only other difference [05:42:17] There are no more ui regressions so I'll fix and recommit [05:56:47] 03dantman * r40066 10/trunk/phase3/includes/EditPage.php: [05:56:47] Recommit the EditPage changes: [05:56:47] Thanks for the heads up brion. $attribs was being overridden in EditPage::showTextbox rather than having individual things set which caused the tabindexes inputted to be ignored. Your test case is fixed. [05:56:47] I did a page diff, there are no more ui regressions. The only difference is the preview-toolbar

has been moved from the inside of the preview to outside of it. There's no real difference in that. [05:58:03] hello, i moved over a wiki from one server to another, anytime i click basically anything i get "Warning: session_start() [function.session-start]: open(/home/users/web/b872/ipw.insomnia-consulting/phpsessions/sess_1acd1e9c78ecd043156389f19f694cd9, O_RDWR) failed: No such file or directory (2) in /var/www/www.pghcodingdojo.org/htdocs/includes/User.php on line 627" [05:58:23] i can't seem to find the settings to fix this [05:58:50] looks like an issue with your php session settings [05:59:36] sessions work fine with everything else, just not media wiki [06:03:41] 03(mod) tag cannot be rendered correctly when more than one tags are in the same line - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=15333 summary (10liangent) [06:04:25] Dantman: Parse error: syntax error, unexpected T_DOUBLE_ARROW in EditPage.php on line 1505 [06:04:43] Agh.. checking [06:05:10] Sorry bout that [06:05:23] I fixed on my webserver, then redid the same locally... [06:05:30] cept I forgot to remove the > this time [06:06:52] 03dantman * r40067 10/trunk/phase3/includes/EditPage.php: Minor error... sorry bout that, forgot to remove the > when I redid the fix locally. [06:07:16] fixed [06:08:17] :/ [06:13:28] 03dantman * r40068 10/trunk/extensions/StringFunctions/StringFunctions.php: Committing Juraj Simlovic's updated StringFunctions.php code. [06:13:52] Dantman: stringfunctions is deprecated. [06:14:03] Whatsthat? [06:14:19] AFAIK stringfunctions was merged into parserfunctions [06:14:29] brion reverted that [06:14:29] TimStarling: or did that get reverted? (stringfunctions being in parserfunctions) [06:14:33] o rly [06:14:35] why? [06:14:59] He took one look at the code, and said he found them to be etremely memory inefficient [06:15:07] That's what the stringfunctions update is about [06:15:18] everyone work on krimpet's lua extension instead [06:15:23] Someone did some work to try and make it more memory inefficient [06:15:59] Though, I'm not completely confvinced it's good... it's probably, better, but still not pfunc worthy [06:16:02] TimStarling: brion doesn't like that. [06:16:13] I talked to him the other day about it. [06:16:58] brion would like it if we had some kind of support for external mediawiki installations [06:17:11] like abuse filter :/ [06:17:34] he wants me to rewrite the parser before it goes live. [06:17:38] but if that's the only thing holding it back, it's going to become a pretty weak excuse [06:17:39] erm, the PHP one. [06:17:56] texvc doesn't work on safe_mode shared hosts either [06:18:27] you can't implement LUA in PHP.. that's insanity. [06:20:45] 03(mod) Install the StringFunctions extension - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=6455 (10dan_the_man) [06:24:40] <_wooz> lo [06:31:45] ^_^ heh... creating a dom-diff engine is going to be tricky when I have little knowledge of diff algorithims [06:33:34] look up longest common subsequence problem. [06:33:44] or just derive from a generic implementation. [06:44:33] 03(mod) some pages are delivering raw GZIP encoding - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=15149 (10tk1b) [06:46:01] 03aaron * r40069 10/trunk/phase3/includes/DefaultSettings.php: Add $wgPhpCli var so shell outs know what exec name to use [06:47:11] Dantman: just do a text diff [06:47:21] if you want it to ignore whitespace, strip the whitespace first [06:49:16] hmmm [06:49:23] Well it's more than that' [06:49:33] I wan't to ignore attribute location differences [06:49:53] you can normalise that. [06:49:57] ie: type="text" accesskey="," vs. accesskey="," type="text" should output the same [06:50:02] but it's ugly. [06:50:02] 03(NEW) Bad rendering - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=15334 normal; normal; MediaWiki: Page rendering; (liangent) [06:50:24] We'll see [06:50:26] yeah, normalising will be easier than writing a diff algorithm for the tree [06:50:47] hhmm... right... ^_^ doms are trees... [06:50:48] heh [06:51:05] Mkay.... [06:51:08] you can use one of the XML parsers to give you an appropriate view into the tree [06:51:13] Mhmm [06:51:14] and use that to output a normalised form [06:51:42] I'll use a xml parser to output into a kind of special format showing only the relavant data line by line and sorting things... then a simple text diff will show differences [06:51:57] sounds good [06:52:57] But first... the murder of a frozen block of ground beef needs my attention.... ((cue meniachal laughter...)) [06:53:26] 03aaron * r40070 10/trunk/extensions/FlaggedRevs/ (14 files in 2 dirs): [06:53:26] * Add some urlencode calls and refactor ugly link code [06:53:26] * Add some HTML escaping [06:53:26] * On windows, use NUL:, not NUL [06:53:26] * Use wfShellExec() [06:53:27] * Let $wgFlaggedRevsStatsAge be set to false to disable stats updates [06:53:29] * Move some message loading to constructors [06:54:09] thanks Aaron [06:57:14] 03(mod) DISPLAYTITLE doesn' t always work when current revision is sighted - 10http://bugzilla.wikimedia.org/show_bug.cgi?id=15330 (10dapete.ml) [07:08:28] mmm... any chance to have a preference to set a max number if diff lines to attempt to render... [07:08:45] preferences need to be fixed. [07:08:54] (those damn overflow table cells can be so slow to load) [07:09:15] ((and there is little indication in the byte change to indicate how bigg the diff will be)) [07:09:58] morning [07:10:20] if/of,gg/g [07:20:07] simple question, but how do I link from an image to a different article (i.e. not to the image)? [07:20:18] !imagelink [07:20:18] --mwbot-- Image linking is intentionally not supported in MediaWiki, so access to the image's description page is always available. If you need image links, see for methods and information. One way to achieve this is . [07:20:32] omnivibe: ^^ [07:20:40] o_O thanks! [07:23:23] *Splarka still thinks that should be (default off) optional in core [07:23:59] [[Image:foo.png|link=[[bar]]|baz]] [07:36:46] PLEASE?!? And have it work with class="icon-click". [07:36:53] *Lady_Aleena gets on her knees and begs. [07:37:15] *AaronSchulz loves Apache [07:37:35] (the melody) [07:38:39] 03nad * r40071 10/trunk/extensions/SimpleSecurity/SimpleSecurity.php: bug fix: userCanReadTitle not accounting for $wgPageRestrictions [07:38:52] Splarka: I tried and implemented it once, but it didn't seem to work well, so I dropped that patch [07:39:32] doh [07:43:10] oooh icon extension works great! :) [07:43:13] thanks [07:45:28] time for scap? [07:46:08] as long as EditPage.php is ok [07:47:08] Dantman tells me it make the same HTML now as the old one [07:47:25] don't worry, I haven't committed anything since the last scap :) [07:47:59] I've got something big in a few days, though. [07:51:39] mm nice, MediaWiki:Loginlanguagelinks doesn't support html entities [07:51:54] Relatively the same [07:52:00] The DOM isn't really different [07:52:39] There might be a whitespace difference... the

has moved from inside the preview to the outside... and a few attributes may have their locations inside the tag reorganized [07:52:40] The MediaWiki: namespace makes me very sad. [07:52:45] say guys is there a way to edit the navigation block without manualy editing its html on the skin file? [07:52:57] kfir: MediaWiki:Sidebar [07:53:13] !sidebar | kfir [07:53:13] --mwbot-- kfir: To edit the navigation menu on the left, edit [[MediaWiki:Sidebar]] using its special syntax. For more details, see . [07:53:32] thanks :) [07:59:33] hi - is there a technical description of the mediawiki-syntax? [08:00:14] i like to implement the syntax in perl for my app [08:00:30] Well, there's Parser.php... [08:00:32] !syntax | jegade [08:00:32] --mwbot-- jegade: For help with MediaWiki's Wikitext syntax, please see . For an (incomplete) formal specification, see . [08:00:32] 'unportable' [08:00:42] !parsers | jegade [08:00:42] --mwbot-- jegade: For alternative parsers, see . A new formalization and parser for mediawiki syntax is being discussed on wikitext-l, see . For an (incomplete) specification of mediawiki syntax, see . [08:00:54] jegade: easy to get to 90%, impossible to get 100% [08:01:15] 90%? made up number? ^_^ [08:01:33] yes. 78% of all figures are made up. [08:01:35] I'd say, more like 5% (not counting plain text) [08:01:35] Duesentrieb: great list [08:01:48] [[Link]] is impossible to parse, for example, without the full database [08:01:59] Splarka: bullshit. [08:02:07] class="new" or not? [08:02:09] Heh. [08:02:11] image? category? [08:02:13] interwiki? [08:02:15] you can't tell [08:02:20] Splarka: that's not parsing. [08:02:21] Splarka: you can parse that, you just can't output necessarily. [08:02:30] exactly [08:02:31] Splarka: you need configuration, not database access. [08:02:31] Heh. [08:02:35] i need only basic text-formatting, links, images and tables [08:02:40] Bull [08:02:48] you need database to class="new" or not [08:02:53] config won't help much with that [08:02:57] yes, that's for *output* [08:02:59] Depends what the goal of the parser is. [08:03:01] not for *parsing* [08:03:02] Splarka: but that's not PARSING, that's RENDERING. [08:03:03] the two are distinct. [08:03:05] bah [08:03:16] well, the SHOULD be distinct :) [08:03:18] well what about {{foo}} ? [08:03:25] jegade: that should be doable. [08:03:38] if Template:foo exists, your *parsing* is different than if it isn't [08:03:44] because itself might contain code to parse [08:03:48] jegade: it gets complex when you get into templates, and impassible when you get into parser functions [08:04:09] and extensions muck it up nicely [08:04:18] jegade: also note that image links have a special syntax, and for recognizing image links, you need to know the wiki's config. [08:04:32] So do other odd variables like HTMLTidy and server versions... [08:04:43] jegade: but if you don't want to parse stuff from an existing mediawiki, but just want to implement a largely compatible subset, that's not so hard. [08:05:02] jegade: the nasty bit is the edge cases people rely on :) [08:05:12] 03(FIXED) Change configuration for autopromotion on de.wikipedia.org - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=14975 +comment (10JSchulz_4587) [08:05:14] tag extensions, parser hook extensions, free text hooks, localizations for namespaces, unpredictable interwikis, partially unpredictable interlang, listed external link protocols... ugh [08:05:28] Splarka: yes. [08:05:57] Splarka: write a parser for existing wikipedia content? UGH! write a parser suporting a compatible subset for use with your own prog? not a biggy. [08:06:00] jegade: you might consider hooking into the API with action=parse of whatever wiki you want to do [08:06:01] Duesentrieb: i create the rules :-) - so people must live with my parser [08:06:17] what wiki is this for? it has to be for some wiki [08:06:36] Splarka: core discussion board. or cms. or something [08:06:37] otherwise you must be highly masochistic to want to mess with mediawiki syntax [08:06:49] *Splarka grins [08:06:51] Splarka: again, a compatible subset is no problem [08:07:30] sure, but the subset is vanishingly small [08:07:30] jegade: look at the (incomplete) formal spec if you want, but it's probably better to just go by the usage help/tutorials and cover the most used features. [08:07:34] 95% of text, maybe [08:07:41] 50% of used syntax maybe [08:08:01] it all depends on what you want to do with it [08:08:02] but on en.wp, quite a lot of individual markup is reliant on extensions, config, and db [08:08:22] yes, sure [08:08:38] though... not that much for parsing. for rendering, yes. [08:08:39] so, my made-up 5% might be '' ''' {| |- || [[, while every template, magic word, parser function, and tag extension is the rest fo the 95% [08:08:50] there are not that many templates that produce parts of syntactical constructs [08:08:52] arr [08:08:54] and those are the main problem [08:09:15] dues: I would say the difference in parsing [[Foo]] and [[Image:Foo]] exists, not just rendering [08:09:22] Splarka: for most people, paragraph separation, '', ''' and links is all they need. maybe * and # too. [08:09:23] but depends where you draw the line [08:09:40] Duesentrieb: thanks for your help [08:09:42] Splarka: yes, image links need to be parsed differently, because they can contain nested links. [08:09:48] exactly [08:09:58] Splarka: and to identify them, you need to know namespace names. this is one of the nastier bits. [08:09:59] so you can't predict what localisation the image namespace might have! [08:10:01] whenever you parse, you parse for a *purpose* [08:10:13] yah [08:10:16] Splarka: you don't need to predict it. [08:10:20] You can say "I'm parsing the text out of this text" [08:10:22] well [08:10:25] jegade: have fun. [08:10:27] Duesentrieb: I mean you can't assume it [08:10:29] $parsed_output = array( $text ); [08:10:33] you have to check, or know [08:10:35] Splarka: you don't have to assume it either. [08:10:43] you do for a generic parser [08:10:53] who said something about a generic parser? [08:10:53] which de-facto can't exist until major changes come about [08:11:09] why, I believe jegade did ^_^ [08:11:38] *Splarka wonders what convo Duesentrieb was having [08:11:40] you guys probably scared him off. [08:11:56] all I was doing was saying it was more impossible than you were saying it was [08:12:05] 5% possible vs 90% possible [08:12:07] no, he said somethign about implementing mediawiki syntax for his own use. not for usse with existing wikitext. and not necessarily without special config. [08:12:30] Splarka: you're just throwing up roadblocks, which can mostly be worked around, or aren't show-stoppers. [08:12:34] Splarka: depends on what you base the numbers on. [08:12:45] Werdna: road blocks are usually for a reason [08:12:54] prefer to have people drive into the steamrollers? [08:13:01] which is why I had the second clause of my statement [08:13:03] Splarka: number of pages that don't use any "nasty" features? number of syntactical constructs? whatever. [08:13:03] Dues: as said, all made up [08:13:07] they can be worked around, or aren't show stoppers. [08:13:28] hello [08:13:33] Splarka: sure. there's no measure here. only an impression. [08:13:35] whatever. [08:13:37] Werd: sure, but then they are only approx, unless you work from a vanilla install [08:13:48] from a specific revision... [08:14:02] and specific default configuration [08:15:15] Splarka: ... he just wants links, images and tables! [08:15:24] heh [08:15:33] Image: namespace localized? [08:15:38] that can make a big difference [08:15:49] Presumably, he won't be setting up his software with an 'image' namespace. [08:15:58] I would imagine that he'd use the image-url syntax. [08:16:05] anyway, I actually requested action=render in the API (later changed to action=parse, which did the same thing but with more info passed, which again confuses the difference between the two) so Wikia could make a better wikiwyg, based in wikicode and not html [08:16:20] even if it's localized, it's perl. just make it an option. [08:16:23] no problem. [08:16:30] and outlined to Bartek how it could be used [08:16:50] eg, parsing all [[links]] as some neutral color live and periodically batch checking them to render red/blue [08:16:58] 03nad * r40072 10/trunk/extensions/SimpleSecurity/SimpleSecurity.php: comments [08:17:06] and all {{}} as temporary placeholders waiting for next ajax hit to the action=parse [08:17:15] (I think he gave up on it though) [08:20:28] 03nad * r40073 10/trunk/extensions/SimpleSecurity/SimpleSecurity.php: remove debugging [08:20:55] Splarka: how's fckeditor at wikia coming along? [08:21:26] no idea, been about a year and a half since I was interested in that X_X [08:21:35] *Splarka pokles JSharp [08:22:01] eep [08:22:13] I once wished for a syntax hilighter mode that could be used along with it, and a raw code view, I think Datrio still worked there at the time though [08:22:20] indeed, thought it's getting some attention [08:22:36] I'm not on the project so I'm not quite sure [08:22:36] is it wikicode based or still html based? does it use the API? [08:23:35] nau [08:32:15] *Dantman|Food wanted a syntax highlight mode to [08:33:53] Tim tried to make an expandtemplates mode with associative mouseover twixt code <--> output, IIRC.. I wished it had worked:/ [08:34:56] Dantman|Food: WikEd does that, though you have to click abutton to make it update the highlighting. it's also a bit slow. btu it's a start. [08:35:13] Mhmm [08:35:25] I was just wanting something inside the FCKeditor [08:35:52] A nice compromise that could make keeping wysiwyg enabled nice for even advanced users [08:36:15] well, modifying FCKE towards wysiwym would be nice. you know, mixed markup, highlight and formatting. [08:36:27] Also... I wanted a keyword you could add to a page to force wysiwyg mode off on a page... [08:36:29] when you type == foo == it gets formatted as a heading, but you still see the == [08:36:52] I like the idea of a mix [08:37:42] would be nice if fck understood closing tags [08:38:09] ie... when you type the ]] on a [[link... it backtracks and checks to see if it can convert that into a link [08:41:52] one of the things that pisses me off with wysiwyg editors: the often automatically link stuff, but it's really tricky to unlink. and often impossible without using the mouse. [08:42:00] an editor that forces me to use the mouse is useless [08:42:28] i do use the mouse for some things, but i should never have to. [08:43:12] <_mary_kate_> Duesentrieb: without using fck, i think basic syntax highlighting would be nice [08:43:17] <_mary_kate_> the way vim formats HTML [08:43:36] yes, something like that [08:43:55] foreground colors for different markups... [08:44:06] background colors for different depths (especially on {{ {{ {{ {{ {{) [08:44:11] maybe even a bit more. like formatting == foo == as an actual heading. [08:44:24] and possibly an indent preview mode for {{}} [08:44:34] Splarka: i like the idea of background colors. well, one color, but going darger when you go deeper, or something [08:44:35] <_mary_kate_> well, vim is limited by being a terminal app, but a textarea could do proper headings and stuff [08:44:44] yea [08:44:56] Dues: well, one for [[]], which is only two deep, in Image links.. [08:45:04] one for {{}}, say darker shades of red... and one for html maybe [08:45:08] WikEd goes into that direction, but isn't quite it [08:45:33] and if it did nothing but hilight it'd be sweet [08:45:48] Splarka: {{ and {{{ yes. and image links can be nested indefinitly (though whoever does that should be taken out and shot) [08:46:00] mmm, bang [08:46:46] just need to replicate the preprocessor in javascript [08:47:23] or do we... someone go rewrite the preprocessor in javascript, and then write a php interpreter to use it, then we can use it native, (cue Werdna throwing rocks at me) [08:47:39] *Werdna duly throws rocks at Splarka [08:47:44] ow [08:51:39] 03(mod) Technical updates to bs.wiki - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=13451 (10demicx) [08:52:51] Hi [08:52:58] Can anyone tell me why via the API I get only a trunkated version of the comments? and not the hole text in there? [08:53:28] URL? [08:54:58] http://commons.wikimedia.org/w/api.php?action=query&titles=Image:Capillarity.svg&prop=imageinfo|categories&iiprop=timestamp|user|comment|url|size|sha1|mime|metadata|archivename|bitdepth&iiurlheight=200&iiurlwidth=200&format=xml [08:56:51] TimStarling: I do something wrong? [08:58:15] the comment there appears to be a truncated version of the content, which is normal [08:58:28] http://commons.wikimedia.org/wiki/Image:Capillarity.svg <-- truncated there too: ...Author=[[us) [08:58:54] 03(mod) diff messages i18n problem - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=15299 (10bugzilla.wikimedia) [08:59:03] under "file history" [08:59:04] (autosummary) [08:59:36] anyone ever pondered giving image uploads a separate comment field? [08:59:53] seperate, even [09:00:32] bit counterintutive... the textarea is the comment and the content for new uploads, but only the comment for reuploads [09:00:54] Splarka: I see now that is trunkated also on the page ... [09:01:04] alecghica: isn't really truncated.. what happens is... [09:01:23] separate, right the first time [09:01:26] the summary field on uploads is used for the content, license info and such, but the first ~250 bytes of that is used for the upload summary [09:01:51] if everyone could spell, wiktionary would be pretty useless [09:01:57] oh wait, it is, except english [09:02:13] almost no other languages have such a thing as a "Spelling Bee" [09:02:23] although the french have a gameshow based on conjugating verbs [09:02:40] well, english is intermediate, as languages go [09:03:04] the spanish have a game called tortuga [09:03:06] some are phonetic, some are historical, some are so historical that it's like learning a different language when you write [09:03:15] between what? a language and random keystrokes? [09:03:21] ahh [09:03:38] chinese people often have to learn a different language when they write, for instance [09:04:04] "Most languages borrow from other languages. English follows them down dark alleys, knocks them over, and goes through their pockets for loose grammar. [09:04:09] and in arabic there are several regional forms [09:04:35] TimStarling: huh? I thought the grammar is pretty much the same for Chinese [09:04:43] from what I've seen of it, french spelling is easily as hard as english [09:04:50] spoken language is quite natural for our species, no remote isolated tribe has ever been found without a spoken language, writing is counter-intutive [09:05:25] Nikerabbit: spoken chinese is divided into about a dozen mutually unintelligible dialects [09:05:58] Splarka: I understand now ... to rephrase my question ... is there a way via the API to get the full description from summary? :) [09:06:04] sure [09:06:08] but does written chinese have different grammar from spoken? [09:06:19] not if you happen to speak mandarin [09:06:29] http://www.shlomifish.org/Files/files/code/mediawiki/mw-fix-inc-Search-t.patch - please apply this patch - it fixes t/inc/Search.t . [09:06:32] but if you speak any of the other dialects, there's going to be differences [09:07:19] prop=revisions&rvprop=contents probably easiest [09:07:20] Splarka: you saw my API URL earlier? what i do wrong? [09:07:25] http://commons.wikimedia.org/w/api.php?action=query&titles=Image:Capillarity.svg&prop=revisions&rvprop=content [09:08:23] I am not sure if you can combine it with your previous query [09:09:25] heh, I managed to answer an email about wikimedia in french the other day. [09:09:31] somebody emailed me about toolserver in french. [09:09:47] Splarka: thx, thats what I needed :) [09:10:42] # 20:15 brion: set wgNewUserSuppressRC to true, was false unsure why it's annoying <-- brion has an ethical objection to commas. [09:11:04] Nikerabbit: this is one of the reasons why we have zh-min-nan.wikipedia.org [09:11:44] because some people in Taiwan think it's unfair that they have to learn a new grammar in order to write [09:22:00] Hi all. [09:22:01] http://www.shlomifish.org/Files/files/code/mediawiki/mw-fix-inc-Search-t.patch - please apply this patch - it fixes t/inc/Search.t . [09:24:06] rindolf: credited to who? [09:24:16] TimStarling: Shlomi Fish. [09:25:44] 03tstarling * r40074 10/trunk/phase3/t/Search.inc: Patch by Shlomi Fish to fix this test [09:26:15] TimStarling: thanks. [09:27:25] thanks for fixing it [09:27:40] but I'm sure you know, it's a drop in the ocean as far as testing goes [09:30:24] Hj, im newbie, can u help me install Mediawiki? [09:30:45] !installation | tuantrinh85 [09:30:45] --mwbot-- tuantrinh85: Installing MediaWiki takes between 10 and 30 minutes, and involves uploading/copying files and running the installer script to configure the software. Full instructions can be found in the INSTALL file supplied in the distribution archive. An installation manual can also be found at . See also: !download [09:31:01] ok [09:31:09] but i install again [09:31:20] and find bugg, [09:31:48] pls Can u see http://tracuu.tainguyen.vn/wiki [09:33:06] tuantrinh85: without a more detailed description of the problem you are running into, and how you got there, there is no way to help you. [09:33:23] *tuantrinh85 slaps siebrand around a bit with a large trout [09:36:02] I have got bug in wiki [09:36:10] im install again but can not find file index.php in dir config [09:36:17] but i see index.php and type parameter [09:36:24] pls help me [09:37:45] U can click button "Install Mediawiki" and see bug 406 [09:37:48] tuantrinh85: which webserver are you using? [09:38:00] i use linux [09:38:05] U can click button "Install Mediawiki" and see bug 406 [09:38:10] tuantrinh85: have you properly configured PHP for it? [09:38:43] im havent got server, i use hosting in server services [09:38:55] tuantrinh85: HTTP Error 406 - Not acceptable ? [09:39:33] I can install complete firts, but second, im istall again not complete [09:39:40] huhu i dont know [09:39:58] tuantrinh85: you are referring to "bug 406". What "bug 406"? [09:40:13] huhu i dont understand Error 406? [09:40:52] because on one server, i isntall complete firts [09:41:03] because on one host, i isntall complete firts [09:41:38] but install again, error 406? [09:42:23] i chmod 777 dir "config", not complete, [09:42:33] An appropriate representation of the requested resource /wiki/config/index.php could not be found on this server. [09:42:33] Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request [09:42:49] tuantrinh85: I am at work and I am having understanding the exact problem you are having. I hope someone else is able to help you. [09:43:09] huhu [09:43:35] sounds like an apache/php configuration error. but no clue [09:43:36] pls, Can u know some poeple know error? [09:43:38] (and lunch time) [09:43:51] oh [09:44:31] but im not system manager, i dont edit config [09:44:49] What doing now Duesentrieb? [09:45:53] What doing now Duesentrieb? [09:45:55] HEY [09:46:04] HELP ME, DUESEN [09:46:27] tuantrinh85: please don't beg like that. [09:46:42] It is unlikely to endear you to developers, who, after all, aren't being paid to help you. [09:47:11] As he said, he went to lunch. It would be unreasonable to expect a volunteer to delay their lunch to help you with your problems, especially if you shout at them for "ignoring" you [09:47:31] oh noes [09:49:18] yeah [09:53:51] How are links with class="external free" generated? [09:55:59] I am trying to output some HTML of the form and it's getting turned into http://X"> [09:56:03] And that is fucked up. [10:00:10] davidmccabe: what revision are you on? [10:02:54] 03mkroetzsch * r40075 10/trunk/extensions/SemanticMediaWiki/includes/ (SMW_GlobalFunctions.php SMW_Settings.php): move array of available formats from GlobalFunctions to Settings where they belong [10:04:06] Gah... [10:05:05] TimStarling: It's nice and fancy now... it works with xml quite nicely... cept.... aaagh, when I throw it output from MW it gives me xml errors that make no sense [10:05:26] davidmccabe: http://svn.wikimedia.org/viewvc/mediawiki?view=rev&revision=39980 seems like some parser changes have been wheeled back and forth, so you just need to be in the right revision to not have it happen (?) [10:08:14] Thank you Splarka. [10:08:44] I am on 37740 fwiw. [10:08:53] hey davidmccabe [10:09:13] yo werdna. [10:09:21] david: might not be related then, these seemed to be in the last week [10:09:45] ooh, we're up over 40k. [10:09:55] davidmccabe: I rearranged liquidthreads to be more like a mediawiki extension, btw [10:10:06] Werdna: more like... a mw extension? [10:10:07] used the autoloader, refactored classes, etc [10:10:09] Dantman|Food: mmm can you give me some food too [10:10:18] heh... [10:10:20] werdna, sounds good. thansk for mentioning it. [10:10:22]