[00:18:28] Guess it's time to get a more modern and robust nginx config for mediawiki [00:20:19] okay, order of rewrite rules was off. [01:54:04] what options are there for totally replacing the presentation of the category page? [01:59:15] drobbins: "Don't do it" is hopefully one of them. :) [01:59:52] You might need to create an extension for that - I'm not aware of any existing functionality that does it. [02:01:55] Okay. I guess the typical approach is to create an alternate page with a different presentation and use that as the primary link, such as in the sidebar. [02:05:32] Oh yeah, that's the much easier option. [02:06:06] You can use the "category" SMW format to simulate a category page - although if you want to do a complete overhaul, that might not be useful. [02:14:53] I think the most logical way to add an extension for this is to have some kind of magic word that will suppress the category listing on a category page. [02:14:57] like __NOCATEGORY__ [03:00:17] Yaron: can you think of a way to have a template conditionally expand something only for the first semantic internal object? For example, imagine a bunch of log entries, but the top one represents the current status, and you want that stored semantically in the main page. [03:01:24] You could do an #ask query with "limit=1", I suppose... [03:02:09] I have done this before, for an historical list of user roles. I would have the template only store the semantic data if the end date was not specified (ie. it was a current user role) [03:02:33] Sure - whatever works. [03:02:59] what I am trying to figure out is how to create an auditing log for a document. Something higher-level than the page history, to track version numbers of the doc, and approval and implementation status. [03:04:34] What's the difficulty there? [03:04:53] Yaron: well, let me ask this way. Is there a way to retrieve the top internal sub-object as defined on a form? [03:05:26] Yaron: I guess there is a position stored somewhere? [03:05:47] Well, there was just a discussion about this on the semediawiki-user mailing list - I don't know if you saw that one. [03:06:10] I don't think it's too hard. I am defining wiki pages of proposals. The proposals need to be revised, approved, and then some will be implemented. So the log is there to track this process. [03:06:17] I didn't. [03:07:08] Well, the most foolproof way may be to have another field, for the status or something, that can be "Current" or "Past" or what have you. [03:07:49] That would especially make sense if there are more than two statuses. [03:09:23] Yes, the user experience is okay but not wonderful, as it requires manually keeping those set. And ensuring you don't have two both set to current. [03:11:24] I guess it's just two possible statuses, then. [21:41:52] Yaron: is there a good way to use SMW to create tree structures, like for sections/chapters of a book? [21:42:16] Yaron: I imagine I could figure some approaches, but wondering if you're familiar with any existing approaches [21:43:26] Well, sort of - you could have a page for each section/chapter, each one with a "Parent" field/property, pointing to its parent. [21:44:06] You would also need an "index" field, though, indicating whether it's the 1st section, the 2nd, etc.; and that's where it gets tricky. [21:44:37] Was thinking of something like a SMW reimplementation of the Collection extension. [21:44:51] That could be interesting. [21:45:00] Having [[Category:Book]] and then have a form to choose sub-objects that link to chapters. [21:46:04] I can play around with ideas. [21:46:28] Yes, you could link from parents to children... it's usually better to go the other way, but maybe not for every case.