Forum:Infoboxes and Template:Bp
If this thread's title doesn't specify it's spoilery, don't bring any up.
czechout<staff /> ☎ ✍ <span style="">02:15: Thu 15 Mar 2012
czechout<staff /> ☎ ✍ <span style="">19:11: Wed 21 Mar 2012
Conversation between Tybort and CzechOut
Are you carefully overseeing the navigation templates yourself, or is it fine if I do tweaks where I see fit? -- Tybort (talk page) 20:28, March 9, 2012 (UTC)
- Or is the bot still in the middle of things as well? -- Tybort (talk page) 20:39, March 9, 2012 (UTC)
- Yeah, the bot and I are fully engaged. The problems of bulletised lists in infobox has been an unexpected "joy". It's probably best for the weekeend if you just send me notes on problems you find, instead of attempting to fix them yourself. The bot is having to make several individualised runs over the stories, which means you might trip up the bot if you decide to focus your editing on stories. I'm not saying "don't edit story pages", though. If you can improve the pages by adding new content, fine. But don't focus your energies on the infoboxes, and don't edit several infoboxes in a row, until Monday.
czechout<staff /> ☎ ✍ <span style="">23:54: Fri 09 Mar 2012
- Yeah, the bot and I are fully engaged. The problems of bulletised lists in infobox has been an unexpected "joy". It's probably best for the weekeend if you just send me notes on problems you find, instead of attempting to fix them yourself. The bot is having to make several individualised runs over the stories, which means you might trip up the bot if you decide to focus your editing on stories. I'm not saying "don't edit story pages", though. If you can improve the pages by adding new content, fine. But don't focus your energies on the infoboxes, and don't edit several infoboxes in a row, until Monday.
Yeah, don't bother manually deleting {{bp}}. I'm just going to change what it does. A lot more efficient. Might take me a bit of time to get around to it, but it's a simple fix.
czechout<staff /> ☎ ✍ <span style="">07:07: Sun 11 Mar 2012
- Either way, I assume that the fix won't cover for <li> and <ul>, or <br>, right? -- Tybort (talk page) 14:55, March 11, 2012 (UTC)
- {{bp}} has been neutered now. As for raw HTML, it's easily removed through a couple of bot processes. I'm behind schedule, so it's probably now more likes next week when I'll have all this done. But the bot runs were refined yesterday and seem to be working well enough.
czechout<staff /> ☎ ✍ <span style="">18:29: Sun 11 Mar 2012
- {{bp}} has been neutered now. As for raw HTML, it's easily removed through a couple of bot processes. I'm behind schedule, so it's probably now more likes next week when I'll have all this done. But the bot runs were refined yesterday and seem to be working well enough.
- Hmmmm, sorry if that was vague. The "above code you mentioned" is "raw HTML". So, yes, I'll take care of fixing all things about the infoboxes. Please move on to other things except the infoboxes for a while, if you would. Keep notifying me if you see strange things, of course. But I'll take care of both the {{bp}} and HTML ways of creating bulleted lists. It'll be fine :)
czechout<staff /> ☎ ✍ <span style="">19:26: Sun 11 Mar 2012
- Hmmmm, sorry if that was vague. The "above code you mentioned" is "raw HTML". So, yes, I'll take care of fixing all things about the infoboxes. Please move on to other things except the infoboxes for a while, if you would. Keep notifying me if you see strange things, of course. But I'll take care of both the {{bp}} and HTML ways of creating bulleted lists. It'll be fine :)
Gousha's question to CzechOut
I saw your note on Tybort's page asking to hold off on making changes for a day or two. At the very least, the bot should be putting breaks in here instead of just removing the list tags. I hope there's an easy solution to this, since so many lines are being smashed together.
- Should we leave the smashed-together listings for the bot to handle, or should we manually separate them?
- Similarly, should we start removing the BP uses, or let the bot handle those?
- How should we separate these lines, now and later? a break only, a comma only, a comma and a break, or something else? -- Gousha talk to me 03:04, March 11, 2012 (UTC)
- There is indeed a simple bot fix for the phenomenon of "smashed together links", but it takes place on a second bot run. I thought I was caught up on doing the rounds, but I may be mistaken. Please give examples of where you're still seeing the "smash up".
- The {{bp}} thing is put on ice for a few days. It will eventually be cleared by either a bot run or by simply changing the nature of what {{bp}} does. Please don't make any attempts at manual cleaning, as there's a very simple fix that needn't waste any of your valuable editing time.
czechout<staff /> ☎ ✍ <span style="">03:14: Sun 11 Mar 2012
- The prime examples I saw were pages like Dalek Emperor, Arcturan and Axos, and fixes I already applied to Transolar disc and a few lesser ones. It appears the issue may already be in hand, as I see the changes done to Cyber-Wars points at just using a comma between items. However, even there the changes aren't complete. (see the result box). -- Gousha talk to me 05:37, March 11, 2012 (UTC)
- Thanks for the bug report! It made me adopt a more sophisticated post-bullet-removing approach. You should now find in category:species a lot fewer cases of "the squashing problem". I didn't quite realise there were so many different variations on what happened to an infobox after removing the HTML. THus, I had to build a "proper" user fix that handled all cases simultaneously, rather than just doing a couple of runs. IF you detect more problems, please let me know.
czechout<staff /> ☎ ✍ <span style="">06:37: Sun 11 Mar 2012
- Thanks for the bug report! It made me adopt a more sophisticated post-bullet-removing approach. You should now find in category:species a lot fewer cases of "the squashing problem". I didn't quite realise there were so many different variations on what happened to an infobox after removing the HTML. THus, I had to build a "proper" user fix that handled all cases simultaneously, rather than just doing a couple of runs. IF you detect more problems, please let me know.