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)
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)
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)