[04:15:22] New patchset: Pastakhov; "fix Leaflet problem with resource loader" [mediawiki/extensions/Maps] (master) - https://gerrit.wikimedia.org/r/49202 [08:53:53] New review: Jeroen De Dauw; "Patch Set 1:" [mediawiki/extensions/Maps] (master) - https://gerrit.wikimedia.org/r/49202 [09:30:49] New patchset: Pastakhov; "fix Leaflet problem with resource loader" [mediawiki/extensions/Maps] (master) - https://gerrit.wikimedia.org/r/49202 [09:33:44] New review: Pastakhov; "Patch Set 1:" [mediawiki/extensions/Maps] (master) - https://gerrit.wikimedia.org/r/49202 [14:25:18] I have a page that shows up in a concept list and is found in the search box, but isn't found on a form in a combobox field that uses the concept. Other pages in the same category are found in the field. Any idea what might cause that? [14:27:41] have you waited some time? [14:29:38] Yes, quite a while. And it's an older page. While doing this I did an Admin data repair and the page is there now... so now my question is, how often (or for what reason) do admins run the data repair function, or something else to keep things healthy? [14:31:00] do you mean repair or update? [14:31:20] oh, wait [14:31:22] it's the same [14:31:24] yes [14:31:35] I never do that [14:31:59] if I made a lot of changes to templates that set properties, I usually run runJobs.php by hand [14:32:56] I had a lot of problems like the one you are having right now. Usually it helps to create a smaller form/template with the same thing in it and debug that [14:33:09] doing #ask format=debug might help aswell [14:33:23] Yes, me too. Plus I'll do it if things "seem slow", even though that might be a network issue. [14:33:43] also a lot of times I just changed stuff and changed it back to make things work ;) [14:35:04] That's how I'd usually debug it, but in this case it had the right context to show up on the concept page, and now it's working. Weird. I'd almost guess db corruption, but I don't know enough about the inner workings to know how likely that is. [14:35:56] I guess I'll mark it as something to look out for, thanks [15:34:04] is there any performance gain when I use concepts instead of direct queries? [15:41:09] sven^: there should be, yes - there's less querying involved on the back end. [15:43:47] ok, I now create a cache for my concept and set the $smwgQConceptCacheLifetime to 10 minutes [15:44:08] *created [15:44:16] let's see what happens [15:46:57] I have a page with 7 #ask of which 3 now use the same concept [15:47:03] page load time is unchanged [15:53:54] when exactly are queries updated? [15:54:31] I mean, how long are they cached? [16:40:22] sven^: as far as I know, queries aren't cached - only the set of pages in a concept is cached. [16:40:37] The query still has to go out and assemble the results. [16:41:37] But if you mean that a query involving a concept takes the same amount of time as the same query without a concept, that's strange. [16:41:59] The difference might be just too small to measure. [16:58:03] hmm, having some issues seting up a query, but not sure how to explain: I want to create a table with properties, however I don't think I can use an #ask for this. right now I can return the pages I need using a #show, but this gives the arraymap that contains these values. [17:01:22] basically we have user-pages and projects. and users can subscribe to projects by putting the pagenames in an arraymap in their template. [17:02:11] now I just want to generate a nice table with projects and their properties on the user-pages [17:02:49] I must be overlooking something. but can't figure it out [17:05:32] and I can't use {{#ask: [[Category:Projects]] [[ProjectParticipants::{{PAGENAME}}]] }}, since this property on the project-page is filed using an #ask to the user-pages! seems a bit of a chicken<->egg problem :P [17:06:34] I can return the bare arraymap using: {{#show: {{PAGENAME}}|?Working_on}} though, but I'm not sure how I could generate the table from this [17:10:20] dreamer: try this: {{#ask:[[-Working on::{{PAGENAME}} |?property1 |?property2 }} [17:10:50] Oops - I missed a "]]" in there. [17:11:01] After "{{PAGENAME}}". [17:13:36] what magic is this o.O [17:14:28] The darkest. :) [17:14:33] somehow I knew it would be some trivial solution using some esoteric function :D [17:17:28] is this documented somewhere? [17:19:10] The inverse-query thing? I'm sure it is, somewhere. [17:19:24] Probably in the "Help:Inline queries" page, or one of its subpages. [17:20:28] http://semantic-mediawiki.org/wiki/Help:Inverse_properties << this? [17:22:37] interesting. and now it totally makes sense :D [17:22:39] thnks man :) [17:22:57] as you can see I was nearly going to pull out my brain ;) [17:23:24] Well, I'm glad I could help avoid that. :) [17:23:46] haha, awesome. I'm sure this is going to be usefull in other ways too :) [17:23:54] ok, now to write this up in a nice template ;) [18:26:55] yaron: uhm... There is a reload option on the page header which refreshes queries. as far as I know queries are not instantly "requeried" when the data changes [18:27:42] Yes, that's true... that's not a query cache, that's just the MediaWiki page cache. [18:27:54] That one usually lasts for about 24 hours, I think. [18:29:52] uh ah [18:30:00] can I just make that time shorter? [18:30:26] if I add __NOCACHE__ to relevant pages pageload time goes up from 2s to 8s [18:30:54] I'm pretty sure there's a way to set the cache expiration, but I don't know it. [18:31:37] I mean, it's acceptable to have 8s pageload time every 10 minutes or so, while displaying "old" data for 24h is not [18:31:43] kk, I'll google it [23:38:31] hmm, odd thingy: on my own userpage I can use {{PAGENAME}} as is, but within a template we just made it doesn't work o.O [23:38:50] doh, I know why :)