Page MenuHomePhabricator

Transclusion of variables like {{PAGENAME}} fails in imagemap
Closed, DuplicatePublic

Description

The transclusion of variables like {{PAGENAME}} fails in imagemap. Try to save
or preview this code:

<imagemap>
Image:Commons-logo.svg|24px|Commons

Fiktives Rechteck der Größe 0, der nachfolgende default bedeckt dann das ganze

Icon
rect 0 0 0 0 [[commons:{{PAGENAME}}]]
default [[commons:{{PAGENAME}}]]
desc none
</imagemap>

You will get an empty screen. Really empty, zero byte...


Version: unspecified
Severity: normal
URL: http://de.wikipedia.org/wiki/Benutzer:Raymond/imagemap_bug2

Details

Reference
bz8600

Event Timeline

bzimport raised the priority of this task from to High.Nov 21 2014, 9:33 PM
bzimport added a project: ImageMap.
bzimport set Reference to bz8600.
bzimport added a subscriber: Unknown Object (MLST).

conrad.dunkerson wrote:

There are similar problems with parameters if the imagemap is included in a
template.

<imagemap>
Image:{{{1|smiley.jpg}}}
rect 0 0 50 50 [[Frog]]
</imagemap>

The above fails because the contents of the parameter are ignored (regardless of
whether it is set or not). The same thing happens if the link, size, or other
values are defined by parameters. This effectively prevents <imagemap> from
being used to replace older 'clickable image' methods like 'Template:Click'...
since it can't accept parameters or magic words it has to be individually coded
for each image/size/destination combo. For instance, 'Template:Portal' on
en-wikip can't be recoded to use imagemap with the existing parameters... and
writing up separate imagemap statements for every portal/page with a portal link
is not feasible. Hence, the current logic that 'imagemap' was meant to replace
will continue being used.

ayg wrote:

*** This bug has been marked as a duplicate of 2257 ***

timeroot.alex wrote:

I'm having the same problem, and I can't find an answer on the page for bug 2257... I'm confused. And on the version of the MediaWiki software I'm using, I can't use tempalte:click, either.

robert_horning wrote:

While bug 2257 may be the root cause of this problem, this seems like a very legitimate bug in its own right. It certainly hasn't been "resolved" by any means, as the solution listed on 2257 is merely an ugly "hack", nor does it really address the real issues expressed by this bug report.

I'm not going to let myself get stomped by the dev team by reverting a re-opened but report to closed again, but this doesn't work, nor is it an exact duplicate of but 2257.

Gilles raised the priority of this task from High to Unbreak Now!.Dec 4 2014, 10:11 AM
Gilles moved this task from Untriaged to Done on the Multimedia board.
Gilles lowered the priority of this task from Unbreak Now! to High.Dec 4 2014, 11:21 AM