[05:27:14] New review: Tbleher; "This change (verified by git-bisect) causes a fatal error on my wiki: " [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/15627 [05:44:30] New review: Mwjames; "It would seem that the problem described by Tbleher is not directly related to this change but due t..." [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/15627 [05:49:16] New review: Tbleher; "The specific query that fails is" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/15627 [07:47:22] Hi, [07:48:27] Does someone know what is going on with http://smwplus.com? Just downtime or something else? [07:51:52] Hi, Have anyone experienced runJobs.php to produce "Timeout yy" when it tries to refreshLinks in page that has very heavy Semantic Query? In some pages in my wiki, query and rendering the page may take up to 10-15 seconds due complex queries [07:52:38] I tried to google solution for that with no luck [08:00:25] New patchset: Nischayn22; "Proper sorting of properties in Special Properties" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/16007 [08:05:09] New patchset: Nikerabbit; "Update Norwegian translations of datatypes" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/16008 [08:06:41] New review: Nikerabbit; "Btw this file should be renamed from 'no' to 'nb' to match MediaWiki core changes." [mediawiki/extensions/SemanticMediaWiki] (master); V: 0 C: 0; - https://gerrit.wikimedia.org/r/16008 [08:12:29] New patchset: Nischayn22; "Fixing errors in hooks and bug 38418" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/16010 [08:37:36] Change abandoned: Nischayn22; "submitting better change soon" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/16007 [08:38:18] New patchset: Nischayn22; "Proper sorting of properties in Special Properties and no default limits`" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/16012 [10:46:22] New patchset: Nischayn22; "Sanity for UnusedProperties" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/16018 [13:57:02] Good morning, folks. Can anybody help me figure out why pages created by some forms aren't using all (or in some cases ANY) of the properties which I built the forms to use? [14:01:50] What defines the properties used by the data in that page? The template used by pages in that category, or the field names in the page? [14:02:17] Ah, apparently it's the template. [14:08:42] nischayn22: can you add me as reviewer to the commtis you want me to review? [14:08:51] So....on the template, I have a few entries which are supposed to use properties, but which honestly don't have to, because those properties aren't called by any #ask statements....at least not yet. [14:10:31] I'm not sure i can put the square brackets into the parser functions that I'm using to format that data for output, however. Like with #arraymap.....can I? [14:16:49] Apparently I can't do it in the #time parser function. #arraymap seems to handle it. [14:18:19] New review: Jeroen De Dauw; "Nike, is your -1 actually blocking this? kgh can delete it from twn, so I guess not?" [mediawiki/extensions/SemanticForms] (master); V: 0 C: 0; - https://gerrit.wikimedia.org/r/15906 [14:26:02] New review: Jeroen De Dauw; "I just looked at this again and really need some more info to fix this, as I'm not able to reproduce..." [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/15627 [14:26:04] New review: Kghbln; "I deleted the message yesterday. I just have to make sure that it stays like this until this change ..." [mediawiki/extensions/SemanticForms] (master) C: 1; - https://gerrit.wikimedia.org/r/15906 [14:29:24] Change merged: Jeroen De Dauw; [mediawiki/extensions/SemanticForms] (master) - https://gerrit.wikimedia.org/r/15906 [14:43:49] New review: Jeroen De Dauw; "Definitely looks a lot more sane! :) Waiting for markus for ok" [mediawiki/extensions/SemanticMediaWiki] (master); V: 0 C: 1; - https://gerrit.wikimedia.org/r/16018 [14:54:27] New review: Markus Kroetzsch; "This can never work on bigger wikis. See inline comments. I don't see how this could be fixed withou..." [mediawiki/extensions/SemanticMediaWiki] (master); V: 0 C: -1; - https://gerrit.wikimedia.org/r/16018 [15:14:44] New review: Jeroen De Dauw; "After having a closer look and discussion with Markus, I think an alternative approach is needed, as..." [mediawiki/extensions/SemanticMediaWiki] (master); V: 0 C: -2; - https://gerrit.wikimedia.org/r/16018 [15:16:35] JeroenDeDauw: Ah, I forgot to add anyone to review today was in a hurry [15:18:34] New review: Markus Kroetzsch; "I added another inline comment, but its true that the discussion would better happen elsewhere than ..." [mediawiki/extensions/SemanticMediaWiki] (master); V: 0 C: -2; - https://gerrit.wikimedia.org/r/16018 [15:49:01] New review: Jeroen De Dauw; "Passing protected fields to hooks is not an issue." [mediawiki/extensions/SemanticMediaWiki] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/16010 [15:49:03] Change merged: Jeroen De Dauw; [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/16010 [16:07:58] New patchset: Nischayn22; "Proper sorting of properties in Special Properties and no default limits`" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/16012 [16:39:41] Change merged: Jeroen De Dauw; [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/16012 [17:19:02] New review: Tbleher; "I added the following code:" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/15627 [17:22:49] New review: Tbleher; "BTW: Thanks for responding so fast :)" [mediawiki/extensions/SemanticMediaWiki] (master) - https://gerrit.wikimedia.org/r/15627 [17:27:55] Hi, I got myself confused with property names and field names. I think I filled out a few semantic forms to have a property "Has summary" with field "Summary". Now for one page that worked, "sfgFieldProperties":{"Aisle/Paradigm[Summary]":"Has summary"}, and for others I get "sfgFieldProperties":{"Aisle/Use Case[Summary]":""}. Is there anything I can inspect or fix, or something I done stupid? [17:51:50] New patchset: Mwjames; "(bug 38504) Adds new result printer flot time series" [mediawiki/extensions/SemanticResultFormats] (master) - https://gerrit.wikimedia.org/r/16047 [17:51:51] New patchset: Mwjames; "Fix some messages" [mediawiki/extensions/SemanticResultFormats] (master) - https://gerrit.wikimedia.org/r/15762 [17:58:11] New patchset: Mwjames; "(bug 38504) Adds new result printer flot time series" [mediawiki/extensions/SemanticResultFormats] (master) - https://gerrit.wikimedia.org/r/16047 [18:16:26] New patchset: Mwjames; "(bug 38504) Adds new result printer flot time series" [mediawiki/extensions/SemanticResultFormats] (master) - https://gerrit.wikimedia.org/r/16047 [18:39:37] New patchset: Mwjames; "Fix some messages" [mediawiki/extensions/SemanticResultFormats] (master) - https://gerrit.wikimedia.org/r/15762 [18:42:44] mozPike - that sounds like a bad idea; you're setting the same property for two different fields on a page? [18:44:15] Yaron: nope, different pages (Use Case vs Milestone), but both have a summary that's Text. Or supposed to be Text, the one with "" seems to fall back to String [18:45:14] mozPike - I don't know, but I'm guessing that in the page that doesn't work, SF isn't able to make the connection between the form field and the property. [18:45:35] In that case, you can manually do it, by adding "|property=..." to the {{{field}}} tag. [18:50:27] {{{field|Summary}}} -> {{{field|Summary|Has summary}}} ? [18:50:36] that's in the form? [18:52:01] {{{field|Summary|property=Has summary}}} [18:52:32] ah, that seems to help, thanks [18:58:40] Change merged: Jeroen De Dauw; [mediawiki/extensions/SemanticResultFormats] (master) - https://gerrit.wikimedia.org/r/15762 [19:09:25] New review: Jeroen De Dauw; "Outdated dependency: you can create a new branch from master and then cherry pick this change and do..." [mediawiki/extensions/SemanticResultFormats] (master); V: 0 C: 0; - https://gerrit.wikimedia.org/r/16047 [19:13:30] New review: Foxtrott; "I wanted to try this out before approving it, but I just do not find the time." [mediawiki/extensions/SemanticFormsInputs] (master); V: 0 C: -1; - https://gerrit.wikimedia.org/r/13875 [19:21:05] New patchset: Mwjames; "(bug 38504) Adds new result printer flot time series" [mediawiki/extensions/SemanticResultFormats] (master) - https://gerrit.wikimedia.org/r/16047 [20:15:16] Guys, I'm having fits getting a template to work with properties when I'm formatting the output. I don't want a date property to show the way it's being stored, so I'm putting it through the #time function to format it. [20:15:38] But when I put in the [[Property1::{{{Property1}}}]] format as an argument in #time, it doesn't work. [20:16:11] How else can I get the [[Property1::{{{Property1}}}]] syntax into the template without having it show in the template output, per se? [20:16:27] It doesn't work inside the tags, for obvious reasons. [20:17:09] I've got another one that doesn't work when given in that format as the test string of #if [20:17:49] Well, more accurately, the test string works, but the string isn't treated as a property when I browse the properties on the page output. [20:18:09] Any ideas? [20:18:33] [[Property1::{{{Property1|#time something}}}]] ? [20:19:15] I'd try the alternative display post |, but I'm doing semwiki for the first day, so I might very well be clueless [20:20:17] Alt text won't work unless the string is empty, I thought, and it would be some kind of recursive rendering anyway, wouldn't it? [20:24:30] I'm almost thinking I need a template for the time rendering, but I'm not sure that the property would be treated as such as an argument to the template, either. [20:25:05] {{formattime|[[Property1::{{{Property1}}}]]}} [20:30:58] [[Property1::{{{Property1| {{#time: Y m d | {{{Property1}}} }} }}}]] is my guess, but I don't have data to test that against [20:49:43] uncleben I am doing it like this: [[Property1::{{{Property1|}}}|{{#time:Y-m-d|{{{Property1}}}}]] The Y-m-d may of cause be changed as desired. mozPike's proposal may work too. This has indeed to be tested. [20:56:36] Hrm....ok. Let me try that. [20:59:53] kghbln: I'm pretty sure that mozPike's idea would only work if {{{Property1}}} was empty in the first place. [21:00:36] And then it wouldn't have {{{Property1}}} to parse through the #time function. [21:01:21] uncleben Ah ok, yes. My solution works for sure since I use it that way for over a year now [21:08:43] kghbln: ok, so your solution worked like a charm for the #time [21:08:54] Not so much for another property I've got. [21:09:18] It's odd because there are nested parser functions [21:09:41] it should be a property of datatype date [21:11:53] This last property is a string [21:13:03] ah the date one is working, the string one does not, hmm ... how to reformat a string property [21:13:42] Is this possible? I do not think so O_o [21:13:45] Well...it's a little ugly [21:32:39] kghbln: {{#if: {{{StringProperty}}} | ({#arraymap:{{{StringProperty}}}|\n|@@@|:@@@|\n}} | {{#ifexpr: {{#timel: U}} <= {{#time: U | {{Date|}} | Nothing happened yet | Nothing to report }} }} [21:32:49] Like I said. Ugly. [21:35:04] Basically, if there is something in the string, I want to parse it through #arraymap to print. If it's emtpy, I want to determine if it's earlier than a specific date, and print one message if so, and one if not. [21:36:51] Hu, I have never done such a thing O_o [21:37:34] If I try something like your trick and do [[StringProperty::{{{StringProperty|}}}|{{#arraymap:{{{StringProperty|}}}|\n|@@@|:@@@|\n}}]], it actually prints twice, and has square brackets printed with it. [21:38:04] Ouch [21:38:38] yeah, and it still doesn't show up as a property of the template [21:38:51] O_o [21:40:20] Meanwhile, I also have {{#if: [[StringProperty1::{{{StringProperty1|}}}]] | [[StringProperty1::{{{StringProperty1|}}}]] | Some alternate output }}, which does work for the property. [21:40:28] I know it's not necessary, I just did it to test. [21:40:43] What about the mailing list? Since I am not the sharpest knife in the draw I cannot help right away O_o Usually there is always a smart cookie around. [21:41:02] I'm putting it back to [[StringProperty1::{{{StringProperty1|Some alternate output}}}]] before I finish [22:15:04] kghbln: I may have to go to that list....bah. I really wanted this done by the end of the day. *sigh* [22:15:18] Thanks for the help [22:16:43] I am afraid that I was not much of a help. Sometimes a good nights sleep provides a new perspective on the problem the next day. Probably you will find the solution within minutes. *hopefully* [22:24:53] So....I was wrong about one thing. Property type is Text. [22:25:46] Also, apparently it helps to have some wiki formatting in the contents of that property, like unordered list markup, for example. [22:25:49] Odd, right? [22:31:32] And if you have any square brackets in the field, it jacks it all up. [22:31:35] wow. [22:31:38] ok, i'm done for the day [22:31:42] thanks again [22:40:01] uncleben The square thing is a php related issue. Hopefully this will go some time in the future. The datatype text should perhaps only be used as a last resort. I guess you may switch it to String in your case. Cheers [23:00:37] sup [23:57:05] How do you know you're thinking correctly?