2009/7/22 Robert Ullmann <rlullmann(a)gmail.com>om>: Indeed... it seems to me that any config variables that impact on anything you access via the API could well be relevant. Hmmm...I could probably even manage to write a patch to add this. If we keep adding items to siprop in meta=siteinfo, will that be the right place for them? e.g. api.php?action=query&meta=siteinfo&siprop=rcmaxage cheers Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/

2009/7/25 Roan Kattouw <roan.kattouw(a)gmail.com>om>: OK... so, like api.php?action=query&meta=configsettings&csprop=rcmaxage ? And then add other csprop values as relevant? Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/

2009/7/25 Roan Kattouw <roan.kattouw(a)gmail.com>om>: Is there something else in the API that has works in a similar fashion? To my thinking this is another level of nesting. I don't know PHP well enough to write it from scratch, but if I can see something that has basically the same structure I can adapt it. ... or maybe it should work similar to api.php?action=query&meta=siteinfo&siprop=statistics - you just get everything back and then figure out yourself which ones you're interested in? After all for config variables, they're not going to be costly to calculcate, so you could just as well put everything every time. Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/

Well... not much luck: https://bugzilla.wikimedia.org/show_bug.cgi?id=19937 https://bugzilla.wikimedia.org/show_bug.cgi?id=17027 Where does that leave wgRCMaxAge? It does affect the API, so can I at least add it somewhere if nothing else? I am not really sure what the alternative is. cheers Brianna 2009/7/26 Roan Kattouw <roan.kattouw(a)gmail.com>om>: -- They've just been waiting in a mountain for the right moment: http://modernthings.org/