The previous discussions are archived as per Admin Tools Wiki’s talk archiving policies. Wikians may want to survey the archives before starting a new discussion to determine if any issue of interest is dealt with therein. This current talk page is for starting new discussions not covered in the archive, or for re-visiting older issues. The archives themselves are not to be edited. Thanks! — SpikeToronto
What is this template used for exactly? Per the title, it appears that it would only be used for links to Mediawiki pages rather than also being used for other things (like Wikimedia). ~Curiouscrab (talk) 19:11, June 20, 2015 (UTC)
Template:Mediawiki is used specifically on pages brought over to SP and ATW from MW. It’s their template that they use for links to other WMF wikis. It doesn’t need fixing. It works as it’s supposed to. Did you see the comparo at Template:Mediawiki/testcases?
Also, and this is surely my fault for not having made it clearer at the outset, testing administrators come here to test admin tools, their own templates, their own CSS/JS, mass processes in the Test namespace (only!), seek admin mentoring, advice, etc. Testadmins do not come here to do maintenance to ATW itself. In other words, they don’t alter ATW’s own templates, CSS/JS, etc. They may, of course, copy them, import them, etc., to their home wikis. But, they don’t alter our stuff. Of course, ideas suggested on talk pages are truly welcome.
For example, suppose you wanted to test your autoSign.js code before rolling it out at your home wiki. It would be perfectly acceptable to input your JS as either a MediaWiki: namespace subpage, or a subpage in your userspace (the latter is, by far, preferable). You would then add an import statement to one of the top-level JS pages: i.e., MediaWiki:Common.js, MediaWiki:Wikia.js, or MediaWiki:Monobook.js. (If we have a JS sub-page of the same name, you may temporarily comment it out while testing yours.) When you’re done testing, editing, fixing, etc., your JS, you must revert the top-level JS page into which you had been importing your code to the revision it was before. (Same for CSS testing, of course: revert top-level CSS pages to their pre-testing state.) Finally, because all your edits are made to a CSS/JS sub-page in either the interface space, or your own userspace, it minimizes the edits to the top-level CSS/JS pages in the MediaWiki: namespace.
It is better for you to put your test CSS and JS in your own userspace (e.g., User:<insert name here>/autoSign.js). Why? Because no one else can edit it, and you’ll know exactly where it is. The MediaWiki: namespace can get very cluttered at ATW. After people are done testing, as a regular sysop, I often move their test CSS/JS pages from the interface namespace into their own userspace.
Ok. One thing, though, is that a lot of other wikis use scripts that are located here and so to work on them I'd have to work here. ~Curiouscrab (talk) 14:09, June 22, 2015 (UTC)
┌───────────────────────┘ “A lot of other wikis use scripts that are located here” → which is why you cannot change them. You have to work on a copy. So, for example, to test your powerUser.js script here, you would do the following:
In this way, yours is running at ATW, but the current, accepted version remains untouched, and is still running – unchanged!! – at all the other wikis that import it. When you are done testing, do the following:
You must return our current, accepted version to loading, and yours to not loading
Warning: When you are done, all currently accepted pages in the MediaWiki: namespace must be as they were before you did any testing
As a Testing Administrator, you are not authorized to make any permanent changes to the MediaWiki: namespace at this wiki. I hope this clarifies what I was trying to say earlier. Thanks! — SpikeToronto 21:43, June 22, 2015 (UTC)
I think my script is ready to replace the old one. You can see it in action here and play around with the variables here to see what they do. By default, the error message does NOT show. Only if a specific variable is set to false will it show. ~Curiouscrab (talk) 14:07, June 22, 2015 (UTC)
Sorry. I didn’t miss this one. I’m just still thinking on it… Thanks! — SpikeToronto 20:52, June 24, 2015 (UTC)
Archive Talk Page
When are you going to archive this? If pages in the userspace were put in Special:LongPages, your talk page would be ranked number 98. I'm asking here because my browser can barely load the page let alone leave messages. ~Curiouscrab (talk) 14:27, June 22, 2015 (UTC)
Never!! I want it to be #1! — SpikeToronto 21:47, June 22, 2015 (UTC)
I thought you were talking about this talk page!! Since this talk page was #2 at Special:LongPages, I’ve gone ahead and archived this talkpage. — SpikeToronto 22:22, June 22, 2015 (UTC)
I've currently switched out the Mediawiki version for my version. Check it out. ~Curiouscrab (talk) 14:22, June 23, 2015 (UTC)
Question: Crabman, are these the only differences between the two? Thanks! — SpikeToronto 22:39, June 23, 2015 (UTC)
While working on creating a script that adds another tab to the top of protected pages that a user can't edit, I discovered that the "edit this page" tab hover text in Monobook is missing a line break. I don't know whether or not this can be changed here without using JS, but it is different from the view source hover text. If you use your put your test account in the user group (none) and go to a page in the mediawiki namespace, hover over the view source tab and see the text. Then, go to a page that your test account can edit (such as the user's page) and hover over the edit this page tab. See the missing line break? For the Monobook version of suggestEdits.js (minor project I started), do you recommend I have the line break or not? — Curiouscrab (talk) 02:35, June 28, 2015 (UTC)
It seems like a good idea! But, we do not need it here, or at SP. As I’ve mentioned to you on talk pages over at SP, we have the same edit-protected system as they do at WP. When you press ViewSource, you see it at the top of the editor. When you press the “submit” button, you can see what happens next. It uses system messages, edit notices, and preloads. No JS. JS is not always the solution to everything. Scripts are cumbersome, resource hungry, and always need maintenance. I generally see scripts as a last-resort solution to a problem.So, while we do not need it here at ATW, or over at SP, most sites here at Wikia, have no system at all for suggesting edits to locked pages. So, if you can get this working fully — and in both skins (Monobook-only scripts are essentially of no use at Wikia) — this could be quite worthwhile to other Wikia sites: You could post it at Dev wiki! Now, for some specifics:
Line breaks. I don’t see any line breaks in the tooltips when I hover over those tabs you mentioned. We’re probably not using the same browser. Perhaps you could upload a screencap of what you’re seeing.
Oasis. It does not seem to be working in the default Wikia skin. I do not see a suggest edit option in either the edit-button pulldown list, or on the bottom toolbar. However, when I select view source and am taken inside the editor, I do see ATW’s default protected-text edit notice with its submit button. I don’t see any part of your script-based system inside the Oasis view source editor.
Monobook. In Monobook, I see the edit suggest tab. It looks good! Also, when I click on it, it does something!
Target. Once the suggest edit tab (Monobook) is pressed, it takes the user to a page in his userspace. While that’s a clever approach, it is not the norm at WMF and Wikia sites. Normally, such edit-protected systems take one to the locked page’s associated talk page.
Like I said, you could be on to something useful here. Let me know when you want me to some more testing! A lot of Wikia wikis should find this quite useful. Thanks! — SpikeToronto 06:22, June 28, 2015 (UTC)
Alright. This was more of a "if you want to make edits click here" sort of deal rather than just making a suggestion on the talk page. I haven't gotten around to the Oasis skin due to minor issues that aren't found in Monobook (thus easier to work with on Monobook). I hope to figure out a way to solve the issues and get this working and maybe change the text so that rather than using the word "suggest" I'll have something else (suggestions?). I've also been working on side projects such as http://punbb.atspace.cc (forum style previewer) and other various things. — Curiouscrab (talk) 21:12, July 7, 2015 (UTC)
Done I changed "suggest edits" to "create copy" and added the item for Oasis. — Curiouscrab (talk) 22:01, July 7, 2015 (UTC)
Actually, make a copy makes sense. Or even, sandbox a copy. That could be very useful! We’d have no purpose for it at SP, but we could add it to the gadgets here at ATW. I’ll take a look at the Oasis version now. Thanks! — SpikeToronto 19:38, July 8, 2015 (UTC)
UPDATE: I just tested the Oasis version. I found it on the Edit this page button pull-down. It works perfectly! — SpikeToronto 19:43, July 8, 2015 (UTC)
While roaming the dev wiki, I found QuickTools. I tested it here and it seems to work fine, but is a work in progress. When it's complete, I think it will be very beneficial since it allows admins to easily perform actions. But, as I said, it is a work in progress. I've contacted the author to see if it would be possible for me to finish the project since he hasn't been doing to much with it. — Curiouscrab (talk) 17:47, July 8, 2015 (UTC)
UPDATE: I actually just found another script that seems to be complete and combines a lot of things (such as mass creation, deletion, etc.). — Curiouscrab (talk) 20:51, July 8, 2015 (UTC)
CC, we already have multiple versions of QuickTools kicking around. It is not a work in progress. I can point you to at least four different versions of it. We don’t need another one. I’ve been using various versions of it for at least four years. Right now, I’m using this one: importScriptPage('WHAM/code.2.js', 'dev');. (The original one is in its creator’s userspace over at the VSTF wiki.) By the way, many people call it Wham!. So, when you hear that term, that’s what they’re talking about. To be honest, I was hoping you’d never find it. It’s very powerful and dangerous: It must be used carefully. It gets even more dangerous when people start messing with its code. — SpikeToronto 21:41, July 8, 2015 (UTC)
I personally like when a box pops up rather than just a shady clicky thing. ~Curiouscrab (talk) 00:44, July 9, 2015 (UTC)
Just be careful. It’s an extremely complex, densely coded program. And, it’s in jquery! — SpikeToronto 01:39, July 9, 2015 (UTC)
UPDATE: You and I were talking about two different things. I was talking about Wham! (which appears with the heading Quick Tools for normals, and Quick Tools for VSTF), while you were talking about w:c:dev:QuickToolsv2. — SpikeToronto 10:16, July 9, 2015 (UTC)
Do you have auto-refresh ticked? There is some conflict between the [show]/[hide] JS and the AjaxRC code that causes this. So, if you want them collapsed, untick auto-refresh. If you want auto-refresh ticked, then you’ll have uncollapsed boxes. — SpikeToronto 22:15, July 10, 2015 (UTC)
P.P.S. Of course, you might be referring to how things look in the Monobook skin. We don’t support the Monobook skin. — SpikeToronto 07:44, July 11, 2015 (UTC)
P.P.P.S. But then, if you could figure out what’s causing it and fix it, that would be truly appreciated. — SpikeToronto 07:44, July 11, 2015 (UTC) Don’t make a mess of our MediaWiki namespace! — SpikeToronto 07:44, July 11, 2015 (UTC)
UPDATE1: Just checked. There are no collapsible boxes on any of these pages in the Monobook skin, same as for Oasis. The only exception is atop the Special:RecentChanges pages, which has collapsible boxes in both skins. — SpikeToronto 08:30, July 11, 2015 (UTC)
UPDATE2: I just remembered: I dismissed the last sitenotice. So, I won’t see it again until there’s an update, or a I use a different browser. By the way, remember that “sitenotice” refers only to Monobook. The Oasis system is completely different; it does not use MediaWiki:Sitenotice. — SpikeToronto 10:13, July 11, 2015 (UTC)
Do you see a red asterisk next to your username? ~Curiouscrab (talk) 01:23, July 16, 2015 (UTC)
Yes, I do. Sir: What have you done?! — SpikeToronto 08:06, July 16, 2015 (UTC)
Whatever you’re doing now is messing up our ProfileMastheads. Please stop working in Monobook and start working in Oasis so you can see the impact of your work. Thanks! — SpikeToronto 13:25, July 16, 2015 (UTC)
UPDATE: The problem seems to be something that Wikia’s done. — SpikeToronto 13:41, July 16, 2015 (UTC)
Yeah. It only affects things in the page content (inside the div tags with the specified id not including the masthead). ~Curiouscrab (talk) 20:38, July 16, 2015 (UTC)
I don't know if you noticed, but at some point FixLinks wasn't working. That was me altering the script to run more efficiently and then debugging it. ~Curiouscrab (talk) 01:32, July 22, 2015 (UTC)
Nope. Wasn’t around. Thanks for the notification though. — SpikeToronto 22:13, July 22, 2015 (UTC)