User talk:GeneralNotability/spihelper/Archives/2020/October

Can't self-endorse

Could you take a look at Pfbeqmrgkoqrijuvvnafj, please? I'm trying to self-endorse, but it's not putting that option in the menu. -- RoySmith (talk) 02:36, 13 September 2020 (UTC)

RoySmith, saw that myself the other day. Should be fixed in the latest version. GeneralNotability (talk) 13:18, 25 September 2020 (UTC)

Moved report - "originally filed under this user" added to a different report

I moved a report from Yogeshkaushik19 to Theyogeshkaushik where there was already a report with the same date - Special:Permalink/980220172. The report was added as the second report but the "originally filed under this user" was added to the first report. Thanks, Cabayi (talk) 15:18, 25 September 2020 (UTC)

...and the edit summary points to a strange page - "Moving case section from w:en:Yogeshkaushik19, see page history for attribution". Cabayi (talk) 15:29, 25 September 2020 (UTC)

Cabayi, that one should be fixed - I was using the wrong value for "previous case page," Dreamy Jazz reported it earlier, I think it's fixed in my latest version. GeneralNotability (talk) 15:33, 25 September 2020 (UTC)

Cabayi, hmm, I could probably do the "originally filed under" transform before moving the section... GeneralNotability (talk) 15:30, 25 September 2020 (UTC)

Hide user names?

Under what circumstances would you want to use the "Hide usernames when requesting global locks" option? -- RoySmith (talk) 02:01, 3 October 2020 (UTC)

RoySmith, it's an option in the lock request and multilock template which, uh, hides the username. I assume it's for requesting locks for particularly offensive usernames, though I've never actually used it in an SPI. GeneralNotability (talk) 03:05, 3 October 2020 (UTC)

Feature request: Tagging already locked socks

I don't know if this is desired by others at SPI, but I think it is worthwhile that already globally locked accounts are automatically marked as such (the parameter locked being yes) when tagging their userpage. I haven't used the locked parameter much, but there is no way in the script to use it. Automatically tagging seems the best way to integrate it into the tool, as otherwise it requires checking the contributions page / CA of each user which you want to tag. I'm not too fussed if this isn't implemented, but can see it could be useful. Dreamy Jazz ^{talk to me | my contributions} 19:19, 20 September 2020 (UTC)

Dreamy Jazz, I can look into it, it just requires that I try interfacing with the centralauth API (not impossible, just haven't done it yet). GeneralNotability (talk) 16:35, 23 September 2020 (UTC)

For the record - implemented in 2.2.10. GeneralNotability (talk) 18:24, 5 October 2020 (UTC)

Incorrect formatting?

Could you take a look at this edit please? The clerknote should have been put on a new line. -- RoySmith (talk) 15:14, 12 October 2020 (UTC)

RoySmith, ha, I think I know exactly what went wrong there: it added the original casename (with newline), then case-insensitively matched the new casename and removed it (plus its newline). I'll put it on the to-do list, but this should be a pretty rare occurrence (only would happen when the case mis-capitalized the master's username) GeneralNotability (talk) 16:44, 12 October 2020 (UTC)

Chronological order?

It might not be worth the effort, but it would be cool if case moves put the sections in chronological order. See this example. -- RoySmith (talk) 14:43, 13 October 2020 (UTC)

Clerknotes in wrong section.

Could you look at this edit. My clerknote (and your previous one) got put in the wrong section. -- RoySmith (talk) 15:20, 13 October 2020 (UTC)

RoySmith, acknowledged, stupid complicated regexes. Testing a fix in -dev. GeneralNotability (talk) 16:15, 13 October 2020 (UTC)

GeneralNotability, Learned from hard battles and many scars: using regexes to parse things is a losing battle. -- RoySmith (talk) 17:11, 13 October 2020 (UTC)

Type change to watchBlockedUsers

As part of the just-released 2.2.11 update, watchBlockedUsers is now a boolean value. This fixes a behavior issue where blocked users would always get watched (because the block API expects a boolean and non-empty strings are treated as "true"). If you do not want to watch blocked users, set watchBlockedUsers: false in your config file. I have updated the config documentation to reflect this. Courtesy ping AmandaNP and L235 since you've both complained about this. GeneralNotability (talk) 13:30, 18 October 2020 (UTC)

Feature suggestion: Confirmation to refresh, close the tab or navigate away when there are unsaved changes using the tool

If you have unsaved changes in the edit window, you are asked to confirm if you want to abandon them when refreshing, closing a tab or navigating away. Perhaps if there are unsaved changes which are being made using the tool, then the same confirmation is shown when refreshing, closing a tab or navigating away. I would find this useful, as every so often I will accidentally click a link instead of opening it in a new tab whilst using the tool. I'm not sure what would be defined as "unsaved changes", but suggest it could be when any changes have been to the options in a menu (i.e. if the values are not the default values). Dreamy Jazz ^{talk to me | my contributions} 23:10, 20 October 2020 (UTC)

Probably easiest to just assume that if someone's got the "action" view up (the dynamically-populated second window) they should be prompted when navigating away. Testing in dev. GeneralNotability (talk) 18:47, 23 October 2020 (UTC)

Yeah. That's probably easier (and on reflection probably better as I occasionally don't change any setting in the "action" view/menu when using the tool). Thanks, Dreamy Jazz ^{talk to me | my contributions} 19:06, 23 October 2020 (UTC)