User talk:Remember the dot/Archive/2017

https://de.wikisource.org/wiki/Der_Pentateuch,_%C3%BCbersetzt_und_erl%C3%A4utert/Genesis/4
Hello Remeber the dot,

we thank you for your contribution at de:ws. Unfortunatly we can not keep your article in the current state. The scan is not really provided. We need fat least the scan on Commons. Otherwise we will have to delete the article. If you have further questions please contact me at.

Thanks --THE IT (talk) 15:47, 21 January 2017 (UTC)

Protection of Template:Mod
Can you lower protection to "template protection", so "template editors" can edit Template:Mod? I appreciate it. --George Ho (talk) 03:25, 16 February 2017 (UTC)


 * Is there a problem with that template? —Remember the dot (talk) 03:49, 18 February 2017 (UTC)

Syntax highlighter
text text template | returns a "|" and turns the construction into a table. How can I avoid infinite "parameter" highlighting on a text? ( In the same way it is used in many articles and I can not change a large number of articles just because of the highlighter, but maybe somehow you can improve your highlighter (it is not necessary to change your main script, I can use this change only in my local copy of your script )) --Sunpriat (talk) 17:56, 14 May 2017 (UTC)


 * Thanks for the example. Unfortunately, I don't think I can fix this in the highlighter. You could use HTML tags instead:


 * —Remember the dot (talk) 21:52, 14 May 2017 (UTC)

Quit working
I've been using syntax highlighting with few problems until now. The last couple days highlighting doesn't work at all. No colors, just black and white pages of code. I tried disabling extensions and plugins but that didn't help. I'm using Firefox 39 for Mac OS 10.6.7 I refreshed the browser, deleted cookies, logged in and out of Wikipedia, and did some maintenance on my computer, but nothing has helped. This has been a really great tool for me. I hope it will work again. –Vmavanti (talk) 03:11, 1 July 2017 (UTC)
 * I have had a similar problem, except that it works sometimes. It is not working on this page, for example. – Jonesey95 (talk) 03:32, 1 July 2017 (UTC)
 * Likewise, it's not been working for me either for the last couple of days. (Pale Moon (web browser) v27.3.0 on Windows 7, no recent changes to browser or Wikipedia profile settings that I'm aware of.) Now that it's not working I'm reminded of how useful it is. Mitch Ames (talk) 02:03, 2 July 2017 (UTC)

–Vmavanti (talk) 01:10, 3 July 2017 (UTC) –Vmavanti (talk) 17:13, 3 July 2017 (UTC)
 * Are you all using unsupported versions or derivatives of Firefox? I have Firefox 54 and am not seeing any problems. The most recent version that Mozilla supports is Firefox 52. —Remember the dot (talk) 23:55, 2 July 2017 (UTC)
 * No, I can't go any farther than 39. It does seem to work on Opera 25.
 * I'm using Pale Moon (web browser) v27.3.0 - which is the current version - on Windows 7. The problem appears to be cache-related. Specifically, it only failed when I was editing a page that I had already edited, and when I cleared the cache or reloaded the page with Ctrl-Shft-R, the syntax highlighter started working again. It worked for a while but then started misbehaving again. I deleted the entire "%LOCALAPPDATA%Moonchild Productions" (not %APPDATA%...) and it seems to be working properly again. Although it has failed once or twice when I clicked Edit (the wikipedia page) while it was still loading the article page or history. Mitch Ames (talk) 11:25, 3 July 2017 (UTC)
 * I've seen it work again but only briefly, perhaps randomly. Most of the time it doesn't. I tried it on Mint with the latest version of Firefox (for Mint), but it didn't work. I'm not sure what to do now. Syntax highlighting is almost a necessity for me. I hate to use Opera. My connection is already so slow.

–Vmavanti (talk) 23:16, 7 July 2017 (UTC)
 * I was able to reproduce this a couple of times by refreshing the editing page repeatedly. I just changed the way the syntax highlighter loads, but I don't know if it will make a difference. Please tell me whether the highlighter is more or less reliable for you now. —Remember the dot (talk) 05:26, 6 July 2017 (UTC)
 * It's still working intermittently for me. The success or failure is not consistent or repeatable enough to say whether it's any better or worse since your post of 05:26, 6 July 2017 (UTC). However the workaround of refresh-bypassing-cache still appears to work. Mitch Ames (talk) 12:11, 7 July 2017 (UTC)
 * No change.


 * I'm baffled. Some ideas:
 * If you press Ctrl+Shift+K to open the Web Console, does it display any suspicious errors?
 * If you run the command  in the Web Console, what does it say, "interactive" or "complete"?
 * If run the command  in the Web Console, does highlighting appear? (Don't do this on a page that already has syntax highlighting or it will freeze your browser.)
 * —Remember the dot (talk) 02:35, 8 July 2017 (UTC)


 * With Pale Moon, web console says (when editing this section on this page):

Use of getUserData or setUserData is deprecated. Use WeakMap or element.dataset instead. requestNotifier.js:53:0 TypeError: $.client is undefined index.php:1:13074 "Use of "wgServer" is deprecated. Use mw.config instead." load.php:153:968 "Use of "wgArticlePath" is deprecated. Use mw.config instead." load.php:153:968 "Use of "wgScriptPath" is deprecated. Use mw.config instead." load.php:153:968 "Use of "wgCurRevisionId" is deprecated. Use mw.config instead." load.php:153:968 "Use of "wgPageName" is deprecated. Use mw.config instead." load.php:153:968 POST XHR https://en.wikipedia.org/w/api.php
 * The "deprecated" warnings appear even when syntax highlighter is working, but the TypeError only appears when syntax highlighter is not working.
 * document.readyState says "complete"
 * mw.loader.load(...) causes the highlighting to appear. If I then refresh the page (F5), the highlighting stays and I see the same warnings as above but not the TypeError.
 * Note that I can reproduce the problem (although it may take a few attempts to do so) with Pale Moon Portable (32-bit) and the default browser profile. It might be worth your trying to reproduce the problem with that same browser.
 * Thanks for your continued time and effort to track down the problem. It really is a wonderful tool. Mitch Ames (talk) 06:14, 8 July 2017 (UTC)


 * That was extremely helpful, thank you. I googled the error message and found a discussion of a very similar problem on Meta. I just altered the highlighter to load the jquery.client module before executing. I expect that this will resolve the whole problem :-) —Remember the dot (talk) 07:17, 8 July 2017 (UTC)

–Vmavanti (talk) 17:13, 8 July 2017 (UTC)
 * It worked! That is just so great. Not only did you make this great tool, but you fixed it within days of my reporting a problem that few people have. If only everyone had your skill. Thanks v. much. It makes a huge difference in my editing.
 * It also appears to be working reliably now for me. Thanks again. Mitch Ames (talk) 00:08, 9 July 2017 (UTC)