MediaWiki talk:Gadget-VisualFileChange.js/Archive/2013
 | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
libjq-proceed-title: Parse error
When trying to nominate this user's uploads for deletion: Special:Contributions/Esteezy, the "Execute" button is always greyed out and on mouseover gives the error:
- libjq-proceed-title: Parse error at position 8 in input: Proceed [Enter] in single-line text fields
Seems pretty obscure, I've not seen it before. Cheers, moogsi (blah) 17:48, 30 January 2013 (UTC)
- I have also seen this message sometimes in the last days. Once I had to change the syntax (replacing text), but all the other times the images have been processed normally. --Funfood ␌ 17:54, 30 January 2013 (UTC)
- Something whith mw.message changed. Are you sure you entered a reason with at least 11 letters? -- Rillke(q?) 18:22, 30 January 2013 (UTC)
- Yes that was the problem... somehow the error caught my eye before I had finished filling in the form. I reloaded and put something like 'ds0rnynrt' in the reason box because I thought it would only check if it was empty :) Thank you and sorry for the hassle :) --moogsi (blah) 20:04, 30 January 2013 (UTC)
- This section was archived on a request by: Rillke(q?) 20:53, 30 January 2013 (UTC)
Empty lines
Would it be possible to restrict the empty lines on top of deletion requests (example) to one or to remove them entirely? --Leyo 08:59, 5 February 2013 (UTC)
{{subst:nld}}
This tool supports a number of different tags, such as {{Delete}}, {{Copyvio}}, {{subst:npd}}, {{subst:nsd}} and {{subst:dw-nsd}}, but it doesn't seem to support {{subst:nld}}. Could that be added? --Stefan4 (talk) 15:22, 8 March 2013 (UTC)
\n
'nl': { tag: "{{subst:nld}}", summary: "Missing a valid [[Commons:Copyright tags|copyright tag]] (/[[Commons:Licensing|license]])." },
Please add \n at the end of the text which is added to the file information page. --Stefan4 (talk) 19:39, 15 May 2013 (UTC)
- This section was archived on a request by: Leyo 14:31, 19 November 2013 (UTC)
Minor edits
Deletion nominations shouldn't be minor edits. For example, this is bad. If you make a minor edit to a talk page, then the uploader won't get an e-mail notification. If the uploader doesn't visit Commons regularly, he may therefore not notice anything until after the file has been deleted. --Stefan4 (talk) 23:46, 3 November 2013 (UTC)
Colon
A colon is needed somewhere in the source code to avoid errors like this. --Stefan4 (talk) 13:49, 19 November 2013 (UTC)
User:OgreBot/Uploads by new users/2013 December 13 00:00
Use the "full page name" option to get all files used on this page. The last file it loads is File:Bari teaches physics.jpg, after that I get a red error message: "Error: -- NO TASK DESCR. FOR mdFormattNumber PLEASE ADD IT -- ##### TypeError: pg.revisions is undefined" --Stefan4 (talk) 13:22, 13 December 2013 (UTC)
- That's because the file description of File:Délégation générale du Québec à Londres 2013.JPG is missing. Interestingly, the error message on this page is also in the wrong language for me: La révision n° 0 de la page intitulée « Délégation générale du Québec à Londres 2013.JPG » n'existe pas. before purging and now using &action=purge&uselang=qqx it is
(missing-revision: 0). - I am going to handle this in VFC and gallery tool and will also report the 2 bugs to bugzilla:. -- Rillke(q?) 13:47, 13 December 2013 (UTC)
- Fixed with version 0.9.45.3. Purge your browser's cache in order to get the latest version of VFC. -- Rillke(q?) 14:57, 13 December 2013 (UTC)
- This section was archived on a request by: Rillke(q?) 14:57, 13 December 2013 (UTC)
Numbering
Is there a strong reason why the file numbering starts at 0 instead of at 1? The latter would be more intuitive. --Leyo 12:32, 31 October 2013 (UTC)
Spaces and RegExpr
When clicking for conversion to RegExpr any spaces remain unaltered. Does this mean that “ ” is identical to “\s”? An advantage of converting spaces, too, would be that “\s” could quickly be modified to e.g. “\s?”, “\s*” or “\s+”. --Leyo 19:14, 19 November 2013 (UTC)
- “ ” is a space (char code 32), while “\n” (char code 10), for example is a new line. Both are matched by “\s”. So converting any space into \s would have possibly unwanted side-effects. You can also write " *". This is perfectly valid in JavaScript RegExps.
/^ *$/.test(' ')→ True/^ $/.test(' ')→ False/^\n*$/.test(' ')→ False/^\s*$/.test(' ')→ True
- -- Rillke(q?) 21:18, 19 November 2013 (UTC)
- Thank you for the explanation. Is the above applicable to any RegExpr incl. pywikipedia? --Leyo 14:01, 20 November 2013 (UTC)
- Frankly, I don't know. I could tell you for VB(A) 6.0 but that would not help, I guess. I think the above would comply with the standard PCRE. However, note that when specifying the multiline flag (
/^RegExp$/m), the RegExp may behave differently. I do never use the m-flag and I did not use Python, yet. -- Rillke(q?) 15:02, 20 November 2013 (UTC)- @Leyo: python does work with this:
re.match(r'^ *$', ' ').group(0)
→ ' 're.match(r'^ $', ' ').group(0)
→ AttributeErrorre.match(r'^\n*$', ' ').group(0)
→ AttributeErrorre.match(r'^\s*$', ' ').group(0)
→ ' '
- --Zhuyifei1999 (talk) 15:54, 20 November 2013 (UTC)
- Thanks, but that's a bit cryptic for me. I am a user of existing python scripts such as replace.py only. --Leyo 18:40, 21 November 2013 (UTC)
- @Leyo: python does work with this:
- Frankly, I don't know. I could tell you for VB(A) 6.0 but that would not help, I guess. I think the above would comply with the standard PCRE. However, note that when specifying the multiline flag (
- Thank you for the explanation. Is the above applicable to any RegExpr incl. pywikipedia? --Leyo 14:01, 20 November 2013 (UTC)
- This section was archived on a request by: Rillke(q?) 13:00, 15 June 2014 (UTC)