Extension talk:VariablesExtension

Variables and Conditional Parser Functions
It must be noted that everything in conditionals gets executed (though only one result gets displayed). Because of this, every instance of #vardefine will always get executed, regardless of to what the conditional gets evaluated.

Given the following:

gives prevvalue.

Instead you have to nest the conditional inside #vardefine:

In this case, gives nextvalue.

&mdash;Sledged 16:12, 24 October 2006 (UTC)

Multiple assignments
It would be good if this extension allowed multiple assignments. Say I have a template data that contains a=1|b=2. I call and usedata gets one template-variable, a, with value 1|b=2. If I could make data say a=1,b=2 and usedata could call variablesextension to set both variables at once, that would be useful.--201.216.136.95 18:24, 10 January 2007 (UTC)

Bugzilla request
The bug requesting this to be added for the big sites (wikipedia, etc.) is 8570. If you really want these functions, go (register and) vote for that bug. If you have an concern, that bug would also be an appropriate place to express it.--201.216.136.95 18:24, 10 January 2007 (UTC)

MediaWiki version 1.9
How is the compability with MediaWiki version 1.9?

use of undefined variables
Sometimes you want to use a variable which has not been set before and you expect it to return an empty string. I suggest to change the code of function "varf" as follows: function varf( &$parser, $expr = '' ) { if (isset($this->mVariables) && array_key_exists($expr,$this->mVariables)) return $this->mVariables[$expr]; return ''; }
 * 84.58.192.102 09:11, 28 January 2008 (UTC)

Number incrementing through page
I'm trying to write a template, two templates in fact, that will increment a number through a page, ie. @undefined @undefined @undefined

@undefined @undefined

@@ starts the counter at 1 and prints it and @ increments the number and prints it.

I expect the following to appear: 1 2 3 4 1 2 3

But I get the following: 1 2 2 2 1 2 2

I'm using the following code for the templates.

Template: @@

Template: @

Thanks.

--Wahooney 14:05, 11 April 2008 (UTC)
 * Your problem is that variables don't persist across templates, so you need to pass the value of n from @@ to @. So, your page needs to be:

@undefined @undefined @undefined

@undefined @undefined
 * --Snuck 05:31, 15 April 2008 (UTC)

@undefined @undefined @undefined
 * On a 1.12 version of MediaWiki, I get 1 2 3 4 1 5 6 which is not what was expected, but:

@undefined @undefined gives (to me): 1 2 3 4 1 2 3. --Nbrouard 14:38, 25 June 2008 (UTC)

@undefined @undefined @undefined

@undefined @undefined is also working with the new parser. --Nbrouard 15:14, 26 June 2008 (UTC)

Multiple inclusions in a template, still counting
Let funcone be the following template: @undefined @undefined @undefined @undefined Inclusion of content

Redefining n for second inclusion

@undefined @undefined Second inclusion of content

after second content

Trying on the following wiki text: Testing Funcone

@undefined

I get:
 * Testing Funcone 1 2 3 4 5 Inclusion of content 6 7 8 9 10 Redefining n for second inclusion
 * 37 38 Second inclusion of content 6 7 8 9 10 after second content 39

instead of:
 * Testing Funcone 1 2 3 4 5 Inclusion of content 6 7 8 9 10 Redefining n for second inclusion
 * 37 38 Second inclusion of content 39 40 41 42 43 after second content 44

Any idea to make substitution earlier? --Nbrouard 13:10, 30 June 2008 (UTC)


 * Mmmh, until now I thought the default behaviour is, that a variable is global (global means all over the article for all templates which are called from the article). I often use a variable with very special name like "countCalls<>" as "global variable" which is defined in template X. In another call of Template X or another Template Y I can see if the template was already called in this article or not.
 * Perhaps it should be possible to define local variables and global vars like . So the default would be local variables which are only available at the current call of the template or on the article page but NOT in sub-calls of templates.
 * On the other hand, perhaps default behaviour should be global variable like it's now in the current version of MW so you would have for local ones and  for global ones. Than you could call it with  btw. . Global variables are also good for using them as a kind of template parameters in very complex templates which work with semantic forms arraymap function or something like that where you can call a template but can't give common template parameter values.
 * Normally I would say that local must be the default behaviour of such a variable. But the compatibility to the oder versions of these plugins should be as big as possible and it looks like currently (MW 1.13) all variables are “global”. But perhaps here should be a cut and everybody who wants to use the new version perhaps must change some templates. I hope this is going to be implemented, would be very useful and it would ensure that we could avoid such strange behaviours in the future. --Danwe 22:04, 11 February 2009 (UTC)

Complications
The wiki I work on is on the brink of updating from 1.11 to 1.13 (two days from now). We use a huge number of variables, mostly so we can get data in and out of templates. Some of our templates set many variables meanwhile other templates utilize multiple dynamic variables. We use the variables and templates to centralize information and make editing easier on the user. They can utilize a template that accesses many variables and not have to deal with the very ugly logistics of where the data is coming from.

If you need some examples:
 * http://wiki.secondlife.com/wiki/Template:LSL_Param - Variable parameters get floating text by taking the variable name and plucking the description from memory. The user need not know where the information is to have it accessible.
 * http://wiki.secondlife.com/wiki/Template:LSL_Constants/PrimitiveParams - Utilizes a huge number of templates to set the values of a huge number of variables, the end result is a table and many additional variables that have accumulated in the process.
 * http://wiki.secondlife.com/wiki/llSetPrimitiveParams utilizes the previous templates, the actual source of this articles is very light compared to what it is actually doing for the articles.

What can I do so that I literally don't have to rework 50 to 100 templates and thousands of articles? -- BlindWanderer 21:54, 21 October 2008 (UTC)

Default Value
Am I missing how to declare a default value when recalling it? Or does that need to be defined only when defining it? 68.226.0.35 16:58, 8 December 2008 (UTC)
 * It's not possible to use a default value like . I think that would be a great improvement. I really often have to use something like:   what is much more code than only  would be!


 * Please, would you add this feature into the plugin? --Danwe 21:46, 11 February 2009 (UTC)

Use in Wikiprojects
Is it planned to install this extension in Wikipedia and other projects too? It would be extremelly useful for creating templates. Nevertheless, now it doesn't work. --Petrus Adamus 22:06, 19 February 2009 (UTC)
 * I think this is the wrong place to discuss this. Perhaps you should ask that on the wikipedia project page. But I don't think they will use it because every new extension could be a security hole and maybe they are afraid of it would be to complicated and to much for some users. --Danwe 17:01, 21 February 2009 (UTC)
 * It has been requested here, but the answer was (and still is) "no." —Sledged (talk) 23:47, 25 February 2009 (UTC)