[00:00:31] thats a very reasoned opinion, similar to your opinion of michael jackson [00:00:41] "one plastic dude is "dead" and everyone needs to edit about this?" "it sucks & so does M$" [00:02:14] i wish it were msie that had died instead [00:02:27] lol [00:02:57] now i would assume that the addportlet code worked in IE6 - it was written a few years ago [00:03:44] ive even grabbed the resulting innerHTML to compare and the only differences is that my portlet doesnt have id's for each list item and the standard ones have lang="en" xml:lang=en for each h5 [00:04:08] but i can't find any logic in any of the css based on list id's or h5 lang's [00:05:39] all i can think is their might be some msie fixup css hidden somewhere [00:06:11] but - did you try my suggestion? try IE6/7/8 [00:06:16] the visual differences are that the generated portlets lack the white box around them and their h5s are much too big [00:06:35] i only have access to ie6. sorry i missed your comment [00:07:09] you're using addPortletLink right? [00:07:12] im rolling my own portlet code too. the only "standard" portlet code i saw just added a list item not a whole portlet [00:09:39] the code is part of this wiktionary extension: http://en.wiktionary.org/wiki/User:Hippietrail/nearbypages-alpha.js [00:43:31] anyone here know how to combine phpfox and mediawiki? [00:49:43] Are there any mediawiki user groups in the San Francisco Bay area or silicon valley? [00:50:45] (searching on google for "mediawiki" user groups gets' lots of stuff about setting user group permissions... [00:52:05] http://www.mwusers.com/ looks like a good resource. [00:52:08] I don't think there are any MediaWiki user groups anywhere in real life. [00:52:13] http://en.wikipedia.org/wiki/Wikipedia:Meetup/San_Francisco [00:52:16] God, what would you discuss? The parser? [00:52:30] Uses of the pipe trick? [00:52:55] Lead pipe to the head of vandals? ;-) [00:53:57] I"m actually looking for technical writers in the bay area that are familiar with wikis - there's lots of best practices to share and learn about organizing your writing for wikis. (topic based writing, etc.) [00:54:40] GreenReaper: Thanks! Two meetups this year - that's encouraging. [00:55:38] The people who attended them might be interested, you could drop them a note on their talk pages. [00:55:51] Whoops, that's for wikipedians... [00:56:02] still, you are right about that. [01:28:47] test [01:29:26] west [01:29:57] best [01:30:51] jest [01:31:07] fest [01:32:02] apple [01:33:39] Oh my. Simetrical is poking the bear. [01:33:53] (Regarding your wikitech-l post.) [02:48:49] did $wgHooks['UserLoadFromSession'] get changed recently? [02:49:12] 03yaron * r52430 10/tags/extensions/SemanticForms/REL_1_7_2/: Tag for version 1.7.2 [02:52:39] mshadle: http://svn.wikimedia.org/viewvc/mediawiki?view=rev&revision=34772 ? [02:54:12] odd, so im using what supposedly is the newer one. [02:54:56] 03yaron * r52431 10/trunk/extensions/ReplaceText/SpecialReplaceText.php: Fix for search strings for page titles containing spaces [02:54:57] $wgHooks['loadFromSession'][] = 'Custom_Authentication'; [02:55:03] so would that work then? [02:55:07] this worked previously [02:56:11] is mediawiki suited for use by a single person as a way to organize information with a pretty interface? [02:56:31] no, but everybody does it anyway [02:56:52] do you have a better suggestion? [02:57:23] well, it'll work fine, it is just rather heavy [02:57:44] heavy? resource hog? steep learning curve? [02:58:08] yes, all that [02:58:11] Pretty much all of the above. It's not intended as a single user CMS [02:58:20] are you going to put it on the web? [02:58:43] no... [02:58:55] i'm essentially going to be using it as a personal LIMS for grad school [02:59:10] what OS/platform? [02:59:23] 03yaron * r52432 10/trunk/extensions/ReplaceText/ (README ReplaceText.php): New version: 0.6.5 [03:00:21] Linux [03:00:27] specifically TinyCoreLinux [03:00:50] i was thinking about making one with python since i just finished reading a book on it [03:01:56] well, probably the best reason to use MediaWiki for such a project is if you are already familiar with it [03:02:19] i'm having to read a book on it to become familiar with it since my current lab manager insists on using it as a lab-wide LIMS [03:02:44] (which is a big reason why it gets (ab)used for blogs, news aggregation, forums, support, documentation, CMS, and lots of other weird stuff) [03:03:11] spvensko: ever edited a page on Wikipedia? [03:03:16] there is actually a company that is basically doing what i'm trying to do [03:03:18] no [03:03:55] http://blog.bioteam.net/tag/wikilims/ [03:05:08] 03yaron * r52433 10/tags/extensions/ReplaceText/REL_0_6_5/: Tag for version 0.6.5 [03:06:30] well, that might be a rather good reason to install a personal mediawiki, so you can learn how to use it without experimenting on the lab's install [03:07:17] it's actually been suggested to use the lab's install [03:07:29] as we are experimenting with integrating programs into it currently [03:09:01] from what this book was saying it sounds like mediawiki is higly refined, lightweight, etc. etc. but i guess that may just be propaganda [03:10:22] for the #8 website in the world, it is highly refined and lightweight [03:10:45] a few dozens of machines and two or three million a year [03:10:47] well i meant the actual client :P [03:11:33] but compared to a text editor it is a medium sized whale [03:11:56] ha [03:12:42] Splarka, ;) and if you include extensions it's the full deal [03:14:28] though if you want a combination of a pretty skin, a view/edit UI that a large fraction of the population of the planet has dealt with at some level, full versioning of all changes to infinity, and extendable in the sense that, for most of the things you might want to do with the data or UI, there is probably an extension to do just that somewhere... [03:15:26] oh hell.. the thing is, people often come in and say "convince me to use MediaWiki" and then later "you aren't selling this very well", the problem is, the developers don't really care that much if people use it or not [03:16:05] most are volunteers working from their own agenda or from the Wikimedia perspective, and the few paid or contracted ones from WMF are all paid for by a non profit org [03:16:54] I suppose a few people have a stake in the popularity, like Wikia developers... the more people that start to use MediaWiki, the more popular wikis they can import (as there will be a bigger pool) [03:17:06] [03:20:22] I dunno, the more people using it, the less need there is for their services in general. [03:22:50] GreenReaper: well, for example, say a fan site is going to set up a wiki for their fandom [03:23:09] As more people gain MediaWiki experience, you end up with more WikiFurs striking it out on their own. Which I think we can all agree is a terrifying idea, but there you go. ;-) [03:23:13] if they choose mediawiki, and find their host bogged and db bloated, they can easily be brought into Wikia [03:23:42] yes yes, the transformers left too, heh [03:24:31] They forgot to take the Source with them! [03:24:49] what do you guys think about Extension:Lua? [03:25:01] Or the Allspark or whatever they call it. [03:25:18] It seems easy enough to read. certainly an improvement over ParserFunctions/StringFunctions [03:25:40] i have been writing some of the nastiest looking PF statements lately. they are only surpassed by the ones you can find on the english wikipedia [03:25:56] has anyone tried this extension? or knows how to code in Lua? (looks to be quite basic) [03:26:27] If your code is that complex, you might be better off writing your own extensions. [03:26:38] that's not a viable solution for community websites [03:27:37] and there are lots of trivial-seeming situations that you shouldn't have to extend mediawiki for [03:28:38] in fact, asking people to extend mediawiki is dangerous as compared to them using a sandboxed interpreted language within mediawiki itself [03:28:49] extending mediawiki is in invitation for introducing security vulterabilities [03:32:52] 03shinjiman * r52434 10/trunk/extensions/DynamicPageList/ (10 files): [03:32:52] Update the DPL codebase to 1.8.6. [03:32:52] code based on Gero aka Algorithmix [03:57:04] I'm having a strange issue where, when I change the wgLogo to my chosen logo, the whole mediawiki home page doesn't load [03:57:13] what's likely to be the problem? [03:58:43] Missing a ' or a ; [03:59:07] that is, the LocalSettings.php is now an invalid PHP file so it crashed. [03:59:39] yeah, that would be it [03:59:40] thanks [03:59:44] No problem. [03:59:54] You can get more detailed errors if you turn them on. [03:59:55] I can see why MW is the most popular wiki [04:00:03] elapsed setup time, 18 minutes [04:00:40] anyway, you just helped the San Francisco Open Data Project, so you can feel good about it [04:00:41] thanks [04:00:58] No problem. [04:01:32] Useful debugging statements [04:01:41] error_reporting(E_ALL); [04:01:41] ini_set('display_errors', 1); [04:01:41] $wgShowExceptionDetails = true; [04:01:53] but probably best not to have them enabled all the time on a public wiki. :-) [04:02:16] They have to be above where you actually run into a problem - I normally put them at the top of LocalSettings.php [04:08:26] 03(mod) Make section edit links more usable/understandable - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=11270 +comment (10public) [04:09:40] 03(mod) Make section edit links more usable/understandable - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=11270 (10public) [04:09:43] Splarka: ^ [04:14:54] *Splarka wonders wtf is confusing about section [edit] [04:15:19] yes, saw the revert, but that is only temporary [04:15:28] until Simmy and Roan can figure it out [04:16:13] 03demon * r52435 10/branches/maintenance-work/ (38 files in 3 dirs): [04:16:13] * Rename addParam() to addOption() for consistency [04:16:13] * Port rebuildall (refreshLinks not done, only partially works), rebuildtextindex, rebuildrecentchanges, populateCategory, deleteArchivedRevisions [04:16:13] * Go back to using $self as a b/c way for $maintenance->getName() [04:16:20] hmm [04:16:20] [21:46:57] (Silly Trevor, using child selectors as though this were 2009 instead of 2001.) [04:16:21] [21:47:54] They . . . kind of don't work in IE6. :) [04:16:31] I reported they don't work in IE5 actually, do they not work in IE6 too? [04:22:34] heh [04:23:10] i hate ie6 [04:23:22] GreenReaper: thanks [04:23:45] yeah, using brand new things that are barely even implemented in Safari and Firefox probably isn't a good idea for a skin meant to be usable [04:23:55] i cannot track down why portlets created by js don't look like the normal ones on ie but do on other browsers [04:24:28] 14(WFM) The
/
tag around GeSHi-highlighted code does not have a class "source" - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=11274 +comment (10herd) [04:25:12] hippietrail: where is such an example of a native/js portlet? [04:26:06] Splarka: the ones i refer to as native are generated by the normal php code. the ones i refer to as js are ones im making with js code i wrote [04:27:03] yes [04:27:04] where? [04:27:07] wiktionary? [04:28:19] yes [04:28:47] http://en.wiktionary.org/wiki/User:Connel_MacKenzie/Preferences [04:29:19] turn on "Add links to previous and next pages." and "Use the preferences set on this page" [04:30:10] then go to any normal page [04:32:10] 03(mod) Upgrade to the latest version of GeSHi (1.0.8) - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=10967 (10herd) [04:32:52] gods ... too many skins [04:32:58] *agliodbs decides not to skin [04:32:59] good night [04:35:12] hippietrail: too much work, can you make a minimal test case? [04:35:28] also per 10967, why is it so hard to understand [04:35:32] *Splarka stabs everyone [04:36:21] Splarka: probably not right now. im on holiday with only a 7 inch netbook )-: [04:36:28] *hippietrail stabs msie6 [04:36:31] sigh [04:36:38] okay, where is the code for the new portlets? [04:37:36] http://en.wiktionary.org/wiki/User:Hippietrail/nearbypages.js [04:38:28] line 137 [04:39:34] mmm, hmm [04:40:03] have you tried with/without IE60 fixes? (obviously it would be horribly broken, but wondering if that would expose the diff) [04:40:17] ah actually thats the production code that was coped from somewhere else and is missing part of the portlet structure anyway [04:40:57] i copied the portlet code from another js extension that adds links to other wiki projects in the navbar [04:41:22] but a true portlet has two divs. class portlet and class pBody [04:41:32] well [04:41:41] a "true" portlet also has the generated sidebar class thing too [04:41:53] on my dev branch of the code i try to do it right and it ends up even worse even though the dom looks better [04:42:08] and there is a reason all the sidebar portlets have that extra class [04:42:41] .generated-sidebar, #p-tb, #p-lang, #p-search {} [04:42:55] will grab all sidebar portlets, excluding logo, personal, cactions [04:43:10] without having to apply to all .portlet and remove from logo/personal/cactions [04:43:13] aha [04:43:30] so possibly that is a reason too [04:43:35] not sure ^_^ [04:44:09] im sure the code i copied from got into the same trouble and their hack solution was to leave out the portlet div and instead add their pBody div to the previous portlet [04:44:22] X_X [04:44:28] yes indeedie [04:44:33] thanks for finding it for me [04:44:41] I did nothing but make you look at it [04:44:47] but sometimes that is the best tech support [04:44:54] ive rolled portlets with js before and they worked but the code and the css evolves over the years [04:45:08] i looked at it but i was blind (-: [04:45:08] btw, you have IE6? [04:45:45] yeah no space to upgrade to 7 or 8 on my netbook with ms giving you no choice of app install path [04:45:58] does IE6 support css child selectors? [04:46:08] but since its the lowest common denominator i kinda need it for this type of evil work [04:46:09] or, at least, does it not explode into firey death therein? [04:46:17] nope, IE5 is the lowest [04:46:24] i dont know. i dont really speak css [04:46:24] as proven by the existence of IE50Fixes.css [04:46:31] heh [04:46:38] well, try this CSS if you can [04:46:45] a simple logo hider, one might see [04:46:56] odd that the js portlets looked fine on every non ie browser [04:46:56] #p-logo > a {display:none;} [04:47:27] this means,