FANDOM


This talk page is for discussing changes to or problems with the Infobox template.
  • Be polite
  • Assume good faith
  • Be welcoming

Wow wiki's version Edit

I think the template used on wowwiki look better (yay for darktable!) and easily allows for even more customization (headers as well as labels and specific style parameters) than this one does. But that's just my opinion. Osetc 21:52, 2 January 2009 (UTC)

Incompatability with Wikipedia version Edit

The documentation should make it clear this is incompatible with the Wikipedia template:Infobox used in many articles imported/copied from Wikipedia. So many uses visit central trying to get infobox and other templates to work in wikipedia articles, due to the different parameters used for the basic inputs of row labels and data items (ignoring the additional more sophisticated functions of the wikipedia version that makes it over complex for beginners). - {{SUBST:Nosubst|user:BulldozerD11/sig}} 21:35, November 29, 2010 (UTC)

Personally, I believe this template should just be replaced with a simplified version of Wikipedia's infobox. I'd love to know what the original author was thinking when they decided on the parameter names this one uses. =P ダイノガイ千?!? · Talk⇒Dinoguy1000 21:45, November 29, 2010 (UTC)
Template:Infobox WP was created due to this incompatibility; it just calls this template and translates the parameter names. Just changing the parameters would make the infobox incompatible with templates that transclude it, although here only one half-finished template does. We could do internal parameters, or whatever {{{1|{{{2|}}} }}} is called…, that does seem to me to be the best option. --Yoshord 00:14, December 2, 2010 (UTC)
At this point, of course, I would not advocate dropping support for the original parameter names (ultimately, we would probably never be able to do that), but we could convert all the infoboxes here to use the WP parameter names and undocument the "original" names. ダイノガイ千?!? · Talk⇒Dinoguy1000 04:44, December 2, 2010 (UTC)

Dynamic Row Count Edit

What do i need to do on my wikia site to allow for the InfoBox template to not be statically assigned a set number of rows?
I know in the past Wiki 1.6-1.10, it was pretty much a hard code setup but with 1.11 or roughly around then, there was an abstract/generic way of doing the iteration with the loops, but it obviously required a loop counter mechamism which i am not quite to the level of with my developing ;)
Goldbishop 23:17, January 17, 2012 (UTC)

ColorEdit

Is there any way I can change the background color? Ninjaroy (talk) 23:41, May 24, 2013 (UTC)

You'll have to change it in your MediaWiki:Common.css or MediaWiki:Wikia.css file (or wherever else you've put the infobox CSS at). ディノ千?!? · ☎ Dinoguy1000 23:59, May 24, 2013 (UTC)
How do i do that? Ninjaroy (talk) 00:50, May 25, 2013 (UTC)
Can you link me to the infobox you're wanting to customize? ディノ千?!? · ☎ Dinoguy1000 01:08, May 25, 2013 (UTC)
http://code-breaker-fanon.wikia.com/wiki/Template%3AInfobox1.
Okay, I would suggest moving that back to "Template:Infobox" and restoring the original code. After that, you can change the infobox's appearance by modifying the .infobox styles in MediaWiki:Common.css. To change the background color specifically, change background-color: #f9f9f9; to something else - for instance, to make it red, change it to background-color: #800;. ディノ千?!? · ☎ Dinoguy1000 01:32, May 25, 2013 (UTC)
But I want your infobox, not the normal one. Ninjaroy (talk) 01:35, May 25, 2013 (UTC)
Okay, recopy our infobox over to your wiki, and then copy the following CSS to your MediaWiki:Common.css page:
/***** CSS placed here will be applied to all skins on the entire site. *****/
 
/* Mark redirects in Special:Allpages and Special:Watchlist */
.allpagesredirect {
   font-style: italic;
}
.allpagesredirect:after {
   color: #808080; content: " (redirect)"
}
.watchlistredir {
   font-style: italic;
}
 
/* Giving headers and TOC a little extra space */
h2 {
   margin-top: 20px;
}
.toc {
   margin-top: 20px;
}
 
/* Infobox template style */
.infobox {
    border: 1px solid #aaaaaa;
    background-color: #f9f9f9;
    color: black;
    margin-bottom: 0.5em;
    margin-left: 1em;
    padding: 0.2em;
    float: right;
    clear: right;
}
.infobox td,
.infobox th {
    vertical-align: top;
}
.infobox caption {
    font-size: larger;
    margin-left: inherit;
}
.infobox.bordered {
    border-collapse: collapse;
}
.infobox.bordered td,
.infobox.bordered th {
    border: 1px solid #aaaaaa;
}
.infobox.bordered .borderless td,
.infobox.bordered .borderless th {
    border: 0;
}
 
/* Forum formatting (by -Algorithm & -Splaka) */
.forumheader {
   border: 1px solid #aaa;
   margin-top: 1em;
   padding: 12px;
}
.forumlist td.forum_edited a {
   color: black;
   text-decoration: none;
}
.forumlist td.forum_title a {
   padding-left: 20px;
}
.forumlist td.forum_title a.forum_new {
   font-weight: bold;
   background: url(/images/4/4e/Forum_new.gif) center left no-repeat;
   padding-left: 20px;
}
.forumlist td.forum_title a.forum_new:visited {
   font-weight: normal;
   background: none;
   padding-left: 20px;
}
.forumlist th.forum_title {
   padding-left: 20px;
}
 
/* Recent changes byte indicators */
.mw-plusminus-pos {
   color: #006500;
}
.mw-plusminus-neg {
   color: #8B0000;
}
 
/* Image frame fix */
div.tright, div.tleft {
   border: 1px solid silver;
}
 
div.thumbinner {
   background: inherit;
   border: none;
   color: inherit;
}
#article div.thumb {
   color:inherit;
}
 
/* === Babel === */
 
div.babelbox {
   float: right;
   margin-left: 1em;
   margin-bottom: 0.5em;
   width: 246px;
   border: 1px solid #99B3FF;
   padding: 2px 0 2px 0;
}
.lang-blockN, .lang-block0, .lang-block1, .lang-block2, .lang-block3 {
   margin: 2px 4px 2px 4px; /* t, l, b, r */
   width:238px;
   border-collapse: collapse;
}
td.lang-codeN, td.lang-code0, td.lang-code1, td.lang-code2, td.lang-code3 {
   text-align:center;
   font-size:14pt;
   width:45px;
   height:45px;
}
td.lang-descriptionN, td.lang-description0, td.lang-description1,
td.lang-description2, td.lang-description3 {
  font-size:8pt;
  padding:4pt;
  line-height:1.25em;
}
 
.lang-block0 {
   border:1px solid #FFB3B3;
}
td.lang-code0 {
  background-color: #FFB3B3;
  color: black;
}
td.lang-description0 {
  background-color: #FFE0E8;
  color: black;
}
 
.lang-block1,  .lang-block2, .lang-block3  {
   border:1px solid #99B3FF;
}
td.lang-code1, td.lang-code2, td.lang-code3 {
  background-color: #99B3FF;
  color: black;
}
td.lang-description1,  td.lang-description2, td.lang-description3 {
  background-color: #E0E8FF;
  color: black;
}
 
.lang-blockN {
   border:1px solid #6EF7A7;
}
td.lang-codeN {
  background-color: #6EF7A7;
  color: black;
}
td.lang-descriptionN {
  background-color: #C5FCDC;
  color: black;
}
After you do that, you'll have to bypass your browser cache to see the new styles. From there, you should be able to customize your infobox as I mentioned in my last reply. ディノ千?!? · ☎ Dinoguy1000 03:06, May 25, 2013 (UTC)

I can't get any of these templates to work on my profile i copied and it just shows the tex not the actual info box RickGrimes Sheriff (talk) 22:03, August 4, 2015 (UTC)

Portability Edit

I have made a portable and modular infobox at Modular infobox. What is the reason for maintaining this modular infobox when portable infoboxes are capable of the same modularity? (I believe they weren't always so capable, but they now are.) And why is Modular infobox marked for deletion? Is a modular infobox required to NOT be portable?

The fact of the matter is that people are going to want single-use infoboxes. You can tell them all you want to use the same dedicated infobox for all their characters, and for all their locations, but in the end, some aren't going to listen, and they're going to damn well find an infobox and it will probably be non-portable garbage. Furthermore, for some purposes like silly irreverent userpage infoboxes, a single-use infobox is more appropriate anyway.

I propose that "Modular infobox" be moved to this location, and the existing infobox at this location discarded. We can very happily include a disclaimer advising the user of the limits of correct usage of such an infobox. But we have to have one. Henstepl (talk) 10:48, December 31, 2017 (UTC)

No more uses Edit

All uses of Infobox have been cleared. The fate of this template and its related template Modular infobox need to be discussed. Lady Aleena (talk) 10:38, January 7, 2018 (UTC)

Community content is available under CC-BY-SA unless otherwise noted.