Discussion/Things that are broken

From TheKolWiki
Jump to: navigation, search

This page is for issues with the wiki css/styles/layout/skin. Other discussions should remain on the Discussion page or on individual article/category talk pages.

Please, although everyone is free to express their own opinion, try to make it constructive.

Things that are broken

Bug Number Bug Description Reporter Possible Fix Dev Comment/Discussion Fixed?
1 (URGENT) External links no longer have an image displayed next to them

SomeStranger (t|c)

Either add #bodyContent to skin or remove the selector in css, but at the risk of side effects. - working on this one, not sure yet what causes it --Mag 17:53, 31 May 2006 (CDT)
  • This is broken because you don't have the image required in the skin.--SomeStranger (t|c) 19:53, 31 May 2006 (CDT)
    • Actually, from what I can see it's called from the CSS, the images is there too /thekolwiki/skins/monobook/external.png --Mag 15:56, 1 June 2006 (CDT)
      • The CSS only adds it to links that are in the #bodyContent div, which wraps all of the actual page content in the normal Monobook skin. The new coldfront-ey skin doesn't have a #bodyContent div, hence no link icons. This is probably the cause of a lot of the problems... a lot of the monobook CSS has a #bodyContent selector on it... Phlip 10:35, 27 June 2006 (CDT)
        • Actually, now that I look at it, the coldfront skin has a lot of objects which don't have IDs. For example, all the buttons that appear at the top of the page (article, discussion, edit, etc...) should have IDs so that they can be accessed easily.--SomeStranger (t|c) 18:20, 27 June 2006 (CDT)
2 The ==Title== tag seems to not give space below it when it is followed by a template (or the collections extension)

SomeStranger (t|c)

Give tables a default margin like 1em.
  • The headings are working exactly as they should, unfortunately it doesn't look nice. It's not particularly templates that but simply tables (and occasionally center tags) that don't look good after a heading. Normally, a p tag would be there and create the appropriate space but tables and center tags don't necessarily get a p tag. Giving tables a default margin should fix things. For any tables that we would preferably not have a margin we could set manually on that page.--Dehstil (t|c) 14:01, 15 July 2006 (CDT)
3 The paragraph across from/containing a floated image is single spaced, while other paragraphs are not, see paragraphs following floated pics in Penguin Mafia for an obvious examples or the features article on the front page. See pic of the featured article (with problem bracketted in red) here. - JRSiebz!

SomeStranger (t|c)

See the one about "line-height: 1.5em;", currently #20 below.
  • I figured out that the paragraph was not getting placed within a 'p' tag so it's spacing was different. I tweaked a few pages to force the wiki parser to put the text across from the pics in a 'p' by putting them on a new line. But all text not in 'p' tags seems not to be line-spaced appopriately (lines too close together). Things within 'center' tags are not placed in 'p' either but left as 'center's or 'div's and so are underspaced because they are not 'p's. These other elements should have their line-spacing increased to whatever it is set for 'p' tags.
4 When searching by entering text into the search box and pressing the Return key or clicking the Go button, text entered into the search box is prepended with a ':', then the search for a page by that name is executed on the finished text. Example: I enter "badger" into the search box, and the results page says "For query "badger" There is no page titled ":badger"." echan Do nothing.
  • This isn't a bug... that's normal behaviour. :Main Page for instance links to the same thing as Main Page... it just explicitly says there's no namespace involved ({{:Main Page}}, for instance, would include :Main Page, but {{Main Page}} would include Template:Main Page). I'm not sure why the search adds that colon, but it's explicitly added by the search... not a bug. Phlip 01:39, 3 July 2006 (CDT)
5 (minor) Requested classes Dehstil   a.stub{


 border-bottom:1px dotted #888685;
 font-size: 1.5em;
 margin:0.6em 0 0 0;
 padding:0 0 1px 0;


  • Here is a list of problems with the new skin. The URGENT problems are bolded. SUPER URGENT problems are bold and italicized. Before adding something to list please READ the current list to make sure that the bug you have found has not already been mentioned.
  1. Headings are not properly sized as they get smaller (===Title=== is far too large for that many equal signs).
  2. The "Mark as patrolled" message should be placed in the bottom right hand corner of pages and should have smaller text.
  3. Bullet lists have large amounts of space in between indents. - I think this is fixed, not 100% sure though --Mag 17:04, 1 June 2006 (CDT)
  4. Margin is too large under floated images, see circled portion of the same image.
  5. Wikipedia links are no longer a slightly different color than normal links.
    • were they ever differently colored? are you confusing visited and unvisited links?
    • They were indeed different.--Dehstil (T | C) 14:51, 12 June 2006 (CDT)
    • Wanted to throw in my two cents here - having slightly different colors for internal and interwiki links (link provided to show you the color difference the standard template provides) is immensely helpful when viewing a page, and especially when viewing its references. --Alpaca (T/C) 11:48, 1 August 2006 (CDT)
  6. In Safari, the logo looks veeeery weird. Screenshot here: Image:Bug screenshot trilusion.png (since the thumbnail thing doesn't work properly, it's just the link name.)
  7. There is a wiki user preference in Special:Preferences, "Misc" section, that says "Underline links: " and gives the choices of 'Always', 'Never', and 'Browser Default'. Whatver css these invoke is not working, or is being overridden. (Setting it to always underline links no longer works like it used to).
  8. The box which surrounds a page's categories, always has a larger top margin than bottom, meaning the space above the texxt is larger than the space under the text. They should be equal. I think it may not be margin or padding, but the fact that a <p> or a <br /> may be getting placed above the start of the text.
    • In the css #catlinks { ... margin-top: 1em; ... } should either be removed or reduced.
    • Changed it, better ?
    • I checked the html again, the #catlinks should be changed to .catlinks and then it should look right.
  9. The horixzontal rules created by using ---- are gigantic and don't match the header lines created with the header commands.
    • Those lines create a hr, here is the css code from the orig skin (modified with thisskins line colors) minus newline. hr { height: 1px; color: rgb(136, 134, 133); background-color: rgb(136, 134, 133); border: 0; margin: .2em 0 .2em 0; }
    • Perhaps these could be made to match whatever header bottoms are made to be, either dashed or dotted (see the next bug). --cor_nocae 02:00, 6 June 2006 (CDT)
  10. h2 bottom borders are in the css as "dotted". This renders as "solid" in FF, "dashed" in IE, "dashed" is the correct css term. But "dashed" borders are odd looking, prob should be type "solid" because the dashed lines look odd and are distracting.
  11. Visited links are now light green, many tables, divs have a light green backgound already, making reading them nearly impossible. Visited link and normal link colors should be light/darker versions of the same color. I assume one should just be a darker blue closer to black. Pages look spotted with 2 totally different link colors (especially when you visit a lot of pages). The frostly blue is already hard to read, see recent changes, all the light blue links on a white background, what a headache.
    • The frostly blue may make a decent visited link color, if the regular link color is a darker blue closer to the usual font color.
      • The new color (dark blue) is nearly indistinguishable from plain text, making it incredibly difficult to see links which you've followed at least once. --Quietust 20:57, 1 June 2006 (CDT)
        • Now visited links are fine, but UNVISITED links are impossible to distinguish from plain text. --Quietust 13:59, 2 June 2006 (CDT)
    • that better ?, if so move this point to the fixed list.. --Mag 16:51, 1 June 2006 (CDT)
    • A little better, but now the links are too close to the color of regular text, can't see them well in a paragraph. Why not make the text color black, and link color regular blue (#0000FF)? That will solve the problem of differentiating between unvisited links and regular text. For visited links, perhaps some greenish-blue color. That will look good with other colors in the current color scheme, and yet will differentiate well from unvisited links/regular text.
      • I think the main problem with the links is that they are no longer underlined. This not only makes them much harder to see, but goes against de facto Web standards -- everybody is used to links being underlined, so removing the underlines only causes confusion. -- Old Ned 19:33, 3 June 2006 (CDT)
        • You change link underlining in the preferences; don't hardcode underlining into the css (See #14).--Dehstil (T | C) 14:51, 12 June 2006 (CDT)
    • Also, visited dead links turn blue. I think they should be a different shade of red instead.--Dehstil (T | C) 14:51, 12 June 2006 (CDT)
      • Link colors are entirely unacceptable right now. I can barely see clickable links in my usual browser, and when using IE from a random computer earlier today was ENTIRELY unable to see links. This has to be fixed. Also, this discussion page is horribly unwieldy to edit and add comments. Argh. --jin 00:27, 13 June 2006 (CDT)
      • Should be ok now, please move item to fixed list unless color is still not right --Mag 14:49, 26 June 2006 (CDT)
      • The color is definitely still not right.
  12. Pop-ups that seem to come every few minutes, no matter what page I'm currently viewing.
    • Huh ?, we're not serving popup ads for the reason that we hate 'em, sounds more like you have a local spyware/adware issue there ;) --Mag 14:51, 26 June 2006 (CDT)
  13. In css&smaxage=18000 (line 1) Selector expected. Ruleset ignored due to bad selector. and Unexpected end of file while searching for closing } of invalid rule set. Entire contents of css&smaxage=18000 is &lt;Common.css&gt; I think it's one of those conditional css includes (attempting to list them below).
  14. On the main page, the squares are black and the text is red on IE7
    • According to the discussion in Talk:Main Page, this is apparently just in honor of 6/6/06 and will be gone tomorrow. -- Old Ned 00:00, 7 June 2006 (CDT).
  15. When searching, the text you searched for matching in the article no longer appears in red like it used to.
  16. The buttons that were on top of the edit pages no longer exist.
    • they are now on the left in 'personal tools
  17. Previewing is now under the edit box, when it should be over it like it used to.
  18. Not sure if this belongs here or not, but searching the wiki resulted in nothing. Also, I'm not sure if this is a general wiki problem or not, but here goes. Redirects to specific sections of articles end up linking to the start of the article instead. Normal links, such as Ascension#Normal Difficulty work fine, but when you put that in a redirect as in Softcore, it takes you to the beginning of the article instead. --Fryguy9 11:21, 16 June 2006 (CDT)
    • This is a problem with the MediaWiki software itself, not just this site. See this page. Phlip 03:06, 17 June 2006 (CDT)
  19. The horizontal line below ==headings== is far too close to the content below it - there should be a gap.
  20. Text<br />Text - the preceeding renders as two lines, but the lines are too close together when it is inside a td or a div. This is becuase the wiki places "normally entered text" in a p, but when in a div or td it doesn;t created a p. In the css the default includes p { ... line-height: 1.5em; ...}. The default spacing for generic tds and divs should be defined as td { line-height: 1.5em; } div { line-height: 1.5em; } up where the generic p {...} is defined for consistency. This is why some text by images and centerted text looked "singles spaced" or too close together, they are techincally in divs or tds. No p, line-height: 1.5em. --JRSiebz (|§|) 22:22, 14 July 2006 (CDT)
    • Actually, the standard MediaWiki stylesheet puts the "line-height: 1.5em" inside the #content { ... } section (which covers the entire page), as well as within p { ... }. --Quietust 22:39, 14 July 2006 (CDT)
    • Then there we go, the main.css has line-height: 1.5em; withint #content {...} and the maincf.css we use doesn't, but it should. Prob solved. Too bad nobody who conpulsively checks the wiki a lot has the ability to change it ;-) --JRSiebz (|§|) 22:57, 14 July 2006 (CDT)
      • I'm not sure, but possibly the problem stems from the inconsistancies of when <p> tags are added...
        will not have <p> tags added, but
        will. As a side-effect of how this is implemented,
        will have <p> tags around bar, but not foo or baz. The same presumably applies to <td>'s too... this is a "feature" of MediaWiki itself... nothing specific to this site. Phlip 11:44, 15 July 2006 (CDT)
        • Well mediawiki has always done that, We've already posted a fix for why tds and divs are not spaced the same as p tags above, having line-height: 1.5em; in #content { ... } would make sure that not only ps, but all tds, divs, and other elements in the main "content area" are spaced the same. --JRSiebz (|§|) 18:29, 20 July 2006 (CDT)
  21. Pages are not printer friendly in either firefox or msie.--Dehstil (t|c) 15:50, 30 July 2006 (CDT)
  22. Images such as botoom_g.jpg appear misaligned in msie, giving a cracking at the seams look.--Dehstil (t|c) 15:50, 30 July 2006 (CDT)
  23. Pages such as this have horrendously long horizontal scroll bars, instead of wrapping. (I blame the "code" box.) I use Safari. --Alpaca (T/C) 12:16, 1 August 2006 (CDT)
    • Pages with those boxes you get by putting a space at the beginning of the line also have this effect - if the content inside the box is long, I get a horizontal scrollbar. Also, this thing happens in both Safari and Firefox for the mac. --Alpaca (T/C) 09:57, 2 August 2006 (CDT)
    • Firefox on the PC also get a giant horizontal scrollbar for the little dotted-line boxes. --Alpaca (T/C) 09:57, 2 August 2006 (CDT)
    • All these issues have to do with the <pre> tag. I tried using the in-wiki CSS file to fix it, but it doesn't seem to work. --Alpaca (T/C) 11:42, 2 August 2006 (CDT)
    • Dunno if it was the CSS refreshing itself finally or some external fix or what, but these issues seem to have been resolved. --Alpaca (T/C) 17:19, 2 August 2006 (CDT)

<style type="text/css">/*<![CDATA[*/
@import "/thekolwiki/index.php?title=MediaWiki:Common.css&action=raw&ctype=text/css&smaxage=18000";
@import "/thekolwiki/index.php?title=MediaWiki:Monobook.css&action=raw&ctype=text/css&smaxage=18000";
@import "/thekolwiki/index.php?title=-&action=raw&gen=css&maxage=18000";

Is this causing any issues ?, because I think that's a mediawiki code thing caused by the cache rather then a skin or CSS problem.. --Mag 17:18, 1 June 2006 (CDT)

From the 'fixed' list below: "The old skin is not amongst the available preferences. - not going to happen". Explain to me why this will not happen. Is it so difficult for you to rename this new skin to something else, configure it to be the active skin for all users (registered or not), and then readd the original monobook skin so people who don't care if the wiki does or does not look the same as the rest of coldfront (like myself) can explicitly choose to use it? You still have all of the other default MediaWiki themes present and none of them look anything like Coldfront, so why are you unwilling to do the same with Monobook? --Quietust 14:07, 2 June 2006 (CDT)

  • I've already explained why, it's below the solved list.. --Mag 15:33, 2 June 2006 (CDT)
      • Actually, you just explained why you're not going to restore the wiki to the way it looked before, and that was fair enough - new users should see the wiki in a style that matches with Coldfront. You did not, however, explain why you're not going to allow existing users to manually select a skin that causes the wiki to look like a default MediaWiki installation (like Wikipedia), even though Chick, Cologne Blue, MySkin, Nostalgia, Simple, and Classic (the other skins supplied with MediaWiki by default) are still available to use. Do you have something in particular against the way Wikipedia looks? --Quietust 16:28, 2 June 2006 (CDT)
  • Minor: Give tables a 1em margin to make them looks prettier; in some cases (like when following a section header) it stands out.

Since we are changing things around anyways....

  • Enable User Style, by enabling the followings settings through LocalSettings.php:
$wgAllowUserJs  = true;
$wgAllowUserCss = true;
  • Enable ImageMagick for image resizing (more information here) - should work --Mag 15:49, 1 June 2006 (CDT)
  • Enable TeX support (math equations) (more information here) - This might be a bit harder to do, getting a nasty SQL error when enabling TeX support, going on my longer term todo list --Mag 15:49, 1 June 2006 (CDT)
    • Doesn't seem to work yet, when it does, the following will render:
Failed to parse (Missing <code>texvc</code> executable. Please see math/README to configure.):
  • Make the wiki's actual page bodies easier to read in smaller resolutions. For example, in a maximized browser at 1024x768, the left and right column take up fully one third of the screen, leaving only two thirds of the screen for the page body.
  • Install the ParserFunctions extension... I could easily see some use for #expr and #switch... especially seeing how much use {{if}} gets in various templates...
  • Make the search entry field a little wider than the buttons (both for visual symmetry and so that a horizontal scrollbar doesn't appear with the auto-fill drop-down menu (I'm sure I'm not the only one using that).
  • The Delete (next to Insert and End in your keyboard) doesn't work in the Search. Pressing enter instead of clicking Go also doesn't work.
    • Works for me... this is probably a browser issue, not a problem with the site.

Things that were broken but are now fixed

  1. User messages (editing someone else's talk page) are not very noticeable to the receiver. Possible fix below.
  2. I figure you realize this, but the little bar on the pages is now at the top of the page, overlapping the "Coldfront" logo.
  3. Images that are floated left or right take up their own line (are no longer inline/wrap with text), messing up the images in the featured articles and other pages such as Penguin Mafia.
  4. The edit box font color is Grey. You can't see grey.
  5. main.css (line 103) Expected ':' but found '='. Declaration dropped.
  6. The first paragraph after a floated image is single spaced, while other paragraphs are not, see paragraphs following floated pics in Penguin Mafia for an obvious example.
  7. The edit window has shrunk to be only half of the potential space
  8. In the differences pages it no longer highlights changes in red. (additions in green, removals in red)
  9. User messages (editing someone else's talk page) are not very noticeable to the receiver. Possible fix below.
  10. main.css (line 553) Error in parsing value for property 'position'. Declaration dropped.
  11. The pic on the top left corner always links the the page being currently viewerd rather than the wiki's home/main page.
  12. The search box on the left is longer than its container box.
  13. There is no search button. (this one was fixed with the latter one)
    • Actually, there is still no search button, just a go button. On the old wiki and in wikipedia there are two buttons, a "Go" button, and a "Search" button. The "Go" button attempts to go to the exact page name before searching, and the search button just searches.--SomeStranger (T | C) 17:58, 30 May 2006 (CDT) Fixed that for real now !! ;) --Mag 18:08, 30 May 2006 (CDT)
  14. There is no longer a "page hits" display at the bottom of each page
  15. main.css (line 791) Error in parsing value for property 'margin'. Declaration dropped. (line number subject to change)
  16. main.css (line 791) Error in parsing value for property 'padding'. Declaration dropped. (line number subject to change)
    • Line 791 is/was #siteNotice p { margin: none; padding: none; }
  17. The "Go" button, should be placed under the search box =)
  18. The <pre></pre> no longer create the cool box around the enclosed text. See below for a possible fix.
  19. the "go" button should have a "search" partner.
  20. Links used to be underlined on hover. There is a wiki user preference in Special:Preferences, "Misc" section, that says "Underline links: " and gives the choices of 'Always', 'Never', and 'Browser Default'. Whatver css these invoke is not working, or is being overridden. (I have it set to always and no links are underlined).
  21. Categories at the bottom of the page no longer have a pretty box around them. Without the box, they appear to be a part of the actual article.
  22. The entire wiki loads a lot slower (I think this is caused by the Eve online ad) - Let me know if it's better, I sticked it in it's own div section, shouldn't depend on the rest of the site anymore --Mag 17:49, 31 May 2006 (CDT)
  23. The <small></small> tags no longer work. (There seems to be an issue with small text in general, especially on History and diff pages) - This better ?, or should it be even smaller ? --Mag 17:52, 31 May 2006 (CDT) / That is good, fixing the link sizing next would be awesome. --SomeStranger (T | C) 17:59, 31 May 2006 (CDT)
  24. Changed the name of the stylesheet file in the source, it should solve some stylesheet issues people are encountering due caching.. --Mag 17:56, 31 May 2006 (CDT)
  25. Links are unresizable and appear the same size no matter what the situation. - should be fixed, I removed the hardcoded link sizes (else give me a page example where to look) --Mag 18:05, 31 May 2006 (CDT)
  26. The old skin is not amongst the available preferences. - not going to happen
  27. Link text in headings is not properly sized to match the font size of the unlinked text ( an example).
  28. Not sure if this is intentional, but areas that were once italicized in Recent Changes are no longer italicized. It's a minor issue, but it was easier to see before what was a comment and what was just the name of the page's subcategory (i.e., → Things that are broken - added signature) . (And can the text color also be a light grey)
  29. Visited links are no longer a different color than unvisited links. - made them red --Mag 16:15, 1 June 2006 (CDT)
  30. Link color is a very light blue, and can be hard to read, - I darkened the blue somewhat, better like this ? (TFT screen here doesn't have this problem) --Mag 16:15, 1 June 2006 (CDT)
  31. maincf.css (line 866) Expected declaration but found '.'. Skipped to next declaration. (needs a close brace before ".error {"
  32. maincf.css (line 870) Unexpected end of file while searching for closing } of declaration block. (caused by missing } above)
  33. Preformatted text is too small; nearly illegible. - set it to 120%, better like this ? --Mag 16:28, 1 June 2006 (CDT)
  34. The color of links that you've already cliked on are almost the same color as links that have no page. I was very frightend when I thought there was no main page. - picked a different color --Mag 16:28, 1 June 2006 (CDT)
  35. The edit box uses a non-fixed-width font. (Monospace would be prefereable)
  36. The Text in input types button and edit (box)es and dropdowns are in grey text, hard to read, prob should be black.
  37. There is no link to the TheKolWiki:General disclaimer page at the bottom of each article.
  38. The unpatrolled exclamation mark on the recent changes page should be red for more noticeability. (I think this is a sysop only thing) - I need the class/id tag for that one from the source from you, as much as I can do, I'm not setup as a sysop/admin in the wiki itself --Mag 16:44, 1 June 2006 (CDT)
    • Actually I think that Jinya made you one, but the class name is "unpatrolled".--SomeStranger (T | C) 16:48, 1 June 2006 (CDT)
    • Check if it works, I added the class --Mag 16:54, 1 June 2006 (CDT)
  39. links stand out too much when links are mid sentence.
  40. The personal ads on the left side of the page are no longer working....is this you, or is this under Jinya's control?
    • Jinya's, I disabled them yesterday because Jinya had a power outage, it pulls the ads from her server, and it was crashing the wiki.., I reenabled them.
  41. Template:Click is broken.
    • What is this exactly ?, got an example of how it should work ? --Mag 17:23, 1 June 2006 (CDT)
      • Oops, it appears it works again. It is a template which creates a div over an image so that you can make images link to pages other than the image page. It is used in all the ZAP templates.--SomeStranger (T | C) 17:26, 1 June 2006 (CDT)
  42. With Internet Explorer, much of the text on the left menu gets cut off, examples "Community portal" and "Log in / creatw account", etc.
  43. Titles of pages are displayed in a giant font, can we shrink it down a bit?
    • The layout in IE should be a lot nicer now, I added some better coding for font sizes --Mag 15:59, 2 June 2006 (CDT)
  44. I know I am being nitpicky, but can the disclaimers link at the bottom be on the same line as the "About the kol wiki" message?
    • Now is the time to be nitpicky, I'm tuning now anyways ;-) --Mag 16:02, 2 June 2006 (CDT)
  45. all boxes on the left do not have their right boundary border showing.
  46. The text in the edit box when editing page is now monospace (whoopie), but now is quite small, looks almost 8pt. Kinda squintworthy.
    • Made it a bit bigger, this better ?
  47. The autogenerated recent text messages still don't look quite right....(see below for possible fix).
  48. The search box on the left column is kind of small.
  49. Numbers on the Special:Templates page go off the border. Ordered (numbered) lists are right up against the left margin, large numbers run off the page. Here's the css to fix it (from the wiki default css) minus the linebreaks (so I could put it on one line: .ol { line-height: 1.5em; margin: .3em 0 0 3.2em; padding: 0; list-style-image: none; }
  50. Redirect pages no longer have the nice looking arrow graphic.
    • The image points to /thekolwiki/skins/common/images/redirectltr.png, which does not seem to exist. Wikipedia's image is: redirectltr.png
    • I created the image, move to list below if fixed --Mag 14:45, 26 June 2006 (CDT)
    • This can be fixed by creating MediaWiki:Common.css and setting it to something blank (though not completely blank or MediaWiki will refuse to save the page)... /* */ works best. Phlip 23:38, 9 June 2006 (CDT)

Stop asking for the old skin, it's not going to be put back. Let me elaborate a bit.
1: We're unifying the look and feel of the wiki with the Coldfront KoL site.
2: People are complaining about the right banner.., it's not there to piss you guys and gals of.., do you have ANY idea what the costs are in running a massive site like KoL coldfront and the Kol Wiki together ?, these 2 sites pull in an average of 19,000 visitors a day, serving around 500,000 pages.., that's about 5,5GB a day of data (the 350MB one day ascension videos and stuff like the Radio show MP3's not even included).., sum it up, and you have around 565,000 visitors a month pulling in 160GB of Wiki and KoL coldfront pages alone.., these sites are highly database driven, so there's 2 servers.., a powerful MySQL database server and a similair webserver.., then add in the costs of the T1 uplink on which most of the sites are running.. The banners are there to catch some of these costs. We're NOT serving annoying flash banners, popups, popunders, asking for donations, sex ads, etc, etc.. We NEED these ads to pay the bills.., we like to do this stuff, but we cannot throw $1000 on the table each month out of our own pockets to provide these sites..

We're not getting rich by doing this, we do this because we have fun doing it, and the advertising is a necesarry evil..

So please give CONSTRUCTIVE feedback like the bug reports from above.., we're very willing to work with everyone to make this work to everyone's wishes.., so give your input and I'll hammer on implementing new features and fixing bugs that everyone encounters.. --Mag 17:05, 31 May 2006 (CDT)

To aleviate the peoples problems with the advertisements on the right... could we move them under the player ads and the EVE online ad? They still get seen and it makes the sight look better? Just an idea.... --Ksumoe 19:59, 31 May 2006 (CDT)

I'd love to, but we have to display those ads above the 'fold' (i.e. they have to display for at least 50% on first page load, scrolling down to get to the ad is a nono), advertiser requirement --Mag 17:11, 1 June 2006 (CDT)

  • Not to be a stickler but you ARE serving flash ads. The base directory for on the bottom right is http://kol.coldfront.net/thekolwiki/skins/monobook/images/250x240_final.swf* and the ad on the right is often a flash ad. One is a cnbc microsoft videos ad with sound too. Another is an animated ms office flash ad http://m.2mdn.net/1092524/PID_85124_msx50563_lake_120x600_pare.swf?*.....etc. and a green national car rental flash animation. So saying you do not use annoying flash ads is untrue. They are often siezurific. I don't mind google ads, static banners or adsense words, but with anyhting that makes noise or blinks (even animated gifs), I adblock the iframe.--JRSiebz (|§|) 21:54, 31 May 2006 (CDT)

Yes I know, I meant the type of popup flash ads that take over your screen and are impossible to click away, we're trying very hard to filter out all the annoying ones, but we get all these served too.., it's not like we can select which banners to run, we can only select which we want to exclude.. --Mag 15:21, 1 June 2006 (CDT)

  • To comment on those, we try to remove the most annoying ads. If you find ones that are sieuzurific, just point them out to someone in charge. (Myself, Jinya or Frosty would all be good subjects for a mail regarding them.) --Dotts
  • That and the ads are hardcoded so wide that is impossible to view the wiki with a resolution of 1024x768 or 800x600 without a horizontal scrollbar.. if the ads were a little more dynamic or wrapped better, It;d be nice. --JRSiebz (|§|) 21:57, 31 May 2006 (CDT)

Stick it in the wishlist above.., I'll look if it's possible to make them more dynamic for lower resolutions.. --Mag 15:21, 1 June 2006 (CDT)

Here is a possible change for the recent link text colors (I am just pulling this stuff from the wiki monobook page, I have almost no knowledge of CSS): --SomeStranger (T | C) 17:02, 1 June 2006 (CDT)

/* Page history styling */
/* the auto-generated edit comments */
.autocomment { color: gray; }
#pagehistory span.user { 
    margin-left: 1.4em;
    margin-right: 0.4em;
#pagehistory span.minor { font-weight: bold; }
#pagehistory li { border: 1px solid White; }
#pagehistory li.selected { 
    border:1px dashed #aaaaaa;

Here is a fix for the missing space under the headers. Readding the code below to the stylesheet should fix it. --SomeStranger (T | C) 17:04, 30 May 2006 (CDT)

/* Some space under the headers in the content area */
#bodyContent h1, #bodyContent h2 { margin-bottom:0.6em; }
#bodyContent h3,
#bodyContent h4,
#bodyContent h5 {
    margin-bottom: 0.3em;
.firstHeading { margin-bottom:0.1em; }

Possible Fix for external links: (you need this image)--SomeStranger (T | C) 18:29, 31 May 2006 (CDT)

#bodyContent a[href ^="http://"],
#bodyContent a[href ^="gopher://"] {
    background: url(external.png) center right no-repeat;
    padding-right: 13px;

Oh, and you need to also have this (lets people turn off external link markings by using the class plainlinks):

/* this can be used in the content area to switch off
special external link styling */
#bodyContent .plainlinks a {
    background: none !important;
    padding: 0;

That's already in the CSS, the image also is there, that's why I'm still busy figuring it out :) --Mag 17:09, 1 June 2006 (CDT)

Drop the Skin Change Notice?

Can we drop the "The Kol Visual Wiki has had a skin change. Please hang with us while all bugs are sorted out. If you see anything not working correctly go over to the list of bugs and add the one you found." notice that's at the top of every page? Or do we still need it?

  • Sure. Anyone else object?--Dehstil (t|c) 23:34, 7 September 2006 (CDT)