Wikia

Wikia Developers Wiki

Cqm

Admin
1,524 Edits since joining this wiki
April 13, 2012

Archive 1


If you have any questions that do not require my specific attention, please consider asking in forums first.


Unless requested, any messages posted here will be replied to here in order to keep a centralised, easy to follow discussion.

ReferencePopups‎

Thank you very much always for your kind support!!

I'm sorry to trouble you, but would you mind if I asked adding the translation to ReferencePopups again (because of the new extension, JavaScript review process)? --Plover-Y (talk) 2015-11-07 05:04 (UTC)

Unfortunately it's still locked down. I should be able to sort something out within a week or so though :) cqm 22:34, 12 Nov 2015 (UTC)
Thank you very much for the reply! --Plover-Y (talk) 2015-11-13 14:11 (UTC)


This might come off as rude, but I'm not trying to be. Have you constiered archiving your talk page?

In truth I haven't. I probably should sometime soon though :P cqm 22:34, 12 Nov 2015 (UTC)

Protect PrintableVersion/code.js

I created a new script called PrintableVersion that I need protected with codeeditor level.
~Curiouscrab (talk) 22:11, November 12, 2015 (UTC)

I can, but no one can edit js at the moment anyway, and we should be moving to the JS review system within a week or so which makes the codeeditor right/protection obsolete.
If I may ask however, what does your script do that MediaWiki:Print.css doesn't? It's probably better implemented via CSS. cqm 22:29, 12 Nov 2015 (UTC)
On closer inspection, and as this is all skin based, why not simply request additions to github:Wikia/app/blob/dev/skins/oasis/css/print.scss and something extra to kill the wikia specific stuff at the bottom of monobook? It's even better to have support for this stuff natively :) cqm 22:52, 12 Nov 2015 (UTC)
Well, it provides a good view of what the intended target page would look like. In CSS, I've found that hiding items generally leaves large undesirable spaces which take up perfectly usable space and requires more pages to be used in the process of printing. Of course, I guess you could try and scale those items to almost non-existence, but it's nearly impossible without removing them altogether.
~Curiouscrab (talk) 03:10, November 13, 2015 (UTC)
In addition, if we want to somehow stamp the page with the user's username as well as the URL that leads directly to the page rather than the current revision view, JS would be required.
~Curiouscrab (talk) 03:15, November 13, 2015 (UTC)

Check script

Hello, Cqm! Sorry for bothering, but I need you help.

Since Wikia have some problems with security and JS, we should be carefull. I've written one script, which have all data outside of .js page, because it's simple way to change script's config without waiting of JS review result. Here is script and data. I'm going to push it here, but before I want to be totally sure, that everything is ok. Can you, please, check it?

Idea of is script is alternative of custom achievement. Admin can create new badge and give it to user.

Thanks in advance! FANMADE_Luna_S1_flying.gifKopcap94@Wikia18:24, 18/11/2015

If you want people to review your code, you can post a request at Board:Code Review, although you should probably place a copy for review somewhere on this wiki. --Saftzie (talk) 01:16, November 19, 2015 (UTC)
Ah, okay, thanks! FANMADE_Luna_S1_flying.gifKopcap94@Wikia15:28, 19/11/2015
  • I'd avoid using onclick attributes, it's safer to use a proper click event handler such as jQuery's .on('click', ...) or .click(...)
  • Make sure to escape anything you aren't absolutely 110% sure about when working with html. In this case, it applies to the config stored in JSON. Simply use mw.html.escape(...) before adding the inner text inwhich saves a lot of potential headache in the future.
  • <center> is deprecated in HTML5. It'll work, but there's no real reason to use it when it can be easily replicated with CSS.
  • The debug and allinone query parameters do nothing when combined with action=raw.
  • Seeing as you're working with the DOM, it might be prudent to wrap your init call with $(...) (but don;t invke the method). For example, $(foo.init)
  • You're using some very generic regexes. I'd look at either making them a little more specific or commenting why you're using them in that way. Regex is one of those things you tend to have difficulty fixing when they break.
Otherwise, it looks ok. I haven't tested it in any way, the above is just some initial notes based on what I could see. cqm 16:48, 19 Nov 2015 (UTC)
I've fixed problem with html by another way (.attr()), so there shouldn't be any problems, because it's not allowing to add something like 'onclick' and so on. Button's 'onclick' is kinda crazy, I know, but it's same as 'click()', thought. About center - yep, my fail, was lazy to make it via CSS and totally forgot about this. Also was not informed about 'allinone' and 'debug' - will know it. Thanks for checking, I really appreciate it! FANMADE_Luna_S1_flying.gifKopcap94@Wikia17:37, 19/11/2015

Page Deletion

Is there a way to get some of my pages deleted, I marked them for deletion almost 2 weeks ago. I have also blanked them and added the delete template to the 4 pages. I have listed them below.
Sophie Profile Talk/Message Wall Contributions 10:45, November 21, 2015 (UTC)

(1) User:Sophiedp/Clean_Up_JS_Inports
(2) User:Sophiedp-Clean_Up_JS_Inports
(3) Template:Sophiedp-Clean_Up_JS_Inports
(4) Sophiedp-Clean_Up_JS_Inports
Category:Candidates for deletion has a few more. --Saftzie (talk) 04:33, November 22, 2015 (UTC)
Sorry, it's a little quiet here on Dev, so I don't tend to check such things very often. I'll get right on it :) cqm 16:30, 22 Nov 2015 (UTC)
Thanks :) Sophie Profile Talk/Message Wall Contributions 03:00, November 23, 2015 (UTC)

diff 34523

http://dev.wikia.com/wiki//?diff=34523
#WikiaArticle should probably be #mw-content-text, since #WikiaArticle exists only in Oasis. I'd post on Rappy's page, but I doubt he'd even read it. --Saftzie (talk) 22:44, November 23, 2015 (UTC)

Wikimarks not loading

Greetings Cqm! It appears that Wikimarks is hanging again (no console errors are generated, but the menu fails to appear and the "wait state" covering the "On the Wiki" menu cycles forever). Last time that happened I believe all that was needed was a null edit of the source code to reset it. 60px-Spsig.png (talk) 12:08, 24-Nov-2015 (UTC-7)

See Talk:Wikimarks#Stop_working.3F. Unfortunately, it's not a quick fix. cqm 10:27, 25 Nov 2015 (UTC)

Border Radius

On Template:Infobox JavaScript the infobox looks awfully boxy. I think it might look better if the corners were rounded with the border-radius property. I'm sure others would agree.
~Curiouscrab (talk) 16:05, November 25, 2015 (UTC)

Personally, I disagree for 2 reasons: I don't think it would add anything the the aesthetic quality of the infobox, and modifications to PI CSS have the potential to break in the future as wikia change things. I'd rather keep away from those modifications, unless absolutely necessary. cqm 22:26, 25 Nov 2015 (UTC)
Well, there is a standard feature now. The europa theme that can be activated in Special:Wikifeatures. That may be worth activating as it probably looks way better than the default theme .Dessamator (talk) 11:24, April 14, 2016 (UTC)

suppressredirect

Considering that codeditors move stuff around, do suppose it's reasonable to ask Wikia to add suppressredirect to codeditor? --Saftzie (talk) 10:33, November 28, 2015 (UTC)

I don't see why not, I'll send something in to request it. cqm 10:38, 28 Nov 2015 (UTC)
And done :) cqm 20:27, 1 Dec 2015 (UTC)

Thank You

Cqm,

I wanted to thank you personally for your work on Wikimarks. I have been using the script for what I now realize has been literally years, and your effort towards keeping Wikimarks up to date with Wikia now that Pecoes seems to have moved on is greatly appreciated.

Regards,

--Whistle9 (Talk) 20:38, November 30, 2015 (UTC)

No problem, I've been using it for years as well so I was quite put out when it suddenly broke. It's surprisingly how many people really relied on it. cqm 21:19, 30 Nov 2015 (UTC)
Great to see you've fixed up that script. I might actually make use of it myself now. --SuperSajuuk Talk Page | Tabber Code | Channel 20:52, December 3, 2015 (UTC)

PurgeBlogs

Hi. I just noticed that my PurgeBlogs script was added to the MediaWiki namespace here. Will the former page at PurgeBlogs be needed any longer, as well as it's associated code page?

Also, I may just have to request codeeditor to manage some of my scripts. --SuperSajuuk Talk Page | Tabber Code | Channel 21:44, December 7, 2015 (UTC)

I'm unsure exactly why a few scripts were duplicated and not others, but I think it's due to the new JS import page tha was added a couple of weeks ago. For now I'd keep your script where it is, along with it's documentation until there's a formal announcement for what the plan is with JS here. cqm 09:46, 9 Dec 2015 (UTC)
Alright, thanks for letting me know. And thanks for adding codeeditor. :) --SuperSajuuk Talk Page | Tabber Code | Channel 11:12, December 10, 2015 (UTC)

FixSourcePages

Regarding this, I finished the script some time ago and was thinking it could be tested and possibly implemented unless there is a way to enable source page formatting without the script. I set up the script so that it removes the extra pieces and parts of the script caused by the source tags, but we could always go through and manually and/or automatically remove the tags.
~Curiouscrab (talk) 03:22, December 10, 2015 (UTC)

I just went through and did some work to condense the script, but now I can;t move it back to where it belongs. If you could please move FixSourcePages/temp to FixSourcePages/code.js.
~Curiouscrab (talk) 03:36, December 10, 2015 (UTC)

Hide Deletion

I think due to the profanity in the deletion of the article deleted here, the deletion log for this page should be hidden from recent changes as well as the deletion log.
~Curiouscrab (talk) 02:31, December 11, 2015 (UTC)

That not really what revdel's for, hence LadyLostris elected not to use it. In any case, I don't have the user right here to do anything about it. cqm 09:11, 11 Dec 2015 (UTC)


Message Script not working

Seeing you are an ADmin here, I deemed it appropriate to ask you. I have attempted to use the Message script and have hit send two days in a row and it seems to be dysfunctional. I was wondering if the possible reason was that it hasn't been approved to match with the new JS Review system. Thanks so much —Preceding unsigned comment added by Superdadsuper (talkcontribs)

I'm not sure what message script you're referring to. Perhaps it would be better to contact the script's author? cqm 13:34, 30 Dec 2015 (UTC)
They have been inactive for over a year. The script is the one here. It has seemed to work, up until the introduction of the JS Review. I was thinking perhaps it hasn't been approved so the script is dysfunctional because of that (I have no way of knowing this). I have it installed on my global js and all other global js scripts are working. The extent of the dysfunction is, the dialog pops up, but it doesn't post after hitting send nor does it preview very well. —Preceding unsigned comment added by Superdadsuper (talkcontribs)
It's not a script I'm familiar with, but at a glance it's reliant on the less stable Wikia API and JS library, rather than the much more stable MediaWiki ones, so it could be any number of issues.
I don't have the time to look at it in any detail at the moment, so perhaps try posting on the forums here of at community central? cqm 15:45, 30 Dec 2015 (UTC)
After asking on the forums and on CC chat I have recieved no help. I was wondering if the issue lies in the script not being approved. If not could you sumbit it and get it approved and if that doesn't fix the problem I will message a skilled JS user or do it manually? Thanks, Superdadsuper
Alright thanks for the help anyway —Preceding unsigned comment added by Superdadsuper (talkcontribs)
JSReview isn't implemented on the scripts in the mainspace here yet, I assume there's a plan coming in the new year that will add it. cqm 12:39, 3 Jan 2016 (UTC)

Dutch Translation of CategoryRenameAuto-update

Hi, I've translated CategoryRenameAuto-update into Dutch. I cannot at it to CategoryRenameAuto-update/nl.js, however. Can you do that for me instead? The translation is located on my Sandbox. Thanks in advance! Mainframe98 talk·edits 14:24, January 1, 2016 (UTC)

Fixed a couple of quotes, just a reminder that you'll need to change the supportedLanguages array at CategoryRenameAuto-update/code.js as well once you add that language page. What's up with editing scripts now by the way? I'm a codeeditor and still can't edit scripts. Thanks Cqm! — Foodbandlt (talk) 00:32, January 2, 2016 (UTC)
No one can edit scripts here at the moment, except staff (and maybe utilities?). The workaround for the time being is to move the page to a non .js extension, edit it and then move it back. It's a pain and was meant to be fixed before Christmas, but it would seem they ran out of time. cqm 12:41, 3 Jan 2016 (UTC)
Ah, that explains a lot. I'll try that later then. Mainframe98 talk·edits 14:31, January 3, 2016 (UTC)
I got Mime to do it. Thanks Mime! — Foodbandlt (talk) 03:38, January 7, 2016 (UTC)

ajaxbatchundelete

since i don't have codeditor rights, me and noreplyz updated oz's version 2 of the original ajaxbatchdelete script. We removed the protect and "add category" options since that's not useful. Are you willing to help me transfer it over, i tested it and it works but did not have staff review it. I can have staff review it, just submited. its located here. Probably won't get codeditor since i'm not planning to make any further scripts or modify any.

Nerfmaster8 (talk) 06:06, January 8, 2016 (UTC)

New process for submitting code

As staff has decided to move all code to the MediaWiki namespace, I think that it will probably be useful to update the rules on submitting new code (for code-editors). Also including things such as "don't try to mess with the common.js" and related messages. Alternatively, those pages could be admin protected.

It might also be a good idea to re-submit popular scripts. Staff seems to have just pre-approved all of them without any review. —Preceding unsigned comment added by Dessamator (talkcontribs)

I agree with this. In fact, what Wikia should consider is disabling the editing interface (using JS or something) of the community JS/CSS files on this wiki so they don't work if the user is not marked as being a sysop. This unilateral wikia change requiring the mediawiki namespace to be used for code files is silly imo and doesn't really make it possible for new coders to get started, as their files will be moved to the mediawiki namespace, barring them from changing their own scripts. --SuperSajuuk Talk Page | Tabber Code | Channel 19:42, January 14, 2016 (UTC)
Actually, code editors can edit the MediaWiki namespace in this Wiki. So they can continue improving their scripts if they so wish. Strictly speaking, no code changes go live immediately, so it doesn't really matter if people try to edit it a hundred times only the revisions approved by staff will ever go live. Although I'm not sure if the editinterface right gives people permission to request a javascript review. They might have customized it for this wiki anyway. Dessamator (talk) 21:14, January 14, 2016 (UTC)
I've implemented an abusefilter to protect non .css and .js pages, as well as Common.js and variants to prevent people editing pages outside the intended scope. I've raised the issue of insecure scripts being grandfathered in previously, and staff apparently don't have the resources to review all the js here (or it was a decision made by someone who simply hoped it would be fine). Either way, the current revision has been approved so simply resubmitting it makes no difference unless we review them ourselves to fix any security issues. cqm 21:25, 14 Jan 2016 (UTC)
Makes sense, anyway, I made changes to the code help page. It would be easier to review scripts if we knew which ones are the most popular. I know of less than a dozen that seem to be widely used. With JSimport perhaps staff will have the stats on popular scripts that should be reviewed. Perhaps I should at least review my own scripts, since they were made without much care about security. Dessamator (talk) 21:56, January 14, 2016 (UTC)
Just noticed that apparently all autoconfirmed users now have the edit-interface right. I guess that makes the code-editor group pointless. Dessamator (talk) 12:41, January 16, 2016 (UTC)
Code-editor is obsolete for the time being, but everyone having the ability to edit NS_MEDIAWIKI is only a trial. If it works, we can look at removing code-editor. If not we'll have to look at other ideas.
I'll be keeping an eye on how it works out for now, as will staff. If there's anything that you or others spot that shouldn't be happening, just let me know :) cqm 15:45, 16 Jan 2016 (UTC)

ProfileTags.js needs review and more testing

I left some notes in :

http://dev.wikia.com/wiki/MediaWiki_talk:ProfileTags.js#Script_needs_review_and_more_testing

In addition you may also consider adding some visible way of showing regular users that the script is actually working. Most users are ignorant of things such as browser console.Dessamator (talk) 11:50, January 16, 2016 (UTC)

Question about editing using Threads / Wall api

Hi, your input would be appreciated in Thread:8646.Dessamator (talk) 11:09, February 10, 2016 (UTC)

RE: Profile Tags

Whoops, that shouldn't have happened. Thanks. I'll make sure to prevent that. Mainframe98 talk·edits 14:07, February 17, 2016 (UTC)

Script Tracker

Are you aware of any script trackers that allow developers to track who uses their scripts so they can make sure everything is working fine for other wikis? Also, it would be nice to be able to warn wikis when major changes might occur.
~Curiouscrab (talk) 21:53, February 25, 2016 (UTC)

Nothing like that exists to my knowledge. cqm 23:07, 25 Feb 2016 (UTC)

Overzealous abuse filter?

Hi there! I'm trying to save a script page at MediaWiki:MonobookHighlight.js, but it seems to be hitting the abuse filter 'NS_MEDIAWIKI Protection', which seems odd... I thought it was only to block non-CSS/non-JS pages, as mentioned above? - OneTwoThreeFall (talk) 18:34, February 27, 2016 (UTC)

Should be fixed now. Let me know if you have any more issues :) cqm 18:44, 27 Feb 2016 (UTC)
Seems all good now. Thank you! - OneTwoThreeFall (talk) 18:56, February 27, 2016 (UTC)

Few Wiki Fixes and Helpers

In my common.js I have some scripts under wiki fixes and helpers that do simple tasks such as add the small text that appears on sub articles linking to the parent article that doesn't show up now that the scripts are located in the mediawiki namespace and the parent is in the main namespace and fix the preview button for scripts (right now it just previews the script text, but doesn't run it).
~Curiouscrab (talk) 00:47, February 28, 2016 (UTC)

Your test script snippet is inherently secure via use of eval and doesn't account for the fact that cookies are limited in size or number. It's very likely to cause issues with large scripts, and I don't see a way to clear the cookie or end the test. Perhaps you'd like to look at MediaWiki:DemoScripts.js for demoing scripts instead? cqm 07:55, 28 Feb 2016 (UTC)
Yeah, I wouldn't recommend using what I have now but possibly adding more to it. As for the sub links and (recently added) the revid I think those would be helpful. I'll see what other ways one can test a script without copy-pasting or putting it in the common.js. I didn't add the cookie remove option because I figured cookies wouldn't be the way to go, and I thought maybe you might have knowledge of another way to store temporary data (other than the URL).
~Curiouscrab (talk) 15:23, February 28, 2016 (UTC)

Category:Candidates for deletion

A few pages need deletion as listed in the above category.
~Curiouscrab (talk) 20:55, February 29, 2016 (UTC)

Delete

Hi. Can you delete [[WikiGuard|this]] and [[MediaWiki:WikiGuard/VirusTotal.js|this]]? Wikia Staff have rejected the script twice over and there is no use of it. DaNASCAT has also given an official statement about the script on the talkpage, so there is no point in the script files being present on the Dev Wiki. Thanks. --Sajuuk 22:08, March 1, 2016 (UTC)

DaNASCAT is waiting for Deadcoder to reply to his message before taking any further action, which I'll respect rather than jumping the gun. ToU violations are very firmly within the jurisdiction of staff, so it's not something I'd like to get involved in unless absolutely necessary. I'll give my opinion on such things, as I have in this case, but I'm not going to impose my opinion with regards to admin actions. cqm 22:24, 1 Mar 2016 (UTC)

CSS Category

Hey! I noticed you were an admin on this Wiki, and I think there is a bit of a problem with the CSS category.

If you take a look at the Category, the pages are out of order. Usually they are listed alphabetically, but for some reason various pages are clumped together under C.

Is this intentional or some weird bug?

Thank you :) —Preceding unsigned comment added by Elexorien (talkcontribs) 22:31, March 5, 2016‎

Thanks for pointing it out :) It should be fixed now, we'll just have to wait for the page cache to clear over the next 24 hours or so. cqm 00:58, 6 Mar 2016 (UTC)

Tabber

I don't know much about how CSS works. I was playing with the code I got from TabberDesign, and I don't want the tabs to be any one set color. I want people on my wiki to be able to chose their own tab colors that best suit the page they're using the tab on. Is there any way to put variables into CSS, like a template? Or is CSS rigid? -R.A.B. 16:29, March 6, 2016 (UTC)

Rights question

Hi! I'm just wondering: as a sysop/vol dev, are you allowed the right to remove the codeeditor flag from anyone who is misusing it? Just curious. --Sajuuk 21:05, March 13, 2016 (UTC)

As an admin, yes. Generally, I'm the person that handles requests, so it's reasonable to say that I can do the opposite (assuming staff don't have any disagreement with my judgement). However, I'd be unlikely to do so without very good reason. cqm 17:54, 15 Mar 2016 (UTC)

Desktop Script Policy

Is there currently a policy on scripts that run offline that are Wikia related? I created an offline counterpart for the Status script and have successfully run it offline. It alerts users via desktop notifications when a certain user is on a specified wiki per user input onto a settings document. I might try something similar with the PrivateMessageAlert script. Offline scripts aren't mandatory for the online script to work, but are helpful. I have a safe hosting site where I can drop a zipped folder with the offline parts.
~Curiouscrab (talk) 17:50, March 26, 2016 (UTC)

At first glance, this seems exactly like what the new security regime is intended to prevent. Does the offline script in any way get loaded by the wikia? — SpikeToronto 16:21, March 31, 2016 (UTC)
I'm not really sure what you mean by offline, but I assume you mean something you run on your computer as opposed to something that runs within the confines of your browser.
There's no policy for it on Dev, although I would encourage you to host such code on github and have the appropriate installation instructions there so users can review the code for their own piece of mind. Downloading a .zip file from a random place on the internet raises concerns about the overall security of the system used, irrespective of any guarantee you, or any other author who may do the same, can provide. cqm 12:06, 1 Apr 2016 (UTC)
You can look at MultiUploader for some clues. It seems similar to what you are saying--~UltimateSupreme 18:11, April 1, 2016 (UTC)

Demo CSS

Hiya Cqm! Would you please consider adding the following to MediaWiki:Common.css?

/* Set <tt></tt> tags */
    tt { font-family: monospace; }
/* END Set <tt></tt> tags */
 
/* Set <code></code> tags */
    code { 
      color:black;
      background-color:#F9F9F9;
      border:1px solid #DDDDDD;
      border-radius:5px;
      padding: 1px 4px;
    }
/* END Set <code></code> tags */

The addition of this CSS would make it easier to demonstrate small snippets of code, etc. Thanks! :) — SpikeToronto 16:19, March 31, 2016 (UTC)

Is that a “no”, then? :P — SpikeToronto 12:27, April 21, 2016 (UTC)

As tt is deprecated, I'm not going to make any changes there. I'd be more inclined to make it non-functional as it's current styled, but that can be for another day.
I've added some styles to mirror the styling of pre tags to both skins, hopefully it'll have the effect you had in mind. cqm 12:30, 27 Apr 2016 (UTC)
That’s cool. Thanks! As for the “tt” tags, that was an accident: It seems I may have cut-and-pasted too much. :$ I only meant to ask for the re-styling of the “code” tags. Oops! — SpikeToronto 02:09, May 13, 2016 (UTC)

Mercury

Hy, Yes an answe Here would be great. —Preceding unsigned comment added by Adrianevs (talkcontribs) 17:32, 3 April 2016‎ (UTC)

Countdown no-leading-zeros

Currently using Countdown over at Acepedia's Main Page under "Countdown to E3", and the no-leading-zeros option is enabled in that countdown, but leading zeros are still showing up. Could you take a look? « SlyCooperFan1 » [message wall - contributions] 03:32, May 21, 2016 (UTC)

It seems to be working correctly based on what I can see. Could you clarify the issue you're seeing, possibly with a picture? cqm 17:04, 21 May 2016 (UTC)
For some reason, I didn't get a notification about this reply. :( Anyway, the issue is still persisting. Here's a picture: File:Countdown Leading Zeros Bug.png. « SlyCooperFan1 » [message wall - contributions] 00:12, May 31, 2016 (UTC)
There are no leading zeros in your screenshot. A leading zero would be something like "05" instead of "5". "0" would always be "0". --Saftzie (talk) 00:23, May 31, 2016 (UTC)
The code's page description disagrees with you. « SlyCooperFan1 » [message wall - contributions] 03:18, May 31, 2016 (UTC)
Then by the code's description page, there still aren't any leading zeros. Your screenshot says "14 days, 0 hours, 49 minutes, and 30 seconds." The option is "no-leading-zeros," not "no-zeros-anywhere." When days=0, then days won't be shown. When days=0 and hours=0, then days and hours won't be show, etc. --Saftzie (talk) 05:12, May 31, 2016 (UTC)

Wikimarks AF

It might be a good idea to put in an Abuse Filter to prevent people editing other people's Wikimarks page, as that is currently possible. --Sajuuk 16:46, May 24, 2016 (UTC)

AjaxRC

Can you see the message I've left to Rappy? He told me to send you the list of translations: w:c:quentum:auto-refresh.

What you need to know: 3 languages there don't have own code (Ærisk Friesk, Hessian, Arabic Tatar), some languages use two or more alphabets (like SR TT MN AZ), AR has 2 versions because two users translated it but I'll ask which is better and remove one.
~[Quəntumiið the Wise]→answer/write 11:25, May 27, 2016 (UTC)

Code editor

Is the code editor permission still in use? --Sophie 19:51, May 28, 2016 (UTC)

It still exists, but it's no longer required to edit JavaScript. Anyone can edit now. The option remains to use it again if too many people go crazy. --Saftzie (talk) 20:46, May 28, 2016 (UTC)
Some scripts (like ChatHacks) are still protected for codeeditor only, probably for being high-traffic pages from being constantly edited (and from putting a lot of wikis importing the script in risk). So I say the premission is still useful. -- Dorumin 20:51, May 28, 2016 (UTC)
There's very little that's still protected anymore, most of it is stylesheets from before the migration to the MediaWiki namespace. The userright itself is thus largely unused.
With the specific example of ChatHacks, it seems to have been a mistake caused by protecting it in the mainspace and moving it to MediaWiki: after the migration and subsequent unprotection of all moved pages (there's a bug/feature where you can't (un)protect MediaWiki: pages). Nonetheless, it's protection has now been removed so thanks for drawing my attention to it :) cqm 19:25, 31 May 2016 (UTC)

Page Move request

Can you move MediaWiki:ThreadIndicator.js/code.js to MediaWiki:ThreadIndicator/code.js? Thanks! --Sajuuk 11:51, June 4, 2016 (UTC)

Unfortunately not, moving was prohibited in the MediaWiki namespace over security concerns, but instead of preventing it between namespaces of to a non .js suffix they clamped it all down.
If you want to preserve the history, you'll need to write into staff. ALternatively you can copy the code to the new page title and manually redirect the old page to it. cqm 14:31, 4 Jun 2016 (UTC)
Are you able to delete the pages in that namespace? If so, that would be better. Preserving page history is not important, given the script hasn't been approved. --Sajuuk 16:57, June 4, 2016 (UTC)
Deleting I can do :) Just let me know when you're ready. cqm 17:12, 4 Jun 2016 (UTC)
I've copy/pasted the code on the former article to the latter article, so the former page (MediaWiki:ThreadIndicator.js/code.js) can be deleted safely. --Sajuuk 17:20, June 4, 2016 (UTC)

?useskin=oasis

Um, hello. Do you think you can help me with this problem. Apparently, whenever I don't enter ?useskin=oasis, wiki pages become the same as my mobile view, even though I'm using a laptop to do my edits. It's interfering with my editing and this hasn't happened before. Do you think you can fix it? Super Kami Guru (Swiggity swass, I'm gonna violate 'dat ass!) 04:02, June 5, 2016 (UTC)

Hey, I'm not able to help with that particular issue. I'd suggest writing into staff via Special:Contact/bug who have far more tools at their disposal to help diagnose your issue :) cqm 18:02, 8 Jun 2016 (UTC)

Linking scripts back to their main page

Are you able to edit arbitrary MediaWiki: messages here? If so, it would be very useful to have a link added to MediaWiki:Clearyourcache pointing from script pages (and CSS pages, where they're in the MW namespace) back to the mainspace documentation page; something like {{ #ifeq: {{NAMESPACE}} | {{ns:8}} | {{ #ifexist: {{ #titleparts: {{PAGENAME}} | 1 }} | For this {{ #ifeq: {{ #explode: {{PAGENAME}} | . || -1 }} | js | script's | CSS page's }} main page, see [[{{ #titleparts: {{PAGENAME}} | 1 }}]]. }} }} (though the wording might stand to be improved, and it probably wouldn't hurt to have it in an ambox or similar to visually distinguish it from the other content in that message). ディノ千?!? · ☎ Dinoguy1000 22:14, June 10, 2016 (UTC)

I've had the same thoughts, often times trying to go back to the docs is a pain. But I would suggest a simpler non-expensive version, something like:
For this {{ #ifeq: {{ #explode: {{PAGENAME}} | . || -1 }} | js | script's | CSS page's }} main page, see [{{fullurl:{{ #titleparts: {{PAGENAME}} | 1 }}}} this].
I think Cqm cannot edit the mediawiki namespace, aside from pages that a normal admin can. Although it is easy enough to request staff / helpers to make the change.

Dessamator (talk) 22:36, June 10, 2016 (UTC)

I'm not terribly concerned about the use of #ifexist here, since it's only a single use and it won't (can't) impact anything further down the page (since the pages are just JS/CSS, they won't be using any parser functions or other wiki markup, and thus don't run the danger of hitting any of the template limits, including the expensive function count). If there are other performance concerns associated with using it in a MediaWiki message, which itself is normally only displayed on other MediaWiki messages, I am unaware and to be frank it's not my concern anyways (that would fall to staff, unless and until they told me otherwise).
I wouldn't doubt it, though this wiki is a bit of a special case and so it's possible that admins here have that ability (I've probably been told whether they do or not, but it's been long enough ago that I don't remember, if so). Even if it's not the case, though, one reason I posted this here in the first place was just so I wouldn't forget the request or any of the details, and also in the off-chance that a passing staffer happened to see it before someone actually filed a ticket for it, they could take the initiative and do it themselves if they wished. ディノ千?!? · ☎ Dinoguy1000 23:21, June 10, 2016 (UTC)
It actually does affect performance see (http://dev.wikia.com/wiki/Help:ParserSpeed#How_to_make_improvements). We should preferably not use any parser functions there at all, although it might not matter much here since this isn't a "typical" wiki anyway.
There have been several occasions where Cqm has been asked to edit the MediaWiki namespace to change a something and it wasn't done because of that fact. Things might have changed though. Anyway, in the worse case scenario we can always implement it using javascript.Dessamator (talk) 00:05, June 11, 2016 (UTC)
Performance is one of the holy wars of programming, but the general advice is don't optimise until you have to. A single expensive parser function is unlikely to make much of a difference in terms of performance, if it does then that's a concern of it's own.
I'll have a look at implementing one of these though, as it's obviously a pain point. It probably won't be until week after next though. cqm 10:40, 12 Jun 2016 (UTC)

MediaWiki:Licenses

I notice that Dev uses the MediaWiki default, but Community has a custom one. In particular, Community has a license statement for screenshots of Wikia, which I think would be pretty useful for documenting scripts. I've sort of copied Wikia-screenshot from Community to Dev. It might be worthwhile making a local MediaWiki:Licenses to add it to the default. --Saftzie (talk) 10:02, June 14, 2016 (UTC)

SCSS

Do you know if there is any way to use .scss on Wikia? I remember you doing the LESS stuff on RSW so was wondering if you knew Ozank Cx (talk) 21:03, July 5, 2016 (UTC)

Traditionally, the answer is no. SASS was originally written in Ruby iirc, whereas LESS was written in JavaScript. You might notice that MediaWiki core have support for LESS rather than SASS as the SASS parser did not exist in PHP at the time.
Since then, someone has written the SASS parser in C++ which has then been compiled to JS with Emscripten, which is also what Jagex used for their apps and alog viewer. The JS compiler is at https://github.com/medialize/sass.js/ and there's a quick guide in their README.
You may have some issues with imports as I did with LESS, see comments marked with // dev wiki change in MediaWiki:Less/less.js. Otherwise, you'll probably be able to make some minor modifications to MediaWiki:Less/code.js to convert the compiler to SASS and you'll have it running in no time. cqm 06:48, 6 Jul 2016 (UTC)

Renaming and deleting pages

Hello, Cqm. You seem to be the most active administrator; therefore, I’m asking you this:

The page WHAM should be renamed to WHAM!, since the template is called “WHAM!” (with an exclamation mark) and not just “WHAM.”

The page WHAM! already exists, but it’s just a redirect. WHAM should redirect to WHAM! and not vice versa. It seems as though moving pages is disabled to regular users on this wiki, which is strange, but I nor anyone else who is not a sysop are able to move the page because of that.

I was wondering if you could just move the page when you have the time.

Also, when you have the time, you might want to look at the Candidates for deletion category, which includes several pages which should be deleted.

Thank you!
PapíDimmi (talk) 19:50, July 6, 2016 (UTC)

Thanks for pointing me in the direction of the deletion category, obviously I've been lacking in that area of late.
As for the request to move the page, I'm not entirely sure what there is to be gained from the move. Excluding it using the 'canonical' name, it potentially requires moving associated script(s) assuming we implement the automatic doc links discussed above which in turn breaks everyone's import of the script. As we have {{DISPLAYTITLE:...}} if it was a real issue, I'm strugling to see why this is necessary. cqm 20:24, 6 Jul 2016 (UTC)
Thanks for your quick response and action. About the WHAM article, I just thought that it’d be beneficial to name the page what the template is actually, officially called and not something else (however, it’s definitely not a serious issue). I didn’t realize that it could potentially break people’s import of the script, though. I’ve now added the DISPLAYTITLE magic word to the WHAM article, in order to change its title’s appearance to “WHAM!”
PapíDimmi (talk) 20:27, July 6, 2016 (UTC)

Could you help me finish the codes?

http://plantsvszombies.wikia.com/wiki/User:Zam-Bot/common.js Supreme Lord of Supremeness II (talk) 19:32, July 7, 2016 (UTC)

Seeing as you're attempting to create a chatbot in Python on a page that only supports JavaScript and have what seems to be nothing more than the example code, I'd suggest that you don't have the necessary experience to be able to run or maintain such a script in the first place. Have you considered asking someone who already has a chatbot if they'd be willing to run it on your wiki instead? cqm 07:29, 8 Jul 2016 (UTC)

Layout of list of Javascript enhancements

Apparently, some users seem to be undecided about whether to use tabbers in the List of JavaScript enhancements. Considering that is a fairly popular page and the only way to make sense of all the scripts hosted it might be a good idea to come up with a definite layout. Perhaps one that is also friendly to most browsers (including mobile).

My suggestion would be to move out all old scripts/ broken or incomplete scripts to a separate sub-page, and perhaps use the design like Global Lua Modules that is easier to understand and maintain.

See also  http://dev.wikia.com/wiki/Thread:7839 .


Dessamator (talk) 09:39, July 8, 2016 (UTC)

Script problem

Hi. The script which you provided.
$(function () { var $input = $('#wpSummary'), summary = $input.val();  if (summary.indexOf('Undo') === 0) { $input.val(summary.replace('Undo', 'Undid')); } });
It does not work with AjaxUndo nor AjaxPatrol. Is it possible to fix this? It seems like such a simple and trivial script, yet it breaks two of my the most important scripts which I use. I would really appreciate some help.
PapíDimmi (talk | contribs) 00:26 (updated 15:31), July 14, 2016 (UTC)
In short, no.
AjaxUndo relies on the message as defined on a per wiki basis. It cannot be configured via the script, nor can it be changed to suit personal preference.
AjaxPatrol doesn't do anything related to undo, so I'm not sure what you mean.
Also, as you evidently have a strong interest in personal customisations, have you considered learning to do them yourself? Many of them are simple enough that you wont need to learn much to get going. cqm 14:42, 19 Jul 2016 (UTC)
I don’t mind if the script doesn’t change the edit summary when using AjaxUndo, but I just want it to change the edit summary when using regular undo. When I used your script, clicking on the “Mark as patrolled” button took me to a different page, instead of staying on the same page (meaning that it makes the AjaxPatrol script not work). It also makes the AjaxUndo button not appear.
PapíDimmi (talk | contribs) 20:22, July 19, 2016 (UTC)
Can you swap if (summary.indexOf('Undo') { to if (summary && summary.indexOf('Undo') { and let me know if that fixes the issue? You may have to wait 5-10 mins for the cache to update. cqm 09:07, 20 Jul 2016 (UTC)
That seems to work. Thanks! By the way, why do I have to wait if I can just bypass the cache of my browser?
PapíDimmi (talk | contribs) 11:28, July 20, 2016 (UTC)
Bypassing hasn't always been 100% effective in my experience, so I tend to recommend waiting or getting the uncached version which is never cached. cqm 17:06, 3 Aug 2016 (UTC)

Wiki navigation fix

Thread:9750 yhynerson1talk 15:42, July 30, 2016 (UTC)

Some CSS for your portable infoboxes

/*** tabber customisation ***/
ul.pi-image-collection-tabs li.pi-tab-link {
    background: #fff;
    border-style: none;
    margin: 0;
    padding: 0;
}
ul.pi-image-collection-tabs li:first-of-type:after {
    content: "•";
    font-weight: normal;
    width: 1em;
    padding-right: 3px;
}

Test for tabber.

Some pages have before and after images for demonstration (and not the clickbait kind). This CSS helps bring that into the fold of the infobox.  Speedit   talk contribs  01:26, July 31, 2016 (UTC)

Which pages is it needed for? cqm 17:05, 3 Aug 2016 (UTC)

Special:JSPages link on Monobook

Hey cqm, could you add a link to Special:JSPages to MediaWiki:Sidebar? It's really annoying trying to re-find it all the time. Thanks! ディノ千?!? · ☎ Dinoguy1000 16:38, August 3, 2016 (UTC)

Of course, but is there anything else you'd like on there? I notice it's a bit sparse compared to the oasis nav. cqm 16:39, 3 Aug 2016 (UTC)
A link to quickly switch to the Oasis skin on the current page (and maybe one to do so for mobile, too) would be nice, but other than that I'm not sure what links might be needed. There's probably some pages that would be useful when linked from the sidebar, but I've never gone exploring long enough to have a list of such pages in mind. ディノ千?!? · ☎ Dinoguy1000 16:42, August 3, 2016 (UTC)
Both done, let me know if there's any more you think would be useful. cqm 17:35, 3 Aug 2016 (UTC)

Codeeditor Request

I have been waiting for this wiki to accept my request, but I have been waiting for 9 days. Supreme Lord of Supremeness II 11:26, August 12, 2016 (UTC)

LangSwitch

Hey, Cqm! I'm trying to use the Template:LangSwitch here, but for some reason it does not work. Can you help me? I'll be very grateful! TheCreedX (talk) 21:33, August 17, 2016 (UTC)

Translations

Hey Cqm, I've been trying to get my little script to take translations and I've gotten a little stuck. I've taken a look around a few of other people's scripts and tried to get it to work, but can't get the hang of it. I'm also not getting any errors when running in the console, so I'm very confused. Can you tell me where/what I'm doing wrong?

$( document ).ready(function() {
 
var translations = {
	en:       'Discussions',
	it:       'discussioni'
},
 
 linkText = (typeof window.DiscussionText === 'string' && window.DiscussionsText) || translations[mw.config.get('wgContentLanguage')] || translations.en;
 if (mw.config.get('skin') === 'oasis') { 
    $('<li class="subnav-2-item"><a class="subnav-2a" href="/d/">' + linkText + '</a></li>').appendTo('ul.subnav-2.accent.firstChild');
} else {
    $('#p-tb ul').append('<li><a href="/d/">' + linkText + '</a></li>'); // putting it in the toolbox seems sensible, feel free to ask to move
}
});

Thanks! — Original Authority (talk) 22:48, August 22, 2016 (UTC)

This script itself seems to work in terms of adding the link and giving the correct text. What problems are you seeing?
It's a little off-topic, but I'd be inclined to not support setting window.DiscussionText. I've only ever seen it done for AjaxRC, and that was down to legacy reasons. If you do decide to keep it though, don't forget to escape it with mw.html.escape(linkText) to prevent XSS issues. If you're not familiar with XSS, it's essentially where someone inserts a script tag, any tag with an onclick attribute or an a tag with a javascript: href all of which can contain malicious javascript. cqm 07:04, 23 Aug 2016 (UTC)
The problem I'm seeing is that it will not run inside the browser. When I run the code, I get "cannot read 'ready'", but if I remove the $(document).ready(function() { part and run in the browser, it works fine. My theory is that: when using $(document).ready the code will not run until the document is ready for example when first visiting a page. So it should work if used through actual import, right?
Also, thanks for the heads up, I removed that portion from the code. — Original Authority (talk) 10:54, August 23, 2016 (UTC)

Around Wikia's network

Random Wiki