@Dianafa - That's a thread in the exclusive Community Council. Not many people will be able to access it.

There isn't much there, so you're not missing much.

Here's what it says:

thanks and sorry for the mess! :)

Apparently someone found a bug: w:c:Thread:914472. It seems to prevent the navigation tag from showing up in a horizontal group.

I'm not sure how staff planned to implement the navigation tag inside the horizontal group, but perhaps this is a solution:

WoW that was a long discussion.

After spending a couple of days re-writing my wikia’s main template I would like to suggest that the group layout=horizontal, tag be supplemented by something like a cells=4 to specify the maximum number of items that can appear before the next row is used.

At the moment there does not seem to be an upper limit so you may get 6 elements crammed on to a row that can hold, at most, 4 before becoming distorted. I know there is a workaround where you split the main group into headerless sub groups like so:

	<group layout="horizontal">
	<header>Item is used to unlock the adventure(s) for...</header>
	<data source="unlock1"><format>[[Image:{{{unlock1}}}.png|50px|link={{{unlock1}}}]]<br/>[[{{{unlock1}}}]]</format></data>
	<data source="unlock2"><format>[[Image:{{{unlock2}}}.png|50px|link={{{unlock2}}}]]<br/>[[{{{unlock2}}}]]</format></data>
	<data source="unlock3"><format>[[Image:{{{unlock3}}}.png|50px|link={{{unlock3}}}]]<br/>[[{{{unlock3}}}]]</format></data>
	</group>
	<group layout="horizontal" show="incomplete">
	<data source="unlock4"><format>[[Image:{{{unlock4}}}.png|50px|link={{{unlock4}}}]]<br/>[[{{{unlock4}}}]]</format></data>
	<data source="unlock5"><format>[[Image:{{{unlock5}}}.png|50px|link={{{unlock5}}}]]<br/>[[{{{unlock5}}}]]</format></data>
	<data source="unlock6"><format>[[Image:{{{unlock6}}}.png|50px|link={{{unlock6}}}]]<br/>[[{{{unlock6}}}]]</format></data>
	</group>

But this is not consistent with easy editing. Speaking of editing I hope something is done to make that editor more user friendly. I may be ok for new infoboxes with short lines but for editing pre-existing stuff it can be a bit of a hindrance. A the very least should be full width editing not leave huge margins to the side and add a scroll bar at the bottom just so you can see the left and right edges.

Fablanta (talk) 04:26, September 29, 2015 (UTC)

Thank you for the feedback Fablanta!

A the very least should be full width editing not leave huge margins to the side and add a scroll bar at the bottom just so you can see the left and right edges.

That's by design. I doubt wikia will change it because having long lines makes the code very untidy and harder to read, and this tends to dissuade people from doing so. It might not be a particular problem for people with huge screens, but it remains an issue of readability. That's one of the reasons why  templates are atrocious frankeinsteins, because there are no standards being enforced for them. 

When designing anything in a wikia you have to consider the fact that one day you'll go away and not be there to explain to the next editor what you did and why.It happens all the time with people afraid of meddling with templates because they may "break" something. 

As far as rows of groups in infoboxes, I do agree that there could be a setting to limit the number of rows in a group, but on the other hand it might make the code less readable for the next user. So perhaps this may force people to reduce the number of elements in any particular grouping. 

If you have several elements that belong in a common group but where many of them can be blank and you don't want them to show up, having a rowsize argument would be convenient. Using different groups you have to arbitrarily make the cut after, say, 3 possible elements, but if some are unspecified you can end up with rows of 1 or 2 or 3 elements breaking your table's symmetry. To be honest, I don't see how such a simple parameter would affect code readability; it would be similar to using colspan on a table.

P.S. How many posts before a thread gets split? My laptop is coughing up blood.

Colspans are not without their problems [1]. Personally, whenever possible I avoid them like the plague.  In fact, wikitables don't particularly handle colspans all that well (sorting doesn't work),  there are certain things it simply messes up, and doesn't display properly on mobile or even desktops for example. 

My point was that much like how gallery was designed, wikia has the opportunity to do the same for the infobox markup. Adding too much stuff, not keeping to certain guidelines, and allowing feature creep will make it worse than wikitext.

P.S. How many posts before a thread gets split? My laptop is coughing up blood.

Agreed. Some of us have moved to the w:c:infobox wiki to reduce the load here.

Hey folks! I am closing this thread, because it is very very very long and apparently the leading cause of Dessamator's computer health woes.

Please check us out over there!