All posts by Penguin-Pal

A reply to Aks6609

Penguin-Pal·3/3/2022

Fandom's layout has been changed over the years. Nowadays the move arrow is by the dropdown next to the edit button. You can also press M on the keyboard to do that. This option will not, however, be presented if the article is move-protected.

A reply to MrTahpHayt

Penguin-Pal·8/18/2021

Hi there! If you're looking for something super basic and only for a single template, then create a page called Template:Stub and try this format by creating:

<div style="padding: 4px 20px; background: #ffc; border: 1px solid #333; color: #333;">
'''Stub'''<br />
This article is incomplete. You can help by editing it.
</div>

Then add:

{{Stub}}

To any stub article. that requires it. It's a basic design but it should do the trick, and they'll also stack properly if you're making more templates based on this design. Also, you can play with the background, border and text colors- there are many online hex color pickers that are very convenient to use.

A reply to Inoyamanaka98

Penguin-Pal·4/10/2021

This is quite an old thread, but either way, you automatically become one upon creating a new wiki, or by being promoted by another bureaucrat in an existing wiki. Inactive wikis can be adopted to become an admin and/or a bureaucrat.

A reply to Aks6609

Penguin-Pal·11/20/2020

Oh lol that's an old thread. But you can still do it- in your bottom toolbar click "Customize", and type in the popup window's text box "Move". Click Enter and then you can also rearrange the order of your buttons.

A reply to Penguin-Pal

Penguin-Pal·11/6/2020

Alright, thank you guys :)

Penguin-Pal·11/5/2020 in Technical Advice & Coding Help

Wikia API (/api/v1) changes

Hi,

I was wondering if there was any recent update involving the Wikia API in some wikis (e.g. TTR's)- there used to be a "comments" property when for article queries, but it's no longer there.

Also, whenever opening /api/v1/ in the browser (or a deeper pathname, but without the actual query), it displayed a documentation, but doing so in UCP wikis returns an actual API response with an error message, e.g. TTR's currently returns:

{"status":404,"error":"ControllerNotFoundException","details":"Controller not found: ApiDocs"}

If anyone knows about these (or one of these) topics, I'll really appreciate any help :)

API Unified Community Platform

A reply to HumansCanWinElves

Penguin-Pal·7/7/2020

Try also removing the !important keywords from the last 2 blocks of CSS from your global.css, at the very bottom- perhaps this is what's affecting it (also the .Nam part is missing semicolons after each line). Other than that, it doesn't seem like the wiki's common.css has anything that can override it. So try updating your global.css and if it doesn't work, clear your cache just to be sure. if this still happens, try opening your console to see if Wikia's throwing any error messages, or inspect the links to your userpage to see if there's any other css code that might override the custom one.

(Edited by Penguin-Pal)

A reply to HumansCanWinElves

Penguin-Pal·7/7/2020

I guess you're referring to the Keeper of the Lost Cities and Experimental Coding wikis. Here are the errors about them as far as I can tell: <hr>In the Keeper of the Lost Cities wiki, you can't use !important after the code block- it must be specified after each individual property value. Tho it looks like the css works even without using !important, at least on a first glance. <hr>In the Experimental Coding wiki, !important! needs to be placed before the semicolon- otherwise it merges with the next CSS property name (like !important background-color) so the browser counts it as an invalid css. Try moving it like this: <div dir="ltr" class="mw-geshi mw-content-ltr"><div class="css source-css">

 a<span class="br0">[</span>href$<span class="sy0">=</span><span class="st0">":HumansCanWinElves"</span><span class="br0">]</span><span class="sy0">,</span> a<span class="br0">[</span>href$<span class="sy0">=</span><span class="st0">"/HumansCanWinElves"</span><span class="br0">]</span> <span class="br0">{</span>
   <span class="kw1">color</span><span class="sy0">:</span> <span class="kw2">white</span> !important<span class="sy0">;</span>
   <span class="kw1">background-color</span><span class="sy0">:</span> <span class="kw1">blue</span> !important<span class="sy0">;</span>
   <span class="kw1">font-weight</span><span class="sy0">:</span> <span class="kw2">bold</span> !important<span class="sy0">;</span>
 <span class="br0">}</span>

</div></div>

(Edited by Penguin-Pal)

A reply to Rycharde Pendraig

Penguin-Pal·10/19/2019

From your description it looks like you're only willing to affect external links, so: <dl><dd><dl><dt> If you want this to affect your account only: </dt></dl></dd></dl>You could add to your /global.js something like this (or your /common.js if you want this to only be applied in specific wiki(s)): <div dir="ltr" class="mw-geshi mw-content-ltr"><div class="javascript source-javascript">

<span class="coMULTI">/* make all external links open in a new tab */</span>
$<span class="br0">(</span><span class="st0">"body"</span><span class="br0">)</span>.<span class="me1">click</span><span class="br0">(</span><span class="kw1">function</span><span class="br0">(</span>e<span class="br0">)</span> <span class="br0">{</span>
	<span class="kw1">var</span> a <span class="sy0">=</span> e.<span class="me1">target</span><span class="sy0">;</span>
	<span class="kw1">if</span> <span class="br0">(</span>a.<span class="me1">nodeName</span>.<span class="me1">toLowerCase</span><span class="br0">(</span><span class="br0">)</span> <span class="sy0">==</span> <span class="st0">"a"</span> <span class="sy0">&&</span> a.<span class="me1">href</span>.<span class="me1">indexOf</span><span class="br0">(</span>location.<span class="me1">origin</span> <span class="sy0">+</span> <span class="st0">"/"</span><span class="br0">)</span> <span class="sy0">!=</span> <span class="nu0">0</span><span class="br0">)</span> <span class="br0">{</span>
		<span class="co1">// user clicked an external link</span>
		$<span class="br0">(</span>a<span class="br0">)</span>.<span class="me1">attr</span><span class="br0">(</span><span class="st0">"target"</span><span class="sy0">,</span> <span class="st0">"_blank"</span><span class="br0">)</span><span class="sy0">;</span>
	<span class="br0">}</span>
<span class="br0">}</span><span class="br0">)</span><span class="sy0">;</span>

</div></div> <dl><dd><dl><dt> If you want this to affect everyone in an entire wiki : </dt></dl></dd></dl>I'm not sure if the use of JavaScript for this behavior matches the customization policy, as i haven't made any public wiki scripts in a few years. If you are an admin there, you could ask a Wikia staff member to enable such behavior. However, note that if a reader wants to open a link in a new tab, they could do just that whether they are in pc or mobile. Maybe it's just my opinion, but sites don't let me open a link the way i want really grind my gears.

(Edited by Penguin-Pal)

A reply to JoePlay

Penguin-Pal·10/7/2018

All hail JoeBot our savoir!

(Edited by Penguin-Pal)

A reply to Rappy

Penguin-Pal·8/2/2018

Great, i was looking forward for an update that would allow me to use the title how much supercalifragilisticexpialidocious could a supercalifragilisticexpialidocious chuck potatoe in forum posts as nature intended.

(Edited by Penguin-Pal)

A reply to ArtemisKnab

Penguin-Pal·7/30/2018

Wouldn't it be simpler to use all icons with the same color, and then use CSS filters on Wikia.css to invert the color for said icons, which is only applied on desktop view anyway?

(Edited by Penguin-Pal)

A reply to DSandstorm

Penguin-Pal·3/8/2017

It's sometimes better to start a new discussion; this way, the most recent messages are related to the original question in the thread, which makes keeping track of the current question easier. Though it's completely up to you.
However, if the template question involves the same mechanisms/templates, it can be a good idea to keep posting on the same thread.

(Edited by Penguin-Pal)

A reply to DSandstorm

Penguin-Pal·3/8/2017

Try replacing it with #. HTML entities don't get parsed (even though they contain number signs) the same way normal wikitext does. By the way, you might want to change the syntax to:

[[Chapters{{#ifexist:{{{Arc Title|}}}|<span style="color: red;">&#35;</span><span style="color: red;">{{urlencode:</span>{{#replace:{{{Arc Title}}}|Arc|}}<span style="color: red;">|WIKI}}</span>|}}|Chapters]]

To make sure that there aren't any characters that require escaping, in terms of the link URL.

(Edited by Penguin-Pal)

A reply to Saua1

Penguin-Pal·2/23/2017

This tip always helped me when i needed

Go to your wiki's main page.
Find a point in your screen and stare at it for 30 seconds
Close your eyes for 10 seconds, and then stare at this point for 20 more seconds
Quickly move your eyes and look at step 5
If you still don't understand the trick, rotate your screen 90° clockwise and try again until it works

Nah but seriously now. If you made a wiki, then you should know what it's about. Try writing articles about things from the wiki's subject (e.g. characters, items, places, etc.). You don't need to write 24/7 for your wiki to start looking good 8) Just write some here and add some there, try inviting other people who are interested in its subject, and before you know it you'll have a pretty nice source for info... or a vandalcity :p

(Edited by Penguin-Pal)

A reply to Adginer's Cost

Penguin-Pal·2/18/2017

Well, short pages can be viewed either in Special:ShortPages or via the API's list=allpages. But short pages are probably divided into several categories:

Short incomplete stubs
Disambiguation pages or lists- normally very small in size
Redirects- shouldn't take more than a few bytes
(as you mentioned) articles about a topic that has very little available info out there, so all the relevant info is already in the page and yet the result is a small page size. Therefore, making it longer would simply make readers waste extra time for reading the exact same thing- something everyone should avoid.

I like the idea of __NOSTUB__, but adding it to pages is pretty much the same idea of adding {{STUB}} to short pages, only the other way round, i guess :p So you should probably rely on the links above and then use your judgement to see what page needs to be marked as a stub.

(Edited by Penguin-Pal)

A reply to Furry1832

Penguin-Pal·2/18/2017

so ugly everyone died the end

(Edited by Penguin-Pal)

A reply to Oganesson

Penguin-Pal·12/29/2016

That's because the main page uses column tags. Try putting these templates after the final <mainpage-endcolumn /> tag. This way, they shouldn't be bounded to a specific column.

(Edited by Penguin-Pal)

A reply to Timppali

Penguin-Pal·12/8/2016

Seems like the sorting date patterns, derived from $.tablesorter, are the following:

MM DD YYYY (month can be single-digit, day can be single-digit, and year can be 3- or 2-digits long)
monthname daynumber year (daynumber is 1-2-digits long, monthname has shorter forms and year can be 3- or 2-digits long)
daynumber monthname year (same comments as above, only a different order)

Between each day/month/year value you can use the following characters as separators:

A space
-
,
.
/
'

It's kinda strange, since you seem to be able to mix #1 and #3 formats, but the second format that i listed seems somewhat broken. Try perhaps to switch to one of the other formats, or use data-sort-value for a each table cell with the "broken" format if you wish to use it.

(Edited by Penguin-Pal)

A reply to Victor Kazuma Nicholas

Penguin-Pal·12/3/2016

Check the instructions in Adoption:Requests. If no admin in that wiki is active, and you fulfill the criteria, you will be given bureaucrat rights in that wiki.

(Edited by Penguin-Pal)