I'm confused as to what the point of action=render is. How is it different
from using the API?
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com | tylerro...@gmail.com
On Sun, May 19, 2013 at 11:44 PM, Brian Wolff bawo...@gmail.com
It predates the API.
-- brion
On May 20, 2013 9:12 AM, Tyler Romeo tylerro...@gmail.com wrote:
I'm confused as to what the point of action=render is. How is it different
from using the API?
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
On Mon, May 20, 2013 at 12:23 PM, Brion Vibber bvib...@wikimedia.orgwrote:
It predates the API.
Yes, but I mean what is the argument for keeping it and not deprecating it?
As far as I can tell this has been deprecated by API functionality.
*-- *
*Tyler Romeo*
Stevens Institute of Technology,
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 tylerro...@gmail.com wrote:
On Mon, May
// @todo FIXME: This causes breakage in various places when we
// actually expected a local URL and end up with dupe prefixes.
if ( $wgRequest-getVal( 'action' ) == 'render' ) {
$url = $wgServer . $url;
}
--
~Daniel Friesen (Dantman,
On Mon, 20 May 2013 19:51:50 +0200, Daniel Friesen dan...@nadir-seen-fire.com
wrote:
// @todo FIXME: This causes breakage in various places when we
// actually expected a local URL and end up with dupe prefixes.
if ( $wgRequest-getVal( 'action' ) == 'render' ) {
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.
On Mon, 20 May 2013 12:45:32 -0700, Bartosz Dziewoński
matma@gmail.com wrote:
On Mon, 20 May 2013 19:51:50 +0200, Daniel Friesen
dan...@nadir-seen-fire.com wrote:
// @todo FIXME: This causes breakage in various places when we
// actually expected a local URL and end up
On Mon, 20 May 2013 12:55:24 -0700, Thomas Gries m...@tgries.de wrote:
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
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
On 05/19/2013 02:47 PM, Chad wrote:
Where was any discussion regarding this? Or pointers to where it's been
causing problems.
-Chad
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
On 21/05/13 05:45, Bartosz Dziewoński wrote:
On Mon, 20 May 2013 19:51:50 +0200, Daniel Friesen
dan...@nadir-seen-fire.com wrote:
// @todo FIXME: This causes breakage in various places when we
// actually expected a local URL and end up with dupe prefixes.
if (
On 21/05/13 09:38, I wrote:
// @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 );
}
Note that there are already five API
On 05/18/2013 03:40 PM, MZMcBride wrote:
These two diffs explain what happened better than I could. I think this
was the best outcome, but I'm posting on this list in case I missed some
other discussion about the render action and it is, in fact, now
deprecated. I checked the talk page, but
Where was any discussion regarding this? Or pointers to where it's been
causing problems.
-Chad
On May 19, 2013 11:35 AM, Matthew Flaschen mflasc...@wikimedia.org
wrote:
On 05/18/2013 03:40 PM, MZMcBride wrote:
These two diffs explain what happened better than I could. I think this
was the
On Mon, May 20, 2013 at 4:34 AM, Matthew Flaschen
mflasc...@wikimedia.org wrote:
We should give people a heads up, unless/until it's reconsidered and we
decide to undeprecate it (maintain support indefinitely).
Matt Flaschen
Um, how it be discussed and considered to deprecate it in the first
On 2013-05-19 10:09 PM, K. Peachey p858sn...@gmail.com wrote:
On Mon, May 20, 2013 at 4:34 AM, Matthew Flaschen
mflasc...@wikimedia.org wrote:
We should give people a heads up, unless/until it's reconsidered and we
decide to undeprecate it (maintain support indefinitely).
Matt Flaschen
Hi.
https://www.mediawiki.org/w/index.php?diff=597288oldid=579490
https://www.mediawiki.org/w/index.php?diff=691576oldid=686908
These two diffs explain what happened better than I could. I think this
was the best outcome, but I'm posting on this list in case I missed some
other discussion
Foreign file repo is using action=render to get file descriptions from a remote
wiki. (I think that's how file descriptions from Commons are loaded on all WMF
wikis, too.)
--
Matma Rex
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
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@gmail.com wrote:
Foreign file repo is using action=render to get file descriptions from a
remote wiki. (I think that's how file
It may not be explicitly deprecated now, but it would be nice to deprecate
and remove action=render.
We STILL have this sitting around Title:
// @todo FIXME: This causes breakage in various places when we
// actually expected a local URL and end up with dupe prefixes.
21 matches
Mail list logo
