No problem, it happens every so often so I'm used to fixing it. Just make sure that theres a newline after the </noinclude>, otherwise when mediawiki parses that line it doesn't think the content after it is at the start of the line and therefore doesn't consider it a proper header. Maybe worth submitting a bug report for Twinkle if that happens often. Aidan9382(talk)15:49, 9 October 2023 (UTC)[reply]
Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
New Page Patrol is currently struggling to keep up with the influx of new articles. We could use a few extra hands on deck if you think you can help.
Reviewing/patrolling a page doesn't take much time but it requires a good understanding of Wikipedia policies and guidelines; Wikipedia needs experienced users to perform this task and there are precious few with the appropriate skills. Even a couple reviews a day can make a huge difference.
Kindly read the tutorial before making your decision (if it looks daunting, don't worry, it basically boils down to checking CSD, notability, and title). If this looks like something that you can do, please consider joining us.
If you would like to join the project and help out, please see the granting conditions. You can apply for the user-right HERE.
If you have questions, please feel free to drop a message at the reviewer's discussion board.
Wow, I never would have expected someone to fix that within a day of me pointing out it was busted. That's really brilliant work -- I owe you one! jp×g🗯️14:22, 24 December 2023 (UTC)[reply]
No problem. I had done a significant overhaul to the module a while back, so I was subscribed by email to the talk page to make sure nothing immediately crumbled without someone to fix it, which was the main reason I caught it so early (I should really go clear up my watchlist so I don't miss stuff there). Aidan9382(talk)14:39, 24 December 2023 (UTC)[reply]
Hi Aidan9382, I was wondering if you could help. A while ago I came across an issue with Template:CFB Team Depth Chart were scripts have been converting the hyphen used in one of its parameters (|DScheme=) to an endash, which causes the template to break as it's only expecting a hyphen. Is it possible to change the template so it accepts either a hyphen or an endash? My knowledge of such technical matters is still rather limited. -- LCU ActivelyDisinterested«@» °∆t° 23:54, 26 December 2023 (UTC)[reply]
Sure. I've gone ahead and added a string replace to every occurance of DScheme so it sees an endash as a hyphen, which should fix any currently broken cases. Aidan9382(talk)07:08, 27 December 2023 (UTC)[reply]
Hello! I saw you changed some settings on the archive bot i had put in place on Talk:Brett Cooper (commentator) (Here). For reference and for the future I was hoping when you have time, if you could explain what I should do differently on the next occasion I impose a bot as such on another talk page. Or should i just refer to the exact edit you made? Thanks! Elvisisalive95 (talk) 14:07, 31 January 2024 (UTC)[reply]
Sure. The only reason I had come across the page in the first place was because the original |archive= target was incorrect (the namespace was wrong and there was a space after the colon), which lands the page in a hidden tracking category. The reason I changed the parameters around a lot is because normally, in article talkspace, archives are done as incrementing "/Archive N" archives instead of one constant static archive for the sake of page size. For a version which does this, you can see the example given in the documentation at User:Lowercase sigmabot III/Archive HowTo § Example 2: Incremental archives. You can also scroll down a bit from there for a general explanation of what each parameter does. Hopefully that answers your question well enough. Aidan9382(talk)17:40, 31 January 2024 (UTC)[reply]
Thank you for taking the time to explain this to me, it makes sense & I appreciate the help! Here’s a freshly baked cookie!
No problem, it happens quite often and it isn't the biggest issue (the bot won't archive if it isn't a subpage of the current page barring a special condition, so it's not like anything's gonna suddenly break from having a bad value). Aidan9382(talk)18:51, 4 March 2024 (UTC)[reply]
Aidan9382-Bot's task "Monitoring page moves" failed to run per the configuration specified at Wikipedia:Bot activity monitor/Configurations. Detected only 0 edits in the last 13 hours, whereas at least 1 was expected. If/when the issue is fixed, please change the section title (e.g. append " - Fixed") or remove this section completely. When that is done, this notice will be reposted if the bot task is still broken or is re-broken. If your bot is behaving as expected, then you may want to modify the task configuration instead. Or to unsubscribe from bot failure notifications, remove the |notify= parameter from the {{/task}} template. Thanks! – SDZeroBot (talk) 13:20, 7 August 2024 (UTC)[reply]
Note: Apparently a redirect loop is causing pageids to just... not exist? as part of the query info. I can't rectify the page loop either since both pages seem to have lost history. This might mean I lose a few pages in the upcoming logs, which isn't great. Depends how fast I can implement some sort of fix here. Aidan9382(talk)13:58, 7 August 2024 (UTC)[reply]
The issue for the page in specific causing problems is now fixed, so the next script run will work (probably), but there really should be some sort of failsafe on the bot one way or another for this weird case (not yet sure how that'll be handled though). Will leave this section here instead of removing it as a note-to-self. Aidan9382(talk)21:56, 7 August 2024 (UTC)[reply]
Aidan9382-Bot's task "Monitoring page moves" failed to run per the configuration specified at Wikipedia:Bot activity monitor/Configurations. Detected only 0 edits in the last 13 hours, whereas at least 1 was expected. If/when the issue is fixed, please change the section title (e.g. append " - Fixed") or remove this section completely. When that is done, this notice will be reposted if the bot task is still broken or is re-broken. If your bot is behaving as expected, then you may want to modify the task configuration instead. Or to unsubscribe from bot failure notifications, remove the |notify= parameter from the {{/task}} template. Thanks! – SDZeroBot (talk) 01:20, 21 August 2024 (UTC)[reply]
Hi Aidan, I'm trying to find out whether a template is embedded inside another template. For example I want to know if {{WikiProject Biography}} lies inside {{WikiProject banner shell}}. This means I need to work out where the closing braces for the banner shell template are, and extract this stuff:
{{WikiProject banner shell|
STUFF
}}
(Note: STUFF may also contain closing braces). Then in STUFF I will look for something like \{\{%s*WikiProject Biography and if it's not there then I will assume it is outside the banner shell. Can you help me with this please? — Martin (MSGJ · talk) 21:51, 7 September 2024 (UTC)[reply]
Actually there may be false positives with this method, so instead I should probably check if WikiProject Biography occurs before the start of
One trick I learned from Trappist is to first hide/collapse all non-WPBS templates (search for "__0P3N__" in [1][2][3] for examples), then the only 2 remaining sets of curly brackets should be WPBS's (assuming no typos/unbalanced brackets, and no dup WPBSs).
The next problem is the redirect problem. That is, how to distinguish each of the ~1100 WikiProjects from each of their ~6000 redirects. Cewbot and others have certainly made that problem a lot smaller by standardizing many millions of WikiProject template calls, so maybe it's not a big deal after all. I'd be prepared for a good fraction of false positives though - #Rs inside WPBS masquerading as being outside, if they can't be found. ~Tom.Reding (talk ⋅dgaf)11:38, 8 September 2024 (UTC)[reply]
I don't understand 0P3N - is that some kind of metadata? In this case we only have the raw wikitext and I am not planning to preprocess it as I suspect it would affect performance significantly. I can't think of any way to detect redirects, but as you say these have mostly been replaced now — Martin (MSGJ · talk) 07:57, 16 September 2024 (UTC)[reply]
0P3N is just a string of your choice to identify opening & closing braces in case you want to restore them later; no preprocessing happening. %b{} ftw though! ~Tom.Reding (talk ⋅dgaf)17:03, 19 September 2024 (UTC)[reply]
@MSGJ: apologies for the lack of reply, been a bit in-and-out in terms of doing wikipedia stuff (waiting for burnout to pass mostly). Is this still an issue? If it is, is this being checked from the perspective of the banner shell or the banner and what information do you already have? Aidan9382(talk)23:28, 14 September 2024 (UTC)[reply]
It is being checked from the banner, so I know the name of the template will in most cases be {{WikiProkect PROJECT}}. I am trying to detect if this is inside the banner shell or not. Unless you can think of a better way to do this? — Martin (MSGJ · talk) 07:48, 16 September 2024 (UTC)[reply]
If the main question is how to find where the banner shell lies on the page, the approach that comes to mind is finding all templates on the page and then check the names until you find the shell, which gets you its content, and from which you could work out its position (though how exactly doesn't immediately come to mind without me literally writing the code for it). I'd recommend searching for the banner's position and checking if it's explicitly outside of the shell, since in the event the banner call is a redirect you don't detect, you under-flag (an unrecognised redirect outside the shell is not reported) instead of over-flag (reported to be outside the shell even though its inside the shell, just with an unrecognised name). Hopefully that answers the question? Aidan9382(talk)19:57, 16 September 2024 (UTC)[reply]
Yes, under-flagging is what I meant in my 21:53 comment. But what I really need help with is the regex. Specifically, how to detect where the closing braces of the banner shell template — Martin (MSGJ · talk) 20:38, 16 September 2024 (UTC)[reply]
Some quick testing seems to look fine. One minor note is that, due to how lua %b matching works, you will only grab top-level templates. In the case where the banner shell was a parameter of a different template for whatever reason, it wouldn't get picked up, and you'd need something like what Module:Template parameter value#L-10 does to pick it up. Aidan9382(talk)08:41, 20 September 2024 (UTC)[reply]
