[00:11:12] sparr: you might need to create pages for all those properties first; I'm not sure. [01:02:42] oh [01:02:51] my non-subobject properties on that page also aren't showing up on the Properties page [01:02:56] maybe my namespace isn't being indexed? [12:12:18] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#682 (regression-110 - 9266d37 : mwjames): The build has errored. [12:12:18] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/compare/7f9904010a87^...9266d3793022 [12:12:18] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17335711 [15:53:48] neither the main page properties or the subobject here are getting indexed. do I need to do something specific to index a custom namespace? http://olywiki.asciiking.com/wiki/index.php?title=Item:Wood&action=edit [17:06:16] sparr: yes; see http://semantic-mediawiki.org/wiki/Help:Configuration#smwgNamespacesWithSemanticLinks [17:07:10] thought so. I *think* we've set that [17:07:30] I've made a namespace called Item [17:07:50] will the identifier for that automatically be NS_ITEM or is there some other step I need to take or info I need to gather? [17:09:38] No, you would need to set NS_ITEM in LocalSettings.php to be the appropriate number. [17:10:26] where do I get that number? [17:10:51] nm, found it. http://olywiki.asciiking.com/wiki/api.php?action=query&meta=siteinfo&siprop=namespaces [17:11:16] I should put a link to that somewhere. I'm confused that it isn't available as a special page already [17:13:10] I don't know if there's a real need for it... the relevant number (504, it appears) is presumably in your LocalSettings.php file already. [17:22:59] is there a way to get the API to spit out the configuration variables, such as $smwgNamespacesWithSemanticLinks, so I can make sure they are set correctly? [17:27:14] we think we've set it correctly now, but it's still not indexing [17:28:48] http://pastebin.com/kN4h1pnn [17:32:03] got it [17:32:06] just took time! [17:32:13] and editing the page in question to make it re-index [17:32:17] is there a way to force re-indexing? [17:45:56] sparr: I don't believe so. [18:29:29] I have a bunch of hidden semantic propertiestags on a page and I don't want the newlines around them to insert empty space into my rendered document. Is there a tag I can wrap them all in to crush the whitespace? [18:31:37] (PS1) Yaron Koren: New version: 1.3.1 [extensions/SemanticDrilldown] - https://gerrit.wikimedia.org/r/108710 [18:32:23] Are you using templates? [18:33:33] Well, in any case, the easiest solution is to remove the newlines. [18:34:01] (CR) Yaron Koren: [C: 2 V: 1] New version: 1.3.1 [extensions/SemanticDrilldown] - https://gerrit.wikimedia.org/r/108710 (owner: Yaron Koren) [18:34:03] (Merged) jenkins-bot: New version: 1.3.1 [extensions/SemanticDrilldown] - https://gerrit.wikimedia.org/r/108710 (owner: Yaron Koren) [19:02:20] Yaron: removing the newlines makes the source annoying to read. I know I can put html comments around the newlines to fix it. Might do that. [19:03:24] http://olywiki.asciiking.com/wiki/index.php/Item_table <-- this has begun working, but was missing a lot of data. now I've started a Data Repair from Special:SMWAdmin and there is a second entry for every row in that table [19:03:30] with #_QUERYblahblah at the end of the page url [19:22:41] the data repair is finished, and the #_QUERY lines are still showing up, probably because there's a query on every one of those pages [19:22:58] how can I exclude queries from queries? :) [19:47:26] when sorting a table by a boolean property, blank/empty is sorted as equivalent to false. is this intentional? how can I prevent it? [19:59:57] and sorting by number equates zero to blank [20:54:22] http://olywiki.asciiking.com/wiki/index.php?title=Special:SearchByProperty&offset=0&limit=100&property=Item+weight&value=300 [20:54:28] why does "nearby" only include greater values? [21:15:06] When I create multiple subobjects if I give them the same name then it acts like I created one subobject with multiple of each type of named parameter. Is there a way to avoid this? My dumb approach is to just append a number to the name of the subobject, but that's not ideal in terms of querying [21:19:29] sparr: you shouldn't give names to subobjects; the first argument to #subobject should be "-". [21:19:36] err... [21:19:48] the docs say that giving them a name is an option, and something I can query against later [21:20:10] if I don't give them a name then will this problem go away? that didn't even occur to me [21:20:48] Yes, it will. [21:21:05] Yeah, it's a dumb option - if I had designed #subobject, I wouldn't have included that option. [21:23:12] I'll give that a try [21:23:28] to identify different types of subobject, I should give them some property unique and always-defined for that type? [21:23:51] can subobjects have subobjects? [21:44:27] sparr: I would recommend adding to each subobject call a property pointing to the page it's on. [21:44:53] Like "|Is recipe for={{PAGENAME}}". (I recall you had something with recipes.) [21:45:06] I don't think subobjects can have subobjects. [21:45:10] recipe was just a hypothetical example [21:45:43] the link back to {{PAGENAME}} is superfluous, because I can query for subobjects of a specific page, right? and it's dangerous if I transclude the page! [21:46:03] http://olywiki.asciiking.com/wiki/index.php?title=Item:Cyclops&action=edit [21:46:06] that's one of the pages in question [21:52:04] Well, up to you. [22:11:51] http://olywiki.asciiking.com/wiki/index.php?title=Item:Wood&action=edit