All posts by Lamosq1027

<p>Thank you Andrew and Castelo for the help! The tabbers are behaving correctly now and purging pages does restore the original look of the gallery. </p>

<p>Thank you for the insight Jessepinky. I was able to fix it by looking more into the behavior of Template:T that you described. The original template creator seemed to have the styling itself within each Template:T, yielding a total redundancy where </p>

{{T|1=[styling of a particular table row]}}

<p>Removing Template:T so that the styling stood by itself, as well as removing the instances where the same variable appeared twice, fixed the problems with this confusing template. Ultimately, the solution wasn't that complicated--it was based on the basics of MediaWiki and reading up on some documentation. The way the original coder was trying to achieve the desired results was just confusing. </p><p>No, in all honesty a much easier template like the one you described could have totally been created. It certainly would have saved a lot of headache. I was just curious what was wrong with this template. I am pleased that it's solved now. Thank you both. </p>

<p>Ah, I see I misunderstood the process. You're right. After I looked at the documentation that I linked to more closely, the way to group headers with certain group/lists is by simply using the "n" of the group/list you want to start the header at, NOT to go numerically such as header1, header2, etc... </p>

{{navbox
...
 |header1 = 
 |group1 = 
 |list1 = 
 |group2 = 
 |list2 = 
 
 |header3 = note how the header # jumps to header3, skipping header2
 |state3 = 
 |group3 = 
 |list3 = 
}}

<p>Sure, and yes, that is what I said when I looked at it. </p>

1. It's supposed to display userboxes in a list fashion
2. I did not create the template, it was created long ago by another user. The only reason I am investigating this is that a user approached me about it wondering why it was acting so wonky. I don't think the page is used anywhere on any user pages, probably because it behaves so strangely.

<p>It is certainly capable of displaying the userboxes in a list fashion as demonstrated in the example, but there seems to be some code in there that is causing each userbox to be duplicated and normal text to be displayed at the top. Other than those rather glaring errors, the template seems to be equipped to do the job it was designed for </p>

<p>I do have group23 and list23 matched together. The problem is how I want all groups except group23 in header1, but instead they are being pushed to header2. </p><p>Perhaps it will be easier now that I've redone the template so there's less noise: I would like group1, group2, and group3 under header1, group4 to be under header2, and group5 to be under header3. I've constructed the code so it follows the documentation, but the output is not as desired. </p><p>Instead it seems like header(n) will only go with group(n) and list(n). How would I fix this? </p>

Can anyone help?

Anyone?

<p>Understood, thank you! </p>

<p>So there really isn't a workaround to get AWB to work on UCP other than what was suggested before? Is it something on Fandom's end that they just have to add support for (still waiting on custom JS for UCP), or will the AWB team have to push a patch before AWB can work on UCP wikis? </p>

<p>I saw this comment about someone who was able to get it working on a UCP wiki, but the instructions they give are for a bot account (not sure where they're getting the page "Special:BotPasswords", I can't seem to find it). Ignoring all the bot-related stuff, following their instructions on how to fix the login error seems to be identical to Tupka's suggestion. </p>

<p>Yup, I tried that. I still get a login error when I change it to custom -> https:// -> starwarssquadrons.fandom.com </p><p>Not sure what else could it be, when everything works fine as usual on Battlefront Wiki. </p>