XXXXXX User:SOTO/Forum Test/Tech notes/Thread:117183
Hi everyone :)
We're soon starting a whole new way of communicating with each other on this wiki. Wikia have come up with some rather nifty new forum software that's gonna allow us to speak much more quickly with each other. New threads can be made to be seen by all registered users. And once you post in an existing thread, you'll get personally notified when someone adds something new to that thread.
This should mean a drastic reduction in the number of times you kinda forget to wander back into a thread, as well as teh number of occasions on which people legitimately say, "But I didn't know there was a discussion about that at the forums!"
For the moment however, I gotta ask everyone to stay away from the forums. Gimme about 48 hours to figure out all the new styling and make this thing "ready for prime time".
I'll let ya know when we can start talking again, what'll happen to the existing forum threads and all that other jazz.
One thing's for absolute certain though, people: Howling:The Howling is unaffected. It's still the only social area of the wiki where spoilers are allowed. And this new technology will not be made available in The Howling.
(By the way, while I'm working on enabling the new forums, do feel free to post to this thread only and ask questions.)
- Paul Benjamin Austin
What's happening with the Discontinuity section?
the editing of those entries are disabled
- CzechOut
Are you sure they are? Didn't seem like they were disabled. Please double check.
- CzechOut
Just checked. Discontinuity forum is still editable. Which is why the message at the top of every Discontinuity thread makes an exception for that forum.
- Eladkse
CzechOut - admins can still edit the forum namespace, but ordinary user cannot (unless you've gotten staff to do something).
- Eladkse
Wow, this reply system is confusing...
- CzechOut
Eladkse wrote: Wow, this reply system is confusing...
"This" as in something I've done to coding here at tardis, or "this" as in something within the master forum code?
- CzechOut
Eladkse wrote: CzechOut - admins can still edit the forum namespace, but ordinary user cannot (unless you've gotten staff to do something).
Ahhhhh, yeah. Hmmm. Is it something Staff actually can override?
- Shambala108
Eladkse is right about the discontinuity and timey-wimey forums. There is no "edit" button, just "view source", which takes you to "edit intro", which gives you a message that editing the page is locked. Shambala108 ☎ 17:14, December 2, 2012 (UTC)
- Eladkse
You'd have to ask them, but I suspect not. Most likely, hey would make you choose between having the new forums, or the Forum namespace.
- Eladkse
CzechOut wrote:
Eladkse wrote: Wow, this reply system is confusing...
"This" as in something I've done to coding here at tardis, or "this" as in something within the master forum code?
I'm not entirely sure. Some of them are indented, and some aren't. I don't know how each message was achieved.
- CzechOut
And if we make a new namespace to store the Discon/Timeline stuff, it'll count against our three custom namespaces, I'll bet. Even though we didn't explicitly choose to lose the Forum namespace, as such. Hmmmm.
- CzechOut
Eladkse wrote: I'm not entirely sure. Some of them are indented, and some aren't. I don't know how each message was achieved.
There. All the same now. Which is kinda how it seems to be styled on most other wikis.
- TomekO
CzechOut wrote: Just checked. Discontinuity forum is still editable. Which is why the message at the top of every Discontinuity thread makes an exception for that forum.
Only for admins.
- Eladkse
TomekO wrote:
CzechOut wrote: Just checked. Discontinuity forum is still editable. Which is why the message at the top of every Discontinuity thread makes an exception for that forum.
Only for admins.
Bit late to the party there, Tomek.
- TomekO
Bit late to the party there, Tomek.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/Tech notes/Thread:117197
We are in the first wave of wikis to adopt this new forum software after it went live across Wikia. There was an earlier beta testing period, but we're very much one of the earliest adopters. I think we're something like wiki #192 to enable it — out of tens of thousands of wikis.
So you will spot some genuine "issues" around. As you spot 'em, please leave a message here, detailing the problem to the degree possible, and including screenshots if you can. Thanks :)
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/Tech notes/Thread:117244
New forum threads are, frankly, ugly in Monobook for the moment. This is largely because I'm applying styling to Wikia.css instead of Common.css — so all the conflicts between the new forum CSS and our own unique blockquote CSS are colliding disagreeably in Monobook.
It'll be fixed soon — but you don't get all the features of the forum in Monobook anyway. At this point — three years after the introduction of the Wikia skin, you're very much encouraged to just switch over to the Wikia skin permanently.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:117345
I've just filed a bug report with Wikia about errors using the rollback function. Consistently, pressing "rollback" produces an error in which you're told that rollback failed because you've just performed a rollback. It's a lovely bit of thematic timey-wiminess for us here at the Doctor Who wiki, but it's clearly a bug.
So until it gets fixed, be aware that rollback does work, but you'll get an error message falsely telling you it doesn't.
Remember, too, that rollback should be sparingly used because there's no opportunity to add edit summaries with rollback, which can be frustrating to the user whose edits you're rolling back.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:117422
This isn't a genuine discussion thread, but a test of the new forum software. The test will demonstrate whether closing a thread will leave a link to it on the topic page, 118.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:117462
Per a comment made by The Librarian some months ago, the novelisation/adapted from/adapted by lines have been slightly moved in {{Infobox Story}}. Where they exist, they now appear on the first line underneath the image. See: The Lodger, Shada and The Ultimate Foe for typical cases.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:117716
This is just a test of an issue affecting new template placement. Please do not respond to this thread unless you are a Wikia Staff member.
- CzechOut
Here's what's happened. I created the above message, in which I intentionally referenced a template, {{this is a new template}}, which did not then exist. Then I created {{this is a new template}}. Then I reloaded the page. Instead of displaying the now-created {{this is a new template}}, I get a false red-link. It's obviously false, because, well, look at the number of times I've got a blue link in this post. The only way that the red-link in message #1 will resolve is to actually re-publish the message.
Odd, no?
- CzechOut
- CzechOut
Glad I checked that, cause that doesn't work, either. As you can see, File:TestyTestyTesty.jpg does now exist:
- CzechOut
And the final link in this non-functional chain can be found at file:TestyTestyTesty.jpg itself. Like seemingly all links to anything in the Board Thread namespace, the "File Usage" link at the bottom of the file page doesn't work:
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:117799
There are some peculiarities about editing in the new forums, and I'd like to assure users that we've already filed a number of bug reports to try and fix them.
Vertical height of input box
If you're typing in the "start a discussion" main text box, it will expand vertically as you type more stuff, allowing you to see the entirety of your post before you publish it. THat's great, and that's how it should be.
However, this same thing does not happen if you're replying to a post. There, the vertical height is always the same, which means you have to do a lot of scrolling to get through your post.
According to BertH, this is a bug, and is the result of the fact that we've disabled the Visual Editor on this wiki. This seems like the kind of thing that Wikia will almost certainly fix, because it's such a clear bug.
From time to time, particularly when starting a new thread, the "Post" and "Preview" buttons are greyed out, and therefore unusable. Wikia Staff are completely mystified by this one, because they see it across Wikia, but they can't see a pattern behind it.
The only thing that cures it is apparently simply waiting — and maybe clicking around the "Start a Discussion" box a bit. Eventually, the Preview/Post buttons will be usable.
You can bet this one is a high priority for the Engineering department. The problem is figuring out the pattern. If you notice any sort of pattern at all, please submit a report to Special:Contact/bug.
Autosuggest
It's obviously critical that we get autosuggest back into the forums. It's a bummer trying to figure out the exact name for some of our pages without autosuggest. This isn' a bug, but it does seem to have wide support as a feature request. I wouldn't be surprised to see it come back in the first quarter of 2013. But neither would I be surprised if it didn't.
If you want autosuggest in your forum posting — please, please, please ask for it by submitting a Special:Contact note.
Symbols and accented characters
In the normal editor, we have easy access to MediaWiki:Edittools, a nifty little palate of lots of different characters used in various other languages. Like, crucially, Welsh and French and Spanish and Greek — all of which appear with some regularity in Doctor Who
But this has been taken away in the MiniEditor (yes, that's its official name) used on the Forum. However, I've been told by Staff that it's okay to hack a link to it on the MiniEditor window.
So with this issue, basically we're being told what Wikia won't fix it any time soon, so we have permission to fix it ourselves. I'll certainly give it a try, or talk to people who can, but it'll be a few weeks, probably.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:118118
Pursuant to an earlier conversation, we elected to open a new namespace to house the Discontinuity index and the Timey-wimey detector.
Well, the Dectector's been reopened, but the Discontinuity index — being much larger — is gonna take a bit more work. Rest assured that it'll be ready for Christmas. Until you hear the all-clear, though, please do not post at any thread in the Discontinuity index.
Also, please don't try to hep by moving threads. The bot is fully engaged at this point and things are well in hand.
Sorry to fans of these two areas for curtailing their enjoyment as we switched over to the new Forum and had to deal with unexpected fallout.
- Cult_Of_Skaro
Gotcha. Not surprised by the size of the Discontinuity Index. Those people had a tendency to, erm, forget stuff. :P
- CzechOut
Well, it's not really them, but us. There are a lot of little bits and bobs depending on the word "Forum", which now have to be changed to "Theory".
- Cult_Of_Skaro
I'm saying there really was a whole lot of discontinuity. Which considering the sheer number or books, audiobooks, etc, isn't surprising.
- CzechOut
Theory:Doctor Who television discontinuity and plot holes has now been reopened. Due to a number of errors in the way that threads were being created for the theory:discontinuity index as a whole, the automated process of changeover has been slowed.
As new threads are created, please
- Ensure that you are in the Wikia skin
- Pull down the "preloadable format" drop down to "discontinuity"
- Use the resulting format.
This will ensure that all pages in the discontinuity index have a consistent look and operation.
Announcements will be made as other aspects of the discontinuity index are re-opened, but at least the Doctor Who TV area is open in time for Christmas.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:118714
HI I was invited to join by a moderator(?). [hope that's right :)], in September but encountered difficulty with the funny typed words. The "prove you are not a robot" thing.
I messaged the nice person who invited me back, with these difficulties, but before I received a new hyper-cube, I ran into some technical problems, and was unable to return in a timely manner. I did receive further instructions and can't remember the moderator's screen name.
Can you help me please?
- CzechOut
What's the exact problem you're having with the captcha (the "prove you aren't a robot" thing)?
- 184.144.56.93
The text has been distorted, for security purposes. But the text as it appears makes it difficult to differentiate the spacing, and between letters like, an upper case "I" and a lower-case "L". Also because this is a security feature, the "new words for each attempt" makes it IMPOSSIBLE to attempt to make corrections. Add the fact that my password also disappears with each attempt and I'm stuck.
- CzechOut
I'd suggest that you use your browser's controls to zoom in on the page until it's perfectly readable to you. On most Mac browsers this is done through ⌘+, and I guess on Windows machines it's usually alt+ (or maybe it's ctrl+. (If you want to go the long way round, the command to "zoom in" is almost always under your browser's "view" menu.)
Then, keep reloading the page until you get a captcha that you can definitely read. Eventually one will pop up that will be pretty clear.
I'd also suggest that when you're creating your account, make the password stupidly easy — some word or number sequence you definitely won't screw up. Then, after your account is successfully created, you can then go back to Special:Preferences and change the password to something more secure.
Give those suggestions a try. Whether they work for you or not, please come back here and tell us how you got on.
- Merrystar
Hi. If you are still having trouble with the captcha (blurry word), you can try using the sign up here. That is a different captcha system with an audio option.
Hope that helps!
If you continue to have trouble, please contact Wikia.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:119783
The site will be undergoing a fairly significant facelift for the next few days at least. The main goal is initially to change the site colour of blue over to the TARDIS blue recently revealed as the "official" shade by the BBC. You will experience moments where our original shade of blue will persist alongside the new one. In other words, it's gonna get ugly before it gets pretty.
During this period, be sure to clear your cache often, in order to see the latest state of the wiki.
- 4me-2me
Where can you find the exact TARDIS blue colour?
- CzechOut
Yanno what? I"ve now spent a couple of hours actually probing into this a little further, and I don't think it actually is official. All the sources point back to this page, a blog by an American named Tony Delgrosso. He seems to have some expertise with colours, so I think he's just reporting his findings. I can't at all find anything approaching an official BBC announcement. *Sigh*. Looks like I'm just gonna have to make up another palate, cause this "official" blue is lookin' pretty green so far.
Argh. This probably means even more of a delay in getting the colours recalibrated on the site.
- OttselSpy25
I was gonna say... I mean, I think this new "colour" set up is a bit too dark... I'm having trouble difrentiating between the normal text and the links so...
- OttselSpy25
I was gonna say, I think the new "TARDIS blue" is a bit too close to black... hard to tell difference between normal text and linked text.
- OttselSpy25
That's better.
- CzechOut
Oh. we're nowhere close to finished. The Snowmen leads to a new logo for the programme, which leads to a new TARDIS interior, which leads to a new colour scheme for us, which then gets incorporated into our new logo, which then gets reflected back into the site itself, which then leads to a new front page and basically a radically reinvented site. Lots of little things to make right.
There will be bumps on the road over the next bit of time.
- 4me-2me
Good luck!
- Imamadmad
I'm starting to see the new blue around and I like it. I like it a lot.
- CzechOut
I'm going to be "auditioning" a dark blue theme today. There will be times where the text might be unreadable in the main namespace. Apologies for any inconvenience this might cause.
- OttselSpy25
Okay, so just gonna throw this out there, I dislike the ark blue main background. Not complaining, just saying that I don't like it.
- CzechOut
What's ark blue?
- Lego Whovian
On the contrary, I like the dark blue colour. Throughout Doctor Who's history, The TARDIS has been mostly dark blue, instead of a lighter blue colour which used to be this site's background colour. It makes the site look more professional and realistic. Well done!
- OttselSpy25
... As a background? Your cra-
... Your wro-
... I disagree with your opinion.
- CzechOut
Just because you stop short of typing out the full words doesn't mean you're not in violation of Tardis:No personal attacks. In fact, it's kinda worse, because it shows you think it's just a semantic game. It's not.
- OttselSpy25
I was making a joke about my often poor choice of words. The bottom line is what I actually mean.
- CzechOut
It doesn't read as a joke.
- OttselSpy25
Yeah, that's a good point.
Anyways, let's discuss this new background more.
- CzechOut
While your comments are welcome, it's not actually up for discussion. This is the Drax Cave, not the Panopticon. A discussion on the minutiae of site design would paralyse the project, as your exchange with Lego Whovian has just proven.
Still, I'm not saying that you can't comment, but be aware that site design is extremely fluid. Most users will not be looking at the very latest iteration of the design when they choose to comment upon it.
- Trebligoniqua
I like the changes, except that the links are blue, and are hard to read against the background.
- 86.147.17.138
In my opinion, it's nothing like as comfortable reading pale text on a dark background. It also makes anything printed from the Wikia look horrible.
- CzechOut
Printability honestly wasn't something I was at all considering. I guess I could make a print-only style sheet, but it's not likely to come before the screen style sheet is finished.
- 86.147.17.138
Many thanks for that incredibly quick response! Well, I'm sure there will be further changes to the site's appearance so I'm probably speaking too soon anyway. And anything somebody wants to print they could always paste unformatted into Word.
What I should have said first was, congrats on all your efforts on the site and your dedication to DW!
- OttselSpy25
Okay, so I understand that this "Isn't up to discussion", but I think we need a "Link colour that looks good on blue, for normal pages, as well as white, for the box at the top and at info boxes. The colour yellow doesn't go well with white.
- OttselSpy25
http://tardis.wikia.com/wiki/Fourth_Doctor?s=wldiff&diff=0&oldid=1321849
Also, I want you to tell me what's wrong here.
- CzechOut
Why are you asking for comment on an individual page in a thread about sitewide changes? We still have talk:Fourth Doctor, don't we?
- CzechOut
Patience really isn't your strong suit is it, OS? This is not the final design. And, due to caching ideas, I have no idea what iteration you're looking at anyway. If you're seeing actual yellow, I can only surmise you're behind the times.
Continue to chip in your thoughts but bear in mind that we're probably not looking at the same thing.
- OttselSpy25
Tell me about it, I mean it's like "Let's shoot a scene tomorrow when we're ready" and I'm like "No, we're shooting it today!"
But, I was actually referring to the fact that in the edit comparisons page it white on white. On my version at least... Look, never mind.
- Digifiend
Yeah, I'm seeing the same.
- CzechOut
As I've said, it is comparatively hard work changing from a light background to a dark background. There are many things which have to be changed that you don't have to touch with a light background. The MediaWiki software assumes a Wikipedia-like format.
One of the clear casualties of this is the history page. Yep, that's screwed up at the moment, but only in the main namespace.
Here's the deal people: I'm trying to accomplish something which, to my knowledge, has never been done on Wikia: a dark background theme in ns:0 and a light background theme in all other namespaces. It's gonna take some time, but I think it will functionally help new users know exactly where they are on the wiki.
It will definitely be unique.
- Trebligoniqua
Sorry, I just wanted to make sure that I didn't just need to change settings on my computer.
- OttselSpy25
As the first post suggests, you should propably "clear your cache" on your internet browser. I would suggest looking it up online for how to do it on your said browser.
I would also suggest not doing it for a bit. We're in a rough period.
- CzechOut
OttselSpy25 wrote: As the first post suggests, you should propably "clear your cache" on your internet browser. I would suggest looking it up online for how to do it on your said browser.
I would also suggest not doing it for a bit. We're in a rough period.
I'd strongly disagree. It's often quite helpful to clear your cache frequently. You should be doing it on every page load if possible. Follow these instructions:
Note: After saving, you have to bypass your browser's cache to see the changes.- Internet Explorer: hold down the Ctrl key and click the Refresh or Reload button, or press Ctrl+F5.
- Firefox: hold down the Shift key while clicking Reload; alternatively press Ctrl+F5 or Ctrl-Shift-R.
- Opera users have to clear their caches through Tools→Preferences
- Konqueror and Safari users can just click the Reload button.
- Chrome: press Ctrl+F5 or Shift+F5
Your browser may also offer you the possibility to turn off your cache entirely, often disguised as an option which allows you to allocate a certain amount of disk space to the cache. If you turn that down to 0mb, that has the same effect as deleting your cache on every page load.
It's not a horrible idea to do this. It'll marginally slow down page loads, but you'll see the current version of the page every time.
- OttselSpy25
I wasn't trying to say it was a bad idea... It's just I did it and.... Uhhh.... Blue-on-blue... Ughhhhhhhh
- Eladkse
CzechOut, I like what you've done with the main namespace, but what color do you plan on making links? White-on-white just isn't obvious, but I can't think of a colour witch will contrast with both normal text and the background and go with your palette choices.
- 69.254.165.192
It's impossible to read anything in the Crew sections of pages. White text on white background :(
- Eladkse
69.254.165.192 wrote: It's impossible to read anything in the Crew sections of pages. White text on white background :(
Please be patient - it takes time to change a theme as complex as this one. To echo advice above, make sure you regularly clear your cache, and hopefully the wiki will be in a much more stable state by the end of the week (don't quote me on that though - I don't know how far CzechOut is through the work).
- CzechOut
69.254.165.192 wrote: It's impossible to read anything in the Crew sections of pages. White text on white background :(
It actually warms my heart — and I would imagine Tybort's — that someone cares enough about the crew sections to care that they couldn't see them. Rushed to the top of the list in response, crew sections have now been appropriately themed, and are again visible.
- CzechOut
Eladkse wrote: CzechOut, I like what you've done with the main namespace, but what color do you plan on making links? White-on-white just isn't obvious, but I can't think of a colour witch will contrast with both normal text and the background and go with your palette choices.
Hmmm, I'm wondering if (hoping that?) you weren't looking at a current version of the site when you wrote this. Links are a kind of ice blue, not white.
- Eladkse
Oh, yes. I see now. I can only just tell the difference, but that might be my screen...
- CzechOut
Hmmm, that worries me a bit, because the difference is obvious on my screen. Still, I haven't done mouseover effects yet.
- CzechOut
86.147.17.138 wrote: It also makes anything printed from the Wikia look horrible.
Please clear your cache and tell me what printing looks like on your end. I've added some code that should strip away most of the colour formatting and turn the site's content monochromatic for printers.
[Incidentally, and this is not said in anything other than a helpful way, this is a wiki hosted by Wikia. This is not "a Wikia".]
- 2.101.59.154
The titles &c in tables (e.g., Series 7 (Doctor Who 2005)#Television stories) need to be made visible again -- fairly urgently!
- CzechOut
Digifiend wrote: Yeah, I'm seeing the same [problem in reading the edit comparisons].
Fixed. Should be unmistakably easy to see page diffs now.
- OttselSpy25
I dislike how broken links and normal links are basically the same colour in the main interface.
- CzechOut
So do I. Patience.
- OttselSpy25
I know. Just posting issues, really. Turing out good otherwise...
- CzechOut
Okay, I've seen one or two negatives on the text colors for the main namespace. Are others having problems with the colors? They pass W3 contrast standards, so I'm kinda confused by the resistance to the colors. Anyone who's got a problem with the colors, could you please speak up and say what you find disagreeable?
- Eladkse
Well, I've just run a comparison between normal text and links, and as far as I can tell, the pale-blue links do not meet any of the contrast standards when compared to the white text.
- Imamadmad
I can see the difference, but I must admit it isn't obvious. Maybe if the blue was a bit darker?
- CzechOut
Eladkse wrote: Well, I've just run a comparison between normal text and links, and as far as I can tell, the pale-blue links do not meet any of the contrast standards when compared to the white text.
Could you explain this a bit more? You're talking about link compared to non-link. Why does this matter to you? I'm talking background to text. I'm not sure it's possible to have contrast between link and non-link text and at the same time preserve text-to-background contrast ratios.
Incidentally, what contrast checker are you looking at?
- CzechOut
Imamadmad wrote: I can see the difference, but I must admit it isn't obvious. Maybe if the blue was a bit darker?
Can't be darker and preserve contrast levels with the background.
- Eladkse
I have used multiple contrast checkers that conform to various W3 standards - here, here and here.
Why does this matter to me? Because considering this is a wiki, it would be nice to be able to be able to see links to other pages. At the moment, all I see is light text on a dark background. There just is not enough contrast for me to tell the difference between links and normal text without manually hovering my cursor over every word.
I consider my eyesight to be quite good, and I have calibrated my monitor enough times to know that it isn't a problem at my end.
While I love the darker background, I just don't think it is going to work contrast-wise.
- CzechOut
Okay, I've used all of those tools and the colours pass every time. And not by a little bit — by a lot. None of them suggest that there is a standard for contrast between regular text and linked text, do they? You mentioned that the site had failed an objective measure of contrast. Where?
- Eladkse
Testing #FFFFFF (the 'background' text) against '#D5E9FE' (the 'foreground' text) fails on all of those sites. I am talking about contrast between links and normal text - not the background.
- CzechOut
Okay, but is that a contrast comparison that's part of the standard conventions? I thought all the W3 guidelines were talking about text versus background, not text versus linked text. We've long had on this site undifferentiated text. The infoboxes have long used the same colour for text as well as linked text.
I mean, I'm pretty sure that the standard blue link and the standard red link would fail that test, too.
- CzechOut
- Standard text color is #000000
- Standard link color is #006cb0
- Standard red link color is #ba0000
- Contrast of text/link is 3.8:1, which fails
- Contrast of text/redlink is 3.1:1, which fails
I'm sure it's a little bit more of a fail for the two blues of the current design, but if the standard is a fail, what would you have me emulate?
- Imamadmad
Just in case it hasn't come up yet, links are practically impossible to see in the forums, as you can see if I link to a random page. So, while discussing link colour in the main space, can it also be noted that they can't be seen here either?
- CzechOut
As it now says atop every page, we're changing our colour palette. There are a lot of different things to check, and I temporarily leave some things that look particularly bad in one location to investigate how they look in another.
- Imamadmad
IGNORE THAT COMMENT. IT WAS JUST MY MONITOR (well, the monitor I was borrowing) AT THE TIME. I actually tried to delete that comment, but obviously that didn't work. It said it deleted as I asked it to, but obviously it didn't.
- CzechOut
To your deleted-but-not-quite point, however, there are indeed some points where the colors don't work yet.
- 76.88.90.110
oi. i just wanted to say awesome work.
- Digifiend
We currently have blue on blue making text on the front page and articles invisible. I assume it won't be staying that way for long?
- CzechOut
See our Twitter feed.
Nope. Won't be that way for long, but "long" could be a few hours.
- CzechOut
SmallerOnTheOutside wrote: On the final version, you are going to keep the fonts consistent, right? As it stands now, it changes the font and size when you switch between the two schemes. I'm just letting you know of small things in case somehow you fail to notice. I know it's not final and I highly doubt that the final version would still have this mistake regardless. Still, to be safe...
Just moving this over from another thread, so that it's preserved, but in the right location.
- CzechOut
Just to answer one question there, I wouldn't count on the fonts being consistent in the two design. I don't consider it to be a "mistake" in any regard.
It's my current theory that sans-serif fonts will be used on the LOD design. This is because sans-serif fonts are easier to read on computer screens against dark backgrounds. It's also because some people really liked having a serif font, since it reminded them of reading a book. Setting that serif font against a not-exactly-white background maximises its readability, and I'd be loathe to get rid of that unless I found another font that dramatically improved legibility.
So, the DOL design will retain the previous site design's ethic: serif for articles in ns:0 and sans-serif elsewhere. This is a subtle visual cue to let you know when you're reading an in-universe article and when you aren't.
I might change my mind on this, as I'm actively looking for a different font altogether from the ones we currently use. But this will require importation of the font, something we don't currently do. It should also be pointed out that there was a forum question asked early last year specifically about the sans-serif font, with most respondents supporting the serif.
That said, I'm "shopping" new fonts a lot these days so you will find different fonts in different parts of the site. Currently, for instance, the sans serif on offer in the user namespace is quite different to the one you'll find here in the forums. And certainly in the template namespace, we use monospaced fonts for clarity.
My intent is to return to a situation where we have a single font family for each of the major types — monospaced, serif and sans-serif, and for each of these types to have a meaningful use.
But you shouldn't expect for DOL to work like LOD. It would be extremely illogical to have taken about a month making sure that we have the colour change option and then not bother using it.
You'll note, for instance, that plenty of things are different between them, already, and not just the fonts. The color of the search area, the color of the message alerts, the color of the menus, the color of tophat templates — lots of things are different.
- CzechOut
Eladkse wrote: While I love the darker background, I just don't think it is going to work contrast-wise.
This has haunted me for about two weeks. I've literally been spinning a colour wheel ever since. I've gone to BestBuy and moved through a rack of different computers, where I've only been able to see some variability, not the full-on I-can-barely-read-this-thing syndrome you reported. I've gone to the Apple Store, where no monitor in the joint had a problem at all.
Wikipedia:Terry Nation: Where are the links?I've now gone through the design and made sure that, except for the infoboxen and pre and one or two other special cases, white means ordinary text and blue only means clickable text. And then I've examined it under several colour blindness emulators.
I honestly still can't see the problem, but it does appear to me that I've made the blue more distinct from the white without making the blue fail against the background. To me, it's even clearer what's a "blue link", what's a "red link" and what's neither.
As you can see to the right, I've taken screenshots of our site's Terry Nation article and Wikipedia:Terry Nation. Now these are monochromatic shots, mind you, to test the worst kind of colour blindness. The settings are exactly the same for both shots and neither has been retouched in any way. To my eye, you can actually tell where the links are on our site, but you can't tell at all what the blue links are at Wikipedia.
Since I've never clearly seen the problem across several different monitors, browsers and operating systems, I really do need your help. Am I still off base? Do the pictures at right tell me something other than, "we've got better contrast than Wikipedia"? Honestly, I'm not saying you're crazy or even in the same ballpark as "wrong". All I'm saying is that I don't see what you see, so I need you to tell me what you see.
- Eladkse
The contrast is better than it was - I can certainly tell the different now. Whether that is because of your changes to a slightly darker shade of blue, or that my eyes have adapted is another matter. But I wouldn't worry yourself - just get the styling finished so we can enjoy this marvellous site once more. No one else seems to have issues.
- CzechOut
Well, that's a bit of a relief. Thanks for verifying that things have at least gotten better. :)
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:119952
Mobile users may have noticed for quite some time that a mysterious word "left" appears at the top of a lot of our pages, viz:
A technical way forward has now been found, so this mysterious "left" should soon stop clouding the mobile experience. If this solution ultimately requires editors to do anything, I'll keep you apprised in this thread.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:120676
Not quite sure what's going on yet, but there are some Wikia changes to the forums that are placing a lot of new buttons in the speech bubbles and creating good deal of confusion. I'll try to figure out what's going on.
- CzechOut
Word from Wikia is that they had a bit of a disruption on their end and the CSS was thrown out of whack for a bit. Everything should snap back in place shortly. If the forums look weird to you, I'd suggest bypassing your cache. Thanks to Semanticdrifter for his quick response.Clear your cache often around here
After changes are made to this site's CSS or Javascript, you have to bypass your browser's cache to see the changes. You can always do this by going to your browser's preferences panel. But many browsers also offer keyboard shortcuts to save you that trouble. The following shortcuts work in the versions of the browsers that Tardis currently supports. They may not work in earlier versions.
- Firefox: hold down Shift while performing a page reload.
- Opera offers no default keyboard shortcut, but you can create a custom keyboard shortcut with the value Clear disk cache
- Safari users should simultaneously hold down ⌘ + Option + E. You may need to enable the Develop menu first
- Chrome: press Ctrl + F5 or Shift + F5 while performing a page reload.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:121031
Hi, over at RangerWiki (recently renamed from The Morphin Grid: The Power Rangers and Super Sentai Wiki), one of the other admins copied your Lock template earlier (see here). But we can't figure out how to get it to appear at the side of the page instead of above the page content. Could you please tell us how it's done? Discussion on RangerWiki
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:121411
This thread will house announcements about new templates which you might find useful.
Please do not reply in this thread. If you have questions about templates, please start a new thread at Board:The Panopticon, using the name of the template as the first word(s) of your thread title. Thanks. :)
- CzechOut
- CzechOut
New templates for easily adding official Twitter and Facebook links to the bottom of pages about real people are now online. See {{twitter}} and {{facebook}} for simple instructions.
Example page is J. T. Colgan.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:121539
As part of the 2013 site redesign, I've been forced to conclude that navboxes can no longer have pictures. I regret having to remove this feature, because I know precisely how much work has been involved in creating these specialised, 80px width pics.
However, as we added more and more columns to these navboxes (note how the more recent series of DW have more columns at {{DWTV}}), the mathematical formula behind the assignment of column widths could no longer work, in some browsers, in the fixed-width Wikia skin. Many of our navboxes were in fact wholly broken for a long time, but the white background kinda disguised the error. The dark blue background wasn't so forgiving. Ever since our new dark/light duality began, it's been screamingly obvious that something was wrong with the navboxes.
There are a number of possible fixes for the problem, but by far the simplest is just to remove the ability of the navboxes to accept pictures. So that's been done, and {{DWTV}}, {{DWN}} and others now have workable widths again, and I can proceed with actually styling the boxes so that they're legible in the dark skin.
Thanks to all who helped illustrate these navboxes up to this point. Your work was appreciated.
- Memnarc
That's a shame, but if it'll help the site, I guess it's for the best.
- SOTO
As Memnarc said, a shame, but unfortunately necessary. Thank you, Czech, for taking the time to fix this.
- CzechOut
Consequent to the above announcement, you will notice over the next few hours (maybe as long as a couple of days) that the colours in infoboxes will be radically shifting. This is just so that I can identify certain parts of the code. It's been a long time since I installed this part of the code so I've kinda forgotten what controls each part of the box.
Having coloured each part in a clearly-recognisable way, I can then more swiftly style it in both the light and the dark CSS themes.
Apologies for any inconvenience this causes you. Generally speaking, though, the navboxes should be fairly legible in one of the two skins at all times. With any luck. :)
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:121686
I can't see the categories at the bottom of any page, nor are existing categories showing up in the box when you edit the full page.
- SOTO
I noticed that too. Same here. I couldn't tell if the categories I was adding actually worked.
- Shambala108
I'm not having this problem. Maybe it has to do with your browsers? or your preferences?
- Tybort
Seems to be on Firefox, and not IE or Chrome.
- SOTO
Happening to me on Chrome.
- SOTO
Anyone else experiencing this? If not, I'll add a screenshot so you know what's going on.
- SOTO
Fine. Delete my post at the other thread. I'll ask it here: are there any browsers where the categories do work?
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:121721
Wikia have been messin' with categories since last week, and they'll be messin' with them until at least next week. Most of our styling is now gone. And those who had installed MediaWiki:FixMe.css will no longer see red-links for categories that haven't yet been created. In fact, most people can't see any sorta categories.
The situation is very fluid, so I don't really have a great ETA for the return of normal category operations. But I'll keep you apprised of changes as they happen.
In the meantime please do not panic and start adding a ton of categories. The categories that were there are still there. They just aren't displaying properly.
- SOTO
I'm at the moment completely incapable of adding categories, at least not through the category box in edit or through the bottom of the page. I tried adding categories manually, by adding Category:Name of Category to the actual text, but I'm not sure if it's been working, as I can't even see the categories, period. I'm using Chrome? Is there a browser where you can see the categories?
For example, on Zohra Sehgal, I tried adding an As of tag, which didn't work. Then I tried adding Category:Articles containing potentially dated statements from 2012. Which didn't work. I tried many things. I'm not sure what worked.
- CzechOut
Read the title of this thread and post one. Categories are down. Please do not use this thread to tell me that you're experiencing problems with categories. I know that you are. That's why I started this thread.
I will keep everyone informed as the situation changes.
- SOTO
I was just asking if there was one browser that worked. I'll take that as a no.
- CzechOut
Categories are basically back up again, but the whole module has no styling at present. You may expect changes to the styling over the next several days.
Hidden categories no longer display, and there is nothing I can do about this as yet. This seems to have been either a bug introduced by this latest round of Wikia updates, or an intentional and unpublicised deletion of a feature.
I've sent in a bug report to get more information.
The ability to have redlinked category names will not be restored until at least next Wednesday (and even then, you'll have to have installed MediaWiki:FixMe.css in your personal css for it to work).
- CzechOut
Wikia have responded that the disappearance of hidden categories was unintended and that it'll be fixed soon. There is a temporary workaround, but it will remove the "add category" button from the category box — meaning that you'll be forced to edit a page to add a category. If you'd like to avail yourself of this workaround, go to Special:Preferences/Editing and click "disable category module". Hidden cats will then show.
- CzechOut
At present, Wikia have it that the CSS for having the Category Module turned on is different than the CSS used when the Category Module is turned off. Thus, if you perform the action described in the above post, you will see that the styling of the category area immediately changes.
Until Wikia confirm whether this is the way they actually want things to be, I'm not going to spend a lot of time styling the category module for the "disabled" or "off" position. Those wishing to see hidden categories will therefore have an ugly-looking category module for a bit.
- Moreno12
hi
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:121760
It has been confirmed with Wikia Staff that IP users do not get message alerts. Although they are supposed to, this feature has a history of breaking and needing to be fixed. This means that communication with IP users cannot be relied upon to actually reach the intended recipient even if the user has a stable IP addy. (Many IP users, of course, are wholly unreachable because they edit wirelessly or in other environments where their IP addys change rapidly.)
Accordingly, IP users are hereby warned that they may be blocked without warning, and even indefinitely, since Wikia Staff have now confirmed there is no reliable way to communicate with you. Blocking is the only effective protection the wiki has when a pattern of mistaken or even unhelpful edits emerges from an IP editor.
We'd much rather just talk to you about the errors you're making than ban you. Therefore, this wiki strongly urges you to register an account so that you may enjoy the full benefits of membership.
- Moreno12
hi
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:122313
The site indicates that several replies have been left in the thread "Cybermen merging universes", but when I access it, I can't see any replies, just the original message. Please help.
- SOTO
Several? I personally see only the original message and my response. Either I was the only one who responded and your computer's wibbly, or, for some reason, you can only see the original message and whatever you've posted. Can someone post something there as a test?
- Shambala108
OP, at SmallerOnTheOutside's request, I posted a test message on the other thread. It's not much, but can you see it?
- SOTO
Shambala tested. It worked. Are you sure several people replied?
- SOTO
You're too quick for me. :-P Can you just confirm that you can see my two responses there? I can see yours.
- CzechOut
82.20.113.152 wrote: The site indicates that ...
What do you mean? Where are you seeing this indication? What's telling you that multiple responses are there?
- 82.20.113.152
I just did a test post there. It showed up at first, but when I refreshed the page, it had disappeared. No replies were visible earlier when I looked at it on a library computer, so it appears to be a problem with the site.
- SOTO
It's a problem with your specific computer. It's working fine on all of ours. What browser are you using? Also, try clearing your cache.
- Imamadmad
Well, it seems to be a problem with more than just 82's computer. It seems to be a Wikia bug. I have heard another IP complaining on another wiki I edit at that his replies haven't been showing up in the new forums (aka this kind of forum rather than those still present for the Howling and Theories) from his perspective, and so he's sent a special:contact telling Wikia of this problem and apparently in Wikia's reply they said that others have reported the problem as well and it has been passed "straight along to the technical staff for investigation". So, if anyone was interested in this problem, Wikia staff are trying to fix it and you can probably get more through them, or I could just link you to the discussion on the other wiki if you want (where the other user with the problem has been posting Wikia's replies to his messages).
- Imamadmad
Well, it seems to be a problem with more than just 82's computer. It seems to be a Wikia bug. I have heard another IP complaining on another wiki I edit at that his replies haven't been showing up in the new forums (aka this kind of forum rather than those still present for the Howling and Theories) from his perspective, and so he's sent a special:contact telling Wikia of this problem and apparently in Wikia's reply they said that others have reported the problem as well and it has been passed "straight along to the technical staff for investigation". So, if anyone was interested in this problem, Wikia staff are trying to fix it and you can probably get more through them, or I could just link you to the discussion on the other wiki if you want (where the other user with the problem has been posting Wikia's replies to his messages).
- CzechOut
Unfortunately, I never got enough direct evidence from the OP to fully understand the problem, much less offer a possible solution.
Nevertheless, it is safe to say that this is clearly a problem affecting IP users only, and that IP users can't help much with diagnosis, because they're not ordinarily able to upload pics to any MediaWiki wiki. That makes diagnosis of and solutions for your particular problems extremely slow-going.
IP user problems often, regularly, usually, almost always, go unseen for months at a time — because the people who are most likely to report a technical fault are least likely to be seeing Wikia as IP users do.
This is yet another reason that we strongly encourage you to create an account. It takes less than five minutes and you'll be engaging in the site in the most dynamic way possible.
- Imamadmad
Well, the problem has been reported along with screen shots and if you're interested to find out what Wikia has said about it, see w:c:drwho.answers:User talk:Imamadmad#Lost Messages. As much as you may wish they would, not everyone is going to get an account, so it's probably best to at least spare a little thought to the minority of editors who may not yet have signed up. You never know if they might post something here of importance which will then not show up for others to see. Anyway, ignore if you want. Just trying to pass along info I thought you might like to know.
One of the advantages to having an account is that you simply get more out of Wikia. Membership, in other words, actually does have its privileges. I think people sometimes feel that because having an account isn't required that there is no real difference between having an account and not having one. And that's simply not true — as this thread makes pretty clear.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:123289
I just want to know if this happened to anyone else: I was editing, and, all of a sudden, instead of loading pages, I kept on getting messages that I didn't have permission to view the pages. I couldn't post in the forums, either, even though I already had the page open. This went on for about an hour until around 10 minutes ago (or at least that's when I noticed it was working). I couldn't go onto other wikis either - I tried as a test. I notice that there were no edits during the interval when it was down - did anyone else experience this? I'm on Google Chrome (PC), by the way.
- SOTO
Sorry. More like a half an hour/40 minutes.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:123470
I'm sure you've all noticed that barely anyone is editing anymore. While I can't speak for the others, I know why I haven't been editing:
Basically, nothing works. I can't post on threads, I can't edit, I can't follow pages, give "kudos" to messages, no mouse overs work, nothing. I can't bring up my toolbar, either. Clicking on the arrow next to edit doesn't bring up the menu. The time thing at the top is gone. When I try to edit, it simply "establishes interface with TARDIS" perpetually, never loading. Even the Wikia stuff at the top (START A WIKI, Video Games, Notifications, etc...) isn't working!
This is happening on my computer (on every browser I have: Chrome, Internet Explorer, and Firefox) and, surprisingly, also in my iPhone, both on Chrome and on Safari. For some reason, though, it's working on my iPad, which is where I'm posting this message right now.
It is, unfortunately, a real hassle to edit on an iPad, which is why I've had to put a pause to my current project and all editing here, save a little edit a day so as not to lose my day quota. :-)
I've also noticed that certain major players here, like CzechOut, have not edited since Tuesday or Wednesday. Is this perhaps related? Are other people experiencing this? Either way, I would like this problem to be fixed in some way. I at least want Wikia to be aware of the problem!
Can an admin still here perhaps look into this?
- Digifiend
Seems to be a CSS issue, as Monobook is unaffected.
- Imamadmad
Although I personally haven't been experiencing any issues, Wikia tweeted that they were fixing some loading problems or something like that which were appearing across Wikia, so it seems they know about this. See https://twitter.com/Wikia_Community for their twitter feed where they tweeted this to see any updates to the situation and tweet @ them if the problem still doesn't seem to be fixed.
- SOTO
It took like 20 cache-clears, but it appears to be working now. Reply please to confirm that you can read this, just in case.
- Shambala108
I see your message SmalerOnTheOutside, and I was having the same problems too, keeping me from my project too :P
I tried another wiki, and the problem occurred there too, so it's not just us. Things do seem to be back to normal, finally, hopefully, fingers crossed.
- SOTO
Good. Thanks, Shambala.
Thank God it's working. You know, the wiki's been awfully quiet while I've been gone. Something like an edit an hour (once in a while, two). You three are here, plus OS25, The Librarian, TARDIS2468, Revan, Minimitch, Tybort...
...Okay, fine, I take that back - there are still quite a few of us. Anyone know why Czech's been gone for five days?
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:123637
I've noticed a few reports about a possible bug in the Game of Rassilon, so I thought it was time to reissue an old clarification.
For those of you who care about winning the various Tardis Key awards — that is the achievements having to do with consecutive days of editing — please note that there is no bug with the software. A day is defined as that period of time between 0000 and 2359 UTC. The UTC is very important to note. It's absolutely possible to edit on consecutive days in your own time zone but still miss a day. This is true even if you're editing in Britain, because there's a part of the year where the time on your watch and UTC are not the same thing.
Before reporting a bug, please make sure that there is not a gap of more than 23h59m between any two of your edits. If there is, you have legitimately missed a day.
There is no mechanism for resetting your clock or fixing any problems with respect to this award. You must be mindful of the passage of time in UTC.
Also, you must be aware that there are times when Wikia is briefly down for service. It is possible for such a period to come at just the one time of the day when you have time to edit here.
Neither Wikia nor Tardis can "compensate" you if you attempt to edit and are unable to do so because of a network outage. You are encouraged to edit at a variety of times throughout the day to protect yourself from isolated connectivity issues.
- Bubblecamera
What an odd coincidence that this should be posted today! I had only yesterday broken my 71-day streak of edits. (However, I had no intention of reporting a bug, I missed it fair and square :) )
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:123716
On the Theory:Timey-wimey detector, the Forum:Panopticon archives and Howling:The Howling archives, the list of threads are missing and instead there's code showing, followed by a blank thread list. This seems to be the case on IE, Firefox and Chrome.
- CzechOut
I see no evidence of the situation you're describing. Please provide screenshots.
- Tybort
It's a Windows 7 OS, if that helps. -- Tybort (talk page) 16:58, March 6, 2013 (UTC)File:Timey-wimey messed up.jpgTimey-wimeyFile:Panopticon archive messed up.jpgPanopticon archiveFile:Howling archive messed up.jpgHowling archive
- CzechOut
Please provide exact version numbers of browsers depicted.
- Tybort
Firefox 19.0, Internet Explorer 9.0.8112.16421 and Chrome 25.0.1364.152 m.
- CzechOut
Are you quite certain you've cleared your cache?
- CzechOut
I'm completely unable to replicate this problem in any of the latest versions of Firefox, Safari, Opera or Chrome. Of course, I use a Mac, but OS-specific bugs are extremely unlikely at Wikia. There was a problem with forums reported a few days ago, so if you've not cleared your cache recently, you could still be seeing the problem.
- CzechOut
So has this problem abated for you?
- Tybort
Yes it has. Not sure how, but yes.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:123741
Please note that Wikia have temporarily lengthened the delay on autosuggest to 4 seconds. This means that from the moment you give at least 3 letters to the searchbar or link, you have to wait 4 seconds before any responses are produced.
This is temporary, and will be fixed either in tomorrow's code upload (it's been pushed back this week by a day, and so is occurring on Thursday instead of its usual Wednesday), or in next week's.
In the meantime, I'll be working over the next few days to fix autosuggestion's formatting problems here locally that we've had to endure for a few weeks because of other Wikia changes that have now settled down.
With any luck, we'll have completely normal autosuggest functionality returned by the 30th.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:123917
Something's not right over at Tardis:Help. I'm getting this in both Chrome and Safari. It's saying DPL error. I recall seeing it on a few other pages, too.
- SOTO
I'm getting the same thing, on both Chrome and Internet Explorer.
Generally speaking, they resolve after no more than a day. So if you see one, make a mental note of it, but don't report it unless it persists for longer than 24 hours. They're almost always the result of Wikia, and not Tardis, changes.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:124018
I know this is probably completely temporary, and I've only been having these problems for less than an hour, but, just in case, I'm posting it here:
I'm on the latest Google Chrome on Windows 7.
- SOTO
The forum issue seems to only be on the Panopticon; not here.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:124158
I need everyone to go here, then proceed to section 3.3 (called "Help pages") and confirm whether what they see is substantially the same as the image at the right.
Please answer below with a simple "yes" or "no".
- SOTO
No
- Mini-mitch
No
EDIT: Yes, now I can. Works fine on Google Chrome version 25.0.1364.152 m
- CzechOut
Whoa. Wait a minute. You're not seeing that? Please provide screenshots of what you are seeing.
- SOTO
- CzechOut
What browser version number and OS version number is this, please?
- CzechOut
Mini-mitch: are you throwing errors like this, too?
- SOTO
Me: Google Chrome (Version 25.0.1364.97) on Windows 7 (not OS). Mini-mitch?
- CzechOut
What do you mean "7 (not OS)". Windows 7 isn't your operating system? Could you please provide your numerical OS?
- SOTO
Oh. Right. I feel like an idiot. Windows 7 is my OS. I'm having trouble finding this "numerical" operating system you speak of.
- CzechOut
For the moment, please again look at Tardis:Help and tell me what you see.
- SOTO
Whoa. Now it's working. What did you do?
- ComicBookGoddess
Working in iOS and Windows 8/Chrome.
And you don't want to know how much of a pain it was to figure out where they stuck winver in Windows 8. I'm still not sure I know where it is. :)
- Shambala108
Yes (IPad Safari)
- SOTO
Figured it out. V6.1
- CzechOut
Okay, so the deal is this, people. Basically we're waiting for the cache on each of these pages that use DPL to be rebuilt. It does happen naturally over time, but if you encounter a page that starts throwing these "dpl tag not found" errors, just perform a minor edit (like maybe edit one space out of the page) and republish it. This will force the page to rebuild and it should make everything snap back into place. Otherwise it will self-correct.
I'm still not entirely sure why this issue affects Windows browsers, and I'm really not sure why I'm getting different results out of iOS 6.1 than ComicBookGoddess.
Additionally, this issue doesn't affect any other skin — just oasis (wikia).
- Bubblecamera
Yes. Currently on my Mac, using Safari. Will check with Firefox now.
- Bubblecamera
Yes for Firefox too.
- Cult_Of_Skaro
Yes. Google Chrome Windows.
- PrydonianShadow
Yes (Google Chrome)
- OttselSpy25
Yes (Opera)
- Silent Hunter UK
Yes for Firefox.
- Revanvolatrelundar
Yes.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:124551
After months of harassing our friends in Wikia's mobile department, we now have bullets in wikiamobile.
This is an almost revolutionary change that alters the nature of several discussions we have ongoing in the forums. Thanks to Mira84 and his team at Wikia's mobile desk for helping wikiamobile work a little bit more like a "normal" skin. (And thanks to ComicBookGoddess for the photo.)
Everyone please take a moment to thank Mira84 for this change. It means we don't have to reformat tens of thousands of pages just so they would be basically readable in wikiamobile. (And don't forget, about 20% of the people who come to our site do so through wikiamobile.)
- OttselSpy25
Thanks Mira! :)
Does this mean that bullets in references sections is now a non-issue?
- CzechOut
No. It means that the question is now one of what's the better format, rather than of how to respond to a technical need.
- Mira84
I'm glad we were able to help you guys out :) I must say the pages look much much better :)
- SOTO
Mira84 wrote: I'm glad we were able to help you guys out :) I must say the pages look much much better :)
Well, thank you very very much, Mira. This was one of the reasons, along with inability to actually edit, that I always switch to desktop mode on my mobile. Once again, thank you! :)
- Shadowninja016
Great!
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:126904
ACK I've noticed in recent days the main colors for the TARDIS Wiki is dark blue or black lettering on dark blue background. I have to highlight the text to read any of it.
- CzechOut
Could you please provide a screenshot? That doesn't appear to be the general case, though it may be true in one or two spots.
If you don't know how to take a screenshot, could you please give a link to the page where you're seeing this?
Thanks :)
- CaptKirk42
It is pretty much the main data core pages. The forums are fine.
- CzechOut
What browser and version number are you using? This isn't the way the site looks in the latest versions of Safari, Firefox, Opera or Chrome.
(A temporary workaround for you is to hit the button that says "Change colours" btw.)
- CzechOut
If you could please provide the Firefox version number you're using that'd be great.
Also, I kinda sorta think that you may not have been here in a while, and you may be looking at a cached version of the page. Try these instructions:
Clear your cache often around hereAfter changes are made to this site's CSS or Javascript, you have to bypass your browser's cache to see the changes. You can always do this by going to your browser's preferences panel. But many browsers also offer keyboard shortcuts to save you that trouble. The following shortcuts work in the versions of the browsers that Tardis currently supports. They may not work in earlier versions.
- Firefox: hold down Shift while performing a page reload.
- Opera offers no default keyboard shortcut, but you can create a custom keyboard shortcut with the value Clear disk cache
- Safari users should simultaneously hold down ⌘ + Option + E. You may need to enable the Develop menu first
- Chrome: press Ctrl + F5 or Shift + F5 while performing a page reload.
- CaptKirk42
Firefox 19.0.2
- CzechOut
And you're sure you've cleared your cache? I'm on 19.0.2 for Mac and cannot replicate your issue.
- CaptKirk42
"Firefox: hold down the Shift key while clicking Reload;"
Ah that seems to have done the trick Thanks.
- CzechOut
Yeah, clearing your cache is really important around here, because we mess hard with our CSS. Basically, you should remember to clear your cache at least once a day, just to be safe.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:127351
I dont know if this is wikia as a whole or just tardis data core, but the clock up in the top right corner is wrong.
It seems to show GMT, but we have moved to BST (this is in the UK)
I note that the post here about the Game of Rassilon makes reference to UST, (generally the same as GMT)
at this point I am just confusing myself and think I should be heading for bed, but I'm not sure what time it is....
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:127566
I forgot to post my traditional "welcome to British Summer Time" greeting this year, and I apologise for the confusion. Every year, we get some new users from the UK who suddenly get very confused about what time it is, and they swear blue that the clock Wikia is using is wrong.
It's not.
WIkia uses UTC, not BST. This means that when the British go on Daylight Savings, as happened a few days ago, British local time skews off Wikia time by an hour.
There is nothing wrong with the clock you see in the upper-right hand corner of our pages, nor with the timestamps that occur when you sign your posts. Most likely if you're seeing an error, you have simply gotten used to there being no difference between Wikia time and your local time, and you now think there is a problem. Alternately, your Special:Preference time settings are set incorrectly, most likely because you failed to allow for Daylight Savings. Thus your account believes it's in a different time zone than you are, leading to a difference between the time on signatures and the time on the clock in the upper right-hand corner.
- Eladkse
Have you ever thought of putting UTC after the clock? It may prevent some of the confusion, and is something some clock scripts on other wikis have by default.
- CzechOut
Yeah, it did originally have UTC, but I edited it out. Some of our more prominent users have really long names, and I didn't want to incur Wikia wrath because the clock pushed the really long names over the word "Lifestyle". I wanna say that one time, long ago, Revanvolatrelundar or maybe Sichamousacoricothingmabob showed me a screenshot of how the wiki looked to them, and that made me drastically reduce the clock width.
- Eladkse
CzechOut wrote: Yeah, it did originally have UTC, but I edited it out. Some of our more prominent users have really long names, and I didn't want to incur Wikia wrath because the clock pushed the really long names over the word "Lifestyle". I wanna say that one time, long ago, Revanvolatrelundar or maybe Sichamousacoricothingmabob showed me a screenshot of how the wiki looked to them, and that made me drastically reduce the clock width.
Fair enough. That's not something I'd ever considered before. (Goes to check own scripts)
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:127715
Since the code update this week, an ad has started appearing in the right rail. Not sure if it's a bug or if we've just lost a benefit of registration. This week's tech update is silent on the matter. The question has been posed to Wikia, and hopefully an answer will soon be forthcoming.
In the meantime, I can only assure you it's not a local problem and we haven't volunteered for some sort of beta testing.
If it does turn out to be a permanent Wikia change, I'll be able to provide you with some code that you can attach to your personal CSS, but I won't be able to disable it at the wiki level.
- CzechOut
Word back from Kirkburn is that it's a mistake. The ticket has been bumped up to the engineers and should be resolved shortly. In the meantime, you will see an ad on the right rail even when logged in.
- CzechOut
New message from DaNASCAT that this was patched late yesterday, and that the patch will be released system wide tomorrow. Until then, you will continue to see ads, even in weird places like Special:Search.
- Doctordoom61
ok
- Cult_Of_Skaro
Doctordoom61 wrote: ok
Why are all your posts 'ok?'
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:127893
If you've only been here since about December 2012, you may not be aware that there was a whole different kind of forum. There are hundreds of discussions, stretching all the way back to 2005, under the old forum hub at Forum:Index.
However, recently it has become more difficult to search those old forums because the option to select the forum namespace (that is, namespace 110) has been withdrawn from the "advanced" tab at Special:Search. We've put in a repair ticket to try to get that namespace added back. Though Wikia have acknowledged the issue, we're still awaiting a final determination on whether this is a bug that they'll repair, or intended behaviour.
Until then, I wanted to apprise you of a manual workaround. All you have to do is add something to the search URL. Let's say that I wanted to look for discussions about "K9" in the old forum space. Here's the URL I would use:
See what's going on? I just tack on &ns110=1&advanced=1 to tell it to go to advanced mode and make the search active in namespace 110.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:128154
Really, honestly, look away.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:128155
There's no more UNIT really.
BRING ME UNIT
Bring me the head of UNIT. On a platter.
- CzechOut
There's no more UNIT. Or TARDIS.
- CzechOut
There's no more UNIT. Or TARDISES.
- CzechOut
I'm not sure IF IT WILL EVER HAPPEN.
- CzechOut
There's no more UNIT. Or TARDIS.
- CzechOut
He took the TARDIS home. Then he took the TARDIS to the park. Then he took the TARDIS all the way home.
- CzechOut
If he went to UNIT, he knew that he might not be able to recover his TARDIS with the same skill that he had obtained the Rani's TARIDS. Of course, he knew that the UNIT lads were willing and eager to serve, especially because their UN bosses were quite happy to gloat to the USAF about their air superiority over aliens.
- CzechOut
The Doctor shouted, "DON'T TOUCH THAT", but no one was listening.
I wish I could say there was a UNIT. Or a TARDIS.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:128198
A lot of users have been moving pages pretty freely in the past few months, but the truth is, this is causing a bit of a headache for admin.
Why user page moves create admin work
See, if you're a regular user, you don't have the power to perform a page move in a comprehensive way; you always leave behind the original page as a redirect. Most of the time, this redirect is completely useless. Worse, the fact that the old name exists means that people can link to it, which means there wasn't a lot of point to moving the article in the first place.
So when we rename (or move) a page, we usually (not always, but usually) need to:
- Get rid of the original, mistaken page name
- Move all the links from the old page name over to the new one
How you can help with page moves
When you come across a page that you think clearly violates our disambiguation or naming policies, please don't move it yourself.
Instead, flag it with {{speedy rename}}. Usage is super easy.
- Determine how many links there are to the current name. If there are under 10, go ahead and manually move them to the new name. If there are over 10, don't bother, an admin will take care of it for you.
- Affix {{speedy rename}} atop the article you want to move, making sure that you fill in the variables, {{{links}}}, {{{user}}} and {{{new}}}.
{{speedy rename|new=Euros Lyn (director)|links=no|user=CzechOut}}
Then I just sit back and let an admin take care of it.
What'll happen is that the information I provided will automatically populate a table at T:SPEEDY. This list will provide admin with all the information they need to decide whether to move a page — more than just adding the info to a category.
Doesn't replace other templates
Note that this doesn't replace {{rename}} — or {{delete}} or {{merge}}. Those templates are still very useful, but they have the effect of starting a discussion about the more difficult cases. For instance, if you wanted to take issue with the name stingray to describe the main adversaries of Planet of the Dead, then you would need to use {{rename}}, because that alien was never actually named in the episode.
Major characters (like companions or their families, or recurring species) are almost never a candidate for using this template. Sure, we'd want to correct simple spelling errors with this template, but otherwise a good rule of thumb is that if a page has over 50 links, or would seem likely so to do in future, settle the matter through a discussion.
{{speedy rename}} is only for those black and white cases where the page move is obviously correct. Maybe you're requesting the addition of a standardised dab term or maybe the addition of a forename or surname that wasn't known at the time an article was started. Or maybe you've done something silly and spelled an actor's name in a way different to the credits.
Whatever the case, remember: {{speedy rename}} is only for those cases where there is absolutely no cause for discussion.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:128596
I spent some time last night creating some year pages and noticed a weird little glitch happening. When I added a year page to the Years category (per Game of Rassilon) all of the other categories on the page would vanish. The century category, the decade category, even an articles needing citation category in one case. If you look at the history for 1847, 2604, 2605, etc, you'll see that immediately after I add the category years I have to re-add the categories that were already there in the previous edit. I don't know if this is because I was adding the categories using the category module, but this has never happened before and seems weird. The articles needing citation category came back easily, all I had to do was edit the page and make no changes. This seems to have been purely a visual thing (I couldn't see it even though it was there), because the category is never missing when you look at the source through the edit history. But the year categories (century and decade) definitely vanish from the page and have to be re-added.
Also, I noticed that for some decades I had to create the decade category page. Is there any harm in creating those category pages now even if we don't have to use them yet?
- CzechOut
{{timeline}} already adds all the categories that are necessary to the article. We have taken to adding category:years to year articles simply because the year pages are currently involved in the Game of Rassilon. When that track is disabled, category:years will be pulled from all the year pages.
What you're describing isn't really a bug, though it's sort of "technically interesting". See, {{timeline}} adds all the categories automatically. Therefore, there are no categories directly on the page. When you add category:years, it's the only "natural" category on the page. For that moment it therefore appears to clear out the page. But if you simply reload the page, you'll see everything pops back to normal.
The "xth century years" and decade categories should never be added manually. It is correct that these categories should not appear in the category module in the editing window. If you ever see these categories while editing a year page, you should manually delete them. They must only be on the page as a consequence of using the {{timeline}} template.
You should simply get in the habit of reloading the page after using the category module. It has other "technically interesting" features that do not resolve themselves until after a page load.
- Anoted
Got it. Went back and fixed the one page you didn't get (thank you btw).
Interesting...and really explains the whole articles needing citation category disappearing and reappearing without my doing anything. But when I look at the histories of these pages, the century and decade category aren't there until readded. What I'm saying is that the articles needing citation category is only missing visually, it comes back without any provocation and is never missing when looking at the source. But the century and decade categories didn't reappear with the article needing citation category and look missing in the source as well. Are you saying that even though they manifest differently they are both products of the same "technically interesting" quirk? Because if so, then that is really, really interesting. They should both function the same way, right? Categories on a page because of a template? What's almost as weird is that while I was editing my brain interpreted them differently. I remembered that the needing citation tag was tied to the template but somehow forgot that the years categories were. Though while it's possible my brain perceived this because of how missing categories came back, I don't think it's possible that they came back differently because I perceived them to be different.
Wouldn't it be easier per Game of Rassilon to add the years category through the template instead of manually, or is there some reason we don't do this?
- CzechOut
What I'm saying in regard to your second paragraph is that I cannot replicate your results.
Do I wish that the categories displayed immediately upon adding the template? Yes. That's the way it's supposed to be. But they don't anymore as long as you're using the category module. If you turn off the category module in your Special:Preferences or use the Monobook skin, things look and feel completely "right".
Even if you are using the category module, however, all it takes is a simple reload to reliably refresh category display. (Well, with the proviso that I simply cannot provide complete support to you, since you won't/can't upgrade your browser.)
The other possibility is that I haven't adequately explained the automated category process. When you add a category by template, you will not be able to see that category in the page history or on the page in edit mode. You will only be able to see it in the category area at the bottom of the page after a refresh. As long as {{timeline}} is in the history, so too are the decade and century categories.
And that brings us to your last question. Why not just have the template add the year, too? It's because of caching issues over which I have no control. Wikia's installation of networked MediaWiki software has notorious caching issues that make changes to templates, particularly in the area of automated category application, take forever. Now, it's fine for new pages. But if you're talking about a template like {{timeline}} that's on around 1000 pages, it can take a while for changes to the categories to kick in. Generally, you have to "touch" the page to get it to re-apply cats. Thus, I made the decision to just add en masse category:years, and leave it up to editors to add that category to any new pages they might add.
I can certainly see the logic of changing {{timeline}}, but having things the way they are means that I only need to strip cat:years from pages, rather than removing then replacing {{timeline}} to get a full refresh.
- Anoted
It's a bit crazy that it's easier to add a category to 1000s of pages than it is to edit one page. Wow!
Thanks for the clarification on the template issue. It seemed like I was seeing categories added by template in the page history. I had to go through the histories a couple times to understand what I was actually seeing. I never would have caught that on my own. I was looking at the differences between adding Years and re-adding Decade and Century, completely missing that Decade and Century weren't on the page history before adding Year. I took what I perceived had happened and supported it with page diffs, never realising that page diffs didn't actually support what I had seen happen. Wow!
Sadly, you've joined us at just the moment that Wikia are transitioning on how categories display, so categories frustratingly display differently in different situations.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:128768
It contains no substantive information, which means that there is no rationale for keeping the page. A thorough search of all available valid sources should be undertaken before deleting, however.
This template links to the "ongoing discussion" which erm, apparently doesn't exist. Sends me straight to the Zero Room. So...where can I go to find this ongoing discussion?
- Shambala108
It should be at Thread:121256.
- Shambala108
What is the name of the article where you found this?
- Anoted
Um, 5 January, 15 March? One of those a think. Pretty sure it's one of the pages in Category:Date pages that need deleting
;)
Weirdly enough when I tried to fix the template, it didn't work. Major huh? moment.
- Anoted
This should not still be linking to 58, and yet it is. Seriously weird.
- SOTO
He ongoing discussion is most certainly there, as it's my current project. There is no problem with the template in my end. And, anyway, the template's only temporary.
- Anoted
Yeah it's working again now, not sure what was going on there. I cleared my cache, opened it a different browser and still. Wonder what was going on there.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:129089
testing potential bug
1:45 exactly
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:129090
Something was bothering me in regards to edit timings. I tested it and all edits to this wiki appear to be back-dated by 3 minutes. Is it supposed to be this way?
- Anoted
Special:wikiactivity and Special:Recent changes have the proper times while page histories, the time on the forums and signatures are all three minutes early.
- CzechOut
Please give me a link to an example.
- CzechOut
Yeah, really going to need an example, because the time of forum posts matches special:wikiactivity.
- CzechOut
Yeah, really not seeing it. This edit is showing the same time in special:wikiactivity, allowing for the fact that edits aren't reported in fractions of minutes. So it's ±1 minute, which is good enough.
Need your methodology. What clock you using, by the way? Hopefully the one on the site? And are you refreshing both windows before doing a comparison?
- Anoted
posted message at 15:50
signature and history both show the edit was done at 15:47
posted at 15:54, half pastedited: at 15:57
- Anoted
The post I just posted noe shows as 3 minutes ago, 15:51
- CzechOut
You haven't answered my question. What clock are you talking about? The diff you linked to shows the revision was at :47 and the sig was at :47. So where's the problem?
- CzechOut
You're not explaining where the 15:50 came from? You're just typing that in. It's not generated by anything. You're just saying it is 15:50.
- CzechOut
- CzechOut
See? 16:00 in my signature. 16:00 on the clock in the upper right hand corner of the page? 16:00 by the post time stamp. 16:00 by special:wikiactivity. I don't see the problem.
- CzechOut
If you've got some proof of a time issue, I really need to know, because it would be fundamentally catastrophic to the wiki. Please don't move on to other issues before we settle this, because I'd need to alert Wikia if there is a genuine issue. It's very important to resolve where your 15:50 came from.
- Anoted
16:02:01 in the upper corner clock. Message is typed, but not yet posted ...30 seconds later
16:02:31 in the upper corner clock. Message has been posted. time stamp on signature is 15:59 15:59 also shows up on my contributions, and at the recent changes page but NOT at wikiactivity
16:05:23 in the upper clock corner--a little less than three minutes after my userpage post, the edit on wikifollowing shows up as 2 minutes ago, which is correct
also, at the forums
16:30:48 in corner clock-about to post forum message
16:31:28 in corner clock after posting forum message. forum message reads three minutes ago
16:31:28 forum post reads 16:28
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:129249
Test
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:129272
16:08
- CzechOut
Again, you've just typed in the time 16:08. That time isn't coming from anything generated by this wiki. Everything that measures time on the wiki agrees that you actually posted at 16:05.
So where are you getting 16:08 from? Your own watch? Your computer's time? What?
- Anoted
i'm in the middle of taking screenshots and uploading so that I can show you. give me a sec
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:129281
16:31
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:130730
Since Clara's article is protected, shouldn't Clara Oswin Oswald - list of appearances be protected too?
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:130935
We are investigating reports that templates have stopped transcluding properly on pages. Instead, they've been substituting their raw code.
This means that instead of having something like {{real world}} on a page, we're suddenly getting the raw code of the template:real world.
This matter has been referred to Wikia, and hopefully they will see it as serious enough to respond promptly. (They usually do.)
With such a wide-ranging problem as this, there is a good chance that the wiki may have to be reset to a point before this error started. This means that your edits from today may be reverted.
Therefore, it is probably advisable for you to just stop editing altogether until I give the all-clear.
This matter is resolved; get back to editing, people.
- CzechOut
I can now confirm why this was happening. Wikia pushed a "fix" to us yesterday that was supposed to resolve an issue surrounding templates that automatically added categories. It didn't. Instead, it stopped the template from properly transcluding.
I'm now trying to figure out how much damage was done.
- CzechOut
Still actively pursuing this one.
- Cult_Of_Skaro
Oh. Just read this *after* I hit publish on The Keys of Marinus.
- CzechOut
No worries :) Just trying to keep people from making a lot of edits that might be reverted, while i try to put a nail in this coffin. The problem is not actually happening any more, but on the off chance that we have to revert the whole database to some point yesterday, I don't want people to have wasted their time.
- SOTO
You could always save the current text of The Keys of Marinus on your computer, and then publish that again if we end up reverting, Cult.
- Cult_Of_Skaro
I only added a sentence. It's not a big deal. :P
- SOTO
Did you just link to sentence? :D
- CzechOut
Okay, I've developed a plan to fix all this. If everyone could give me about an hour, we'll all be back on the road again shortly.
For one hour, no edits. Thanks :)
- Cult_Of_Skaro
Kinda scary, if you do have to revert the database, this discussion won't have happened. O.o
- SOTO
What discussion? ;)
- CzechOut
Still working at it. Won't be long now. Thanks for your patience.
- CzechOut
Okay, sounding the all-clear. It's possible I missed one or two pages, so if anyone happens to see a page where there's a big, nasty code dump, just undo the last edit and get rid of it.
Thanks again for your patience: edit at will.
- SOTO
Thank you for fixing that, Czech!
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:131006
On the infobox at DWBIT Dalek vs Cybermen Special, the previous and next links both show [[DWBIT ]] even though numbers are listed in the code. It should be links to DWBIT 7 and DWBIT 9. The numbers are wrong in any case, as those issues are five months too early.
- CzechOut
Please read the instructions for {{Infobox Magazine}}. It's not an error. The infobox wasn't designed for non-numbered periodicals. Titles must match the nomenclature spelled out at T:MAGS.
- Digifiend
Ah, fixed it, thanks. I see SOTO flagged that the page needs renaming, could you do that please?
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:131538
A bug has recently crept into the "Forum Activity" module. That's the thing just to the right of this message, there under the search bar.
It used to be — and I assume this is still the intended behaviour — that a thread was only cycled into "Forum Activity" when a new message was added to the thread. Now, however, threads are getting placed into "Forum Activity" when admin make simple administrative changes to the thread, or when people edit pre-existing posts. This means that all of a sudden bot edits are moving really old threads into forum activity, or the simple act of closing a thread ironically puts a thread into Forum Activity — so that more people can see that they cannot contribute to it.
A bug report has been filed with Wikia. Until then, expect for active conversations to get buried by old ones.
- CzechOut
As expected, I've received swift confirmation from BertH that this was not an intended change. He's working with the Engineering Dept. to come up with a speedy resolution, but we'll have to deal with some odd things in our "Forum Activity" for the next few days at least.
Sorry for the inconvenience this will undoubtedly cause to active conversations. However, remember that once you respond to a thread, or click the follow button at the top right of the first post, you'll be alerted to changes made in that thread. This should help you cut through the noise.
IP users, of course, can't really follow threads or receive alerts about them. So if you're an IP user, we encourage you to register for an account so that you can take advantage of this and other benefits of membership.
- CzechOut
This one obviously hasn't been fixed yet, but we're continuing to follow up with Wikia. In the meantime, you will likely see a lot of old threads percolate back up into the Forum Activity, pushing older threads out. We apologise for this situation that's beyond our control to fix, but know that if you're logged in and you've followed a thread, you'll be notified when it changes — no matter how many threads get pushed on top of it. You may also want to get in the habit of periodically clicking on Board:The Panopticon for a list of threads that's ordered strictly by date started, so that you don't inadvertently miss our newest conversations.
- Digifiend
There are advantages to this, even if the disadvantages far outweigh them. In Thread:117218, which was bumped up the forum activity list by CzechBot editing a post, I noticed that you'd said that The First Adventure needed making as a redirect to The First Adventure (video game) and that Alien Armies was a pointless redirect to Alien Armies and should be deleted. So I made the redirect for First Adventure and marked the Alien Armies one for deletion. I wouldn't have noticed those had the thread not been bumped up the list.
- CzechOut
Yeah, but these are rare examples, and it's really not the way the module is intended to work.
As for expanding the total number of threads featured in the Forum Activity module, well, that's definitely not going to be a part of the fix to this problem, but it might be in later upgrades.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:131563
Please use this thread to report any pages where you're finding that the site colours make text simply unreadable or too low in contrast for easy reading. When you give your link, please indicate whether you're looking at the site in the light or dark background. If you're pointing out a single element of a page, please give a specific section link, so that your report can be swiftly verified.
Thanks :)
- SOTO
As I'm sure you're aware, links in navbox headers are completed illegible in the LOD scheme. I usually have to highlight the text to read it.
Example? Just go to the most recent episode, The Name of the Doctor. The three navboxes there appear to have words missing because they are linked.
- Imamadmad
When reaching the search results page though a misspelling in the search box or through searching for something that doesn't have its own page, the word that had been typed is the exact same colour as the search box on that page until it is clicked on. Here's just a random search for the sake of demonstration. As you can see, in the box beside "Search this wiki", you can't see any words. Now click on that box. The text that was typed to search ("Random words") appear as the background colour changes. Now, let's say that the user landed on that search results page because of a typo. Wouldn't it be useful for them to be able to see what they've written before clicking the box to make it active, and so see where they made their mistake?
- Imamadmad
Also, it's hard to see links that have previously been clicked on apart from the rest of the text. Just looking at the word "Here's" in my above post, I can barely tell it's linked because it blends in with the background now that I have previously reached the destination page. Looking over into the main namespace, this difficulty to distinguish previously activated links from normal text seems only to appear in the dark on light theme, with the links in the light on dark being the same as unactivated ones. Unactivated links in both themes are fine.
- 123.50.154.47
if you hover over any comment, the more button on mouse over has low contrast (white text on light gray background) and makes it hard to read.
ps.the reply button (when replying to this form) has a similar issue except the text is black on dark blue background on mouse over.
- CzechOut
Imamadmad wrote: Looking over into the main namespace, this difficulty to distinguish previously activated links from normal text seems only to appear in the dark on light theme, with the links in the light on dark being the same as unactivated ones.
While most of what you said will likely be addressed, this might not be. The standard Wikia setup is to have the same colour for visited and unvisited links. This makes Wikia different to Wikipedia, but it's not Wikia default to change the colour of a link based on whether you've clicked it.
We have in the past done a visited/unvisited distinction, but I'm not sure that I can find sufficiently distinct colours for the LOD theme. White, blue and red is about all I can muster there.
- Imamadmad
I don't care about knowing if I have visited a link before or not, as long as I can see that it is a link. Everything is fine in the dark background theme, but in the light background theme it is annoying not being able to distinguish linked text from unlinked text, even if I have previously visited the link. Unvisited links are fine. Normal text colour is fine. However, visited link colour is only slightly bluer than normal, unlinked text colour, and I think that should be changed. It would be fine having visited and unvisited links the same colour, as long as linked and unlinked were different.
- Digifiend
SmallerOnTheOutside wrote: As I'm sure you're aware, links in navbox headers are completed illegible in the LOD scheme. I usually have to highlight the text to read it.
Example? Just go to the most recent episode, The Name of the Doctor. The three navboxes there appear to have words missing because they are linked.
Yeah, Template:DWTV, Template:Sontaran stories, and Template:Homo Reptilian stories.
On DOL, the missing text shows up, but is blue on a darker blue background, so the contrast is poor.
- CzechOut
Progress report:
- The navboxes are basically done, though I still have some touchup to do.
- The category slider, which many people probably didn't know even existed, cause the colours were so off, is now done. Check it out at category:planets, or any other super-large category. Note that it now does different colours, depending on whether you're searching by first or last name.
- SOTO
Ooh, there's a category slider! Took me a while to figure out what you're referring to. Very efficient; thanks for "bringing that to light," if you'll pardon the strange pun.
Group columns on "child" navboxes appear to be a horrid dark blue on dark brown in the LOD scheme. It's perfect in DOL, though.
- CzechOut
Yeah, I think I'm just gonna wholly invert the LOD navboxes so that they're the precise opposite of DOL navboxes.
But, man, do I ever hate navboxes. Soooo many little "fiddly bits and fjords".
- SOTO
You come to hate anything that you spend hours working on, to no avail. Like celery...
Anyway, would there be any way to make redlinks evident in first posts in threads? Both proper links and redlinks look identical, which can be confusing.
- CzechOut
SmallerOnTheOutside wrote: Anyway, would there be any way to make redlinks evident in first posts in threads? Both proper links and redlinks look identical, which can be confusing.
Done.
- CzechOut
And follow button fixed, too.
- SOTO
In LOD, when you put your mouse over links, it becomes the same colour as the background and simply disappears. Is this on purpose?
- CzechOut
SmallerOnTheOutside wrote: In LOD, when you put your mouse over links, it becomes the same colour as the background and simply disappears. Is this on purpose?
It was on purpose, but it was more in the vein of a test that is now over. :)
- SOTO
In your initial post at recovering unpublished posts, all the keys are invisible. The colouring of {{key}} therefore has to be reworked for the LOD scheme, even though the only time it will ever feature on that scheme is first thread posts.
- SOTO
Very specific one here: {{demonym}} is illegible on the LOD scheme. Look at Mondasian horse, for example; it's white text on a light grey background. It should look more like {{conjecture}} does on pages like Stingray, ie. no grey background.
- Josiah Rowe
A small bug that's been bothering me for a while: on the front page (and only on the front page), the "My Tools" pop-up menu for me is light blue on white. See screenshot here. Not terribly easy to read. I don't know whether other people have that issue, or if it's just me; it does seem to be the case for me when I'm logged in in Safari, Firefox and Chrome.
I hope that the "light on dark" vs. "dark on light" discussion above refers to a now-defunct element of the page design, because I can't find the toggle to switch it.
- CzechOut
Yeah, the front page is a bit of a bitch to code. But hold the phone: what do you mean you can't find the toggle? You're not seeing something that looks like this:
?
[Note that it doesn't appear to work on the front page, though if you push it, it will correct the MyTools problem you've referenced.]
- Josiah Rowe
D'oh! I forgot that was what that was. I was looking for something saying "display" or something like that.
But now that I've tried it on the front page, it doesn't actually fix the MyTools problem. The text is still light blue on white on the pop-up menu, whether the rest of the pages are light-on-dark or dark-on-light.
The toggle changes the "start a wiki" button on Wikia's bar at the top of the screen, but the pop-up menu stays the same.
- CzechOut
Hmmm. Interesting. Oh the joys of the front page. I'll look into it.
- CzechOut
Okay, temporary fix enabled. Seems to be working, so it may not be all that temporary.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:131794
Czechout seems to have just been exiled by the 'abuse filter.' Was this intentional?
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:132014
One of the disadvantages of the forum code is that if you move away from a page where you are composing a new reply — maybe you accidentally click a link on the page, for example — it will appear as though you've lost the message you're composing.
But there is a way to save it!
- Click your back button. You should see one line of your text in the entry box at the bottom of the page.[1] Do not click on the entry box, or your text will be lost.
- Immediately hit ⌘-A on your Mac or ctrl-A on other, inferior operating systems. This will select the text of the entire page.
- Then hit ⌘-C on your Mac or ctrl-C if you're lumbered with another OS.
- Open up TextEdit on Macs or Notepad in Widoze.
- Hit ⌘-V on your Mac or ctrl-V on your cut-price, cut-corners competitor. This will then dump the entire contents of the Thread into your text editor.
- Find the text for your "lost" post, then copy and paste it back into the thread.
It's a bit cumbersome, sure. And it would be better if the Forum mini-editor worked more like the regular page editor, allowing you to navigate away from and back to your edits with ease. But at least there's some way to recover a post, when you accidentally navigate away from it.
- ↑ When you return to the Thread page, you must be able to see a line of your text in the text-entry area. If you don't see that, this method won't work. This method only recovers posts that have been lost due to navigating away from the Thread page.
- SOTO
I've tried that before, and it's never worked...
- CzechOut
It does work. You have to be able to see text in the text-entry window. It won't work if the text has already disappeared because you've touched the window. And it only works when you've navigated away from the Thread page and you come back to it.
- SOTO
Yes, that has been the case many times, and each time I'd try highlighting everything. I even tried just highlighting around it. It just never turned up in the text that I copied.
- CzechOut
Please make a specific test of exactly the instructions I've given. I've just tested it again, without issue.
- CzechOut
It's possible Notepad can't handle this. If the instructions fail with Notepad, please try with Word, or something a little more advanced than Notepad.
- Cult_Of_Skaro
Well, apparently on 'inferior systems (though I generally prefer Windows ;)' it doesn't work. Odd...
- SOTO
Okay, I just tested out exactly what you said. I inserted gibberish into the message box, then went back in Chrome and went forward. I then applied everything you told me to do, and the resulting text can be found here. (it's not letting me post such a long message, I think.
You see — no gibberish! As Cult says, it appears not to be working on so-called "inferior" systems.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:133639
Since Wednesday, the software has been adding additional carriage returns in some situations. Now, a single, additional vertical space, or carriage return, is being added at the bottom of section, when you choose to edit by section, as opposed to editing the whole page.
We're investigating the situation, and have referred the matter to Wikia Staff. We'll keep you apprised as we get more info.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:138016
As a part of today's Wikia code fixes, Wikia have introduced a little bit of a change — possibly an error — in the way that the very top of the page looks. Although this is not a terribly bad look on most pages, the front page looks significantly worse.
The change/error has been noticed on other wikis, and is currently under discussion at community:User blog:Sactage/Technical Update: July 23, 2013, for those interested.
Kirkburn has initially ruled it an unintentional change, so we won't be taking immediate local action to fix it.
- Cult_Of_Skaro
I don't see anything unusual...
- SOTO
Yeah, I'm not noticing anything different either... Maybe it's only on Macs?
- CzechOut
That's because Wikia have now resolved this issue. If you'd like to see screenshots of the problem as it existed, please proceed to the Community Central thread indicated above.
- SOTO
Ah, sorry, I didn't notice it because I didn't think to look in the comments. Didn't see them at first.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:140478
A new bug fix went through today which appears to have messed with our forum font size, due to the fact that our forums are pretty heavily customised. Wikia have increased the base font size for Wall Forum threads, but I'm still trying to figure out by precisely how much so that I can make appropriate changes to our local CSS. Please bear with us; this isn't an intended change.
In the meantime, we hope all our myopic users enjoy the easy reading!
- CzechOut
Blah, couldn't be bothered to wait for the whole explanation from Wikia. It seems to be fixed now. Sorry for the inconvenience.
- ToaMeiko-fduser
I'm still experiencing the bug, but it good be because of browser and/or server caches. Not much of a problem for me. If it's fixed on your end, it should be on my end sooner or later.
- CzechOut
Well, you can force it to correct on your end by clearing your cache, though you may have to adopt the following procedure several times:Clear your cache often around here
After changes are made to this site's CSS or Javascript, you have to bypass your browser's cache to see the changes. You can always do this by going to your browser's preferences panel. But many browsers also offer keyboard shortcuts to save you that trouble. The following shortcuts work in the versions of the browsers that Tardis currently supports. They may not work in earlier versions.
- Firefox: hold down Shift while performing a page reload.
- Opera offers no default keyboard shortcut, but you can create a custom keyboard shortcut with the value Clear disk cache
- Safari users should simultaneously hold down ⌘ + Option + E. You may need to enable the Develop menu first
- Chrome: press Ctrl + F5 or Shift + F5 while performing a page reload.
- ToaMeiko-fduser
Yeah, I know, but I'm not too concerned right now. As long as everything is still legible in an easy-to-read font, I'm good! :P Thanks though. :)
- Midnite Marshall
The font seems fine to me :P
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:141144
The idea is to force content to the fore by making the content area expand and contract depending on the size of your window. This should make the experience of Wikia a whole lot easier on the eyes than the current fixed-width approach. It should especially help people who are on iPads and laptops — as well as those who have the luxury of much larger screens.
Those of you who were around for the adoption of the Wikia skin might remember the that one of the bones of contention was around this very issue. Monobook had been — and still is! — a free-flowing skin, but Wikia wasn't.
Darwin, and especially this free-flowing component code-named Fluid, offers an answer to these criticisms, while still giving helpful boundaries, so that pages can't be warped out of all recognition.
Eventually, all Wikia wikis will move to Darwin. But I've asked for early adoption just so that we can help Wikia troubleshoot some of the kinks before the 50th anniversary kicks in. So please, take a look around the joint. Stretch windows wide. Pull 'em narrow. See if things look weird. If they do, come back here and give a link to the problematic page so that we can examine what's going wrong. This will give useful feedback to Wikia so that any problems we encounter might be incorporated into the final product.
Not only will Tardis admin staff be watching this page and making appropriate changes, but Wikia Staff will be lurking around, too. So please: speak up and speak often!
Let's get the Tardis lookin' great for the anniversary!
- CzechOut
As a part of testing, I'm turning off all javascript extensions on the site for an unknown period of time. Pardon the inconvenience. Better now than on 23 November!
- CzechOut
Javascript has been re-deployed. You may need to clear your cache to have all the js goodies show up again.Clear your cache often around here
After changes are made to this site's CSS or Javascript, you have to bypass your browser's cache to see the changes. You can always do this by going to your browser's preferences panel. But many browsers also offer keyboard shortcuts to save you that trouble. The following shortcuts work in the versions of the browsers that Tardis currently supports. They may not work in earlier versions.
- Firefox: hold down Shift while performing a page reload.
- Opera offers no default keyboard shortcut, but you can create a custom keyboard shortcut with the value Clear disk cache
- Safari users should simultaneously hold down ⌘ + Option + E. You may need to enable the Develop menu first
- Chrome: press Ctrl + F5 or Shift + F5 while performing a page reload.
During this early testing period — roughly the next week — javascript may be disabled as needed, and without warning, by the Wikia engineering staff. We apologise for any inconvenience this might cause — particularly to our users who really like the white-on-blue colour scheme which is only available through the javascript "change colours" button.
Rest assured that we are not currently planning to permanently disable any feature to which you've become accustomed.
- CzechOut
The major fly in the ointment we've noticed at this early page is that some pages "stretch" properly as you widen the window, and some don't.
- This page is an example of a page that does not stretch properly.
- Our main page is an example of a page that does stretch — or go fluid — properly.
We're currently trying to identify whether this is a backend problem, or something to do with our customisations.
Another problem of which we're currently aware is the masthead on user pages. This is definitely an issue on the Tardis side, and so I'll be burning the midnight oil on that one. In the meantime, user pages are bound to be a bit … funky.
- CzechOut
Auto-suggest is playing up. Or, to be more precise, it's only available when you narrow the window, and the search bar is forced into a new position immediately right of the wordmark. When the search bar is in its normal position (to the right of the article name) there's no drop-down of suggested articles.
A fix for this issue is already in the works, but it won't be deployed until the week of 25 September. For a few days, therefore, you'll have to narrow your browser window if you want to avail yourself of autosuggest.
- CzechOut
One component of our javascript has now been turned off, and may remain off for up to 24 hours. Users of the Monobook skin may particularly be impacted.
The biggest thing that goes missing for Wikia users is proper functioning of collapsible tables. So navigation boxes at the bottom of pages will appear open all the time until the javascript is turned back on.
EDIT 12:46, September 14, 2013 (UTC): Some javascript will remain turned off until at least 16 September 2013.
- CzechOut
Darwin is tolerating most of our local customisations quite well, but Chat is basically dead. I'll be examining this part of our code today and trying to fix it. Sorry for the inconvenience.Chat has now been restored.
- CzechBot
Okay, our local javascript modifications have now been entirely turned off.[1] This outage will last until given the all-clear to turn javascript back on by Wikia, which hopefully will be by sometime on 16/9.
A ton of goodies will be gone including:
- spoiler protection
- the skin changer (it's all white backgrounds for a bit, unfortunately)
- the thing that makes titles italic
- preloadable page formats
- some things about the way tables look and behave on mouseover
- the archiving tool
Basically, most everything that makes the site different and kinda cooler than your bog-standard Wikia wiki is turned off.
Why are we doing this? Well, we've got a bit of a mystery on our hands about why some pages stretch to their maximum width (i.e. are fluid) and why others don't. Although our javasript has been pre-emptively cleared of guilt, we're just trying to make super-sure. By turning off all javascript for more than 24 hours, we're being extra-cautious and avoiding all possibility of caching errors.
- ↑ For the boffins out there, we had MediaWiki:Common.js turned off since yesterday. We've now turned of MediaWiki:Wikia.js, which will allow more than 24 hours to have elapsed by the start of business in Europe, Monday, 16/9. MediaWiki:Monobook.js remains on, since it has nothing to do with Darwin.
- CzechOut
Work is being done today (16.9.13) on the navigation bar at the top of pages. This may make the nav bar itself float around a bit.
Those who are using a desktop will probably find extremely odd placement if they narrow their browser windows to the narrowest possible widths.Fixed.Seems to be working correctly in portrait orientation for iPhones running iOS 4 all the way to 6.1. But, oddly, it's not working on iPads running 6.1.Never mind. New design now embraced by the whole iFamily.
Okay, new design is working as intended at all widths and device orientations for Apple® products. Still, those on iPads, and certainly those looking at the full site on their iPhones, are heavily encouraged to use landscape mode.
I am looking for feedback from people with Android/Windows devices, though.
- CzechOut
- Local bug: User Profile Mastheads seriously screwed
Users may experience continued problems today (16.9.13) with the way their User Profile Masthead looks. Now that the wiki navigation bar has been sorted, I can begin work in earnest on the UPM, which shares a common border with the navigation element.
- Fix priority: High
- Status: Somewhat resolved at 16:44, September 16, 2013 (UTC)
- It's about as fluid as the same boxes on standard Darwin installations. Standard installation extends the framing box' all the way to the edge, but not the text within the box. At most widths, our text goes all the way to the edge of the framing box, but the framing box itself is currently fixed width. However, the box as is plays nicely in Firefox, Safari, Opera and Chrome for Mac, and in iOS 6.1, as well as 4.2.1. Presumption is that it works in anything with an Apple logo on it (with an OS made in this decade), and that it almost certainly works on Windows versions of Firefox, Safari, Chrome and Opera. If you use Internet Explorer, stop. (But give us a bug report first.)
- This issue has therefore improved to "resolved for handheld devices and most desktop browser widths" But it's not resolved for very wide browser widths.
- Status update at 17:10, September 16, 2013 (UTC)
- Okay, this is going to be a little more "fiddly" than I thought at first. Expect your UPM (that bit at the top of your user page) to go a bit wonky from time to time today. I'll post back when the matter is fully resolved.
- CzechOut
- Local bug: Preview and reply
The preview and reply buttons in forum posts are now off to the right side when the window is pulled wider than tablet size, but narrower than full width. In total, the effect lasts for about 150px of browser width. In other words, the buttons are temporarily displaced, but never out of the user's reach.
This is not normal behaviour on a default Darwin installation, and may have something to do with local CSS. Although it's being caused by Tardis CSS, it is not a serious threat to one's ability to use the forum.
All I've done so far is to test forum replies on both here and w:c:community in Safari, Firefox and Opera. All three browsers exhibit the problem consistently on this wiki, and not at all on Community. Thus, I'm calling it a local issue, but hardly a serious one.
- Fix priority: Low
- CzechOut
- Local bug: Search bar styling
Search bars have inconsistent styling site-wide. This is due to a lingering issue that isn't really Darwin related, but has been brought into sharp relief now that Darwin intentionally moves the search bar around, depending on browser width.
I'll be looking at a way to make the three main search bars always have the same shape and feel.
- Fix priority: High
- CzechOut
Now that it's been in place for a while, anyone got any thoughts on Darwin that they'd like to share?
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:141282
A quick look at various pages with {{title|''{{PAGENAME}}''}} and {{title dab away}} on them don't seem to have their page title in italics, even though the lead is. In other words, anything that should have their title italicised isn't on my end. This applies to IE 10, Firefox 23 and Chrome 29 on Windows.
- Shambala108
It's a bug right now that will hopefully be fixed by wikia in a few days or so. See Thread:141144 for more information.
- SOTO
Well, it's not technically a "bug" because it was done on purpose, for testing. Our javascript was turned off to test out Darwin, and regular Wikia wikis don't support the {{title}} feature. Apparently, it should be turned back on by the 16th.
Please be sure to monitor Thread:141144 closely for at least the next few weeks, as you're likely to see any number of oddities related to Darwin integration.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:141398
There was a countdown to the 50th anniversary on the main page. I haven't seen it in a couple days. Will it return?
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:143338
Work is being carried out today on the "change colour" button to make it deliver its message with just an icon. The button may be temporarily shrunk or oddly placed, but it likely won't be completely removed from the page. (And yet it might.)
As always, people, clear your cache often, as explained in the following post.
After changes are made to this site's CSS or Javascript, you have to bypass your browser's cache to see the changes. You can always do this by going to your browser's preferences panel. But many browsers also offer keyboard shortcuts to save you that trouble. The following shortcuts work in the versions of the browsers that Tardis currently supports. They may not work in earlier versions.
- Firefox: hold down Shift while performing a page reload.
- Opera offers no default keyboard shortcut, but you can create a custom keyboard shortcut with the value Clear disk cache
- Safari users should simultaneously hold down ⌘ + Option + E. You may need to enable the Develop menu first
- Chrome: press Ctrl + F5 or Shift + F5 while performing a page reload.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:144139
If you normally browse here with Safari and you've recently upgraded to Mavericks (10.9), then you've just lost a little bit of functionality. At some point, you may have installed the QuickTime component called XiphQT. This was the only way that Mac users had of playing .ogg audio files through QuickTime and therefore iTunes. QuickTime is what powers audio and video streaming in Safari. It's therefore what's required to play back our audio clips, such as in the infobox at The Light at the End.
But the problem is that XiphQT is an old 32-bit application. And Mavericks is the first iteration of OS X which requires 64-bit apps. The result: no audio playback of our files in Safari once you upgrade to Mavericks.
Happily, Firefox and Chrome (and Opera, but Opera's not supported by Wikia) easily play audios, even after a Mavericks upgrade.
- CzechOut
Turns out this problem is much more widespread. If you are using the latest OS on the latest Apple® device you won't be able to play any sound clips anywhere on Wikia, regardless of what browser you use.
Those who are running Mountain Lion or below are unaffected, but there's been a basic inability to hear Wikia audio in iOS probably since 1.0. In other words, iUsers have always been unable to hear Wikia sound files.
It's unclear if Wikia Engineering will be able to address the iOS issue swiftly, since that is technically an "Apple problem".
However, they will likely be able to make sounds work in 10.9, in everything but Safari, since sound files there play in Firefox, Chrome and Opera on Wikipedia.
If you're a 10.9 user, you are strongly encouraged to submit a bug report, saying that you're a Mavericks user who would like Wikia to fix things so that you can hear the sound clips on this site. - CzechOut
Just to clarify, what we're talking about here are audio-only files. Audio that's a part of videos works fine. Here's an example of what won't work for Mac 10.9 users, regardless of browser:Trailer for The Light at the End
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:144363
In the following series of posts, I'll demonstrate how you can't put an un-thumbnailed video in the forum and expect it to play.
But first, a few examples of what does work.
Here's a video taken directly from w:c:video. Both of these examples play.
A video at 501px, not thumbnail. The instruction given was that this should align right, but since local customisation keeps the width of the thread to almost 500px, anyway, there's no real difference between |right and |center.
The fact that this video is breaking the boundary of the thread is entirely due to local customisation. Once you add in the padding for the frame, and account for the irregularity of the overall shape caused by the vertical height of this post, the left-margin of the the post is necessarily overhung.
- CzechOut
This is a video which only exists here at Tardis. Again at 501px, these videos play, too. The kicker, as we'll see, is that the presence of the thumb somehow allows the non-thumb to play. 501px non-thumb
- CzechOut
Now let's take the thumb away. What do we get? Nada. A non-thumb alone doesn't play in Wall Forum. 501px non-thumb
- CzechOut
Nor does it matter whether the video come from w:c:video, or what its width is. Basically, non-thumbnailed videos don't play.
This video is set to |center. Notice that:
- we don't get a light box
- The text of the caption is all over the place, but some of it is kinda centred
- The play button has gone walkies.
Just in case you don't think non-thumbs should work in this way, go to user:CzechOut/VideoComparison to see how this example looks on a normal page.
- CzechOut
File:Comic-Con - Doctor Who - Toby Whithouse InterviewSee, by contrast, how nicely a thumb plays?
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:145888
On List of Doctor Who television stories, the pink and yellow colours used for missing episodes in the table looks fine on the light colour scheme, but clashes with the light blue and white text on the dark colour scheme. Would it be possible to make these tables coloured differently depending on which colour scheme is being used?
- CzechOut
Thanks :) This is a known issue, but the reminder is helpful.
- MjaxMajoran
sorry to necropost, but nearly a year has passed and this issue has still not been addressed.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:146625
While stub tags are finding a new home, you may experience them wandering all over the page. Can't give an exact ETA on when this might settle down, but it'll be within the next day or so. This issue will also displace {{protect}}, {{lock}}, {{ImageLink}} and {{wikipediainfo}}.
Apologies in advance if it makes a few words on various articles unreadable.
- Digifiend
Glad to know you're aware of that, I was just about to report it having seen that error on the Legacy (video game) page. Luckily the stub tag isn't obscuring any text there.
- CzechOut
Project may take a little longer than expected to complete, as I have to manually flip all the tags 90 degrees to the right. I thought I was going to be able to do this via a simple CSS command, but that idea had some unexpected problems.
For the moment, you shouldn't be finding text obscured on most pages, so long as the editor put the stub template at the bottom of the page, where it's always supposed to go.
However, on some pages, people have put the stub tag right after the infobox, or at the top of the page, and these are going to cause problems until I can work out a better javascript solution.
- CzechOut
Significant progress has been made on this project, but it's going to take a while to flip all the stub tags. Some of them can't simply be flipped, but must be redesigned, since the images don't make a great deal of visual sense when rotated 90 degrees. So there are some cases where the stub tags have to be completely redesigned.
Another issue is that the image cache isn't clearing quickly. Therefore, there will be an indeterminate amount of time, but usually less than 48 hours, where the stub tag image is both huge and oriented the wrong way. This will settle down properly, so please do not delete stub tags in the meantime.
- Embem5
thank you! everywhere i look there is a stub tag that says CAT and it is bothering me! Thank You!!!
- 108.236.90.188
Anyway I can help?
- CzechOut
Nope. IP editors can't upload pics, which is the main thing now required.
- 108.236.90.188
Thanks anyway.
- 108.236.90.188
Speaking of stub tags check out Song.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:146716
If you're a more adventurous Wikian who at one time put w:c:vda:MediaWiki:VDA.js into your personal global.js, be aware that it is incompatible with some elements of this site's styling. It makes some elements in the source editor "fall down" into the actual editing pane when in widescreen mode.
Note that VDA.js is in fact deprecated.
You should remove it from your global.js, regardless of its impact upon Tardis styling.
- Thanks to User:Corey Chambers for finding this interactivity issue.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:148742
There is an ongoing issue with occasional video thumbnails. It's making some pages look ugly, as can be seen at this example. The videos in question do, however, play properly.
Please do not remove these videos with thumbnail issues, as we expect it to get fixed. The issue has been reported to Wikia Staff, and they have escalated it to the engineering team. It is not a Tardis-only issue.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:148894
I'm issuing a pre-emptive warning to Mac users that they not upgrade to Mavericks 10.9.1 and Safari 7.0.1 (which is a necessary part of that OS upgrade).
It appears to be causing some issues with Wikia, making it impossible to see histories on pages with very long revision histories, like Eleventh Doctor.
The matter has been referred to Wikia Staff, and I will keep fellow Mac users apprised as the situation becomes clearer.
Chrome, Opera and Firefox seem unaffected by this issue, so I've you've already gone for 10.9.1, you still have several viable options.
- CzechOut
This error has been independently confirmed by Wikia staff and escalated up the repair chain. You are now strongly cautioned against upgrading to OSX 10.9.1 if you want to retain full operability of Safari while using Wikia.
Again, if you want to go to 10.9.1 for other reasons, feel free. Chrome, Firefox and Opera do not exhibit this problem in 10.9.1, so you have plenty of browsing alternatives.
It sucks, though, because Safari 7.0.0 was working so incredibly well with Wikia.
- CzechOut
After some serious investigation today, it appears now that this problem is not about page size. I've tested several of our shortest pages, some of them that are exactly the same size to the byte and I'm getting different results. Some history pages display without hesitation, while others hang.
At this point, it's not clear what the issue is, but there is an error, and it can be reproduced consistently.
Safari 7.0.1 does not work well with Wikia. Resist the urge to upgrade for a little while, if you can.
- CzechOut
And just to be clear, this is not a local issue. Safari 7.0.1 doesn't serve the history page of starwars:yoda, muppet:kermit or memoryalpha:spock any better than it does Eleventh Doctor.
- Josiah Rowe
It also has trouble loading most Special pages (Special:Watchlist, Special:RecentChanges, Special:Contributions/whoever and so forth). The pages tend to stall out while loading. That's also a Wikia-wide problem with the latest Safari version. (And I've reported the bug to Wikia staff as well; they're working on it.)
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:149479
If you try to include multiple paragraphs in a blockquote, as on Hunters of Earth (audio story), the second paragraph onwards has white text instead of the usual dark shade. It's only a problem on the dark skin.
- CzechOut
Why are you including multiple paragraphs on a block quote? That's gonna take up an insane amount of vertical space?
- CzechOut
- Digifiend
I didn't add multiple paragraphs to it, I spotted it when reading the article, and haven't actually edited that article at all. So it turns out it violated T:NO HTML anyway, huh. I've tracked it down. An IP editor had originally included it as a normal series of paragraphs, then TARDIStraveler added the blockquote tags. This was in April 2013. Seems like a good faith edit which only made it worse.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:149538
I have a large monitor and the images in all the infoboxes are blurry. It seems that the thumbnails being generated are too small for the width of the infobox on my screen.
- Shambala108
Though there was a similar issue addressed at Thread:148742, I haven't seen this one addressed yet. Infobox sizes have been varying widely for the last couple of days, sometimes taking up half of the page width. That would, among other things, make the images blurry.
If it's a wikia thing, hopefully they will fix it soon and the infoboxes and their images should go back to normal size.
- CzechOut
Scheduled local maintenance regarding this issue was announced a few days ago at Thread:149241, and the thread was highlighted. Perhaps you just dismissed the message without reading it.
- CzechOut
Nevertheless this thread serves as a useful reminder of why we have minimum width requirements for images and indeed why Darwin is going to force us to up that minimum width.
- Shambala108
oops i forgot
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:149637
The template for the story infobox has a coding error that is causing any second behind the scenes video to not be reduced to a 250px size, which causes the page itself to be completely messed.
I've already identified the problem.
Basically, this part of the story infobox template:
{{#if:{{{bts2|}}}|{{!}}class="info-both" colspan="2" style="margin-top:3px;"{{!}}[[File:{{{bts2}}}]] }}
It should be replaced with this:
{{#if:{{{bts2|}}}|{{!}}class="info-both" colspan="2" style="margin-top:3px;"{{!}}[[File:{{{bts2}}}|250px]] }}
Just wanted to let you know.
- SOTO
Thanks for your concern, but this was done purposely by user:CzechOut as a test. Please see Thread:149241 for more details on what he's trying to achieve with the many template, CSS and JS changes you'll see throughout the week. Once again, all these problems are very much temporary, and, as the people of Hot Fuzz' Sandford would have it, for "the greater good."
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:149806
I don't know if this has been already adressed, but when reading the Ambassadors of Death the infobox isn't fully readable, you have to scroll sideways to fully read it. I check on other pages to see if it was just on that page but on Liz Shaw the box extends into the main text with the image covering a lot of it. Additional information you might need, OS Mac OSX10.9.1 Browser Firefox 26.0
- Digifiend
It's either been fixed, or it's not affecting Google Chrome on Windows 7.
- Doug86
- 69.255.48.182
It hasn't been fixed. I'm using Firefox 21.0 on Windows 7.
- Alan-WK
Bug continues. I'm using Firefox 26.0 on Windows XP.
- KiumaruHamachi
The bug is most likely not caused by the OS of your computers but rather, the wiki.com is doing updates. Strangely, on Naruto Wiki, no infoboxes are affected but like a virus on a computer, these bugs affect the software (ie. infoboxes) differently. We will have to wait it out a few days.
- Digifiend
Seems to be browser specific then, and not affecting Chrome. Screenshot:
- Bwburke94
Bug exists for me as well, making articles unreadable. Pictures are "spilling over" onto the main article text.
- CzechOut
Is there anyone here experiencing this bug who is not using Firefox?
- CzechOut
Okay, I'm able to confirm this is basically a Firefox issue (There's a little variant of this issue in Opera, but the pages are still readable there.)
While it's being addressed, you're encouraged to switch to Chrome and/or Safari.
Also, Monobook is profoundly affected at the moment, regardless of browser. You are strongly encouraged to edit in Oasis in Chrome or Safari for the time being.
- Lavacano201014
I've identified the cause.
The max-width CSS property for images is set to "100%" - while Webkit browsers (e.g. Chrome) interprets this as "100% of the parent container", Firefox interprets this as "100% of the page width". I'm not certain if this is a bug in Mozilla or just a difference in opinion between Webkit devs and Mozilla, but it does explain why Chrome and Safari are not affected.
Quite understandably, I am unable to edit the infoboxes to correct the problem. However, what I can do is create a userscript to make the wiki usable until someone with more power than me can fix it.
1. Install Stylish
2. Once you've installed Stylish (and restarted Firefox), install this userscript.
3. Observe as your images are forcibly resized to a maximum width of 350px. You may need to refresh the page.
- CzechOut
Meaning no offence to the above poster — welcome, by the way! — please do not follow Lavacano201014's advice.
A solution which requires the installation of an extension to Firefox is not a solution that this wiki will be undertaking. We will be looking for CSS workarounds only, and if these do not exist, then we will return to a different way of styling the infoboxes altogether.
- Lavacano201014
And what precisely is wrong with my userscript as a temporary solution? Because I never did mean it to be permanent.
And the CSS is simple: Change the max-width property for .info-pic and .info-pic2 to be "350px" instead of "100%". I would have done it to the wiki itself, but again I do not have the permissions to edit the relevant files (again, perfectly reasonable)
edit: Perhaps you thought I meant for you to post this script in a banner or something? No, I just left that there as a temporary band-aid for other users so you weren't constantly heckled with "FIX PLZ THIS IS HARD TO READ"
- CzechOut
On an individual basis, there's nothing wrong with your solution. But the goal here is explicitly not to set a px width. The goal is to get Firefox to behave like webkit browsers.
In other words, the presumption of the wiki is that Firefox's handling of max-width commands is a positive error.
We're not going to go down the road of endorsing, even temporarily, some kind of fix that requires the user to install an extension and operate explicitly contrary to the intended, responsive design.
- CzechOut
edit: Perhaps you thought I meant for you to post this script in a banner or something? No, I just left that there as a temporary band-aid for other users so you weren't constantly heckled with "FIX PLZ THIS IS HARD TO READ"
No, the temporary solution is to switch to Chrome or Safari, not to modify Firefox such that it works around the current state of our CSS. The bug is in Firefox. Altering your personal installation of Firefox is not the way to address this situation.
- Lavacano201014
Alright, you don't want explicit pixel widths. I haven't used much CSS outside of half-effort userscript fixes so I can't fathom why, but I'll roll with it.
Do the infoboxes use CSS3 columns? Firefox bug #720669 might be relevant.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:149809
On Topic:Liz Shaw, it doesn't link to Liz Shaw. This applies to all Discussions about PAGENAME pages (I'm using Liz Shaw as an example because I noticed the issue when looking at Thread:149806). It says "1 active discussion about Liz Shaw", but is meant to say "1 Active Discussion about: Liz Shaw", as can be seen at a page on another Wikia.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:150126
Howling and Theory namespace posts are showing up as part of the "random page" feature. I assume that isn't what we want.
- Shambala108
They also show up in "recent wiki activity".
- SOTO
That is odd. Custom namespaces shouldn't be included in Special:WikiActivity and Special:Random, I don't think. I noticed Theory pages popping up in WikiActivity too. This is obviously not something we want, since Howling thread names could potentially contain spoilers. Hence why Category:Contains spoilers was — for a period of time, at least — not in any other categories; we don't want anyone coming across those pages names unless they've actively chosen to go to Howling:The Howling.
If this were tomorrow, I'd guess this was an intentional tech update, but there's no such report. How long have you seen this happening? Maybe send in a Special:Contact/bug?
- Shambala108
I think I first noticed it Sunday or yesterday.
- SOTO
Huh. This is interesting. Start typing in, for example, "Spoiler" into the search bar, and not only spoiler (ns:0) will pop up, but also Howling:Spoilers for pandorica opens and Howling:Spoilers from The Brilliant Book 2011. Note, though, that Template:Spoiler, Tardis:Spoiler policy, Forum:Spoiler policy discussion from 2006, Forum:Spoilers on upcoming audios, etc, do not appear. This seems to be a custom namespace-specific issue, where Howling and Theory pages are for some reason treated like ns:0 (the "main namespace").[1]
- ↑ You might be thinking, but Tardis is a custom namespace too. It's not — it's simply a custom-named namespace. Tardis (or ns:4) exists on all wikis are Project.
- SOTO
After a bit of searching (okay, okay, I found it completely by accident), I've found that this has happened once before. Last time, it was an intentional change to attempt to synchronise the design of those pages with the design of the rest of the wiki. I'm not sure what motives are at play this time — assuming that this was in any way intentional — but it does seem that Howling and Theory have been again made into content namespaces for a period of time.
- Shambala108
Yeah, I remember that one, but I thought there was a more recent example too. Maybe it was when the forums changed format.
- Digifiend
Are minor edits meant to show up on Wiki Activity? Because an edit I just made to Open All Hours (CON episode) just did.
- Shambala108
Minor edits (except for bot edits) do normally show up in wiki activity.
- Digifiend
Ah, OK then, thanks. Just thought it best to check considering there are several ongoing bugs here.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:151363
Howard Burden's page says he worked on a story called Howard Burden! This is something to do with the pcred template, but I don't know how to fix it.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:151808
This week, Wikia changed over from Dynamic page list 1.9 to 2.0. DPL is a little extension that allows us to create simple dynamically-expanded lists. For instance, there's one at United States Marshal, which will increase that list every time a page is added to Category:United States Marshals, thereby keeping that page as up-to-date as possible.
Unfortunately, as we've discovered at w:c:drwho.answers, there are some pretty major syntax differences between 1.9 and 2.0. Things that have been working fine for a while suddenly don't work at all.
I don't expect that many pages here at Tardis might be impacted. But they might be. If you encounter any pages where the DPL lists don't seem to be working, lemme know.
Or, if you're really ambitious and looking for something to do, you could check this list of pages where we use DPL. Then, you could report back here to indicate any problems you've found.
- Digifiend
Just checked the mainspace links on that list, and all but one are fine. Timeline needs a repair though.
EDIT: And the User talk, Tardis, Template and Forum namespaces are fine too. User:Rob T Firefly/sandbox does contain a dpl error, but it was already there before the upgrade.
- CzechOut
- Jacque1288
how do i add
- SOTO
{{tomato check}} is completely messed up when transcluded on my talk page, but somehow completely normal on the template page itself.
- 24.13.85.36
The picture of the event synthesizer is missing.
- Digifiend
Anon, there was never a picture on that page.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:153534
Hi, I don't know if this is the right way or even the right place to ask this, but could someone please fix the Doctor's page? The images that rotate as the main page image are way too big and are blocking text.
- SOTO
What browser are you using?
- CzechOut
My guess would be Internet Explorer. That picture-changing thing doesn't work in IE. Of course, we locally don't support IE, but SOTO if you wanna give a shot at adding IE support to the picture changer, feel free.
[Actually, just checking now. It's definitely problematic in IE. However the Master's page seems to work differently to the Doctor's. For some reason, the Master at least eventually puts its content within the boundaries of the infobox, even if the content is at full-height.]
- CzechOut
Actually, SOTO, it's probably a tall order to just ask you to just fix it. But here's what you, or any other interested party, could do to certainly help it. Gather up images of the Doctors that are all exactly the same dimensions, all perfect 10:9 widescreen, based on a 450px width. (You'll have to do the math to figure out what the height needs to be.) Then load 'em into the templates at work here. That'll help IE out a lot, and it won't do other browsers any harm either.
Once we take the math out of the hands of the CSS by using exactly the same dimensions across the board, this whole thing will work a lot better.
- CzechOut
Hmmm, this appears to be a problem in Firefox for Windows, too. Odd.
- 108.192.13.243
Hi, I'm the one who made this topic and I'm using Firefox, so it's not just an IE problem.
- 108.192.13.243
I should add that the Master's page has the same problem for me. Not every page is problematic though, and since I don't contribute to the wiki I have no idea why there's a difference.
- CzechOut
It's only a problem on like four pages on the wiki — those that use a carousel slide show effect to demonstrate different actors who have played the role of a Time Lord with multiple incarnations. Obviously, though, the Doctor and the Master are high traffic pages, so we wanna get it right. Most of the admin staff until very lately have not had the ability to easily test the site in Windows, which is why this issue, despite being realtively long-lived, is essentially a "new" problem for us.
We're sorry that those pages are rendering poorly for some Windows users. As a workaround, I can suggest that you use Chrome to view the site. It's not displaying this issue in Windowws.
- Shambala108
I just wanted to point out that this problem is not a wiki problem and is not universal so there is absolutely no cause to delete the pictures on the grounds that they are not showing up properly. Deleting the images could be construed as a violation of Tardis:Vandalism policy.
- CzechOut
This problem has now been solved. The image rotation works in all browsers that Wikia supports, meaning it even works in the latest version of Internet Explorer. It may even work in versions as low as IE 9.0, but I have no easy way to test anything other than 11. .
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:154468
If I am posting this in the wrong place but I seem to be having a problem accessing revision history on my Ipad. It loads up about half way and then freezes. I use Safari. Does anyone else have this issue?
- CzechOut
Hi :) This is an issue that was reported back in Thread:148894. However, the connection between that notification and your problems with the iPad is a little obscure, so I'm glad you've given me the opportunity to amplify the point.
Basically, once Mavericks hit, problems on the desktop side became problems on the iOS side and vice versa. The fact that there's a problem in Safari 7.0.1+ means (almost of necessity) that there's a problem in iOS 7.1.
The problem on the iOS side is a little more severe, though, because all iPad/Phone browsers — and not just Safari — are affected. So it's currently impossible to get some page histories, both here at Tardis and all around the Wikia network, on iOS.
It's a very tricky problem. Wikia staff have spent several months just defining the problem with data — because it's so odd. And that's what we're continuing to do. One thing that we're watching with interest is the release of the next major version of Mavericks, 10.9.3, which is likely within the next month. It might well be that this release (which will trigger an iOS upgrade as well) will solve things. It might not.
Either way, this is something Wikia are very concerned about, and we're literally adding more information about this issue every day. If you want to help in those efforts, fill out this form whenever you discover a special page that won't load.
Recapping, for those who just like to skip to the bottom of posts:
- The issue only affects special pages. Normal articles, forum threads, MediaWiki articles, File pages and others load just fine.
- The issue only affects some special pages. Finding a solution for the issue is difficult precisely because it doesn't affect every special page. It's not all revision histories. Only some of them. It's not every page listed at Special:SpecialPages, just a few of them.
- It's not just you, nor the way you personally have set up Safari. We've eliminated a lot of possible causes and discovered that it exists even in a brand new installation of Mavericks where the very first page one surfs to with a brand new installation of Safari is http://tardis.wikia.com/wiki/Eleventh_Doctor?action=history.
- It can be easily reproduced.
- Only Safari on the desktop side is affected, and only if you've upgraded beyond version 7.0.0.
- All browsers on the iOS side are affected, once you upgrade to at least iOS 7.1. So it's not just Safari on iPad, but Firefox, Chrome, Apollo, Puffin and a ton of others.
- Nothing produced by Apple prior to Safari 7.0.0 or iOS 7.1 is affected.
- TheMasterRace
Thank you for this
- Digifiend
I've heard lots of reports of apps no longer working after the upgrade too. It's a broken OS, pure and simple.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:155509
Ignore me. I'm just a test.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:155863
No matter what I do, I can't seem to unfollow the article for "Death to the Daleks!". I think it may be some kind of glitch. Any suggestions?
- Shambala108
It must be certain pages. I've had that issue with about a dozen pages for quite some time now, and Death to the Daleks! is one of them. I've always put off complaining about it because it seems so minor, compared to some of the other issues here, but I'd like to see it resolved if possible, now that I know others have the same problem.
- MystExplorer
I'm glad to know it's not just me. It seems the problem is with the page itself and not our accounts.
- CzechOut
Have you tried going to Special:Following and hitting the "x" next to Death to the Daleks!?
- Shambala108
Yes, but some pages won't disappear, while others disappear until the next time I load the page.
- SOTO
Just for the record, I was previously following the page 'cause I've probably edited it at some point, and I unfollowed it no problemo with the toolbar. I guess I'll fire off the usual questions: OS, browser and browser number?
- MystExplorer
Hitting the X does nothing. I use Mac OS X 10.6.8. For a browser, I use Safari 5.1.10. I've also tried it with Firefox but that didn't work.
- MystExplorer
Never mind! I found the toolbar and managed to unfollow the page. Thanks for your help.
- Shambala108
Thanks for the hint, Slughorn42, it even works for deleted pages.
- CzechOut
I referred this matter to the Wikia engineers yesterday. In my testing, I found that hitting the "X" on Special:Following only failed to work with this one page, "Death to the Daleks!". Preliminary thought is that it has to do with the initial quotation mark, which is an odd thing to have in a title.
Shambala108, you seem to suggest that you're having problems with multiple articles. If you're finding any more pages that can't be dismissed via Special:Following, please list them here.
- Shambala108
Sorry, I've already removed them using Slughorn42's suggestion.
I do remember that one of the deleted pages was "Time standing still", and another was a deleted version of Putting the Shock! into Earthshock. A couple were Howling pages that only started showing up when Howling posts started showing up in the recent activity list.
If I can recall the other four or five, I'll list them here, but right now my mind is blanking.
- Shambala108
Add 2" quad and The "Doctor Who?" running joke to the list. It seems like it only happens with pages that have some kind of punctuation in them.
- CzechOut
That's a good initial assessment, but it's kinda fouled by the presence of difficulties with "Time standing still". Did that page have some sort of punctuation in it? Were the quotation marks literally present in the title?
- Shambala108
Yes it did have quotation marks, and the Earthshock one had an exclamation point.
- Cqm
@Shambala108 I'm trying to reproduce the error with the mentioned Earthshock page but I'm unable to find the page in question in the deletion log. I know what's causing the error with pages with " in them (hopefully it should be fixed relatively soon), but I can't understand what's causing the issue with that particular page. Could you, or someone who sees this post in recentchanges/notifications, give me the exact pagename so I can test it myself?
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:156099
There's a problem with the last three names on the list: Bear McCausland, Ellie Darcey-Alden and Joseph Darcey-Alden. Something seems to be wrong with their age templates. I've had to remove them temporarily to keep the list readable. Any suggestions for what to do?
- 98.163.235.120
Never mind. I'm pretty sure I fixed it.
- MystExplorer
I tried to add another name to the list but when I did, this appeared next to Joseph Darcey-Alden's name: Template:Number table sorting/positive. Could it be that there's simply too much data on the page? I'm afraid I don't have enough understanding of how the wiki works to be able to tell what's wrong.
- MystExplorer
If the problem is length, I suppose one solution would be to split the list in two i.e. have the first half be for people born between 1900 and 1949 and the second half for 1950 onwards. Just a suggestion.
- SOTO
I'm not entirely clear on what the actual issue is here. What's going wrong? Details, please.
- MystExplorer
When I try to add a new name to the list (as it is now), the aforementioned template appears next to the last name on the list. Trying to add more than one name results in the template appearing next to multiple names towards the bottom. I could be wrong but I think it might have something to do with the size of the list. That's why I proposed splitting it in two.
- SOTO
Huh. Could you reproduce that problem so I can look at it? Special:WhatLinksHere/Template:Number_table_sorting/positive is telling me that that non-existent template is transcluded in Template:Age in years and days and on pages which transclude that... and yet I'm not seeing it in the source of that template or any templates it uses.
- MystExplorer
I'm afraid I don't know what "transcluded" means but I'll make the necessary edits so you can see what I'm talking about: Tardis:List of cast and crew by age.
- SOTO
"Transcluded" means the page uses the template, or at least tries to — and therefore produces a redlink. If the source of a page contains
{{template name}}, it transcludes that template. - MystExplorer
Well, for some reason it's now showing up on the page itself despite never having done so before. What can be done about it?
This has nothing whatever to do with the missing template that SOTO talked about upthread. That template, though now added to our database for completeness, was a simple rounding template that has no meaningful bearing whatever on the parent template, Template:Age in years and days.
The goal of the page in question is to have a single list of BTS personnel organised by age. That goal is impossible on a Wikia wiki. The age calculation template starts to significantly degrade after about 100 calls on a single page, and the cast and crew page has way, way more calls than that.
Since the goal of the page cannot be achieved, the page, and others like them, will shortly be deleted.
Before I do that though, I want to give you guys adequate time to see the proof. You can tell the page used to work by looking at the very first revisions. There, when the list was relatively small, the age was displayed correctly. Also, List of Doctor Who television writers uses the same age template, and it works out alright because there aren't nearly so many television writers as there are cast and crew.
Beyond the technical problem, however, lies the fact that really such things have been voted off the wiki. We decided some years ago not to try to maintain data about the age of real life people, because there simply is no good source for such information — at least nothing that would pass muster at T:VS. Actors routinely lie about their ages in order to stay employed, so they definitely aren't sources for their own ages. I know, Slughorn42, that you love finding out people's ages, but really, it's important that you stop publishing age related information on this wiki. You're kind of undoing the work of removing age data that has already been carried out to date.
Don't get me wrong: your enthusiasm for the subject is great! But it's just not information that we can either philosophically or technically use. It's important, too, that all editors understand that I'm not saying Template:Age in years and days should never be used. I'm just saying there's a limit to the number of times that the template can be used on a single page.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:159767
I see that the page for DWM 476 was started yesterday. Trouble is, on both DWM 475 and Doctor Who Magazine/2014, the links to that page were redlinks - meaning that clicking the link opened the page to edit instead of view. I fixed it by doing a fake edit on those two pages using classic editor. There are two more pages listed in What Links Here and they're both exhibiting the same behaviour.
- CzechOut
Not sure what you mean by "fake edit". If, however, you mean that you did a "null edit" (pressing "Publish" without making any change at all) that makes sense.
The navigational links within {{Infobox Magazine}} are calculated. Thus, it does take some time — maybe less than a day, maybe more — for the previous issue to recognise that you've started a page for the next issue.
It'll always eventually correct itself. But if you're impatient, you can do a null edit on the previous issue's page and it'll then see the newly created page.
None of this is technically an error, per se. It's just one of the effects of caching.
- Digifiend
Yeah, I did mean a null edit. Thanks for the explanation.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:162024
If you've been on Wikia for a while, you may know of the existence of a skin called "Monobook". Most — that is, 99% — of users never see it anymore, but there are still some power users who prefer it. The official Wikia position is that it's offered on an as-is basis, meaning that many new Wikia features don't necessarily work in the skin. A good example is Special:Chat, which doesn't at all work in Monobook.
Our local position is that it's a lower priority than Wikia, and indeed sometimes we forget about it. A few of our local innovations really aren't working in Monobook, but these are mainly just the main page and transmat pages. Otherwise, Monobook is a perfectly legible environment.
However, we do want to make sure it's as useful as possible. So if you do use Monobook, and you see things that are going dramatically wrong there, please leave us a message here, noting the page where you found the error and what you think a reasonable solution would be.
As Wikia do not officially support Monobook, I feel a need to stress that this is a service I'm offering as an admin of this site, not as a Wikia employee. It follows on in the tradition of a long-open discussion at Forum:Monobook styling continues and Forum:Monobook fans: read this.
Also, note that if you are a Wikia Star/Community Councillor, and you just can't stand the way our Monobook looks, we'll gladly give you admin access to fix up the joint to what you see as a reasonable standard of excellence for the Monobook skin.
Further, be advised that this wikia bypassed CSS development of Monobook, and — unusually for a 10-year-old wikia — began its CSS styling with the Oasis/Wikia skin. Monobook is very much a retrofit, so it would be churlish of us to be "precious" about that design.
So again, whether you want to take on the duties of a full redesign, or just want to offer feedback about a particular page that's not working, please put your comments below. Thanks :)
- DarthKnah
I think this is a good idea. One of my other favorite wikis, Wookieepedia, actually recommends monobook over wikia skin. I'm not a very advanced user, but I'll keep a look out.
- CzechOut
Thanks for your help :) Just wanted to stress, though, that we have completely the opposite advice here. We recommend Wikia/Oasis over Monobook, but we do want to try to make sure Tardis is as functional as possible in that older skin.
- DarthKnah
The "there be spoilers here" message doesn't come up when you click on a thread in the howling if you use monobook.
- DarthKnah
Also, what's the deal with the font on many pages when using monobook? It's all thick and nasty and hard to read. Of course, my opinions don't reflect those of all monobook users, but it's something you should look into.
- DarthKnah
When using monobook, on the left hand side there is a box entitled "community." It says "wondering why things are changing around here? Keep up by reading the community news or by visiting the Panopticon." The Panopticon link is to the Panopticon disambiguation page.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:162037
The top header will be changing soon. http://community.wikia.com/wiki/User_blog:Rupert_Giles/Introducing_Updated_Global_Navigation
I've noticed that that purge link/clock you have in the top bar will be nudged out of position, and potentially be blocked by the notifications box. You probably want to do something about that. You can see what I mean here: http://onceuponatime.wikia.com/wiki/Once_Upon_a_Time_Wiki
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:168028
I just loaded up the page for Doctor Who The Vault, and noticed that the rename and non-fiction templates both seem to be plain text (they're calling CSS classes that no longer exist). It doesn't stand out well at all, and looks like page content. I know the Recent Wiki Navigation placement probably resulted in them (and the entire page content?) getting pushed down, but surely a fixed width would solve that problem? Even if you don't restore the relevant css code (which you probably took out for a reason), may I suggest that you at least add a border or a solid colour background to them, please?
- SOTO
We mass-wiped most of our local CSS customisations when we started featuring a prototype of the new article layout. More on that here: Thread:167236. We might at some point either restore bits of the old CSS, or make a simpler design for those templates that better suits the new layout. Or we might just leave those templates uncustomised for a while, just text, plain and simple. I think it actually kind of works right now, as it is.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:178941
I've noticed on the Wiki homepage the text for the links at the top all display in black text and are hard to read. Other pages on the Wiki seem to have a mouse over colour change to white as the default setting which is more readable. I will attach a picture showing the homepage vs another page on the site.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:194341
Sometimes when I edit a TV story page, the story number for that page is automatically edited as well, being usually decreased by 1. When in preview mode the story number displayed is still the correct, unedited one. I noticed that often other users' edits also contains story number changes, but I not sure if they experienced the same issue or if they actually wanted to edit the story number.
- Shambala108
Could you give a couple of examples of pages where that happened to you?
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:196789
It's been past practice to add a topic at the bottom of posts here in the Forums. For instance, if you were talking about something that had to do with The Sun Makers, you'd maybe set The Sun Makers as a topic -- that is, something appearing under the heading, "pages most relevant to this discussion".
For technical reasons, these topics will no longer appear on pages, so there is no need to continue this practice. That space on the page is now directing people to our highly successful, well-attended Discussions in the hopes of getting you to interact with some of our mobile and Community App users.
- Our Wikia Fan App sits a solid five-star rating on iTunes, and is one of the best-reviewed Wikia apps.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:197716
It's a known, Wikia-level issue that the display of Game of Rassilon badges on people's user pages has come slightly out of alignment. Where once there were three columns of badges, now there is just one. A ticket has been filed, but this is something that needs to be solved by Wikia engineers, not Tardis administrators. As this issue just started overnight, there is not yet an ETA for its solution.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:199086
As I edit within the wiki, the page sometimes logs out and then when refreshed logs in again. This has happened on three different computers under three different ISP addresses. Is wikia playing up for anyone else or is it just me?
- DENCH-and-PALMER
Also tags take ages to load and sometimes never do as well as category adding.
- Shambala108
You will need to provide the browsers you've been using in order for someone to be able to help you.
- DENCH-and-PALMER
Google Chrome and Safari
- DENCH-and-PALMER
I also received this "Our main datacenter is down, you are accessing our backup datacenter. We are working to fix the problem".
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:205631
Suddenly, whenever I go to visit a page on TARDIS Data Core I get the page blocked by a stupid and irrelevant Google survey. Yes I know I can click "skip survey" but I shouldn't have to, and sometimes it doesn't appear for about 30 seconds, usually when I'm in the middle or reading a page. Is there any way of disabling this?
- DENCH-and-PALMER
Logging in can get rid of it. Unfortunately I believe this is the only way.
- SOTO
Yes, make an account, and there is very minimal advertising on Fandom (Wikia). Certainly no Google surveys.
- Bwburke94
Perhaps you have fallen victim to adware? Check your antivirus.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:207667
I believe this is very important, all the info boxes on the Slitheen seem to be messed up.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:218755
Hey everyone :)
As is happening a little later this week, FANDOM wide, we're getting a new header. Because this site is unusually heavily coded, you're going to see a good deal of stylistic variations this week as we adjust.
One of the biggest things you'll notice is that the ability to switch skins between dark-on-light and light-on-dark has been removed. It's very important to get the default, dark-on-light, scheme working first.
There are also a number of font issues to work out, so you are quite likely to see a number of different, and clashing, font styles this week.
- Sumanuil
I wondered what was going on. The layout all over the site is messed up, and I initially thought there was something wrong on my end.
- Phoenixclaw
Intresting, I don't have any problems at all (well, ok, I use an own, special modified personal CSS for my account to get rid of the break-point design).
P.S: I hope you don't want to chance the current blanco (or single colour) header to an image header, like the one in the Mass Effect Wiki. It would mess up the design of this wiki a little bit.
- Thefartydoctor
I'm growing to like this new layout. I'm hoping it reaches the Welsh Wiki at some point too. Very exciting stuff.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:237078
I can't seem to create pages using the custom preload feature anymore. Has anyone else encountered this problem?
- Shambala108
I suggest you leave a message at User:CzechOut - he knows a lot about the tech-y kind of stuff. Make sure you give him as much info as possible, like browser and system you're using.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:239079
You need to change the text colours on some of your navboxes please. Some text is invisible, blue on blue, in other places it's nigh unreadable because it's white on a pale colour.
- Scrooge MacDuck
Agreed. The same problem appears on the Old Forums archive, by the way.
- Dmitriy Volfson
It's still an issue, many navboxes have unreadable text!
- Jack "BtR" Saxon
I've been meaning to bring this up. I'm surprised it hasn't been fixed sooner.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:240687
- Danniesen
Are you sure it's not just a one-time error on your side of the screen? I mean, sometimes errors occur.
- CzechOut
Actually, it is working.
You'll notice that it's blocking out the the lead paragraph. That's how things are set up on that page. The nature of the spoiler javascript is that it blocks the first <div id="SpoilerAlert"> that's on the page. Currently, that div only includes the first paragraph.
You may be remembering an earlier form of this code which blocked the entire page. But the code now works on a per-first-div basis, and that can't be altered.
Of course, we could expand the amount covered in that first div, but it can't be the whole page.
Besides, the question now is, how much of that S11 page really needs to be covered by the spoiler warning? And is it really the lead paragraph? I suspect the spoiler warning needs to be taken off that first paragraph and probably moved to the section detailing not-yet-broadcast episode titles.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:240863
For reasons that I don't understand, on the Panopticon Archives, in this section…
…the links all point to pages with those supposed titles — i.e. [[Protection issues]]. Strangely, it does not appear as a redlink there, but if one clicks on them, one is then told that these pages are "the Zero Room" — that is to say that no such page exists.
I was quite puzzled by all of this until I realized that all of the links are written as if linking a page, rather than a category. Thus the example's link should be written as [[:Category:Protection issues|Protection issues]], for Protection issues.
How this mistake could have persisted for this long even though it makes the entire list of links next-to-useless is beyond me (perhaps some upgrade that didn't go well in years past? or a bug when archiving the old Forums?), but it really should be fixed. Thing is, I can't do it, as, being as its name implies an archive, the Panopticon Archive can't be edited by just anybody.
Indeed, perhaps no one, even the admins, can edit it; I don't know. If not, then a possible fix would be to create each linked page as a redirect to the relevant category.
To give you some local advice, however, I'll just say that the section at Panopticon Archives was never meant as a clickable selection of links.
See, it was really just a static list that was used when organising the archived threads on the page, and that's a project that was more-than-less finished back in 2012. It's just meant to be a list of the categories that one would use when putting unsorted forum threads onto the large table. Those categories are mostly useful because of how they organise the list.
I've removed that list, since its utility to that page is pretty weak at this point.
But, you're right, there is something wrong with DPL when it comes to listing categories and some other namespaces.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:242804
It started yesterday. I click the Edit button, but it simply doesn't load. I can use the Classic editor, but not the Visual. I read in Community that it might be a CSS error, but I don't know how to fix it.
- Scrooge MacDuck
Have you tried different browsers?
- 68.131.63.11
In order for someone to help you, you need to provide browser info, including version number.
- Dr Von Wer
I tried with Internet Explorer, but it redirects me to the Classic Editor. I'm using Google Chrome at the latest version, 71.0.3578.98 (64 bits).
- Scrooge MacDuck
It's loading fine with Opera for me; you might want to try that.
- CzechOut
Hey hey :)
Sorry you're having difficulties.
I've checked in every supported browser, including the variant of Google Chrome you mentioned, and the VE pops up fine. "Supported" is the key word. Fandom hasn't supported Internet Explorer for years, so your experience there is what I would have expected to happen.
I honestly don't know what caused your difficulties, since I can't replicate them. But it's possible you could have just experienced a very temporary glitch. Please do let me know if you're still experiencing these issues in Chrome.
Thanks!
- Dr Von Wer
Yes, I'm still experiencing them, and I wouldn't want to install a whole new browser just to edit this Wikia. I can get used to the Classic editor if that was necessary.
- Dr Von Wer
It must have been temporary, now I can access the Visual Editor just fine.
- Shambala108
It's great that you've got it working, but keep in mind what CzechOut said about IE. I used to use it for wikis but then it started crashing all the time so I had to change over to Chrome. It's something to keep in mind for the future if you have any more problems.
- Dr Von Wer
No, I don't usually use IE. I tried once if I could work there, and it didn't work. I mostly use Chrome.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:249582
In Template:Docpic, the last Noinclude closing tag is broken as there is a space in the tag. I don't think the tag does anything since the actual content is on includeonly tags, but I thought it was worth bringing up. This was also the easiest way I could see to notify admins/content mods since message walls aren't a thing on this wiki.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:249604
I didn't want to write this initially (and I'm still not sure if it's the right board), but the issue ramains the same for me.
I don't know about anyone else's experience, but the move from light background/dark text to dark background/light text on this Wiki was really heavy for my eyes. I thought they might adjust with time, but the contrast between Wiki and almost every other major websites that I (and many others, I'm sure) use frequently - Goggle, YouTube, Wikipedia, Twitter, other social networks and so on - remains. When I switch them to this Wiki, it's genuinely hurts my eyes!
So I'm not sure what to do. It's not comfortable at all for me to read or edit here with this dark background, and after long exposure to darkness it's even more painful to adjust back again to the light ones (which, again, is every other that I use, apart from this Wiki).
- Shambala108
I'm in complete agreement with you. It's very difficult reading, much less editing, on this wiki.
- Borisashton
Glad somebody has brought this up; it's very jarring and I much prefer the old design.
- RingoRoadagain
I'm used to dark design in general so it's not an issue for me but I admit that i rarely edit during the day. I am unsure what eye experts actually recommend.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:254279
Hi. I've noticed that some of the links to external sites could do with some renewal. Some of the links to ratings for individual episodes appear broken for some reason. They could do with some fixing.
- Danniesen
Somebody?
- Scrooge MacDuck
I suppose you might get some more interest in if you gave specific examples?
- Danniesen
For example for series 11 and the 2017 Xmas.
And just to note, it's easier for other users if you include links in your examples. That's general forum practice.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:256947
I don't know if it got so big it crashed or something, but the 10,000 Dawns inclusion debate seems to have… disappeared? Does anyone have any idea what's going on? It's not closed or moved to the Archives, but it's not in the Inclusion Debates either.
- Danochy
You should find your answer in the thread history.
- Shambala108
It has been deleted, so not a crash or bug.
- Scrooge MacDuck
…thanks, but if so, why?
- Shambala108
It was deleted by User:CzechOut, so you would have to ask him, but most likely he will address it at some point.
- Snivystorm
It's probably best to directly ask User:CzechOut given they're the one who deleted it.
Shame though. I enjoyed reading through it. Glad I found it when I did.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:281689
There’s an ongoing problem with images on this wiki. If an image has the same file name as a Wikimedia image, it will be replaced by the Wikimedia image.
Here are some examples of TARDIS wiki images being replaced with Wikimedia images. Some were on the wiki for many years before this happened.
- D.jpg was replaced with Heart on a hook with stars.jpg: https://tardis.fandom.com/wiki/Doris_Lethbridge-Stewart?direction=next&oldid=920710
- Static.jpg was replaced with (NSFW!) Static the SuicideGirl crouches.jpg: https://tardis.fandom.com/wiki/Static_(species)?direction=next&oldid=2851941
- The Beatles.jpg: https://tardis.fandom.com/wiki/The_Time_of_My_Life_(comic_story)?direction=next&oldid=973265
The last one was removed for assumed vandalism, but that doesn’t appear to be the case. What if someone gets banned for vandalism that they didn’t actually commit? NSFW images randomly appearing on this wiki is also a serious problem.
- NightmareofEden
I feel the best way around this is to get more specific with our filenames.
- Najawin
If the admins can't do anything about this, yes, I think that's probably the best option. Perhaps add an image policy that requires "DW" or "TARDIS" at the start of all filenames.
- Epsilon the Eternal
I think that would be a nightmare to apply, especially with the already tight policies on images.
Fingers crossed the admins can fix the problem.
- TheDarkBomber
Files from Wikimedia Commons shouldn't be appearing on this wiki to begin with, perhaps this is an issue we should contact CzechOut, a FANDOM staff member, to investigate this.
- TheDarkBomber
Ah, here's the rub: Thread:153478. Local images aren't supposed to be overwritten, yet they are.
- SOTO
Once deleted, there is no local image. It's simply a matter of deleted files still being called on in articles, when it's a problem at all.
- TheDarkBomber
Yep, a search through the deletion log confirms that this is the case. This answers all questions on this topic, as no further research or change is needed, and this thread should be closed.
- Borisashton
So the solution to this going forward is simply for the admins to ensure they remove the links to any images they delete from pages?
- TheDarkBomber
Yes.
- Shambala108
Admin note: User:TheDarkBomber is not an admin and therefore he has no say in the decision or closing of this thread.
I'd like to see some more opinions on this idea: removing the possibility of using wikipedia images. They would mostly fail Tardis:Guide to images anyway, and if it's possible to stop using them, would everyone be amenable to removing them altogether?
- Scrooge MacDuck
Oh, I, for one, certainly would be. It really wouldn't be hard to upload whatever images we needed the normal way, if ever we coveted an image that was already on Wikipedia. And as you say, that's an incredibly rare situation to begin with.
But the thing is, I'm not sure this is possible, on the coding level. The way I heard it told, Wikia defaulting to Wikipedia files when linked to a filename that doesn't exist within the particular Wiki's image library is simply a feature of the root code — not something individual Wikis can turn on and off on their own accord.
- Najawin
I have no strong feelings one way or the other.
Moreover, this use case does not violate Tardis image policy; in fact, it makes T:OOUI massively easier to uphold. There's really no excuse for not using a promotional image of an actor when they're "on-tap" from the Wikimedia Foundation.
The number of conflicts that are caused here are quite limited. Maybe you personally have encountered the odd case or twenty, depending on how much you edit, but the general editor probably never does.
So I think on balance, there's more harm than good in getting rid of this feature, given the age of this wiki. (indeed, the fact that this is the first real statement of a "problem" with this feature in more than a decade indicates it's not all that common an issue.)
The solution really is to just choose a different file name. It's no big deal. Just upload the file under a different name, and then you can ask an admin to delete your original one. That said, there's no particular reason deletion of a WM file needs to happen — the file, after all, doesn't actually live here at Tardis, so you don;'t really have to involve an admin at all.
Finally any NSFW images that you're seeing coming in from Wikipedia should definitely be referred to me, because this wiki may not be the only one having to deal with it.
Category:SOTO archive threads YYYYYY XXXXXX User:SOTO/Forum Test/The Drax Cave/Thread:286200
When uploading images of Fanzine covers I selected the "Fanzine covers" option. However, this adds {{Fanzine covers}} as the license template, which doesn't exist.
The correct template it should add is {{Fanzine cover}}:
This image is of a fanzine cover, and the copyright for it likely resides with BBC Worldwide, even though another individual may have, in some way, "remixed" the image. Since the images were reproduced without permission of the British Broadcasting Corporation, it's believed that the copyright for the image most likely resides with the BBC.
It is believed that the use of this image
- to illustrate an article discussing the magazine in question
- on the Tardis Data Core wiki, hosted on servers in the United States by the non-profit Wikia, Inc,
qualifies as fair dealing under the laws of the United Kingdom, Canada, and Australia, and as fair use under United States copyright law. Other use of this image, on Wikia or elsewhere, may be copyright infringement. See Wikipedia:Fair use for more information.
To the uploader: please add the source of the work and copyright information.
Can someone fix this?.
Category:SOTO archive threads YYYYYY Warning: Display title "User:SOTO/Forum Archive/The Drax Cave" overrides earlier display title "The Drax Cave/Problem with {{Fanzine cover}}".