I II III HB AAB TFA Hale
Legobot Legobot II Legobot III Hockeybot ArticleAlertbot TFA Protector HaleBot


Bot wars edit

@Legoktm: Your bot's been reverting itself twice daily since January 2023, and before that daily since December 2021, on Talk:Crusades/Archive index (history). Similarly, it's been reverting itself daily since November 2021 and more sporadically before that since March 2017 on User talk:Safety Cap/Archives/Destination (history). —Cryptic 17:57, 26 October 2023 (UTC)Reply

Thanks, it was GIGO. Should be fixed. Legoktm (talk) 05:00, 29 December 2023 (UTC)Reply

Wikipedia:Requests for comment/Wikipedia policies and guidelines edit

I edited Wikipedia:Requests for comment/Wikipedia policies and guidelines inserting {{bots|deny=Legobot}} because you keep messing up <small>...</small> tags. Go ahead and remove the bots template, but please stop messing up the <small>...</small> tags. (Also attn: WOSlinker) —Anomalocaris (talk) 07:13, 10 December 2023 (UTC)Reply

(talk page watcher) @Anomalocaris, WOSlinker, and Zinnober9: When editing WP:RFC/POLICY, did you not see the message
  • This list is updated by Legobot; your edits will be overwritten if you edit this page.
The proper thing to do is to fix the problem at its source, which in this case must be in Wikipedia talk:Biographies of living persons, because that is where Legobot is copying text from. See WP:RFC#Statement should be neutral and brief: this says Legobot will copy the markup of your statement (from the end of the {{rfc}} tag through the first timestamp) to the list of active RfCs, if it is sufficiently brief; a long statement will fail to be copied. For technical reasons, statements may not contain ... complex formatting, although these may be added after the initial statement (i.e., after the first timestamp).; earlier on, note [1] says The "statement" is the part that is located between the {{rfc}} tag (exclusive) and the first valid timestamp (inclusive), and which is copied by bot to various pages.
This means that not only was Legobot working as designed, it is a bad idea to follow the {{rfc}} tag with notes that are not part of the RfC statement itself, expecially if a template like {{block indent}} and a HTML tag like <small> are both still open when the next timestamp occurs. Such notes must always be after the timestamp that closes the statement. The problem was introduced by Novo Tape (talk · contribs) with this edit, and the fix is very simple. --Redrose64 🌹 (talk) 10:52, 10 December 2023 (UTC)Reply
Thank you for the explanation. I will admit that while I'm well versed in many other syntax errors, I am not well versed in RFCs, so was unaware of this limitation with their notation. I was not aware of the offending statement being in the wrong sequential location, so thought instead that Legobot was adding a line break within the rfc statement (line breaks surprisingly break a lot of tags). While I did see the "Legobot will overwrite" message, I would have thought that the nobot tag would have had the higher power, and only added it/readded it so that we could have a little timeout from the bot reinstating the issue while we fully figured out what was going on. This issue reminds me again that I really hate transcluded errors since they act all fine and innocent on the original page, but cry bloody hell on other pages. Sorry for the error in my understanding, and thank you for enlightening us on this issue and for the simple solution. Zinnober9 (talk) 18:03, 10 December 2023 (UTC)Reply
@Zinnober9: Where it says "your edits will be overwritten if you edit this page", it really means it. The whole page is built by Legobot, based upon a set of data tables held off-wiki plus the current text of any page that transcludes {{rfc}}. Essentially, Legobot runs once an hour and builds fresh copies of each and every RfC listing page, which it saves, regardless of whatever happens to be on the page at the time. It therefore ignores {{nobots}} and any other content that it didn't add itself on its previous run. Whilst this may seem to be a violation of WP:OWN, it's quite normal for bot-built reports, of which there are many. --Redrose64 🌹 (talk) 23:04, 10 December 2023 (UTC)Reply

Uncategorized RfC subpages edit

The bot won't let me add categories to the category-based subpages of Wikipedia:Requests for comment, such as Wikipedia:Requests for comment/Unsorted, which are currently uncategorized. –LaundryPizza03 (d) 20:22, 1 January 2024 (UTC)Reply

(talk page watcher) @LaundryPizza03: Did you read the editnotice, particularly the red bit? Why do you want to categorise them anyway? --Redrose64 🦌 (talk) 20:28, 1 January 2024 (UTC)Reply
You can probably add the categories to {{rfclistintro}} instead. * Pppery * it has begun... 20:56, 1 January 2024 (UTC)Reply

Some baklava for you! edit

  Wom Juanese1990 (talk) 15:28, 28 January 2024 (UTC)Reply

RFC topic area requested feature edit

Apologies if this has already been answered. If I add a topic area from {{rfc}} Legobot will add that RfC to the respective topic page. If I remove a topic area Legobot apparently won't remove it from that topic page. Could Legobot do this in the future? Schierbecker (talk) 23:17, 30 January 2024 (UTC)Reply

Mysterious non-RfCs edit

Legoktm, what happened here and here? These three rfcids do not occur anywhere in Template:Rfc, nor indeed anywhere other than the two pages in those diffs. I've seen something similar before, at least five years ago, due to somebody putting an {{RfC}} tag inside commented text. --Redrose64 🌹 (talk) 18:33, 11 February 2024 (UTC)Reply

Legoktm, more than a day later, and Legobot is still issuing three bogus rfcids every hour, see page history. Is there a log somewhere that records which pages these rfcids were intended for? If I can find that out, I can examine them to see what might be triggering this action. --Redrose64 🌹 (talk) 23:40, 12 February 2024 (UTC)Reply
Yikes. Looking into it now, unfortunately the database is just as useless as the wiki page:
MariaDB [s51043__legobot]> select * from rfc where rfc_id="8C10D2D";
+---------+--------------+---------------+-------------+---------------+
| rfc_id  | rfc_page     | rfc_contacted | rfc_expired | rfc_timestamp |
+---------+--------------+---------------+-------------+---------------+
| 8C10D2D | Template:Rfc |             0 |           0 |             0 |
+---------+--------------+---------------+-------------+---------------+
1 row in set (0.010 sec)
Legoktm (talk) 03:35, 16 February 2024 (UTC)Reply
Maybe this will fix it. I think this might be related to the self-transclusion change also brought up here. Legoktm (talk) 03:43, 16 February 2024 (UTC)Reply
OK, seems to have done the trick. Thanks for noticing :)
@Redrose64: Also, just as a heads up, as part of moving Legobot over to the new Toolforge infrastructure, I switched it from PHP 7.3 to 7.4. I don't think it'll cause any issues, but if you notice anything weird, it could be related. Legoktm (talk) 04:04, 16 February 2024 (UTC)Reply
Appears to have worked,   Thank you --Redrose64 🌹 (talk) 21:29, 16 February 2024 (UTC)Reply