You define a variable and give it a value, like this:
{{#vardefine:itemcost|17}}
That "hides" the variable from showing on the page like <includeonly>
would; if you want to define a variable and have it print at the same time, use {{#vardefineecho:}}
.
You can then take that variable and perform calculations with it:
{{#expr: {{#var:itemcost}} * 2}} {{#expr: {{#var:itemcost}} * 1.8}}
etc.
TyA wrote:
Original Authority wrote: Not sure why you'd want to hide revisions from users anyway; they serve as a history of the page. Hiding them seems cynical.
Our reasons for doing so are listed here. None of those types of edits belong in the page history.
In any case, both deleted revisions and deleted pages can be viewed by users with the custodian usergroup — we're not restricting it to sysops only.
SVGs are basically text files, so if you open the direct link in your browser and view the page source, or download the .svg and open it in a text editor, you can see its source code. Compare the old revision to my revision and you can see the missing line.
I uploaded a fixed version just now - I hope you don't mind. Your existing SVG had weirdly formatted code and was missing the <?xml version="1.0" encoding="UTF-8"?>
at the top.
You can do it with the filter
property in CSS, which is supported by most browsers except (surprise) Internet Explorer.
You'll need to start with the original color image, apply filter: grayscale(100%);
to it,
then have the grayscale filter go back to 0% (full color) when you hover over the image. Here's a demo I created; I've added a transition so the effect is smoother when you hover over the image.
Try this:
<dpl> category = Category:Foo notuses = Template:Bar format = ,\n* [[%PAGE%]] </dpl>
<dpl> category = Foo notuses = Template:Bar </dpl>
If you upload a background image that's wider than 2000px a "no split" option will appear in Special:ThemeDesigner, which prevents Wikia from automatically splitting the image. If you can't obtain an image that large, you could probably add a background image via CSS.
The Terraria wiki has a Monobook logo set at File:Wiki.png, which doubles as the apple-touch-icon
you're seeing.
It probably has to do with LazyLoading, which doesn't load images outside of the viewport until you scroll down and they come into view.
There's another semicolon that's breaking your CSS:
font-family: 'Ranga', cursive; !important;
<dpl> namespace = category = 1 category = 2 resultsheader = %TOTALPAGES% articles format = , </dpl>
This is unrelated to image compression or file format. Wikia does not support screens that have high pixel densities like the MacBook Pro/iMac and iPhone's Retina displays. They look better than normal screens, but require websites to serve images that are twice the size they normally would be. Here's a link to an Apple Developer page on the topic.
Wikipedia's images look sharp because it has the $wgResponsiveImages setting enabled, which outputs three different thumbnails for each image to cater to 1x, 1.5x, and 2x displays. If you right click on any image on Wikipedia and choose "Inspect Element", you can see the srcset="/filepath.png 1.5x, /filepath.png 2x"
that produces it.
Considering 89% of iOS devices and 87% of Android devices have hiDPI displays, this seems like it should be a major priority, but I've never seen it mentioned in any of Wikia's "modernization" blogs.
LordTBT wrote: I've been at Wikia 7 years longer than you have, and admin a wiki that has more than twice as much content. The Main Page isn't admin only, and it's fine.
I think the reason you don't have much vandalism is because of lack of visitors. Looking at view counts on Special:Insights, the RuneScape Wiki's main page receives 483,088 visits monthly vs. Redwall's 2,368; the main page was vandalized on a regular basis until the community agreed to fully protect it.
You don't need to use Unicode characters or disable subpages in the mainspace. The RuneScape Wiki uses Javascript to hide the base page link — ctrl-f "subpage" on MediaWiki:Common.js. It works in conjunction with Template:Restricted title, which adds class false-subpage
when the subpage parameter is filled in.
Boldmouse2 wrote: Why remove Top 10s anyhow, the real wast of K'bs-per-sec' are the hundresd of abandoned 1 page wikis.