if you name the param and use the = to define it {{template|url = website}}
you will also bypass this issue without having to do special encoding
On Mon, Mar 9, 2015 at 8:46 PM, Jan Steinman wrote:
> > From: "Rowe, Dolores A"
> >
> > I have a template which uses parameters, for example {{{2}}}
> From: "Rowe, Dolores A"
>
> I have a template which uses parameters, for example {{{2}}} for it's second
> argument,
> which is a url. Some url's are similar to this with a query string:
> http://myserver.com/index.aspx?com=85&id=20.
>
> I figured out that "=" was messing up the template
Use |2= directly in your template.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
On 2015-03-02 2:09 PM, Rowe, Dolores A wrote:
> Dear Teammates,
>
> I have a template which uses parameters, for example {{{2}}} for it's second
> argument,
> which is a url. Some url's ar
> I figured out that "=" was messing up the template code, so I substituted
> it's hex equivalent "%3D" for both
> of the equal signs. Some target servers can parse this, and some can not,
> thus creating a problem for the users.
To my knowledge this interpretation is incorrect: it is the task
Dear Teammates,
I have a template which uses parameters, for example {{{2}}} for it's second
argument,
which is a url. Some url's are similar to this with a query string:
http://myserver.com/index.aspx?com=85&id=20.
I figured out that "=" was messing up the template code, so I substituted it
