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=85id=20.
I figured out that = was messing up the template code, so I substituted it's
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 of the
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 are
Hey all,
I'm happy to announce the immediate availability of the new Semantic Meta
Tags extension.
It is a Semantic Mediawiki extension for adding meta tags to a page with
content generated from semantic annotations.
This extension enables to automatically extend the HTML meta tags of a
page
Hi,
I have noticed that when I ask Lua templating-related questions here I
get little, if any replies so I was wondering if someone knows somewhere
I can ask these questions and get fast (within a day) and helpful answers.
Thanks for your time,
Brenton
I'd like to make 2 notes.
It looks like the property - meta tag mapping is done in LocalSettings.
Can you guarantee this will stay that way? There are a number of XSS
vectors that would be introduced if it becomes possible to define a
property - meta mappings handled by OutputPage::addMeta
