Difference between revisions of "Help:Linked images"

From Freephile Wiki
Jump to navigation Jump to search
m (1 revision)
(→‎via Extension: Added Extension:ImageLink to the list. Fixed capitalization of section header.)
(No difference)

Revision as of 20:36, 15 November 2008

Images on a MediaWiki wiki are designed to link to the description page, so that licensing information, upload history, contributors, and full resolution versions are immediately available to the user when he or she clicks an image. In fact, MediaWiki is designed to prevent manual manipulation of images in wikicode which may circumvent this operation: The <img> tag is specifically not whitelisted in the Sanitizer, nor is the background-image CSS attribute.

However, there are several workarounds for those that require them.

1.14+[edit | edit source]

Warning - This version has not been released yet. This feature may be modified or removed before final release.

Native image link support was added in r41727. See b539.

Vanilla install[edit | edit source]

If you only have sysop access to the Wiki, these are your best options.

Site CSS[edit | edit source]

The most simplistic method, if your requirements for external images are specialized (that is, restricted to one page or one image), is to add a CSS rule to your MediaWiki:Common.css (or other CSS files, such as MediaWiki:Skinname.css or /skins/skinname/main.css, etc) giving child links of a certain class of object a background image. This method also has some security, as it requires editing the site-wide CSS files, meaning only sysops have access to modify the image shown.

For example (red sections are parts to configure for each image):

In MediaWiki:Common.css:

.imagelink_somename a {
  width:100px;
  height:100px;
  display:block;
  text-decoration:none;
  background-image: url("http://fullurltoimage") 
}

In your wikicode:

<div class="imagelink_somename">[[Some link|&nbsp;]]</div>

This would give the link the background image specified, as well as the width and height of the image (which you have to set manually). To find the location of an uploaded file, go to the image description page and click the image itself, and copy the image location in the address bar.

For example on Image:Wiki.png, the image location is Wiki.png (location format will differ depending on local settings), and the width and height would be set to 135px and 135px. So to make a link to the main page here using that logo, one would add to MediaWiki:Common.css:

.imagelink_wikilogo a {
  width:135px;
  height:135px;
  display:block;
  text-decoration:none;
  background-image: url("http://upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png") 
}

And then use the wikicode:

<div class="imagelink_wikilogo">[[MediaWiki|&nbsp;]]</div>

Which would give you:

You can also use a thumbnail of an image, but make sure the thumbnail is being used elsewhere, as most installations are not configured to generate thumbnails on demand.

Inline CSS[edit | edit source]

You can also attempt to superimpose an invisible link over an image via CSS, such as is done in Template:Click. An example of a typical click template is:

<div style="position: relative; width: {{{width}}}; height: {{{height}}}; overflow: hidden;">
<div style="position: absolute; top: 0px; left: 0px; font-size: 100px; overflow: hidden; line-height: 100px; z-index: 3;">[[{{{link}}}|&nbsp;&nbsp;&nbsp;]]</div>
<div style="position: absolute; top: 0px; left: 0px; z-index: 2;">[[Image:{{{image}}}|{{{width}}}|{{{link}}}]]</div>
</div>

Known problems: It doesn't work in text-only browsers, and in screen readers for the disabled, and possibly other situations. The technique of using CSS to change page content also completely breaks an article's web accessibility by contravening a WAI priority-one checkpoint.[1]

Redirect[edit | edit source]

A less elegant trick is to make the image description page a redirect to the target. So for example Image:Wiki.png would be changed to content:

#REDIRECT [[MediaWiki]]

There are several disadvantages to this:

  • It doesn't always work, some installations/versions have internamespace redirects disabled.
  • The image appears at the top of the article. This is because MediaWiki redirects aren't really redirects, they simply bring the target page's data to the current URL, but on image description pages this is done after the image itself is shown.
  • It can only be done once per image.

Native with configuration change[edit | edit source]

If you have server access, but do not want to install any extensions, these solutions may work for you.

External image syntax[edit | edit source]

If you enable $wgAllowExternalImages (which allows external images from any domain) or $wgAllowExternalImagesFrom (which restricts the list of domains), anyone can then easily create an "external" link to an "external" image. External simply means: using the full URL rather than a local link, so you can link locally, but you need to use the full URL. The plainlinks class is used to remove the "external link" icon:

<span class="plainlinks">[http://linktopage http://linktoimage]</span>

So for example, were external images allowed here, you could link to the main page with Wiki.png using wikicode like:

<span class="plainlinks">[{{fullurl:MediaWiki}} http://upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png]</span>

This has the disadvantage of not registering the link, or the image use, as well as not being easily portable to forks and mirrors.

Raw HTML[edit | edit source]

If you enable $wgRawHtml, you can use <img> tags freely, but this method is highly insecure.

There are, however, some extensions to make it safer, see Manual:$wgRawHtml#Related_Extensions for details.

Via extensions[edit | edit source]

If you are willing to install an extension, several extensions have been created to address this issue:

Or you can invent your own linked image syntax, by writing an extension that registers it as a parser hook. See Manual:Tag extensions for information on extending MediaWiki syntax.

Other options[edit | edit source]

If you want, you can do some more drastic things, such as modify /includes/Sanitizer.php (where the HTML tag whitelist is), and add <img /> to the list of allowed tags.

See also[edit | edit source]