Yea, it's definitely being used. I've not heard of it causing problems, so this deprecation is news to me. -Chad On May 18, 2013 2:53 PM, "Bartosz Dziewoński" <matma.rex(a)gmail.com> wrote:

On 05/19/2013 02:47 PM, Chad wrote: I wasn't there for the discussion that led Terry to mark it as such. The deprecate tag was removed. If someone still wants to deprecate it, they know where to post. Matt Flaschen

On 2013-05-19 10:09 PM, "K. Peachey" <p858snake(a)gmail.com> wrote: It seems a little odd to deprecate something due to load, when realistically we probably represent 95% of the load due to that feature. (Number pulled out of a hat. I have no idea what the real numbers are, but ive never heard of anyone other than mediawiki using that feature, and we use it quite a lot). Im also not a fan of telling people not to do something and then doing it ourselves. -bawolff

It predates the API. -- brion On May 20, 2013 9:12 AM, "Tyler Romeo" <tylerromeo(a)gmail.com> wrote:

Deprecated means we don't use it and other people shouldn't either. I think you mean superseded, which an argument that can be made here. However, all I've seen is vague hand waving about performance concerns. -Chad On May 20, 2013 9:32 AM, "Tyler Romeo" <tylerromeo(a)gmail.com> wrote:

On Mon, 20 May 2013 19:51:50 +0200, Daniel Friesen <daniel(a)nadir-seen-fire.com> wrote: That TODO has been there since 2006 (r12621), so apparently it doesn't cause that much breakage if nobody bothered to fix it. -- Matma Rex

On 21/05/13 05:45, Bartosz Dziewoński wrote: That fixme comment is a pretty clear indication of what would break if you tried to migrate commons image descriptions from action=render to API action=parse. There's no Title.php hack or anything equivalent for the API action. The problem here is the use of global state, necessitated by Linker interfaces. Ideally, action=render and its hypothetical API replacement would indicate that full URLs are required via ParserOptions. Making sure every caller of a Linker static method passes an appropriate option would be tricky. Maybe a better approach would be to introduce Linker wrappers to Parser in the form of non-static methods, or to introduce a $parser->mLinker object with wrapper methods and the appropriate state. Or, if action=render is undesirable for some reason other than the Title.php hack, you could just migrate it to the API line for line: // @todo FIXME: This causes breakage in various places when we // actually expected a local URL and end up with dupe prefixes. if ( !empty( ApiParse::$forceAbsoluteUrls ) ) { $url = wfExpandUrl( $url, PROTO_RELATIVE ); } At least it wouldn't be any worse than how it is now. I know there's a psychological barrier to maintaining inelegant code. But it's just psychological. Despite appearances, touching it won't make your hand dirty. -- Tim Starling

Am 20.05.2013 18:11, schrieb Tyler Romeo: I do use it (action=render) in rendering the content div of a mediawiki A in a different web page B, in the context of the authenticated user, in an iframe. The different web page B has no additional logic, especially, I cannot add javascript or jquery, so render=action appears to be an easy solution for my problem. Unfortunately, and this is a drawback. action=render does currently not apply the mediawiki A stylesheets.

To include a page within iframe, sometimes it is reasonable to use "?printable=yes". For example there is a gadget in hewiki that shows Wikidata entry in iframe (within dialog) with ?printable=yes to allow uses to edit properties. (the benefit of printable=yes is that the JS is loaded, but there is no sidebar - which is nice for this purpose) On Mon, May 20, 2013 at 11:17 PM, Daniel Friesen &lt;daniel(a)nadir-seen-fire.com > On Mon, 20 May 2013 12:55:24 -0700, Thomas Gries &lt;mail(a)tgries.de> > Am 20.05.2013 18:11, schrieb Tyler Romeo: >> >>> I'm confused as to what the point of action=render is. How is it >>> different >>> from using the API? >>> >> >> I do use it (action=render) in rendering the content div of a mediawiki >> A in a different web page B, >> in the context of the authenticated user, in an iframe. >> >> The different web page B has no additional logic, especially, I cannot >> add javascript or jquery, so render=action appears to be an easy >> solution for my problem. >> Unfortunately, and this is a drawback. action=render does currently not >> apply the mediawiki A stylesheets. >> > > action=render should NOT be used for this purpose. > &action=render is not a valid html page. It's meant to be read by > something that does additional processing (which could use the api instead) > and embedded inside of another html document. > > I also don't see how your technique will logically work at all, since the > moment the user clicks a link they lose action=render. > > > -- > ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/] > > > ______________________________**_________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/**mailman/listinfo/wikitech-l<https://lists.… >