[00:56:22] When using Cargo with format = template, is there a recommended / idiomatic way to pass additional parameters to the template that aren't among the fields of the query? [00:56:51] My first attempt was to include things like 'foo' = argName among the fields, hoping that 'foo' would be understood as a literal rather than a field name, but that didn't work. [00:57:18] I then discovered that I can use CONCAT() to trick it into seeing it as a literal, as in: CONCAT('foo') = argName [00:57:34] That works, but is obviously a kludge. If there's a nicer way to do it, that would be great to know. [00:59:08] To clarify, what I have now is like: {{#cargo_query: tables = x | fields = a, b, CONCAT('foo') = c, CONCAT('bar') = d | format = template | ... }} [02:33:24] Hi, I don't know how the modules work. [03:20:36] I'm getting late, I'll come another day, bye [18:18:22] When a #cargo_store command fails, where can I see the error message? A template of mine that has a cargo_store command is simply failing to add any entries at all to a table, and I can't find a reason for it... [19:18:06] taylan: if anywhere, probably mediawiki debug log [19:18:12] !wg DebugLogFile [19:18:12] https://www.mediawiki.org/wiki/Manual:%24wgDebugLogFile [19:18:36] but it is a very noisey and hard to sort through file [19:20:48] If it is an SQL error, mysql has logging that you can enable as well, but again it is probably hard to sort through