Hi,
We are thinking about installing mediawiki for a R&D project. We like the new features in 1.5 and would like to wait for 1.5 to become the stable version before installing. Does anyone know a rough date for 1.5 to become the stable version? Thanks.
Yong Jin
__________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
Yong J wrote:
We are thinking about installing mediawiki for a R&D project. We like the new features in 1.5 and would like to wait for 1.5 to become the stable version before installing. Does anyone know a rough date for 1.5 to become the stable version? Thanks.
It's already reasonably stable, use the release candidate if you like (caveats for various bugs since fixed in CVS REL1_5 branch, and a few not yet fixed).
-- brion vibber (brion @ pobox.com)
Love extensions! Hate what they do to wiki code, but they are very useful. Thanks to those who made this feature possible.
How can I get the value of a template's parameters while in an extension? I'm talking about an extension that is invoked in a template that has parameters. For example, <extension>{{{1}}}</ extension> somewhere in a template. The text '{{{1}}}' is passed to the extension rather than it's value. It's clear the the parser doesn't parse wiki text before nor after an extension is called, probably by design. That seems to leave this issue to the extension writer. Is there a way to get to such a parameter's value or somehow pass that value to an extension?
Con Rodi Center for Human-Computer Interaction Virginia Tech
Con Rodi wrote:
Love extensions! Hate what they do to wiki code, but they are very useful. Thanks to those who made this feature possible.
How can I get the value of a template's parameters while in an extension? I'm talking about an extension that is invoked in a template that has parameters. For example, <extension>{{{1}}}</ extension> somewhere in a template. The text '{{{1}}}' is passed to the extension rather than it's value. It's clear the the parser doesn't parse wiki text before nor after an extension is called, probably by design. That seems to leave this issue to the extension writer. Is there a way to get to such a parameter's value or somehow pass that value to an extension?
The way I did it was this: $wgParser->replaceVariables($text, end( $wgParser->mArgStack ))
Note that I last tested this on 1.5, a few revisions back. This also only works on the main text input (*not* <foo bar=baz> arguments).
-- Jamie ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB.
Thanks, Jamie. This seems to work for things like {{PAGENAME}}, but so does $wgParser->replaceVariables($text). Neither function call pulls in values for triple brace parameters. Right now all I really need is the PAGENAME of the page being rendered, so this works for me.
Con
On Sep 17, 2005, at 2:25 PM, Jamie Bliss wrote:
Con Rodi wrote:
Love extensions! Hate what they do to wiki code, but they are very useful. Thanks to those who made this feature possible. How can I get the value of a template's parameters while in an extension? I'm talking about an extension that is invoked in a template that has parameters. For example, <extension>{{{1}}}</ extension> somewhere in a template. The text '{{{1}}}' is passed to the extension rather than it's value. It's clear the the parser doesn't parse wiki text before nor after an extension is called, probably by design. That seems to leave this issue to the extension writer. Is there a way to get to such a parameter's value or somehow pass that value to an extension?
The way I did it was this: $wgParser->replaceVariables($text, end( $wgParser->mArgStack ))
Note that I last tested this on 1.5, a few revisions back. This also only works on the main text input (*not* <foo bar=baz> arguments).
-- Jamie
http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB.
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Con Rodi wrote:
Thanks, Jamie. This seems to work for things like {{PAGENAME}}, but so does $wgParser->replaceVariables($text). Neither function call pulls in values for triple brace parameters. Right now all I really need is the PAGENAME of the page being rendered, so this works for me.
Strange. That's the function that would do it (I spent a lot of time tracing trying to figure it out). Parser.php, lines 1969-1999.
-- Jamie ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB.
Brion Vibber <brion@...> writes:
Yong J wrote:
We are thinking about installing mediawiki for a R&D project. We like the new features in 1.5 and would like to wait for 1.5 to become the stable version before installing. Does anyone know a rough date for 1.5 to become the stable version? Thanks.
It's already reasonably stable, use the release candidate if you like (caveats for various bugs since fixed in CVS REL1_5 branch, and a few not yet fixed).
I am in a similar situation. I am ready to install Mediawiki in a live setting in my office, but I'd prefer to wait for 1.5(stable). Is it likely to be released soon?
Thanks, Ferry
mediawiki-l@lists.wikimedia.org