User:SOTO/Forum Archive/The Drax Cave

User:SOTO/Forum Archive/The Drax Cave

page_id	sortkey	page_title	revision_id	timestamp	contributor_id	contributor_name	bytes
117183	20121202000716-188432	Board Thread:Tech notes/@comment-188432-20121202000716	1284989	2012-12-02 T00:07:16Z	188432	CzechOut	1419{{{1}}}{{{1}}} Paul Benjamin Austin What's happening with the Discontinuity section? the editing of those entries are disabled 06:42, 2 December 2012 CzechOut Are you sure they are? Didn't seem like they were disabled. Please double check. 06:44, 2 December 2012 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. 06:56, 2 December 2012 Eladkse CzechOut - admins can still edit the forum namespace, but ordinary user cannot (unless you've gotten staff to do something). 17:04, 2 December 2012 Eladkse Wow, this reply system is confusing... 17:05, 2 December 2012 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? 17:06, 2 December 2012 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? 17:08, 2 December 2012 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) 17:14, 2 December 2012 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. 17:14, 2 December 2012 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. 17:15, 2 December 2012 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. 17:16, 2 December 2012 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. 22:23, 2 December 2012 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. 16:24, 3 December 2012 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. 16:33, 3 December 2012 Edited 16:34 3 December 2012 TomekO Bit late to the party there, Tomek. 16:35, 3 December 2012 Edited 16:36 3 December 2012 CzechOut Archiving this thread, since the title might confuse people if it keeps popping up in the forum activity module. After all, the new forums have now already arrived and been officially opened. 16:46, 3 December 2012
117197	20121202032136-188432	Board Thread:Tech notes/@comment-188432-20121202032136	1285056	2012-12-02 T03:21:36Z	188432	CzechOut	591{{{1}}}{{{1}}} CzechOut No takers in almost five years. 03:15, 15 July 2017
117244	20121202211436-188432	Board Thread:Tech notes/@comment-188432-20121202211436	1285339	2012-12-02 T21:14:37Z	188432	CzechOut	608{{{1}}}{{{1}}} CzechOut So it's almost 8 years now after the introduction of our default, Wikia skin. You are heavily encouraged to switch over. At this point, a fair number of things are deprecated in Monobook, and neither FANDOM nor Tardis makes any sort of promises to make things right in Monobook. 03:43, 15 July 2017
117345	20121204070353-188432	Board Thread:The Drax Cave/@comment-188432-20121204070353	1286410	2012-12-04 T07:03:53Z	188432	CzechOut	785{{{1}}}{{{1}}} CzechOut This issue is being resolved in tomorrow's weekly update, per DaNASCAT. See this Community Central forum thread for more info. 16:17, 11 December 2012
117422	20121205181220-188432	Board Thread:The Drax Cave/@comment-188432-20121205181220	1287735	2012-12-05 T18:12:20Z	188432	CzechOut	271{{{1}}}
117462	20121207012152-188432	Board Thread:The Drax Cave/@comment-188432-20121207012152	1288073	2012-12-07 T01:21:53Z	188432	CzechOut	493{{{1}}}{{{1}}}
117716	20121211163546-188432	Board Thread:The Drax Cave/@comment-188432-20121211163546	1292851	2012-12-11 T16:35:47Z	188432	CzechOut	217{{{1}}} 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? 16:42, 11 December 2012 Edited 17:19 11 December 2012 Edited 17:20 11 December 2012 CzechOut Hmmm, I guess I should test whether this happens with other uncreated things. Let's try a picture. Will this picture show up if I upload it literally ex post facto? 16:49, 11 December 2012 CzechOut Glad I checked that, cause that doesn't work, either. As you can see, File:TestyTestyTesty.jpg does now exist: Nope, it won't show up until I physically republish the comment. Which can't be right. 16:58, 11 December 2012 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: This Board Thread link don't work, man. 17:03, 11 December 2012 Edited 17:03 11 December 2012 CzechOut If you are the Wikia Staff member responding to this bug report, please feel free to reopen this thread and leave messages as desired. This thread has been locked only to preserve the error demonstration. Once you've seen the error, thread closure is less important. 17:07, 11 December 2012
117799	20121214001734-188432	Board Thread:The Drax Cave/@comment-188432-20121214001734	1293637	2012-12-14 T00:17:35Z	188432	CzechOut	2931{{{1}}}
118118	20121218054232-188432	Board Thread:The Drax Cave/@comment-188432-20121218054232	1296364	2012-12-18 T05:42:33Z	188432	CzechOut	846{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}} Cult Of Skaro Gotcha. Not surprised by the size of the Discontinuity Index. Those people had a tendency to, erm, forget stuff. :P 05:58, 18 December 2012 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". 06:01, 18 December 2012 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. 06:16, 18 December 2012 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. 16:41, 24 December 2012 CzechOut Doctor Who prose discontinuity and plot holes is now reopened. Be aware, though, that it had never been particularly well-used, which is why there are so many redlinks. but at least all the redlinks point to the right place now and are italicised on the page. 18:21, 24 December 2012
118714	20121227055559-184.144.56.93	Board Thread:The Drax Cave/@comment-184.144.56.93-20121227055559	1307506	2012-12-27 T05:56:00Z	184.144.56.93	Anonymous	537{{{1}}} CzechOut What's the exact problem you're having with the captcha (the "prove you aren't a robot" thing)? 07:07, 27 December 2012 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. 08:31, 29 December 2012 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. 22:45, 29 December 2012 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. 05:11, 30 December 2012 Edited 05:16 30 December 2012
119783	20130108231223-188432	Board Thread:The Drax Cave/@comment-188432-20130108231223	1322434	2013-01-08 T23:12:23Z	188432	CzechOut	601{{{1}}} 4me-2me Where can you find the exact TARDIS blue colour? 01:01, 9 January 2013 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. 01:48, 9 January 2013 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... 09:04, 9 January 2013 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. 20:57, 9 January 2013 OttselSpy25 That's better. 20:58, 9 January 2013 Edited 21:51 9 January 2013 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. 22:54, 9 January 2013 4me-2me Good luck! 00:07, 10 January 2013 Imamadmad I'm starting to see the new blue around and I like it. I like it a lot. 09:37, 10 January 2013 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. 16:14, 10 January 2013 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. 16:39, 10 January 2013 CzechOut What's ark blue? 16:40, 10 January 2013 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! 17:05, 10 January 2013 OttselSpy25 ... As a background? Your cra- ... Your wro- ... I disagree with your opinion. 17:30, 10 January 2013 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. 17:34, 10 January 2013 OttselSpy25 I was making a joke about my often poor choice of words. The bottom line is what I actually mean. 17:35, 10 January 2013 CzechOut It doesn't read as a joke. 17:37, 10 January 2013 OttselSpy25 Yeah, that's a good point. Anyways, let's discuss this new background more. 17:54, 10 January 2013 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. 17:58, 10 January 2013 Trebligoniqua I like the changes, except that the links are blue, and are hard to read against the background. 20:31, 10 January 2013 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. 20:59, 10 January 2013 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. 21:05, 10 January 2013 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! 21:39, 10 January 2013 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. 21:52, 10 January 2013 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. 21:58, 10 January 2013 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? 22:09, 10 January 2013 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. 22:12, 10 January 2013 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. 22:47, 10 January 2013 Digifiend Yeah, I'm seeing the same. 23:15, 10 January 2013 Edited by CzechOut 23:37 10 January 2013 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. 23:20, 10 January 2013 Trebligoniqua Sorry, I just wanted to make sure that I didn't just need to change settings on my computer. 23:56, 10 January 2013 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. 23:59, 10 January 2013 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. 00:52, 11 January 2013 OttselSpy25 I wasn't trying to say it was a bad idea... It's just I did it and.... Uhhh.... Blue-on-blue... Ughhhhhhhh 00:55, 11 January 2013 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. 09:18, 11 January 2013 69.254.165.192 It's impossible to read anything in the Crew sections of pages. White text on white background :( 09:26, 11 January 2013 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). 09:49, 11 January 2013 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. 15:56, 11 January 2013 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. 16:02, 11 January 2013 Edited 16:02 11 January 2013 Eladkse Oh, yes. I see now. I can only just tell the difference, but that might be my screen... 16:07, 11 January 2013 CzechOut Hmmm, that worries me a bit, because the difference is obvious on my screen. Still, I haven't done mouseover effects yet. 16:14, 11 January 2013 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".] 18:33, 11 January 2013 Edited 19:18 11 January 2013 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! 18:43, 11 January 2013 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. 20:24, 11 January 2013 OttselSpy25 I dislike how broken links and normal links are basically the same colour in the main interface. 15:21, 12 January 2013 CzechOut So do I. Patience. 15:27, 12 January 2013 OttselSpy25 I know. Just posting issues, really. Turing out good otherwise... 16:12, 12 January 2013 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? 19:17, 13 January 2013 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. 19:36, 13 January 2013 Imamadmad I can see the difference, but I must admit it isn't obvious. Maybe if the blue was a bit darker? 19:42, 13 January 2013 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? 20:23, 13 January 2013 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. 20:23, 13 January 2013 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. 10:33, 14 January 2013 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? 14:15, 14 January 2013 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. 19:04, 14 January 2013 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. 20:11, 14 January 2013 Edited 20:12 14 January 2013 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? 20:25, 14 January 2013 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? 12:13, 21 January 2013 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. 15:31, 21 January 2013 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. 17:22, 21 January 2013 Edited 17:23 21 January 2013 CzechOut To your deleted-but-not-quite point, however, there are indeed some points where the colors don't work yet. 20:09, 21 January 2013 76.88.90.110 oi. i just wanted to say awesome work. 04:23, 22 January 2013 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? 20:26, 23 January 2013 CzechOut See our Twitter feed. Nope. Won't be that way for long, but "long" could be a few hours. 20:32, 23 January 2013 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. 09:12, 24 January 2013 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. 21:59, 28 January 2013 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? Tardis:TerryNation (dark skin): Oh, there they are. 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. 05:26, 1 February 2013 Edited 05:29 1 February 2013 Edited 05:31 1 February 2013 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. 13:30, 1 February 2013 Edited 13:32 1 February 2013 Edited 13:34 1 February 2013 CzechOut Well, that's a bit of a relief. Thanks for verifying that things have at least gotten better. :) 15:28, 2 February 2013 CzechOut By the way, if anyone out there is wondering why I have "allowed" navigation boxes to remain unreadable for such a long time, it's because there are other issues affecting navboxes that need to be addressed simultaneously. Beyond the question of illegible colouring — which is easy to fix — the boxes are too sensitive to size of input (i.e., number of characters in an entry). {{DWTV}} has been broken since October 2011 because it can't accommodate the length of The Doctor, the Widow and the Wardrobe. That's now bubbled to the top of the fix list, so hopefully I'll have navboxes back in use again today or tomorrow. In the meantime, {{DWTV}} will intermittently display various incomplete or inaccurate lists of episodes. 15:33, 2 February 2013
119952	20130110220649-188432	Board Thread:The Drax Cave/@comment-188432-20130110220649	1328959	2013-01-10 T22:06:49Z	188432	CzechOut	473{{{1}}}
120676	20130122184826-188432	Board Thread:The Drax Cave/@comment-188432-20130122184826	1340092	2013-01-22 T18:48:26Z	188432	CzechOut	306{{{1}}} 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. 19:33, 22 January 2013 Edited 19:35 22 January 2013 CzechOut This issue is definitely fixed at this point. If you're still having problems with the forums, please bypass your cache. 21:39, 22 January 2013
121031	20130128191903-1398253	Board Thread:The Drax Cave/@comment-1398253-20130128191903	1343622	2013-01-28 T19:19:03Z	1398253	Digifiend	533
121411	20130202233608-188432	Board Thread:The Drax Cave/@comment-188432-20130202233608	1348967	2013-02-02 T23:36:09Z	188432	CzechOut	397{{{1}}} CzechOut A new template for creating a link to the Alex Macqueen version of the Reborn Master has been created at, you guessed it, {{Macqueen}}. As a refresher, there are the rest of them: Delgado Ainley Roberts Jacobi Simm Fallen Macqueen Gomez Pratt Dreyfus Dhawan Tipple Titan McKee Pryce Merlin 23:39, 2 February 2013 Edited 23:40 2 February 2013 Edited 18:04 15 February 2017 Edited 18:06 15 February 2017 Edited 18:06 15 February 2017 Edited 18:08 15 February 2017 Edited 18:08 15 February 2017 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. 00:49, 17 February 2013 Edited 00:49 17 February 2013 CzechOut Yeah "new" these templates aren't anymore. Closing this lying thread. :) 03:45, 15 July 2017
121539	20130205035419-188432	Board Thread:The Drax Cave/@comment-188432-20130205035419	1349846	2013-02-05 T03:54:19Z	188432	CzechOut	1343{{{1}}} Memnarc That's a shame, but if it'll help the site, I guess it's for the best. 05:05, 5 February 2013 Edited 05:05 5 February 2013 SOTO As Memnarc said, a shame, but unfortunately necessary. Thank you, Czech, for taking the time to fix this. 06:14, 5 February 2013 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.  :) 01:45, 6 February 2013 CzechOut Yeah, illustrations in navboxes are even more pointless these days. 03:17, 15 July 2017
121686	20130206172138-4139960	Board Thread:The Drax Cave/@comment-4139960-20130206172138	1350915	2013-02-06 T17:21:39Z	4139960	Tybort	205 SOTO I noticed that too. Same here. I couldn't tell if the categories I was adding actually worked. 17:35, 6 February 2013 Shambala108 I'm not having this problem. Maybe it has to do with your browsers? or your preferences? 17:38, 6 February 2013 Tybort Seems to be on Firefox, and not IE or Chrome. 17:45, 6 February 2013 SOTO Happening to me on Chrome. 17:47, 6 February 2013 SOTO Anyone else experiencing this? If not, I'll add a screenshot so you know what's going on. 19:37, 6 February 2013 SOTO Fine. Delete my post at the other thread. I'll ask it here: are there any browsers where the categories do work? 00:07, 7 February 2013
121721	20130206223313-188432	Board Thread:The Drax Cave/@comment-188432-20130206223313	1351224	2013-02-06 T22:33:14Z	188432	CzechOut	767{{{1}}}{{{1}}} 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. 22:47, 6 February 2013 Edited 22:47 6 February 2013 Edited 22:48 6 February 2013 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. 22:52, 6 February 2013 SOTO I was just asking if there was one browser that worked. I'll take that as a no. 22:53, 6 February 2013 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). 00:44, 7 February 2013 Edited 00:45 7 February 2013 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. 15:00, 7 February 2013 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. 18:02, 7 February 2013 Moreno12 hi 18:42, 17 February 2013 CzechOut We actually pushed hard to get hidden categories restored by Wikia back in 2013 and were successful. You shouldn't have any problems with hidden category styling these days. 03:14, 15 July 2017
121760	20130207173213-188432	Board Thread:The Drax Cave/@comment-188432-20130207173213	1351522	2013-02-07 T17:32:13Z	188432	CzechOut	1139{{{1}}} Moreno12 hi 18:41, 17 February 2013
122313	20130214231443-82.20.113.152	Board Thread:The Drax Cave/@comment-82.20.113.152-20130214231443	1354804	2013-02-14 T23:14:43Z	82.20.113.152	Anonymous	265{{{1}}} 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? 00:38, 15 February 2013 Shambala108 OP, at SmallerOnTheOutside's request, I posted a test message on the other thread. It's not much, but can you see it? 00:52, 15 February 2013 SOTO Shambala tested. It worked. Are you sure several people replied? 00:52, 15 February 2013 SOTO You're too quick for me. :-P Can you just confirm that you can see my two responses there? I can see yours. 00:53, 15 February 2013 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? 04:22, 15 February 2013 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. 15:00, 15 February 2013 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. 15:09, 15 February 2013 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). 06:10, 21 February 2013 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). 06:10, 21 February 2013 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. 06:22, 21 February 2013 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. 06:46, 21 February 2013 CzechOut Oh, I think you misunderstand me. I do want to know about it, and indeed I've filed several reports to Wikia about IP editor-related issues. I'm just trying to point out to the IP user who started the thread that if you're an IP editor, you almost certainly experience more bugs, and for a longer period of time, than registered editors. 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. 17:07, 21 February 2013 Edited 17:08 21 February 2013
123289	20130226002848-26975268	Board Thread:The Drax Cave/@comment-26975268-20130226002848	1362181	2013-02-26 T00:28:48Z	5918438	SOTO	633 SOTO Sorry. More like a half an hour/40 minutes. 00:30, 26 February 2013
123470	20130303022752-26975268	Board Thread:The Drax Cave/@comment-26975268-20130303022752	1363887	2013-03-03 T02:27:52Z	5918438	SOTO	1484{{{1}}} Digifiend Seems to be a CSS issue, as Monobook is unaffected. 02:44, 3 March 2013 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. 02:47, 3 March 2013 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. 03:15, 3 March 2013 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. 03:19, 3 March 2013 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? 03:23, 3 March 2013
123637	20130305050616-188432	Board Thread:The Drax Cave/@comment-188432-20130305050616	1364777	2013-03-05 T05:06:16Z	188432	CzechOut	1603{{{1}}}{{{1}}}{{{1}}} 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 :) ) 11:13, 5 March 2013
123716	20130306155219-4139960	Board Thread:The Drax Cave/@comment-4139960-20130306155219	1365213	2013-03-06 T15:52:19Z	4139960	Tybort	374{{{1}}} CzechOut I see no evidence of the situation you're describing. Please provide screenshots. 16:50, 6 March 2013 Tybort It's a Windows 7 OS, if that helps. -- Tybort (talk page) 16:58, March 6, 2013 (UTC) File:Timey-wimey messed up.jpg Timey-wimey File:Panopticon archive messed up.jpg Panopticon archive File:Howling archive messed up.jpg Howling archive 16:58, 6 March 2013 CzechOut Please provide exact version numbers of browsers depicted. 17:06, 6 March 2013 Tybort Firefox 19.0, Internet Explorer 9.0.8112.16421 and Chrome 25.0.1364.152 m. 17:10, 6 March 2013 CzechOut Are you quite certain you've cleared your cache? 17:12, 6 March 2013 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. 17:15, 6 March 2013 CzechOut So has this problem abated for you? 18:50, 6 March 2013 Tybort Yes it has. Not sure how, but yes. 22:03, 6 March 2013 CzechOut Closing thread as resolved. 03:36, 7 March 2013
123741	20130306214217-188432	Board Thread:The Drax Cave/@comment-188432-20130306214217	1365296	2013-03-06 T21:42:17Z	188432	CzechOut	803{{{1}}}
123917	20130308032914-6433721	Board Thread:The Drax Cave/@comment-6433721-20130308032914	1365857	2013-03-08 T03:29:14Z	6433721	ComicBookGoddess	268{{{1}}} SOTO I'm getting the same thing, on both Chrome and Internet Explorer. 03:44, 8 March 2013 CzechOut Closing as resolved. DPL errors can occasionally occur and the ones like these depicted are browser-independent. If you see it in Chrome, you'll see it in Safari and Opera, too. 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. 05:28, 8 March 2013
124018	20130308221602-26975268	Board Thread:The Drax Cave/@comment-26975268-20130308221602	1366208	2013-03-08 T22:16:02Z	5918438	SOTO	686{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}} SOTO The forum issue seems to only be on the Panopticon; not here. 22:18, 8 March 2013 CzechOut Yeah it is temporary. I had not finished the final color fix for the dark on light design before I had my eye infection, leading to a high degree of variability in the link colours. I'm now continuing that work so that colours can be stable by the debut of the new series. There will be multiple colour changes over the weekend. 22:19, 8 March 2013
124158	20130309235126-188432	Board Thread:The Drax Cave/@comment-188432-20130309235126	1366692	2013-03-09 T23:51:27Z	188432	CzechOut	417{{{1}}}{{{1}}} SOTO No 00:02, 10 March 2013 Edited 00:03 10 March 2013 Mini-mitch No EDIT: Yes, now I can. Works fine on Google Chrome version 25.0.1364.152 m 00:06, 10 March 2013 Edited 12:47 10 March 2013 CzechOut Whoa. Wait a minute. You're not seeing that? Please provide screenshots of what you are seeing. 00:08, 10 March 2013 SOTO Same as ComicBookGoddess. I'll upload a screenshot in a moment. EDIT: Here you go: 00:09, 10 March 2013 Edited 00:14 10 March 2013 Edited 00:14 10 March 2013 CzechOut What browser version number and OS version number is this, please? 00:15, 10 March 2013 CzechOut Mini-mitch: are you throwing errors like this, too? 00:18, 10 March 2013 SOTO Me: Google Chrome (Version 25.0.1364.97) on Windows 7 (not OS). Mini-mitch? 00:18, 10 March 2013 Edited 00:19 10 March 2013 CzechOut What do you mean "7 (not OS)". Windows 7 isn't your operating system? Could you please provide your numerical OS? 00:21, 10 March 2013 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. 00:25, 10 March 2013 Edited 00:25 10 March 2013 CzechOut For the moment, please again look at Tardis:Help and tell me what you see. 00:29, 10 March 2013 SOTO Whoa. Now it's working. What did you do? 00:30, 10 March 2013 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. :) 00:35, 10 March 2013 Shambala108 Yes (IPad Safari) 00:40, 10 March 2013 SOTO Figured it out. V6.1 00:43, 10 March 2013 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). 00:47, 10 March 2013 Bubblecamera Yes. Currently on my Mac, using Safari. Will check with Firefox now. 00:55, 10 March 2013 Bubblecamera Yes for Firefox too. 00:56, 10 March 2013 Cult Of Skaro Yes. Google Chrome Windows. 02:11, 10 March 2013 PrydonianShadow Yes (Google Chrome) 02:53, 10 March 2013 OttselSpy25 Yes (Opera) 04:51, 10 March 2013 Silent Hunter UK Yes for Firefox. 19:36, 10 March 2013 Revanvolatrelundar Yes. 19:43, 10 March 2013 CzechOut Okay guys :) Thanks very much for your help :) Closing as resolved. 20:43, 10 March 2013
124551	20130313055149-188432	Board Thread:The Drax Cave/@comment-188432-20130313055149	1368453	2013-03-13 T05:51:49Z	188432	CzechOut	586{{{1}}}{{{1}}}{{{1}}} OttselSpy25 Thanks Mira! :) Does this mean that bullets in references sections is now a non-issue? 11:09, 13 March 2013 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. 16:23, 13 March 2013 Mira84 I'm glad we were able to help you guys out :) I must say the pages look much much better :) 16:35, 13 March 2013 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! :) 18:24, 13 March 2013 Shadowninja016 Great! 12:54, 7 April 2013
126904	20130405145942-7841417	Board Thread:The Drax Cave/@comment-7841417-20130405145942	1388872	2013-04-05 T14:59:42Z	7841417	CaptKirk42	220{{{1}}} 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 :) 15:17, 5 April 2013 CaptKirk42 It is pretty much the main data core pages. The forums are fine. 15:28, 5 April 2013 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.) 15:45, 5 April 2013 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 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. 16:28, 5 April 2013 CaptKirk42 Firefox 19.0.2 16:53, 5 April 2013 CzechOut And you're sure you've cleared your cache? I'm on 19.0.2 for Mac and cannot replicate your issue. 16:56, 5 April 2013 CaptKirk42 "Firefox: hold down the Shift key while clicking Reload;" Ah that seems to have done the trick Thanks. 16:56, 5 April 2013 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. 16:57, 5 April 2013 CzechOut Oh, and FF just updated to 20.0, so you'll probably want to grab that. 16:58, 5 April 2013
127351	20130408211455-81.153.85.222	Board Thread:The Drax Cave/@comment-81.153.85.222-20130408211455	1392376	2013-04-08 T21:14:55Z	81.153.85.222	Anonymous	453 CzechOut It's not GMT. It's UTC. Which is one hour off of BST right now, because it's a non-daylight savings timezone. For a little over half the year, the British think they're looking at the wrong time. But it's not. 00:58, 9 April 2013
127566	20130411031336-188432	Board Thread:The Drax Cave/@comment-188432-20130411031336	1394282	2013-04-11 T03:13:36Z	188432	CzechOut	1212{{{1}}}{{{1}}} 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. 16:24, 11 April 2013 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. 17:43, 11 April 2013 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) 17:45, 11 April 2013
127715	20130412155344-188432	Board Thread:The Drax Cave/@comment-188432-20130412155344	1395375	2013-04-12 T15:53:44Z	188432	CzechOut	672{{{1}}}{{{1}}} 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. 17:34, 12 April 2013 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. 22:42, 13 April 2013 Doctordoom61 ok 01:50, 2 May 2013 Cult Of Skaro Doctordoom61 wrote: ok Why are all your posts 'ok?' 01:40, 3 May 2013
127893	20130414131636-188432	Board Thread:The Drax Cave/@comment-188432-20130414131636	1396829	2013-04-14 T13:16:36Z	188432	CzechOut	1218{{{1}}}
128154	20130417123459-188432	Board Thread:The Drax Cave/@comment-188432-20130417123459	1399064	2013-04-17 T12:34:59Z	188432	CzechOut	79
128155	20130417123706-188432	Board Thread:The Drax Cave/@comment-188432-20130417123706	1399071	2013-04-17 T12:37:06Z	188432	CzechOut	78{{{1}}} CzechOut There's no more UNIT. Or TARDIS. 12:42, 17 April 2013 CzechOut There's no more UNIT. Or TARDISES. 12:42, 17 April 2013 CzechOut I'm not sure IF IT WILL EVER HAPPEN. 12:42, 17 April 2013 CzechOut There's no more UNIT. Or TARDIS. 12:45, 17 April 2013 CzechOut He took the TARDIS home. Then he took the TARDIS to the park. Then he took the TARDIS all the way home. 12:45, 17 April 2013 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. 12:47, 17 April 2013 CzechOut The Doctor shouted, "DON'T TOUCH THAT", but no one was listening. 12:47, 17 April 2013 CzechOut == No UNIT == I wish I could say there was a UNIT. Or a TARDIS. 20:43, 17 April 2013
128198	20130417201813-188432	Board Thread:The Drax Cave/@comment-188432-20130417201813	1399394	2013-04-17 T20:18:13Z	188432	CzechOut	3530{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}
128596	20130424002107-7302713	Board Thread:The Drax Cave/@comment-7302713-20130424002107	1404212	2013-04-24 T00:21:07Z	7302713	Anoted	1374{{{1}}}{{{1}}} 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. 13:13, 25 April 2013 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? 01:30, 26 April 2013 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. 19:32, 26 April 2013 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! 01:01, 27 April 2013 CzechOut Yeah, we have a lot of templates that add categories automatically. We've tried to note the added category in the template's documentation. So do make sure you check on the template page to understand what it's doing. 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. 01:25, 27 April 2013
128768	20130426150212-7302713	Board Thread:The Drax Cave/@comment-7302713-20130426150212	1406009	2013-04-26 T15:02:12Z	7302713	Anoted	277 Shambala108 It should be at Thread:121256. 15:06, 26 April 2013 Shambala108 What is the name of the article where you found this? 15:08, 26 April 2013 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. 15:15, 26 April 2013 Anoted This should not still be linking to 58, and yet it is. Seriously weird. 15:17, 26 April 2013 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. 16:39, 26 April 2013 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. 16:44, 26 April 2013
129089	20130429014206-7302713	Board Thread:The Drax Cave/@comment-7302713-20130429014206	1409009	2013-04-29 T01:42:07Z	7302713	Anoted	79
129090	20130429014625-7302713	Board Thread:The Drax Cave/@comment-7302713-20130429014625	1409012	2013-04-29 T01:46:26Z	7302713	Anoted	216 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. 01:53, 29 April 2013 CzechOut Please give me a link to an example. 15:19, 30 April 2013 CzechOut Yeah, really going to need an example, because the time of forum posts matches special:wikiactivity. 15:21, 30 April 2013 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? 15:28, 30 April 2013 Anoted posted message at 15:50 signature and history both show the edit was done at 15:47 posted at 15:54, half past edited: at 15:57 15:51, 30 April 2013 Edited 15:54 30 April 2013 Edited by CzechOut 15:57 30 April 2013 Anoted The post I just posted noe shows as 3 minutes ago, 15:51 15:52, 30 April 2013 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? 15:56, 30 April 2013 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. 15:59, 30 April 2013 CzechOut czechout<staff /> ☎ ✍  16:00: Tue 30 Apr 2013 16:00, 30 April 2013 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. 16:01, 30 April 2013 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. 16:07, 30 April 2013 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 16:37, 30 April 2013
129249	20130430151418-188432	Board Thread:The Drax Cave/@comment-188432-20130430151418	1410167	2013-04-30 T15:14:18Z	188432	CzechOut	45
129281	20130430162803-7302713	Board Thread:The Drax Cave/@comment-7302713-20130430162803	1410224	2013-04-30 T16:28:03Z	7302713	Anoted	55 CzechOut Please stop opening all these threads. This can only be solved by us talking live together and establishing that we're seeing the same thing. Please click here now. 16:30, 30 April 2013
130730	20130514210245-1398253	Board Thread:The Drax Cave/@comment-1398253-20130514210245	1429412	2013-05-14 T21:02:46Z	1398253	Digifiend	187
130935	20130516204608-188432	Board Thread:The Drax Cave/@comment-188432-20130516204608	1430736	2013-05-16 T20:46:09Z	188432	CzechOut	955{{{1}}}{{{1}}}{{{1}}} 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. 20:57, 16 May 2013 CzechOut Still actively pursuing this one. 22:45, 16 May 2013 Cult Of Skaro Oh. Just read this *after* I hit publish on The Keys of Marinus. 23:39, 16 May 2013 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. 23:41, 16 May 2013 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. 23:48, 16 May 2013 Cult Of Skaro I only added a sentence. It's not a big deal. :P 23:52, 16 May 2013 SOTO Did you just link to sentence? :D 23:53, 16 May 2013 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 :) 23:53, 16 May 2013 Cult Of Skaro Kinda scary, if you do have to revert the database, this discussion won't have happened. O.o 23:55, 16 May 2013 SOTO What discussion? ;) 23:56, 16 May 2013 CzechOut Still working at it. Won't be long now. Thanks for your patience. 00:10, 17 May 2013 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. 00:17, 17 May 2013 SOTO Thank you for fixing that, Czech! 00:20, 17 May 2013
131006	20130517192232-1398253	Board Thread:The Drax Cave/@comment-1398253-20130517192232	1431912	2013-05-17 T19:22:32Z	1398253	Digifiend	378{{{1}}}{{{1}}} 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. 19:32, 17 May 2013 Edited 19:33 17 May 2013 Digifiend Ah, fixed it, thanks. I see SOTO flagged that the page needs renaming, could you do that please? 00:19, 18 May 2013
131538	20130520210331-188432	Board Thread:The Drax Cave/@comment-188432-20130520210331	1435639	2013-05-20 T21:03:31Z	188432	CzechOut	949{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}} 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. 00:43, 21 May 2013 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. 03:09, 9 June 2013 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. 16:37, 9 June 2013 CzechOut Yeah, but these are rare examples, and it's really not the way the module is intended to work. 16:51, 9 June 2013 CzechOut I have new assurances from BertH that this issue has indeed bubbled up to the top of the Engineering team's work rota. It's looking more likely that that we may have a fix by early July. 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. 14:11, 12 June 2013
131563	20130521004948-188432	Board Thread:The Drax Cave/@comment-188432-20130521004948	1435800	2013-05-21 T00:49:49Z	188432	CzechOut	538{{{1}}} 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. 01:45, 21 May 2013 Edited 01:48 21 May 2013 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? 05:36, 21 May 2013 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. 05:43, 21 May 2013 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. 06:46, 21 May 2013 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. 07:50, 21 May 2013 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. 08:08, 21 May 2013 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. 17:14, 21 May 2013 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. 22:42, 23 May 2013 Edited 22:43 23 May 2013 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. 22:53, 23 May 2013 Edited 22:55 23 May 2013 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". 23:00, 23 May 2013 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. 23:07, 23 May 2013 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. 23:12, 23 May 2013 CzechOut And follow button fixed, too. 23:15, 23 May 2013 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? 16:48, 24 May 2013 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. :) 17:30, 24 May 2013 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. 17:21, 25 May 2013 Edited 17:22 25 May 2013 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. 22:06, 18 June 2013 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. 04:50, 31 December 2013 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.] 05:06, 31 December 2013 Edited 05:09 31 December 2013 Edited 05:24 31 December 2013 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. 05:25, 31 December 2013 Edited 05:27 31 December 2013 CzechOut Hmmm. Interesting. Oh the joys of the front page. I'll look into it. 05:29, 31 December 2013 CzechOut Okay, temporary fix enabled. Seems to be working, so it may not be all that temporary. 05:55, 31 December 2013 Josiah Rowe Fixed for me! Thanks. 16:02, 31 December 2013
132014	20130525171247-188432	Board Thread:The Drax Cave/@comment-188432-20130525171247	1440981	2013-05-25 T17:12:48Z	188432	CzechOut	1741{{{1}}}{{{1}}} SOTO I've tried that before, and it's never worked... 17:15, 25 May 2013 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. 17:22, 25 May 2013 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. 17:24, 25 May 2013 CzechOut Please make a specific test of exactly the instructions I've given. I've just tested it again, without issue. 17:30, 25 May 2013 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. 17:34, 25 May 2013 Cult Of Skaro Well, apparently on 'inferior systems (though I generally prefer Windows ;)' it doesn't work. Odd... 17:35, 25 May 2013 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. 17:38, 25 May 2013 Edited 17:38 25 May 2013 Edited 17:39 25 May 2013 CzechOut Well, how disappointing. Sorry. If this advice isn't more broadly applicable, I guess I'll have to withdraw it. Sucks not to have a Mac, then. 01:34, 27 May 2013
133639	20130609001312-188432	Board Thread:The Drax Cave/@comment-188432-20130609001312	1473145	2013-06-09 T00:13:13Z	188432	CzechOut	457{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}} CzechOut Wikia have this on their schedule to fix by Monday 10 June. Until the bug is fixed, you can avoid the error by editing the entire page, rather than just a section. 02:52, 9 June 2013
138016	20130724162545-188432	Board Thread:The Drax Cave/@comment-188432-20130724162545	1527954	2013-07-24 T16:25:45Z	188432	CzechOut	488{{{1}}}{{{1}}}{{{1}}}{{{1}}} Cult Of Skaro I don't see anything unusual... 17:14, 24 July 2013 SOTO Yeah, I'm not noticing anything different either... Maybe it's only on Macs? 18:54, 24 July 2013 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. 02:17, 25 July 2013 SOTO Ah, sorry, I didn't notice it because I didn't think to look in the comments. Didn't see them at first. 02:30, 25 July 2013
140478	20130905015449-188432	Board Thread:The Drax Cave/@comment-188432-20130905015449	1547911	2013-09-05 T01:54:49Z	188432	CzechOut	506{{{1}}}{{{1}}}{{{1}}}{{{1}}} CzechOut Blah, couldn't be bothered to wait for the whole explanation from Wikia. It seems to be fixed now. Sorry for the inconvenience. 02:49, 5 September 2013 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. 03:38, 5 September 2013 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. 03:43, 5 September 2013 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. :) 03:44, 5 September 2013 Midnite Marshall The font seems fine to me :P 23:27, 19 September 2013
141144	20130912194633-188432	Board Thread:The Drax Cave/@comment-188432-20130912194633	1560284	2013-09-12 T19:46:33Z	188432	CzechOut	1887{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}} 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! 21:34, 12 September 2013 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. 22:59, 12 September 2013 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. 23:03, 12 September 2013 Edited 23:03 12 September 2013 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. 23:24, 12 September 2013 Edited 23:44 12 September 2013 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. 17:19, 13 September 2013 Edited 12:46 14 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. 12:47, 14 September 2013 Edited 16:01 14 September 2013 CzechBot Okay, our local javascript modifications have now been entirely turned off. 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. 13:27, 14 September 2013 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. 13:54, 16 September 2013 Edited 14:39 16 September 2013 Edited 14:43 16 September 2013 Edited 14:44 16 September 2013 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. 14:49, 16 September 2013 Edited 15:06 16 September 2013 Edited 16:44 16 September 2013 Edited 16:52 16 September 2013 Edited 16:53 16 September 2013 Edited 17:10 16 September 2013 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 15:05, 16 September 2013 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 15:11, 16 September 2013 CzechOut Now that it's been in place for a while, anyone got any thoughts on Darwin that they'd like to share? 20:34, 28 October 2013
141282	20130914201851-4139960	Board Thread:The Drax Cave/@comment-4139960-20130914201851	1561436	2013-09-14 T20:18:51Z	4139960	Tybort	454{{{1}}}{{{1}}} 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. 20:44, 14 September 2013 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. 22:02, 14 September 2013 CzechOut Yes, I've intentionally turned all javascript off for the time being. The title italicisation feature is just one of many that's not available at the moment. Hopefully I'll get the all clear later today to turn it all back on. 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. 13:48, 16 September 2013
141398	20130916153151-65.49.68.169	Board Thread:The Drax Cave/@comment-65.49.68.169-20130916153151	1562774	2013-09-16 T15:31:51Z	65.49.68.169	Anonymous	183{{{1}}} CzechOut A lot of little things that make the wiki cooler are now temporarily on holiday. This, and all of them, will return. Please see Thread:141144. 17:08, 16 September 2013
143338	20131017183807-188432	Board Thread:The Drax Cave/@comment-188432-20131017183807	1577138	2013-10-17 T18:38:07Z	188432	CzechOut	405{{{1}}}{{{1}}}{{{1}}}{{{1}}} CzechOut 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. 18:39, 17 October 2013
144139	20131102024230-188432	Board Thread:The Drax Cave/@comment-188432-20131102024230	1583052	2013-11-02 T02:42:30Z	188432	CzechOut	992{{{1}}}{{{1}}}{{{1}}} 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. 16:59, 9 November 2013 Edited 17:13 9 November 2013 Edited 17:14 9 November 2013 Edited 17:14 9 November 2013 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 17:18, 9 November 2013 Edited 17:19 9 November 2013 CzechOut Mavericks is no longer supported, but this issue is currently true of every iteration of OS X and iOS that came after. Effectively, this means that .ogg files are banned here, because they can't be used by a significant number of our users. 03:21, 15 July 2017
144168	20131102142349-24121916	Board Thread:The Drax Cave/@comment-24121916-20131102142349	1583158	2013-11-02 T14:23:49Z	24121916	Davemyt0	1081
144363	20131109144602-188432	Board Thread:The Drax Cave/@comment-188432-20131109144602	1584921	2013-11-09 T14:46:03Z	188432	CzechOut	319{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}} 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. File:Fish fingers... and custard? - Doctor Who - BBC 501px non-thumb File:Fish fingers... and custard? - Doctor Who - BBC 501px thumb 14:49, 9 November 2013 Edited 14:49 9 November 2013 Edited 15:20 9 November 2013 CzechOut Now let's take the thumb away. What do we get? Nada. A non-thumb alone doesn't play in Wall Forum. File:Fish fingers... and custard? - Doctor Who - BBC 501px non-thumb 14:53, 9 November 2013 Edited 14:53 9 November 2013 Edited 14:55 9 November 2013 Edited 15:22 9 November 2013 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. File:Comic-Con - Doctor Who - Toby Whithouse Interview 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. 14:55, 9 November 2013 Edited 14:56 9 November 2013 Edited 15:25 9 November 2013 Edited 15:26 9 November 2013 Edited 15:44 9 November 2013 Edited 15:49 9 November 2013 CzechOut File:Comic-Con - Doctor Who - Toby Whithouse Interview See, by contrast, how nicely a thumb plays? 15:04, 9 November 2013 Edited 15:27 9 November 2013 Edited 15:27 9 November 2013 CzechOut You might very well think that this is a Tardis customisation issue, because our WallForum is ... weird. But such is not the case. For an examination of the problem in a customisation-free Wall Forum, giving exactly the same results, go to: w:c:czechout:Thread:2317. 15:25, 9 November 2013
145888	20131125212217-1398253	Board Thread:The Drax Cave/@comment-1398253-20131125212217	1596180	2013-11-25 T21:22:17Z	1398253	Digifiend	481{{{1}}}{{{1}}} CzechOut Thanks :) This is a known issue, but the reminder is helpful. 03:19, 26 November 2013 MjaxMajoran sorry to necropost, but nearly a year has passed and this issue has still not been addressed. 03:20, 9 June 2015 CzechOut Helpfully, SOTO fixed this issue a few weeks ago. 02:43, 15 July 2017
146625	20131204012708-188432	Board Thread:The Drax Cave/@comment-188432-20131204012708	1612128	2013-12-04 T01:27:08Z	188432	CzechOut	450{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}} 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. 13:06, 4 December 2013 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. 15:10, 4 December 2013 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. 10:46, 6 December 2013 Embem5 thank you! everywhere i look there is a stub tag that says CAT and it is bothering me! Thank You!!! 11:43, 16 December 2013 108.236.90.188 Anyway I can help? 16:27, 17 December 2013 CzechOut Nope. IP editors can't upload pics, which is the main thing now required. 16:28, 17 December 2013 108.236.90.188 Thanks anyway. 16:48, 17 December 2013 108.236.90.188 Speaking of stub tags check out Song. 16:50, 17 December 2013
146716	20131206014458-188432	Board Thread:The Drax Cave/@comment-188432-20131206014458	1613311	2013-12-06 T01:44:58Z	188432	CzechOut	596{{{1}}}
148742	20140101194721-188432	Board Thread:The Drax Cave/@comment-188432-20140101194721	1641488	2014-01-01 T19:47:21Z	188432	CzechOut	354{{{1}}}{{{1}}}{{{1}}}
148894	20140102235853-188432	Board Thread:The Drax Cave/@comment-188432-20140102235853	1642831	2014-01-02 T23:58:53Z	188432	CzechOut	519{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}} 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. 02:55, 4 January 2014 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. 03:21, 4 January 2014 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. 03:24, 4 January 2014 Edited 03:24 4 January 2014 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.) 07:30, 5 January 2014 CzechOut These issues no longer apply to current versions of OS X, and Safari 7 is no longer supported by FANDOM. 02:45, 15 July 2017
149479	20140109234009-1398253	Board Thread:The Drax Cave/@comment-1398253-20140109234009	1648793	2014-01-09 T23:40:09Z	1398253	Digifiend	328{{{1}}} CzechOut Why are you including multiple paragraphs on a block quote? That's gonna take up an insane amount of vertical space? 01:01, 10 January 2014 CzechOut Yeah, just checked. That is way, way beyond what {{quote}} is meant to handle. That's like 1200px of vertical space, or more, in an already bulleted area. {{quote}} is not actually designed for more than about 3 sentences. 01:04, 10 January 2014 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. 16:44, 10 January 2014 CzechOut No action taken since it was a page-specific issue. However, it's possible that the recent 2017 revisions to CSS would have fixed this anyway. Maybe. 04:16, 15 July 2017
149538	20140110195305-17651890	Board Thread:The Drax Cave/@comment-17651890-20140110195305	1649391	2014-01-10 T19:53:05Z	17651890	UncertainError	230{{{1}}} 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. 21:37, 10 January 2014 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. 22:38, 10 January 2014 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. 22:40, 10 January 2014 Shambala108 oops i forgot 23:24, 10 January 2014 CzechOut None of this applies any longer. 03:11, 15 July 2017
149637	20140112194014-213828	Board Thread:The Drax Cave/@comment-213828-20140112194014	1650314	2014-01-12 T19:40:14Z	213828	MisterRandom2	658{{{1}}}{{{1}}} 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." 22:30, 12 January 2014 Edited 22:31 12 January 2014 Edited 22:32 12 January 2014 SOTO This specific problem has now been fixed. Closing thread. 04:36, 13 January 2014
149806	20140115235742-2162194	Board Thread:The Drax Cave/@comment-2162194-20140115235742	1653598	2014-01-15 T23:57:42Z	2162194	AdricLovesNyssa	688{{{1}}}{{{1}}}{{{1}}} Digifiend It's either been fixed, or it's not affecting Google Chrome on Windows 7. 01:52, 16 January 2014 Doug86 The problem also extends to the Monobook skin as well. Doug86 ☎ 02:44, January 16, 2014 (UTC) 02:44, 16 January 2014 69.255.48.182 It hasn't been fixed. I'm using Firefox 21.0 on Windows 7. 13:45, 16 January 2014 Alan-WK Bug continues. I'm using Firefox 26.0 on Windows XP. 14:39, 16 January 2014 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. 16:03, 16 January 2014 Digifiend Seems to be browser specific then, and not affecting Chrome. Screenshot: 17:31, 16 January 2014 Bwburke94 Bug exists for me as well, making articles unreadable. Pictures are "spilling over" onto the main article text. 23:55, 19 January 2014 CzechOut Is there anyone here experiencing this bug who is not using Firefox? 00:20, 20 January 2014 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. 01:19, 20 January 2014 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. 07:29, 20 January 2014 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. 07:38, 20 January 2014 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" 07:59, 20 January 2014 Edited 08:01 20 January 2014 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. 08:03, 20 January 2014 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. 08:12, 20 January 2014 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. 08:16, 20 January 2014 CzechOut Situation no longer obtains. It's talking about the old wikitext boxes, which we no longer use. 04:21, 15 July 2017 Edited 04:23 15 July 2017
149809	20140116020113-1398253	Board Thread:The Drax Cave/@comment-1398253-20140116020113	1654160	2014-01-16 T02:01:13Z	1398253	Digifiend	482{{{1}}} SOTO There. Is that any better? 23:18, 16 January 2014 Digifiend Yeah, that's fixed it, thanks. 02:24, 17 January 2014
150126	20140121025410-1432718	Board Thread:The Drax Cave/@comment-1432718-20140121025410	1658969	2014-01-21 T02:54:10Z	1432718	Shambala108	227{{{1}}} Shambala108 They also show up in "recent wiki activity". 16:01, 21 January 2014 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? 21:32, 21 January 2014 Shambala108 I think I first noticed it Sunday or yesterday. 21:59, 21 January 2014 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"). 22:36, 21 January 2014 Edited 22:38 21 January 2014 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. 22:51, 21 January 2014 Shambala108 Yeah, I remember that one, but I thought there was a more recent example too. Maybe it was when the forums changed format. 23:48, 21 January 2014 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. 02:46, 23 January 2014 Shambala108 Minor edits (except for bot edits) do normally show up in wiki activity. 04:42, 23 January 2014 Digifiend Ah, OK then, thanks. Just thought it best to check considering there are several ongoing bugs here. 15:31, 23 January 2014 Edited 15:32 23 January 2014 CzechOut Guys, thanks for the feedback. This is a part of an effort to make custom namespaces work in much the same way as the normal namespaces. We are working with Wikia to fine tune these adjustments. We figured that we'd try this new approach now, when spoilers weren't quite so abundant. By the time we get closer to the period when spoilers start to leak out, we hope to have this all straightened out. 19:02, 23 January 2014
151363	20140202012939-1398253	Board Thread:The Drax Cave/@comment-1398253-20140202012939	1667875	2014-02-02 T01:29:39Z	1398253	Digifiend	247{{{1}}}{{{1}}}{{{1}}} CzechOut Fixed. Errors like this typically just need to have the page republished. 04:39, 3 February 2014
151808	20140205175140-188432	Board Thread:The Drax Cave/@comment-188432-20140205175140	1669767	2014-02-05 T17:51:40Z	188432	CzechOut	1101{{{1}}} 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. 17:52, 7 February 2014 Edited 18:01 7 February 2014 CzechOut Thanks for the legwork there, Digifiend. Timeline is fixed. 16:06, 8 February 2014 Jacque1288 how do i add 22:05, 8 February 2014 SOTO {{tomato check}} is completely messed up when transcluded on my talk page, but somehow completely normal on the template page itself. 01:34, 9 February 2014 24.13.85.36 The picture of the event synthesizer is missing. http://tardis.wikia.com/wiki/Event_Synthesizer 01:34, 10 February 2014 Digifiend Anon, there was never a picture on that page. 21:48, 10 February 2014
153534	20140315090851-108.192.13.243	Board Thread:The Drax Cave/@comment-108.192.13.243-20140315090851	1681752	2014-03-15 T09:08:51Z	108.192.13.243	Anonymous	280{{{1}}} SOTO What browser are you using? 09:09, 15 March 2014 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.] 12:48, 15 March 2014 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. 13:05, 15 March 2014 CzechOut Hmmm, this appears to be a problem in Firefox for Windows, too. Odd. 13:24, 15 March 2014 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. 03:15, 16 March 2014 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. 03:16, 16 March 2014 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. 05:09, 16 March 2014 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. 01:08, 17 March 2014 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. . 04:37, 6 May 2014 CzechOut OH, and just to be clear, all pages that use this feature now work in FF — so the Master and other Time Lords have rotating images in all Wikia-supported browsers. 04:39, 6 May 2014
154468	20140405190038-2164182	Board Thread:The Drax Cave/@comment-2164182-20140405190038	1687741	2014-04-05 T19:00:38Z	2164182	TheMasterRace	258{{{1}}}{{{1}}} 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. 19:03, 6 April 2014 TheMasterRace Thank you for this 18:15, 7 April 2014 Digifiend I've heard lots of reports of apps no longer working after the upgrade too. It's a broken OS, pure and simple. 16:37, 8 April 2014
155509	20140507204335-188432	Board Thread:The Drax Cave/@comment-188432-20140507204335	1695451	2014-05-07 T20:43:35Z	188432	CzechOut	105{{{1}}}
155863	20140515152300-25566332	Board Thread:The Drax Cave/@comment-25566332-20140515152300	1698593	2014-05-15 T15:23:00Z	5791028	MystExplorer	236{{{1}}} 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. 16:11, 15 May 2014 MystExplorer I'm glad to know it's not just me. It seems the problem is with the page itself and not our accounts. 17:07, 15 May 2014 CzechOut Have you tried going to Special:Following and hitting the "x" next to Death to the Daleks!? 18:15, 15 May 2014 Shambala108 Yes, but some pages won't disappear, while others disappear until the next time I load the page. 18:18, 15 May 2014 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? 18:49, 15 May 2014 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. 20:59, 15 May 2014 MystExplorer Never mind! I found the toolbar and managed to unfollow the page. Thanks for your help. 21:02, 15 May 2014 Shambala108 Thanks for the hint, Slughorn42, it even works for deleted pages. 04:31, 16 May 2014 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. 13:51, 16 May 2014 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. 15:20, 16 May 2014 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. 17:28, 22 May 2014 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? 18:52, 22 May 2014 Shambala108 Yes it did have quotation marks, and the Earthshock one had an exclamation point. 19:02, 22 May 2014 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? 11:27, 29 June 2014
156099	20140521175428-98.163.235.120	Board Thread:The Drax Cave/@comment-98.163.235.120-20140521175428	1700888	2014-05-21 T17:54:28Z	98.163.235.120	Anonymous	343{{{1}}} 98.163.235.120 Never mind. I'm pretty sure I fixed it. 01:14, 22 May 2014 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. 14:29, 22 May 2014 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. 22:22, 22 May 2014 SOTO I'm not entirely clear on what the actual issue is here. What's going wrong? Details, please. 01:05, 23 May 2014 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. 01:10, 23 May 2014 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. 02:10, 23 May 2014 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. 02:22, 23 May 2014 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. 02:29, 23 May 2014 Edited 02:30 23 May 2014 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? 02:34, 23 May 2014 CzechOut Regrettably, I have to inform all users who like these list of <whatever> by age pages that such lists simply cannot be processed efficiently by the software available to us. Not only are page load times astronomically high, but they easily reach a length where they can't properly calculate age anymore. 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. 07:22, 23 May 2014
159767	20140819105227-1398253	Board Thread:The Drax Cave/@comment-1398253-20140819105227	1727515	2014-08-19 T10:52:27Z	1398253	Digifiend	608{{{1}}}{{{1}}} 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. 23:58, 19 August 2014 Digifiend Yeah, I did mean a null edit. Thanks for the explanation. 02:51, 21 August 2014
162024	20140925205904-188432	Board Thread:The Drax Cave/@comment-188432-20140925205904	1746169	2014-09-25 T20:59:04Z	188432	CzechOut	2101{{{1}}}{{{1}}} 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. 21:04, 28 September 2014 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. 01:54, 29 September 2014 DarthKnah The "there be spoilers here" message doesn't come up when you click on a thread in the howling if you use monobook. 01:49, 13 October 2014 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. 02:13, 13 October 2014 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. 01:45, 16 February 2015 CzechOut We're no longer actively developing Monobook, but thanks for the participation in the past. Monobook is currently used by less than .05% of FANDOM users, and even fewer than that here locally at Tardis. 04:12, 15 July 2017 Edited 04:13 15 July 2017
162037	20140926022327-1398253	Board Thread:The Drax Cave/@comment-1398253-20140926022327	1746328	2014-09-26 T02:23:28Z	1398253	Digifiend	506{{{1}}}
168028	20141227033529-1398253	Board Thread:The Drax Cave/@comment-1398253-20141227033529	1802456	2014-12-27 T03:35:30Z	1398253	Digifiend	766{{{1}}}{{{1}}} 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. 03:25, 2 January 2015 CzechOut This situation no longer applies. 04:20, 15 July 2017
178941	20150901151901-26949233	Board Thread:The Drax Cave/@comment-26949233-20150901151901	1924912	2015-09-01 T15:19:01Z	26949233	BadWolf77X	415{{{1}}}
194341	20160528224952-33410583	Board Thread:The Drax Cave/@comment-33410583-20160528224952	2039776	2016-05-28 T22:49:52Z	27668561	ThetaSigma23	502{{{1}}} Shambala108 Could you give a couple of examples of pages where that happened to you? 03:18, 29 May 2016
196789	20160804191742-188432	Board Thread:The Drax Cave/@comment-188432-20160804191742	2059992	2016-08-04 T19:17:42Z	188432	CzechOut	885{{{1}}}{{{1}}}{{{1}}} CzechOut I still see people setting "pages most relevant to this discussion", even as late as January 2017. Though the feature is still present in the Forum namespace, it does nothing anymore. 17:06, 29 January 2017
197716	20160901163101-188432	Board Thread:The Drax Cave/@comment-188432-20160901163101	2071390	2016-09-01 T16:31:01Z	188432	CzechOut	461{{{1}}} CzechOut This did indeed get resolved. 17:10, 29 January 2017
199086	20161006170233-20607870	Board Thread:The Drax Cave/@comment-20607870-20161006170233	2095308	2016-10-06 T17:02:33Z	20607870	DENCH-and-PALMER	286{{{1}}} DENCH-and-PALMER Also tags take ages to load and sometimes never do as well as category adding. 17:05, 6 October 2016 Shambala108 You will need to provide the browsers you've been using in order for someone to be able to help you. 18:36, 6 October 2016 DENCH-and-PALMER Google Chrome and Safari 18:48, 6 October 2016 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". 18:52, 6 October 2016 CzechOut Problem unique to the date of 6 October 2016. Any time you see the error message, "Our main datacenter is down, you are accessing our backup datacenter. We are working to fix the problem," you can be assured you're looking at a brief outage that typically will be resolved on the same day -- often within a few hours at most. 16:51, 29 January 2017
205631	20161206062929-68.146.233.86	Board Thread:The Drax Cave/@comment-68.146.233.86-20161206062929	2151316	2016-12-06 T06:29:29Z	68.146.233.86	Anonymous	387{{{1}}} DENCH-and-PALMER Logging in can get rid of it. Unfortunately I believe this is the only way. 07:54, 6 December 2016 SOTO Yes, make an account, and there is very minimal advertising on Fandom (Wikia). Certainly no Google surveys. 08:30, 6 December 2016 Edited 08:31 6 December 2016 Bwburke94 Perhaps you have fallen victim to adware? Check your antivirus. 00:16, 7 December 2016 CzechOut Original poster is describing an itinerant behavior that only affects logged-out users, and likely is no longer affecting even them. Fandom is constantly working to improve the ad experience, for both logged-in and logged-out users, as evidenced by several recent staff blogs at w:c:community. 16:48, 29 January 2017
207667	20161225150655-20607870	Board Thread:The Drax Cave/@comment-20607870-20161225150655	2166348	2016-12-25 T15:06:55Z	20607870	DENCH-and-PALMER	145{{{1}}}{{{1}}} SOTO It's just a long word. I don't think there's much we can do, and it's hardly much of an issue. That said, I'll look at it again. 18:39, 25 December 2016 Edited 18:39 25 December 2016
218755	20170612181751-188432	Board Thread:The Drax Cave/@comment-188432-20170612181751	2348858	2017-06-12 T18:17:51Z	188432	CzechOut	662{{{1}}}{{{1}}} 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. 20:26, 12 June 2017 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. 20:37, 12 June 2017 Edited 20:43 12 June 2017 Thefartydoctor I'm growing to like this new layout. I'm hoping it reaches the Welsh Wiki at some point too. Very exciting stuff. 02:53, 13 June 2017
237078	20180904180958-5791028	Board Thread:The Drax Cave/@comment-5791028-20180904180958	2544535	2018-09-04 T18:09:58Z	5791028	MystExplorer	178{{{1}}}{{{1}}} 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. 18:28, 4 September 2018
239079	20181014233023-1398253	Board Thread:The Drax Cave/@comment-1398253-20181014233023	2563219	2018-10-14 T23:30:23Z	1398253	Digifiend	299{{{1}}} Scrooge MacDuck Agreed. The same problem appears on the Old Forums archive, by the way. 17:27, 15 October 2018 Dmitriy Volfson It's still an issue, many navboxes have unreadable text! 16:24, 15 April 2019 Jack "BtR" Saxon I've been meaning to bring this up. I'm surprised it hasn't been fixed sooner. 17:28, 15 April 2019
240687	20181105102051-1398253	Board Thread:The Drax Cave/@comment-1398253-20181105102051	2577975	2018-11-05 T10:20:51Z	1398253	Digifiend	324{{{1}}}{{{1}}} Danniesen Are you sure it's not just a one-time error on your side of the screen? I mean, sometimes errors occur. 10:33, 5 November 2018 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. 15:34, 7 November 2018 Edited 15:49 7 November 2018 CzechOut In fact, I've gone ahead and moved the spoiler warning down to the part of the article that likely contains the most spoilers at the present time. And I've changed the spoiler warning itself to indicate that it's only covering a section — not the whole page. 16:05, 7 November 2018
240863	20181107161832-6032121	Board Thread:The Drax Cave/@comment-6032121-20181107161832	2579510	2018-11-07 T16:18:32Z	6032121	Scrooge MacDuck	1476{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}}{{{1}}} CzechOut This is actually a bug in the DPL extension. It's not just happening at Tardis, but on other wikis as well. It's going to require the attention of FANDOM's Engineering department. I've nudged the internal FANDOM ticket about it along, but I can't give you a solid ETA at this juncture. 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. 22:54, 7 November 2018
242804	20181214121018-33372618	Board Thread:The Drax Cave/@comment-33372618-20181214121018	2599258	2018-12-14 T12:10:19Z	33372618	Dr Von Wer	332{{{1}}}{{{1}}} Scrooge MacDuck Have you tried different browsers? 00:21, 15 December 2018 68.131.63.11 In order for someone to help you, you need to provide browser info, including version number. 00:25, 15 December 2018 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). 09:50, 15 December 2018 Scrooge MacDuck It's loading fine with Opera for me; you might want to try that. 22:05, 15 December 2018 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! 00:22, 17 December 2018 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. 08:32, 17 December 2018 Dr Von Wer It must have been temporary, now I can access the Visual Editor just fine. 16:08, 18 December 2018 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. 16:37, 18 December 2018 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. 17:04, 18 December 2018 Shambala108 Ah, ok, I misread. 17:16, 18 December 2018
249582	20190414161409-24922135	Board Thread:The Drax Cave/@comment-24922135-20190414161409	2709770	2019-04-14 T16:14:09Z	24922135	Aaronbill3	441{{{1}}} Shambala108 Fixed, thanks. 16:55, 14 April 2019
249604	20190415164401-5692737	Board Thread:The Drax Cave/@comment-5692737-20190415164401	2710150	2019-04-15 T16:44:02Z	5692737	Dmitriy Volfson	919{{{1}}} Shambala108 I'm in complete agreement with you. It's very difficult reading, much less editing, on this wiki. 02:15, 16 April 2019 Borisashton Glad somebody has brought this up; it's very jarring and I much prefer the old design. 10:06, 16 April 2019 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. 10:38, 16 April 2019
254279	20190728210415-1783865	Board Thread:The Drax Cave/@comment-1783865-20190728210415	2754739	2019-07-28 T21:04:16Z	1783865	Danniesen	245{{{1}}}{{{1}}}{{{1}}} Danniesen Somebody? 17:04, 30 July 2019 Scrooge MacDuck I suppose you might get some more interest in if you gave specific examples? 21:25, 30 July 2019 Danniesen For example for series 11 and the 2017 Xmas. 21:26, 30 July 2019 Shambala108 I'm not sure what you expect from this thread? If you know links are broken, then they can either be removed or changed if someone knows the correct sites. And just to note, it's easier for other users if you include links in your examples. That's general forum practice. 04:23, 31 July 2019
256947	20190912210712-6032121	Board Thread:The Drax Cave/@comment-6032121-20190912210712	2779216	2019-09-12 T21:07:12Z	6032121	Scrooge MacDuck	334 Danochy You should find your answer in the thread history. 21:12, 12 September 2019 Shambala108 It has been deleted, so not a crash or bug. 21:14, 12 September 2019 Scrooge MacDuck …thanks, but if so, why? 21:17, 12 September 2019 Edited 21:17 12 September 2019 Shambala108 It was deleted by User:CzechOut, so you would have to ask him, but most likely he will address it at some point. 21:19, 12 September 2019 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. 21:19, 12 September 2019
281689	20200820202907-28743561	Board Thread:The Drax Cave/@comment-28743561-20200820202907	2949448	2020-08-20 T20:29:08Z	28743561	LegoK9	1093{{{1}}}{{{1}}} NightmareofEden I feel the best way around this is to get more specific with our filenames. 23:45, 20 August 2020 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. 23:50, 20 August 2020 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. 23:55, 20 August 2020 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. 12:08, 22 August 2020 TheDarkBomber Ah, here's the rub: Thread:153478. Local images aren't supposed to be overwritten, yet they are. 22:32, 24 August 2020 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. 07:50, 25 August 2020 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. 14:17, 25 August 2020 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? 15:14, 25 August 2020 TheDarkBomber Yes. 15:21, 25 August 2020 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? 17:02, 25 August 2020 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. 21:27, 25 August 2020 Edited 21:27 25 August 2020 Najawin I have no strong feelings one way or the other. 21:46, 25 August 2020 CzechOut This feature makes the creation of pages about actors and other real life topics a lot easier. You just use the same filename of the image on Wikipedia, and there ya go. Indeed, there are a number of real life pages which would suddenly go image-less if we flipped the switch at this point. And it would be very difficult to find all of them quickly, since there's no mechanism that easily distinguishes between a WM and a Tardis image. 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. 23:11, 31 August 2020
286200	20201028212528-28743561	Board Thread:The Drax Cave/@comment-28743561-20201028212528	3033519	2020-10-28 T21:25:28Z	28743561	LegoK9	348 YYYYYY