For step 5) it should now be updated with ruff since that has been merged now.
for reference: https://github.com/Wikimedia-Suomi/PendingChangesBot-ng?tab=readme-ov-file#manual-commands

These are few resources that might be helpful for contributor to get a better idea about this topic:

Thanks a lot for reviewing my patch and pointing out the caveats. I see how it was too broad and could’ve caused side effects. I’ll be more careful to think about the wider impact of changes going forward. Also, your explanation about how MediaWiki treats | vs | and how the search key handler trims spaces was really helpful, it cleared up certain misconceptions I had about the same and inadvertently had used that in my patch. I tested your diff too and it worked great

Weekly Internship Report
Week 12: August 18 – August 22

Weekly Internship Report
Week 11: August 11 – August 15

Hi @Zache, The issue came from Cat-a-lot not handling empty sort keys ([[Category:Foo| ]] or [[Category:Foo|]]) correctly. During an edit, the code treated them as new categories instead of equivalent to a bare category ([[Category:Foo]]), which caused duplicates with the category name used as a sort key.

Weekly Internship Report
Week 10: August 4 – August 8

Weekly Internship Report
Week 9: July 28 - August 1

Weekly Internship Report
Week 8: July 21 – July 25

I've implemented two features, Category list state and UI open / minimized state using local storage:

• The manually set category list is remembered during the same session
• The ui remains open or closed during the same session based on user's preference.

Perfect! I’ll go ahead with the second version then, where both manual selections and search inputs update the stored category. That way it stays in sync with the search field too.

I’ve been implementing the category list persistence. Currently, the fallback call to updateCats(this.origin || 'Images') also sets catAlot_lastCategory, even if the user hasn’t interacted. This results in Cat-a-lot overriding the visible category on the next page load.

Weekly Internship Report
Week 7: July 14 - July 18

Thanks! For bug #1, I looked into it, it’s related to how sort keys are handled. I tested both versions and the consolidated version silently fails when sort keys are used, while the old version supported it. I’ll work on restoring that behavior.
For bug #2, agreed. Adding a confirmation when navigating away with selected files should be straightforward.

Weekly Internship Report
Week 6: July 7 – July 11

Weekly Internship Report
Week 5: June 30 – July 4

Thanks a lot for the detailed feedback and improvements! I completely agree, your fix makes the behavior much clearer and consistent. I’ve reviewed your version and it all looks great!

Hey, HotCat is now working on Data namespace pages. It now:

• Shows existing categories from mediawikiCategories
• Properly adds/removes categories without JSON errors
• Maintains valid JSON structure

You can test it by disabling HotCat from your preferences and adding following to your common.js :

mw.loader.load('//commons.wikimedia.org/w/index.php?title=User:Adiba_anjum3/HotCat.js&action=raw&ctype=text/javascript');

You can use the files from the following category for testing: Category:Cat-a-lot data namespace test pages
diff for reference

Thanks for testing, @Don-vip! That’s actually not a bug, I had temporarily lowered the manual file selection threshold for easier testing. It’s now been reset to 200, so the confirmation popup should only appear for genuinely large manual selections going forward. It should behave as expected now. :)
If you notice anything else, feel free to let me know!

Hi @Don-vip !
I'm tagging you here since you're a power user of Cat-a-lot, especially for editing large numbers of files. We think this feature could be particularly useful for your workflow. Would love to hear your thoughts or feedback when you have time.

Weekly Internship Report
Week 4: June 23 – June 27

Ah okay! That makes sense. Thanks, appreciate the quick response!

Weekly Internship Report
Week 3: June 16 – June 20

That's awesome! thank you so much for merging and deploying it. Super cool that it even made it to Mastodon, that made my day :)
Really glad I could contribute!

Weekly Internship Report
Week 2: June 9 – June 14

Hey @Zache, quick update, I decided to go with the second approach, removing the checkbox from the UI completely and just letting users turn Simulation Mode on/off directly in the preferences. This new setup applies the preference immediately on page load, so there’s no need to manually reload or delay UI elements. It’s cleaner and avoids the two-step toggle issue we had earlier.

Thanks for the feedback. I've been able to implement everything you suggested:

Hi, I've made a patch that solves this problem. The feature allows users to enable a simulation mode via a checkbox in the UI, which visually mimics category changes without performing real edits. The logic is integrated with Gadget-libAPI.js and respects the concurrency flow. I added the checkbox directly to the main dialog box so there would be minimal edits to the code files.

Weekly Internship Report
Week 1: June 2 - June 6

Hey! I made a patch that aims to make Cat-a-lot's settings work directly through the UI on other wikis like Beta Commons and enwiki, where the gadget modules aren't preloaded by default. It detects whether the script is running outside Commons and dynamically loads SettingsManager and SettingsUI from Commons if needed.

As per our conversation on slack, I wanted to give you an update on the resizing issue.

Thank you so much @Gopavasanth ! I’m incredibly excited to be part of the Outreachy program and grateful for this opportunity.
I’ll make sure to actively engage during the community bonding period, and I’ll refine my project timeline accordingly.
Looking forward to learning, contributing, and collaborating with the community! I’ll definitely reach out if I have any questions.

Hey @Zache, I've made significant progress on the year filter userscript and believe it now aligns well with the task requirements. Here's a summary of the current implementation:

Thanks for the green light and helpful notes! I’ll keep you posted on progress and reach out if I hit blockers.

Hi @Zache, I'd like to start working on this task. Based on the prompt, I’ll:

• Build a client-side user script for Wikimedia Commons that adds a year-filtering widget
• Use PetScan as the image source and QLever SPARQL for year-based filtering.
• Implement:
  • A slider for single-year/range selection.
  • Thumbnail grid rendering.
  • field to define a PetScan ID as a photo source
  • Caching to avoid redundant PetScan/SPARQL queries.

Hey, after testing several approaches,I'm happy to tell you that the Cat-a-lot preferences dialog on en.wikipedia finally works. Here's what worked:

Hey, Thanks for testing the code! I've implemented the sort key changes that you suggested. The copy/move operations now:

• Preserve non-empty sort keys exactly
• Don't include empty sort key if they don't exist in the source category also omit empty/undefined sort keys.

Hi, I've implemented your feedback on the Data namespace support for Cat-a-lot. Here's how I addressed each point:

Hey! I’ve added the implementation for Data namespace support in Cat-a-lot, incorporating your feedback. Here’s a brief overview of the changes:

• The gadget now correctly handles NS 486 pages while preserving sort keys exactly as provided.
• All operations (add/remove/copy/move) work as expected.
• Maintained all existing functionality for both JSON and wikitext pages.

Let me know if you’d like any adjustments or further details. Thanks!

Thanks for the feedback!

Hey, thanks for the feedback! I've:

You're absolutely right—thank you so much for pointing that out. I did notice during testing that the Codex dialog completely covers the page content, but I somehow missed connecting that behavior with how it would hinder Cat-a-lot’s file selection workflow.

Hey, thanks for taking the time to go through the document! I just wanted to clarify—I think you meant that Lookup can be used as an autocomplete component, rather than as a draggable/resizable UI elements?

Thank you for the detailed analysis. I completely agree with your findings, and I'd like to share some observations that I made after my last comment on this task:

Just to confirm my understanding:

Got it! Thanks for the guidance.

Thank you for sharing this practical example - it really helps illustrate the real-world importance of sort key.

Hi, thank you for your feedback and for clarifying the distinction between whitespace and null sort keys in wikitext. I appreciate your guidance on this nuanced behavior.

Hey! Everything works well now—great job!

Hey! I've been examining how Cat-a-lot handles sort keys in both wikitext and JSON pages and following are my key observations:

Hi @Zache , I’ve compiled the Codex feasibility study for Cat-a-lot, ensuring that it aligns with the task prompt. The study is quite detailed and explores:

Hey @Zache, I wanted to share my current progress on implementing JSON category support and thank you for your guidance. Your refactored version was extremely helpful in:

Hey, I've been working on fixing the Cat-a-lot preferences dialog for other wikis especially Wikipedia, but haven't been able to get it fully functional yet. Here's a summary of what I've tried:

1. Loading Dependencies from Commons
   • Attempted to load SettingsManager.js and SettingsUI.js directly from Commons
   • Scripts load successfully, and mw.libs.SettingsUI initializes, but the dialog's show() method hangs indefinitely

Hi @Tacsipacsi, thanks for the feedback! I’ve addressed both points:

• Updated the indentation to use tabs instead of spaces and ensured consistency with the existing code.
• Removed the unnecessary if ( filteredPages.length === 0 ) check at line 1135, as you pointed out.

Hey @Neyehh and @Samreet_kaur_sidhu! Somehow I had missed your messages on here, my apologies. I've made my translations according to the instructions provided in the task prompt and was almost done with them but I'd love it if we worked together.
Here's the link for the hind translation page.

Hi, thank you for your detailed review and the refactored version—it is incredibly helpful in clarifying the key improvements need. I appreciate the time you took to highlight areas for simplification and optimization.
I’ll revise the code based on your feedback.

Hey, Thank you for your thorough review! I’ve implemented the following changes based on your feedback:

Hi @Zache, I wanted to share the current progress on the Codex feasibility study for Cat-a-lot. Here’s the link to the document. While it’s still a work in progress and quite scattered, I’ve covered key aspects such as integrating Codex UI elements, testing compatibility across skins, and identifying initial challenges. I've Also come up with a basic userscript that I utilized for testing across various skins.

Thanks a lot! Testing on sandbox pages is indeed safer and better.

A fix has been proposed in subtask T390252. Please visit it to find the testing procedure and all other related info.

My only concern is that, at the moment, both buttons seem to lead to the same outcome—protected files remain unedited, while all other files are edited.

Hey everyone! Since there is no existing translation for hindi language, I'll start working on it. If someone wants to collaborate, please inform, so that we can work on the same document.
Looking forward to working together!

Oops! My bad. I'll upload it again

Okay! Thanks a lot for the feedback. I'll make the changes you suggested.

Hey @Ademola, Great effort! The UI of the dialog box looks pretty good. I've tested the changes on my end and these are the things I've observed:

• The dialog box correctly appears and displays the appropriate message when we try to edit a protected file using cat-a-lot.
• You have provided 2 buttons on the dialog box, namely - "ignore and continue" and "stop all editing"
  • When I press the "ignore and continue" button, all the other files except the protected one get edited and appropriate message is displayed for the protected file. This is the correct and expected outcome.
  • When I press the "stop all editing" button, I expected all the editing to stop (even for the correct files), However what happens is that editing only stops for the protected files but it continues for all other files.
    • The cause for this issue can be understood from the screenshot i've attached. You can see that even when the user has not pressed any of the buttons, all the other files in the background already appear to have been edited. What should've happened instead is that all the other edits should be paused until user presses either of the buttons.
    • If this was the intended functionality then i think the text on the button needs to be changed to depict that appropriately.

One request: Please list this task in the main Cat-a-lot task for Outreachy 30 so that it’s easy for everyone to find it.

Hey! I'd like to explore the feasibility of using Codex in cat-a-lot. Even if Codex in gadgets isn’t fully ready yet, it’s valuable to understand its current status, how it should be used, and whether it supports legacy skins like Timeless and Monobook. Since Cat-a-lot needs to support legacy skins, this will be a key factor in determining if Codex is a viable option. I'll document my findings on a user page as I go. Thanks!

Hi @Zache, I'm excited to share that I've successfully implemented JSON Data namespace support for Cat-a-lot! After thorough testing, all operations now work correctly for both wikitext and JSON content model pages.

I saw this task in passing and tried to run the hello world user script and successfully got it working! Here are the exact steps I followed:

Hi @Zache ,
I'm happy to share that the Cat-a-lot settings functionality is now working correctly on Beta Commons!
Changes Made

1. The original code relied on mw.loader.using to load dependencies but did not handle cases where these dependencies were missing (e.g., when loaded as a user script). I added a fallback mechanism to dynamically load the required scripts (SettingsManager.js and SettingsUI.js) from the wiki if they aren’t available via mw.loader and used $.getScript to fetch and inject these scripts directly when the gadget loader fails.
2. Split the logic into two parts:
   • Dependency Loading: Handled in manageSettings with fallbacks.
   • Dialog Creation and Settings Handling: Deferred to _manageSettings only after confirming dependencies are loaded.

Hey, thank you for the detailed feedback! I’ve started restructuring the code as you suggested, focusing first on editCategories() to ensure the editing logic works reliably before handling namespace detection. Here’s my current approach:

I’ve been working on fixing the Cat-a-lot settings functionality in Beta Commons, and I wanted to share my progress so far. Here’s what I’ve done and the current status: