User talk:OneTwoThreeFall

Welcome
Hi, welcome to ! Thanks for your edit to the Talk:NoImageLightbox page.

Please leave a message on my talk page if I can help with anything! Cqm (talk) 10:44, July 30, 2014 (UTC)

Custom Status Tags
Do you think you could add a way to add status tags for Mediawiki:Status/code.js so that users could use the script other than for user pages? I looked into it, but it seems like to me it's impractical for page loading sake, but I know a lot of wikis that prefer to have statuses on the page or elsewhere. Also, could you see about adding around/off-site which will identify whether the user is on Wikia or not (whether they are on the specified wiki or another)? For example, if I edit the community Wikia then my status here would be around. ~ Curiouscrab (talk) 00:42, March 14, 2016 (UTC)


 * 1) I'm not too sure what you mean by this… Do you mean, to show a user's status on a page other than that user's own page?
 * 2) Sorry to say, this wouldn't be possible/practical. You'd have to either look up the user's recent contributions individually for every wiki on Wikia, or have the   permission (i.e. be a member of either vstf/staff/helper groups).
 * - OneTwoThreeFall talk 02:27, March 14, 2016 (UTC)

~ Curiouscrab (talk) 22:02, March 14, 2016 (UTC)
 * I mean create custom status tags that would be used such as USERNAME and would in turn replace the text with offline or online or whatever the status is. This would require that for each use, the API would be used, but I don't see a reason for pages to use status tags more than once and so this could be possible for reasonable wikis.


 * Ah, I see... a little refactoring, and done! You can use   to get USERNAME's status on any page.  By the way, might be a good idea for you to get a doc page up for the script.  - OneTwoThreeFall talk 13:22, March 18, 2016 (UTC)

~ Curiouscrab (talk) 20:50, March 18, 2016 (UTC)
 * Thanks. I was going to work on the doc page soon. I was trying to set up a new way that the script and doc are displayed in my common.js.

Log Events
Log events aren't considered contributions with Mediawiki API. Can you incorporate log events into the Status script? The API has them accessible by ~ Curiouscrab (talk) 23:49, March 20, 2016 (UTC)


 * That should be fairly easy - just add it to the current API call. Have you had a go at it yourself, though?  Don't wanna do all the work for you!  - OneTwoThreeFall talk 13:43, March 23, 2016 (UTC)

~ Curiouscrab (talk) 21:13, March 23, 2016 (UTC)
 * I haven't had too much experience with get and post requests yet. I'm still learning the tricks with jQuery.


 * Fair enough, done! logevents doesn't seem to like IP addresses, however, so the script now checks for, and won't run on, anon user pages.  - OneTwoThreeFall talk 09:24, March 24, 2016 (UTC)

ChatSend
Hello, I was wondering if there was a way to change the alignment for the send button that way it will align with the other chat hacks better http://i.imgur.com/dp7wbtL.png Roranoa Drake II (talk)


 * Hi there! I've added a fix for this in the code, and it should be approved by Wikia within a few days.  With the fix, it'll appear at the left of the 'Clear' button for people using ChatHacks.  Thank you for letting me know about the issue!  - OneTwoThreeFall talk 16:32, July 30, 2016 (UTC)

re: PurgeBlogs
(split thread) I don't mind the difference. Rappy copied over that PurgeBlogs script to act as a basic example of the ImportJS script, but given that users could still be importing the old script, it was decided to leave both. I don't really maintain the script, it's pretty basic so anyone can go and update it. :) --Sajuuk 08:50, September 1, 2016 (UTC)

RE: jQuery Ready Callback
There is little to no difference with the code you moved from  to   - moving the code to where you did is inefficient as it's guaranteed to assign the   object even when it shouldn't be. Also they both have  functionality. Ozank Cx (talk) 08:55, September 2, 2016 (UTC)


 * > Also they both have  functionality.
 * doesn't wait for DOM ready - it's immediately run.


 * I agree it's inefficient, though. I was only merging the two versions of PurgeBlogs together, not making any functional changes.  Personally, I'd set a variable such as , rather than search for all   elements, as that's much more inefficient than setting a single object that may not be needed.  - OneTwoThreeFall talk 09:05, September 2, 2016 (UTC)

RE: Recent edits to Pseudo-Vector
(moved) - OneTwoThreeFall talk 14:01, October 3, 2016 (UTC)

ExtendedNavigation borders
Hi there! Could you please revert these edits that you made? The orange borders do not match the themes of my wikias at all. The code worked fine and the boxes looked great before, so why change it?

King Dragonhoff


 * I assume you're referring to Boom Beach Wiki? See my message at Talk:ExtendedNavigation#Border colour for detail, but basically I made a change in both CSS and JS, and JS doesn't go live immediately. In this case, Wikia's server-side cache for JavaScript on your wiki is being a little too persistent, meaning your wiki is running an older revision of the JS.
 * Re. the boxes looked great before: once the cache for your wiki has cleared, you should notice the border colour of the extended menus will be exactly the same as the main menu, whereas before it was a slightly different colour.
 * I'm sorry about the issue though! Give it a few days, and it should clear by itself. - OneTwoThreeFall talk 17:42, November 4, 2016 (UTC)


 * Alright. Thank you.
 * King Dragonhoff


 * Seems the cache has cleared now on Boom Beach and Clash Royale wikis, at least for me. Let me know if there's still issues! - OneTwoThreeFall talk 09:42, November 5, 2016 (UTC)

RE: Infobox formatting
(split thread) I guess this is how you reply to talkage messages? Anyways, I was switching to the &lt;br /> format because a list format makes all the elements space out from the list bullets. This is what I mean. Also, I've seen many other scripts use the same format, I think. How does the new infobox style require them to be a list? I don't see the parameter being parsed or anything...

Cheers! -- Cube - shaped   garbage can  09:47, November 9, 2016 (UTC)


 * Ah, I see. I thought it would be easier for a Lua module to parse it if it was in the &lt;br /> format instead but I guess it doesn't matter much (since Lua doesn't have a string.split anyways). I guess I'll use that format in future. -- Cube - shaped   garbage can  14:35, November 9, 2016 (UTC)

CodeLoad Assistance
Hey, I was wondering if you could provide a little extra assistance with the CodeLoad script. So, I initially set up my definitions and got those approved before I submitted changes to Common.js, Wikia.js, and Snow.js. Well, all scripts work through CodeLoad except my snow. I had  in the preferences but removed it thinking that was the problem (that change isn't approved nor does it appear to be the problem). I did remove the parameters from the snow script itself when I added them to the definitions. Any ideas on what I did wrong? DEmersonJMFM 21:34, December 27, 2016 (UTC)


 * You've done nothing wrong, just I didn't notice you were using an older version of the SnowStorm script!
 * Due to the way the older version is written, you'll have to use . On Snow.js, undoing the diff that removed the default parameters, then adding the below snippet before the line   should allow it to work.


 * - OneTwoThreeFall talk 07:56, December 28, 2016 (UTC)


 * Okay, working in the right direction, thank you (the script works in test mode). So  is now not needed for the script in the definitions, correct?


 * Another issue I am still seeing is that a parameter for AutoEditDropdown set in the definitions as   isn't overrode when I click the checkbox in the user preferences (I couldn't check the snow's or AjaxRC's parameters because one was broken and the other is ignored in favor of global preferences). Left scratching my head again. DEmersonJMFM 16:02, December 28, 2016 (UTC)


 * You're welcome! That's right, now that the script's using, there's no need for   to be set.
 * Looks like AutoEditDropdown is using a slightly different way to set its preferences; rather than set them individually, it keeps all its preferences inside one object named . I've now added support for this in CodeLoad via the   parameter, so adding that parameter like below should let it work:


 * Thanks for the feedback, by the way - I don't know of any other wikis (besides LyricWiki, for where it was originally written) using the script, so knowing how you're using it (and what's lacking) is handy! - OneTwoThreeFall talk 15:10, December 29, 2016 (UTC)


 * Everything's been approved yet it still doesn't work. Maybe there's an issue with the AutoEditDropdown script? DEmersonJMFM 19:23, December 30, 2016 (UTC)


 * is being set in the wiki's MediaWiki:Common.js page. Existing values won't be overwritten by CodeLoad, just to be safe.
 * You can check this in your browser's developer tools ( F12 in most browsers), as CodeLoad will show a warning in the console when this occurs. - OneTwoThreeFall talk 08:50, December 31, 2016 (UTC)


 * I guess for scripts that are written with preferences in this way it's all or none set in the definitions. DEmersonJMFM 14:36, December 31, 2016 (UTC)


 * Afraid so. I had a quick look at implementing it like that, but allowing the script to modify existing objects in a generic + safe way seems overly complex for my liking. It's worth noting that  is only meant to cover basic configurations; for anything more complex,   is available. - OneTwoThreeFall talk 16:04, December 31, 2016 (UTC)

DisplayClock
That's really weird. I edited the page last night to add  to fix that reference error. It must not have saved. Thanks for fixing it. Rappy 18:04, January 18, 2017 (UTC)
 * No problem! - OneTwoThreeFall talk 18:22, January 18, 2017 (UTC)

Language list
Hi! Thanks for creating it. But can you move to doc page to Template:L/doc? I merged your template with mine, as now mine is unuseful. ~ [  Q uəntum ii ð the Wise  ]  12:22, February 12, 2017 (UTC)
 * Hi, and thanks! Rather than move it, might it be better to keep the more descriptive name, and instead make Template:L a redirect? - OneTwoThreeFall talk 12:29, February 12, 2017 (UTC)
 * OK, as you wish. ~ [  Q uəntum ii ð the Wise  ]  12:32, February 12, 2017 (UTC)
 * Maybe existing calls of Template:L should be updated first, then it can be made a redirect? Currently, it looks a bit odd on pages using multiple calls of the L template (e.g. UsernameAvailability). (edit: it works properly for both old and new syntax now) - OneTwoThreeFall talk 12:38, February 12, 2017 (UTC)
 * By the way, I suggested it yet to other user today, maybe we could create a page with a table with codes and local&English language names so we don't have to add languages names in long JS/CSS codes? I already have a list of languages from CreateNewWiki page + few more. We could add a link to it in the infoboxes. ~ [  Q uəntum ii ð the Wise  ]  12:59, February 12, 2017 (UTC)
 * Similar to List of ISO 639-1 codes page on Wikipedia? A page like that could be a handy reference! - OneTwoThreeFall talk 13:12, February 12, 2017 (UTC)
 * I created a basic page to show. But... Maybe it should be called "Languages"? See ~ [  Q uəntum ii ð the Wise  ]  13:28, February 12, 2017 (UTC)
 * Nice work - looks good to me! "Language codes" seems like a suitable name, but I can rename it if you prefer. - OneTwoThreeFall talk 15:05, February 12, 2017 (UTC)
 * Please rename if you can. The page contains more than only codes. ~ [  Q uəntum ii ð the Wise  ]  15:16, February 12, 2017 (UTC)

Uh, sorry to butt in, but do we really need that page? I don't know which category would it fall under, and I'm pretty sure language codes are listed somewhere else... -- Cube - shaped   garbage can  15:19, February 12, 2017 (UTC)
 * I think it could have some use, though I don't know if there is a language list elsewhere. I figured it would go in Category:Guides, as it seems to have other informational pages. - OneTwoThreeFall talk 15:24, February 12, 2017 (UTC)
 * There's a similar page on WLB wiki, but it doesn't have Notes section, which here can be useful. ~ [  Q uəntum ii ð the Wise  ]  15:34, February 12, 2017 (UTC)

Enable personal JS template
I agreed with your last response on this thread and threw together a quick advisory template here. I styled it like the ImportArticles template, but I figured it could be added to the top of documentation pages much like the Personal template.

I'm not sure if this is what you had in mind, so feel free to improve upon it in whatever way you think best. CoH  <font color="#000">☎ 23:01, February 16, 2017 (UTC)


 * I was thinking more like the banner message that appears on MediaWiki namespace script pages when custom JavaScript is not enabled, though something like that would have to be done server-side, of course.
 * Not sure if a separate template is best for this (it seems a bit big for such a note), but perhaps adding a reminder to Script Install / Script Install/ImportJS could help people out? - OneTwoThreeFall talk 17:42, February 17, 2017 (UTC)


 * Ah, I think I understand what you meant now. I've never tried editing JS files on wikis without the review extension enabled, so I've never seen this banner. <font color="#cc0b13">CoH  <font color="#000">☎ 19:02, February 17, 2017 (UTC)

RE: Regarding 'Test pages' category
Ah, I see. Yeah, I guess we could try to find some other use for that category in future. And thanks! -- Cube - shaped   garbage can  05:55, February 26, 2017 (UTC)

Wikia Logo
Not sure why but there's an issue with the logo. It seems to have changed since I updated the script, and I don't know how to modify the script to fix the logo. ― C.Syde  ( talk  |  contribs ) 10:37, May 18, 2017 (UTC)
 * Replied at Talk:WikiaNavigationBarStyle - OneTwoThreeFall talk 11:53, May 18, 2017 (UTC)

Bot Request
Hello! I know we’ve not interacted much, but I’ve heard you’re very knowledgeable. So, would you be able (& willing) to set up a bot that would fix links on a few thousand pages sometime in the near future? Perhaps a couple weeks from now? My Wiki is considering a large merge with another Wiki, taking those thousands of pages into custom namespaces for organization, but the problem is that in a custom namespace the links will no longer work (as they were in the Main Namespace on the other Wiki). If a bot could change instances of  to   & instances of   to , correcting the links but keeping the display-text & leaving Interwiki links alone too, that’d be awesome. There would two other namespaces & links to which would need to be corrected similarly, but they’d be smaller & we could correct the links manually in case a bot wouldn’t be able to discriminate between namespaces. This is only a one-time project so once it’s done it’s done. You don’t have to help of course, but it would be greatly appreciated if you could, because as it stands it looks like the best we can do is replace each link with a Template, but that would likely screw up a great deal of links.
 * Hi! To be honest, I don't have that much experience with bot work - I use Pywikibot every now and again for some fixes and find/replace tasks, but that's about it.
 * Looking into it though, it seems Pywikibot has a built-in function to replace links in the way you mention, and whipping up a bot script for it shouldn't be too hard (I hope…), so I'd be happy to help you out (or at least try)! - OneTwoThreeFall talk 11:08, June 24, 2017 (UTC)
 * Awesome! I have Pywikibot set up already, I just never got around to using it (or really figuring it out beyond the setup). I’ll try my hand at it & if I burn down the house I’ll send you another message lol.
 * Alright! Forgive this possibly ignorant suggestion, but I had a look at the merge outline and was thinking it might be better to request the new namespaces on both wikis, then do the page moving/link updating work at the to-be-merged wiki, before exporting+importing the pages. This could make checking that everything is moved and updated correctly a lot easier, as the main NS of the old wiki will end up having few pages/backlinks (assuming most (all?) pages belong in the new custom namespaces). (P.S. might it be better to continue this conversation over on the Diep.io wiki?) - OneTwoThreeFall talk 19:06, June 24, 2017 (UTC)

That’s not ignorant at all, that’s a good idea. I just assumed Staff wouldn’t want to set up Custom Namespaces on a Wiki if it was closing, but I’ll ask Kirkburn. I have to step out for a few hours, & you can continue this conversation here if you wish, but my Message Wall (& Talk Page) are open on the Diep.io Wiki if you want to move the conversation there. I’ll pick it up in either place when I can.

AllowScript
Woah there, it's for personal use. And it doesn't literally makes everything in the page, just what you add in the div. It even has some security if you think you didn't added that script. http://vignette2.wikia.nocookie.net/steven-universe/images/e/e5/Jaspergem15x15.png ~ ~  D o o r k   w a s   h e r e  14:42, July 18, 2017 (UTC)
 * Just left a message on your talk page about this: User talk:Doork. - OneTwoThreeFall talk 14:50, July 18, 2017 (UTC)

ShowUserGroups Classes & Orders suggestion
Hey, I had some ideas for that script which I wanted to bounce off you. Would you be willing to add classes to each of the generated  tags generated in Oasis & MonobooK? That’d allow for better CSS customization locally. Additionally, I’d be interested in being able to specify the order in which each group is listed, customizable by a window variable. Something like: So if a user had the,  , &   groups, then they would show up in this order:  , & if they had another group, say,  , then it would show up as  , since any unspecified groups could default to   or something whenever   is set to false. The predetermined order would be a list in the script defining orders for several of the default groups, like this: Specifying an order for a group in  would override the above order for that group (so setting   would override the   order), & setting   to false would reset all of the above orders to. Any groups not specified in either the PredeterminedOrder or the local  would be at   by default as well. Would you be open to doing something like that? Is it possible? JS isn’t my strong suit, this is just an idea I thought you might like for the script.


 * Regarding adding classes: it doesn't use individual spans - it just adds plain text - so there's not really anywhere to add such classes. ShowUserGroups was made as a deliberately bare-bones script to show a plain list of groups a user is a member of, so styling/customisation wasn't in mind when I wrote it.
 * Regarding sorting: This isn't something I think the script should do by default (for the above reasons + to keep it simple), however I've added the ability to set a custom array sort function to be used.
 * For detailed info on how these compare functions should work, check the MDN page for Array.prototype.sort. Here's an example that should do what you want (I removed the PredeterminedOrder values for brevity, though what you used above will work perfectly):
 * For detailed info on how these compare functions should work, check the MDN page for Array.prototype.sort. Here's an example that should do what you want (I removed the PredeterminedOrder values for brevity, though what you used above will work perfectly):


 * Hopefully this works for you! - OneTwoThreeFall talk 13:58, September 18, 2017 (UTC)


 * Thanks for the ping! I did miss this. So, if I understood you correctly, this configuration would do what I described? Also, if I were to put that in Common.js, would it reorder the list for everyone using that script in personal JS? I forget if personal or sitewide JS loads first. In regards to classes, I am not referring to the group output, but to the tags which wrap around the output:


 * If the above HTML output could be changed to something like this…


 * That would be perfect. I really appreciate the help you’ve given so far.


 * Yep, that configuration should work as you wish. If I remember correctly, the order is site-wide > personal > ImportJS, so yes, adding that to Common.js would reorder it for everyone using the script on that wiki (unless they've set their own sorter function). Doesn't seem like an issue, though - the default order is simply the order of the groups in the API request, nothing special.
 * Ah, gotcha! I've added the  and   class to the output and title/label, respectively. - OneTwoThreeFall talk 08:41, October 12, 2017 (UTC)


 * Aye, but the reason why I requested it would be to provide a sort of “rank,” or tiered effect. I (& I think Monobook users especially) would want to be able to see the “staff” group first for example, instead of “content-reviewer, poweruser, restricted-login, staff, util, restricted-login-auto, autoconfirmed.” Once you see the Staff group, you can stop reading unless you’re interested in specifics :P Thanks so much!


 * Oh sorry, I didn't mean that a custom order wasn't useful, I meant that the fact that it'd reorder the list for people using the script in personal JS doesn't seem like an issue!
 * Glad I could help! - OneTwoThreeFall talk 08:58, October 12, 2017 (UTC)

LockForum
Hi, your edit to LockForums seems to have broken it, as it can't find the timestamp anymore (https://owo.sh/8038c8.png). --Sophie 06:41, December 27, 2017 (UTC)
 * Odd, that was definitely working when I saved it - I made sure to test it on a few wikis, languages, and date formats. It seems the server is taking a different code path for timestamps than it previously did, making the ISO timestamp unavailable. Not sure why that is, but KockaAdmiralac has undone the change now so at least it'll be working again for people using compatible date formats. - OneTwoThreeFall talk 08:54, January 4, 2018 (UTC)

CSS
I don't get this change, tbh, that is a legacy page. The code was already moved to MediaWiki:AbuseLogRC.css. Actually, I don't think it would much of a problem to directly delete the page, since it was never imported by default by the main code. It was a "suggested" styling. 14:07, January 10, 2018 (UTC)
 * That was most likely done to preserve page history as discussed here. -- Cube - shaped   garbage can  14:26, January 10, 2018 (UTC)
 * That's indeed the reason! It's planned to be moved over properly (instead of a copy and paste), along with the other CSS pages still in main namespace. - OneTwoThreeFall talk 15:12, January 10, 2018 (UTC)

Maintenance page
Hey, Could you delete [ this maintenance page] of yours? I checked WhatLinksHere for each of the pages in first and third column and only Highlight/code.css has pages pointing to it. It's also generating redlinks.

Cheers! -- Cube - shaped   garbage can  17:07, January 19, 2018 (UTC)


 * Gone now! I had kept it around for reference in tidying up leftover links, but looks like you've taken care of it! - OneTwoThreeFall talk 15:42, January 22, 2018 (UTC)

RE: Adding Talkheader to empty pages
Sounds good, thanks for taking the time to let me know! ~TheGoldenPatrik1 (Talk) 12:21, March 9, 2018 (UTC)

Pseudo-Vector for Oasis 🤔
Hey, OTTF. Would you be interested in reimagining Pseudo-Vector as a PseudoMonobook extension or fork of sorts? It'll be tough, but fun!

I mean to eke out some differences to Monobook first, if that's a concern. (Mainly having sidebar dropdowns as static menus, and an expanded global nav user menu.) • speedy • 🔔&#xFE0E; • 🚀&#xFE0E; • 20:46, May 24, 2018 (UTC)


 * Hey! "Tough" seems an understatement! With a MonoBook base, the HTML and general layout were somewhat similar to Vector, but with an Oasis base… I don't think it'd be possible to make Oasis look like Vector in the almost pixel-perfect way Pseudo-Vector did - they're just too different.
 * That said, your PseudoMonobook styles looks interesting. Perhaps it'd be better to adapt a few Vector design cues into that, like positioning the search box beside the action links instead of in the sidebar, and make PseudoMonobook itself a more general Vector and MonoBook take on Oasis? - OneTwoThreeFall talk 14:58, May 25, 2018 (UTC)

Deletion of JSON page
Hi! I just saw you deleted a JSON page I created. I did that, because some time ago I contacted one of Dev's mods, about [ this page] (please delete it by the way) and they replied "Why don't you put it in MediaWiki namespace". I understand from this message that we can make JSON pages. Akso noone has deketed any of my JSON pages before. I also think that JSON is a good sollution, because translations can be stored, before the script is updated to take translations from JSON page (many translators are afraid of editing JS pages). Just when the main script gets updated, there will already have been a JSON page with some translations. Then, may I ask you to restore [ MediaWiki:Custom-DisplayTimer/i18n.json]? ~ [ <font face="times new roman"> Q uəntum ii ð the Wise  ] 08:38, June 4, 2018 (UTC)
 * Hi there! I know you've done work in creating these pages, but there isn't really any point in creating them unless the script is actually using them - having them created early means they will likely become out of date, and people will be confused where to add new translations.
 * JSON can be a good solution, but for many reasons it may not work for every script. If a translator is afraid of editing JS pages, I'd recommend leaving the translations on the talk page instead and I'm sure someone will be able to help add them to the code! - OneTwoThreeFall talk 08:53, June 4, 2018 (UTC)
 * Are the scripts being updated so often that the translations would become outdated? I don't think so. I thought creating JSON pages would encourage some users to implement JSON in those scripts. I would even like to help with implementing JSON into JS, if only I knew how to deal with it. Is there any common way it can be implemented?
 * While deleting the pages, not only you delete my work, but some of the new JSON pages were also translated into new languages. I was planning to create it where possible and then send the pages to some users who told me they'd like to translate for dev. ~ [ <font face="times new roman"> Q uəntum ii ð the Wise  ] 09:16, June 4, 2018 (UTC)
 * Creating those JSON pages is fairly simple - there really is no need to pre-create them. I'm afraid there isn't really any common way to change scripts to use i18n-js - it all depends on how the script is written in the first place - besides, I wouldn't recommend making such major changes to scripts without talking to the author beforehand.
 * For the single page I deleted ([ MediaWiki:Custom-DisplayTimer/i18n.json]), I did indeed verify there were no languages added. In fact, you had made a few odd typographical changes to the text, namely switching ellipses (…) to three full stops (...), and typographical quotation marks ( “ ” ‘ ’ ) to typewriter marks ( " ' ): both changes that are unnecessary.
 * I'm sorry for deleting your work. Just a reminder though: it's worth discussing before making changes/creations to many pages, just in case it's work that might not be needed. - OneTwoThreeFall talk 09:30, June 4, 2018 (UTC)

Explaining the mass cleanup of Script Installs
Hey, thanks for fixing Template:Script Install/Plain just now. I'm trying to clean up:
 * general use of Script Install, which was broken by the new version I wrote
 * Source parameters with syntaxhighlight tags in either
 * configuration being fed into Script Install templates by ^
 * defaults in both Script Install/Plain and Script Install - hopefully this will discourage new scripts from using it. Admittedly, this is a weird one and will need a second pass through all 1000 or so pages.
 * while I'm at it, I'm removing the infobox Skins parameter and any custom (not p/s/ps) Scope inputs

I got permission (after a fashion) on Cqm's talkpage somewhere, but if you have any tips or concerns, I'm willing to listen: • speedy • 🔔&#xFE0E; • 🚀&#xFE0E; • 16:17, June 25, 2018 (UTC)
 * 1) It seems like my extractor function did hit some errors, but the Discord users are using DPL to check for those. Any suggestions there?
 * 2) In particular, should I remove any added   in /Plain templates during my second pass?  might look a little messy in the template.
 * 3) Any comments on the new I18n templating system we're considering?


 * That's alright! It's good you've got some automated editing going for these sort of fixes - I don't think there's been much bot editing/fix-ups here before, so nice work! 👍
 * Dropping/discouraging  sounds good. It was useful back when code was in main NS, but in MW namespace it's a bit unneeded.
 * It's pretty late for me, so I'll have to look at your no.1 (extractor) and 3 (i18n templating) points tomorrow, sorry. Regarding no.2 (using  and  ) though, it is a little messy, but maybe it'd be better to tidy it the other way? Template parameters with names are easier to understand for anything more than basic templates, so always using   might be a good option instead! That'd also keep it in sync with the non-plain version.
 * By the way, I noticed a few times Speeditwo has added the  param to templates. That could actually be mass removed instead as the SUBPAGENAME language code can be detected by the template itself (I think most of the major templates have this support).
 * - OneTwoThreeFall talk 18:02, June 25, 2018 (UTC)

Images
I'll just move the images and the page to specific site. It was put here to share with another library and for others convenience as a courtesy to other developers. These images are actually a part of the actual fandom wiki source. Other editing previously kept removing them then caused the TOC to appear to no longer work. It does not need to get marked with a stub, or have its images moved or removed. Thanks. Celess22 (talk) 16:27, June 25, 2018 (UTC)


 * If the images are for use on a specific wiki and aren't being used here, I think it would be best to copy them over to that wiki instead, especially if the page is being parsed in a way that changes could break it. The main namespace of Dev Wiki isn't really a good place to keep something like that. For example, after your removal of the Stub template, the page is now uncategorised which isn't ideal.
 * If the page is being parsed, I'd recommend add some sort of start and stop marker, and have the parser ignore anything outside of these markers. Something like that should prevent issues like this in the future. - OneTwoThreeFall talk 17:42, June 25, 2018 (UTC)


 * I'm not sure you understand the purpose of the page, or what it is documenting. It's already been stated that its for a common library(s), an those files are assets for that library and others. I'm really not sure what the issue is. I'm not sure why this is suddenly a problem. Celess22 (talk) 18:00, June 25, 2018 (UTC)


 * Then put it in a category. I can't create categories. Celess22 (talk) 18:10, June 25, 2018 (UTC)


 * You're right, I don't, sorry. The page gives no information how or where it is actually being used, just says it has dependent libraries.
 * It's not suddenly a problem - technically it's always been one, as the images were unused and the page was uncategorised - just I noticed this and thought to add the images to the page so they wouldn't show as unused. This page is all fine now, with the images at the bottom (thanks for keeping them there!) and I've added it to a category now. Hopefully that is alright? - OneTwoThreeFall talk 18:14, June 25, 2018 (UTC)

Its either a problem or it isn't. If you are saying its always been a problem, then its a problem. Its either easy to recognize that someone is documenting the valid image cache links for jQuery UI, to help others in the community, or it is not. If you read the links, you can see they are from the actual Wikia wiki code cache files from checked in code base file, the ones you peruse when you are looking though the Wikia server source code. They are implicitly a part of every single Wikia wiki, without exception.

There are times where mistakes were made on the Wikia end with regards to jQuery and jQuery UI, and alternate examples were also provided, so that someone could dig themselves out of a hole. This has happened many times.

Yes, there are also files being served from dev also, and it was very much on purpose, and it was for everyone who has issues where random people accidentally keep deleting them from the actual Wikia codebase, because they couldn't mechanically find a use, not realizing or somehow making the connection they were a part of the core jQuery UI and procedurally loaded. Which is similar to what happens or most happened here. If the are a problem delete them, just send me a note. Ill go check and fix the sites I know about or at least let the admins know. Thanks Celess22 (talk) 19:16, June 25, 2018 (UTC)


 * See my talk Celess22 (talk) 21:25, June 25, 2018 (UTC)


 * It's not a problem in that way any more - the images are linked and the page is categorised so it shouldn't appear on any more maintenance reports. As far as I know, it's fine to have the images here, just wasn't sure where they were being used or the purpose of that page, that's all. The fact they're used in FloatingToc is good to know! - OneTwoThreeFall talk 11:58, June 26, 2018 (UTC)


 * In what way is it still a problem, if any? You said "It's not a problem in that way any more". I would hope its fine to have images here if you allow modules here. Did either of you even look to see who uploaded these images before you started? What do you think would have happened if you deleted them? Would you like me to contact Pecos for and let him know? Celess22 (talk) 16:48, June 26, 2018 (UTC)


 * It's not. I was only referring to the discussion on your talk about the purpose of the jQuery page itself.
 * I was never going to delete the images; the opposite, in fact, I was trying to make sure they wouldn't be deleted due to them not being used anywhere (or more accurately, due to MediaWiki detecting them as unused). - OneTwoThreeFall talk 17:17, June 26, 2018 (UTC)


 * The job of the page is not to tell you who is using either the jQuery UI image links, or to tell you who is using the similar or same images of various kinds added here to be shared on dev.wikia. It is to aggregate and corelate those various images for reference, and to help those less adept in understanding how to make a proper image cache link, and so forth. The page is called jQuery because it is documenting specifics as relates to development on the Wikia wikis for jQuery and jQuery UI, and was named this way so that others could add other things as well, if that was to ever happen. There were various times were people had removed the underlying jQuery UI files accidentally from the whole of Wikia, and I mean deleted form the repository, and that page helped people fix there various wiki customization, modules, and random wiki JavaScript. The page was created in 2013. If you have an issue with images it needs to be fixed in such a way that you would not need the images to show on that page, in order to properly attribute them as dependencies to a module. The reason I worded the 'Note:' at the top of the page that way is to help you, not me. Its like the matrix and this is the 3rd or 4th time I have gone through this with you, and I prefer to measure dev.wikia time in time between these anomalies. I can not bring myself to delete the page because I think it is useful for people even if your admin disagrees. I know for a fact that it has helped people whos code stopped working. I also prefer not to delete it because invariably someone will decide something is wrong with the files and they will tell me about how the files don't belong and should be removed. You were faster then the other, so maybe you are Neo, however I still had to endure a bunch of business form your admin who was more than happy to tell me all about it without listening.


 * Note that I said: "I'm not sure you understand the purpose of the page, or what it is documenting. It's already been stated that its for a common library(s), an those files are assets for that library and others. I'm really not sure what the issue is. I'm not sure why this is suddenly a problem."


 * Before you said: "its always been a problem"


 * I am just trying to help. Celess22 (talk) 18:33, June 26, 2018 (UTC)


 * So tell me about what problems you have with the page, re: "In what way is it still a problem" "It's not. I was only referring to the discussion on your talk about the purpose of the jQuery page itself." Celess22 (talk) 19:13, June 26, 2018 (UTC)