User talk:Technical 13

File:Microsoft Windows logo (Pre-XP).svg has been marked as a possible copyright violation. Wikimedia Commons only accepts free content—that is, images and other media files that can be used by anyone, for any purpose. Traditional copyright law does not grant these freedoms, and unless noted otherwise, everything you find on the web is copyrighted and not permitted here. For details on what is acceptable, please read Commons:Licensing. You may also find Commons:Copyright rules useful, or you can ask questions about Commons policies at the Commons:Help desk. If you are the copyright holder and the creator of the file, please read Commons:But it's my own work! for tips on how to provide evidence of that. The file you added has been deleted. If you have written permission from the copyright holder, please have them send us a free license release via COM:VRT. If you believe that the deletion was not in accordance with policy, you may request undeletion. (It is not necessary to request undeletion if using VRT; the file will be automatically restored at the conclusion of the process.) Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing. Afrikaans ∙ العربية ∙ asturianu ∙ azərbaycanca ∙ беларуская ∙ беларуская (тарашкевіца) ∙ български ∙ ပအိုဝ်ႏဘာႏသာႏ ∙ বাংলা ∙ català ∙ čeština ∙ dansk ∙ Deutsch ∙ Deutsch (Sie-Form) ∙ Zazaki ∙ Ελληνικά ∙ English ∙ español ∙ euskara ∙ فارسی ∙ suomi ∙ français ∙ galego ∙ עברית ∙ hrvatski ∙ magyar ∙ հայերեն ∙ Bahasa Indonesia ∙ italiano ∙ 日本語 ∙ 한국어 ∙ Lëtzebuergesch ∙ македонски ∙ മലയാളം ∙ मराठी ∙ Bahasa Melayu ∙ Malti ∙ မြန်မာဘာသာ ∙ norsk bokmål ∙ Plattdüütsch ∙ Nederlands ∙ norsk nynorsk ∙ norsk ∙ polski ∙ português ∙ português do Brasil ∙ română ∙ русский ∙ sicilianu ∙ slovenčina ∙ slovenščina ∙ српски / srpski ∙ svenska ∙ தமிழ் ∙ тоҷикӣ ∙ ไทย ∙ Türkçe ∙ українська ∙ oʻzbekcha / ўзбекча ∙ Tiếng Việt ∙ 中文（简体） ∙ 中文（繁體） ∙ +/−

 

how do I fix it? Evrik (talk) 01:32, 19 January 2015 (UTC)[reply]

• Hello there Evrik! I'm going to need a little more information. Are you asking for help fixing User:Evrik/monobook.js? Is this in response to a message I have posted on the talk page of your custom script page (note that it would be one of 0, so I have no idea if yours is one of the pages)? If so, I'd be happy to take a look tomorrow. :) — {{U|Technical 13}} ^{(e • t • c)} 03:11, 19 January 2015 (UTC)[reply]

Help: yes

Message: yes

Please help. Evrik (talk) 03:12, 19 January 2015 (UTC)[reply]

• Okay, Evrik. I looked at your monobook, and all you need to do is blank that page and enable the gadget that should be maintained for you. So, go to Special:Preferences#mw-prefsection-gadgets, scroll to the bottom and you'll find a section labeled Tools for authorized users, check the box next to PermissionOTRS: Automatically add {{PermissionOTRS}} or {{OTRS received}} to a media file. [talk]  and then click the Save button at the bottom of the page. Once that is done, you can go to User:Evrik/monobook.js, blank the page, and click save. Let me know if you need any more help. :) — {{U|Technical 13}} ^{(e • t • c)} 14:43, 19 January 2015 (UTC)[reply]

Hi - is [1] correct, or do I need to do more? Pek the Penguin (talk) 07:51, 19 January 2015 (UTC)[reply]

• Hello Pek the Penguin! You need more. I need to ask exactly what this script is suppose to do though. What is "quickbar"? Where does this add a link? Can you give me an example page where this is suppose to work? Thanks! — {{U|Technical 13}} ^{(e • t • c)} 14:28, 19 January 2015 (UTC)[reply]

I think it's a legacy when we could still use Classic Skin - it added extra links to the side bar. It's probably redundant now, but I take the view "if it ain't broke, don't fix it". Pek the Penguin (talk) 20:34, 19 January 2015 (UTC)[reply]

• What links did it add, are they otherwise available now, and what skin are you using now? I could probably update the script for you if you desire. I just had to ask because I couldn't find any thing on any page with a "quickbar" id, which is what that script attempts to attach to. If you don't wish to use an updated script for your current skin, you may want to blank it and request deletion to prevent the broken script (which is adding error messages to your JS console) from breaking all of your code in the next year or so. Happy editing! — {{U|Technical 13}} ^{(e • t • c)} 23:33, 19 January 2015 (UTC)[reply]

العربية ∙ বাংলা ∙ čeština ∙ dansk ∙ Deutsch ∙ Deutsch (Sie-Form) ∙ English ∙ español ∙ فارسی ∙ suomi ∙ français ∙ Frysk ∙ עברית ∙ हिन्दी ∙ magyar ∙ íslenska ∙ italiano ∙ 日本語 ∙ 한국어 ∙ македонски ∙ മലയാളം ∙ norsk bokmål ∙ Nederlands ∙ norsk nynorsk ∙ norsk ∙ occitan ∙ polski ∙ português ∙ русский ∙ sicilianu ∙ slovenščina ∙ svenska ∙ Türkçe ∙ українська ∙ Tiếng Việt ∙ 简体中文 ∙ 繁體中文 ∙ +/−

---

 

An edit you made to MediaWiki_talk:Gadget-GoogleTranslate.js seemed to be a test, and has been reverted or removed. Please use the sandbox for any other tests you want to do. Feel free to visit the community portal if you would like to learn more about contributing. Thank you!

The page your message is about is entirely empty. The deprecation messages left are broad and unhelpful. Please improve the script or search algorithm before you are going to continue. I say this as a Wikimedia Commons administrator who usually cared for edit protected requests on script pages and seeing the category spammed like this, doesn't make things easier. -- Rillke^(q?) 15:47, 19 January 2015 (UTC)[reply]

• Actually, Rillke, it wasn't a test. I understand your frustration, and I'm working on clearing most of these requests out of the edit protected category as we speak. I'm replacing them with just the Category:JavaScripts using deprecated elements category which itself will be a subcat of edit protected requests to be less spamy. As for that page being empty, MediaWiki_talk:Gadget-GoogleTranslate.js#Bug fix <-- that is what triggered the message to be posted there. The goal was to tag all script talk pages where addOnloadHook was mentioned on the talk page or used in the script to this category so that they could be categorized in a way that they could be gone through and addressed by a human. I'd be happy to work with you further to clean these up. Thank you for bringing your concern to my attention on my talk page and happy editing! — {{U|Technical 13}} ^{(e • t • c)} 16:18, 19 January 2015 (UTC)[reply]
  • What is the purpose of matching text from the talk page? -- Rillke^(q?) 16:28, 19 January 2015 (UTC)[reply]
    • Indicative of there likely being other issues that need to be addressed still in the script. There are a lot of things listed on MW:ResourceLoader/Legacy JavaScript and chances are, some of them were missed in most scripts. It is also useful to have an idea of what scripts need jQuerification and to be brought up to coding conventions once the deprecations have been gone through. :) — {{U|Technical 13}} ^{(e • t • c)} 16:33, 19 January 2015 (UTC)[reply]
      • To be frank, I doubt that any script needs jQueryification if it runs fine in the browsers it claims to support, otherwise. are a lot of things - I know - and that's why a generic message à la "There could be something unspecified wrong with your code", is not helpful, while "<specific issue> might cause a problem" is. -- Rillke^(q?) 16:37, 19 January 2015 (UTC)[reply]