User talk:This, that and the other/For the Common Good/Archive 3

[bug] edit summary

depending on the "home wiki" which is set up in the preferences, FTCG should change it's edit summary to [[:w:WP:FTCG]] or [[:w:en:WP:FTCG]] or [[:en:WP:FTCG]], see the bug and the redlink at my contributions at Wikibooks: b:Special:Contributions/wikignome. Regards, mabdul 20:31, 30 October 2012 (UTC)

Ah, good point, will do. — This, that, and the other (talk) 00:15, 8 November 2012 (UTC)

Okay, I've put out FtCG 1.0.4.7 with the following improvements since 1.0.4.5:

• Google image search is now localised to your language
• Useless and broken "decline transfer" feature removed
• Simple detection of a "raw description" now automatically placed inside {{information}} (thanks to Bulwersator)
• Fix edit summary link to work across all wikis
• Ignore warnings checkbox now works properly
• Extra templates are flagged as "potential problems" on en.wikipedia: {{c-uploaded}}, {{deleted on Commons}}; also {{ffd}}, {{bots}} are removed from the Commons source (thanks to Bulwersator again!!)

— This, that, and the other (talk) 00:34, 8 November 2012 (UTC)

User page link

When moving files from en.wikivoyage-old.org, the tool uses {{uv|Username|en:}} in the original upload log although it should be {{uv|Username|voy:en:}}. --Stefan2 (talk) 01:07, 12 November 2012 (UTC)

Yeah, I tried to use FTCG on Wikivoyage too (I am "Another WTS gnome" on WTS), but ran into a few problems. At the time I didn't have spare time to fix it up, and now there is really no point. — This, that, and the other (talk) 01:50, 22 November 2012 (UTC)

One problem is that Wikivoyage doesn't support HTTPS. If you haven't done this, remember to disable HTTPS in the FTCG settings. Another problem is that Wikivoyage Shared uses an unexpected location for api.php, so FTCG only works on WTS and the language versions. The "wts" language code for descriptions is only a minor problem. It's not worse than the "meta" language code I've got when copying files from Meta. --Stefan2 (talk) 15:55, 22 November 2012 (UTC)

Deletion prevents loading Commons page

I used to have my FTCG settings set to open the Commons page after transfer (so I can categorize with HotCat, etc.) and it used to work great, but now that I'm an admin and have FTCG set to delete after transfer, it just pops a box that says "Looks good to me" and doesn't open the Commons file page. It does delete the en.wp copy with the correct reasoning, at least, and on the whole, if I can only have one or the other, I'd rather have it delete, but it would be Really Nice if it would do both. —Darkwind (talk) 07:49, 3 January 2013 (UTC)

This should be fixed in version 1.0.4.8 (which I have not released to autoupdate for various internal reasons, but you can still download it at http://atlight.github.com). Thanks for reporting it! — This, that, and the other (talk) 08:40, 4 January 2013 (UTC)

1.0.5 released, and Norton issue

FtCG version 1.0.5 is out; it includes various minor improvements to localisation (both language files and local wiki data files), as well as a "preview" feature (requested above).

On my system, Norton Internet Security doesn't seem to like FtCG. Every so often, when I run FtCG, the SONAR component detects it as a "security risk" and deletes it from the system. I can assure you there is nothing malicious about FtCG! If you have an issue with Norton and FtCG, please tell me, so I can report it to Norton. — This, that, and the other (talk) 09:44, 5 January 2013 (UTC)

Bug in parsing of {{GFDL-self-with-disclaimers}} license

Hi. I used your fantastic tool to move File:Skroce.jpg to File:Steve Skroce.jpg on commons. FTCG converted {{GFDL-self-with-disclaimers}} to {{GFDL-user|Toquinha|en-with-disclaimers|migration=relicense}} ([1]) i.e. putting "-with-disclaimers" in the wrong place. Thanks for the tool! Awesome stuff. Best regards, Storkk (talk) 16:53, 5 February 2013 (UTC)

(Note: using version 1.0.5) Storkk (talk) 17:06, 5 February 2013 (UTC)

This is bizarre; it works fine for me, converting it to {{GFDL-user-en-with-disclaimers|Toquinha|migration=relicense}}. I added this tag some time last year, and certainly all versions sine 1.0.4.5 have had the correct logic for GFDL-self-with-disclaimers. Are you sure you are not using a custom "local wiki data" file that is out of date? — This, that, and the other (talk) 04:15, 6 February 2013 (UTC)

Pretty sure - I don't have any local wiki data files that I know of. My complete ForTheCommonGood.cfg is:

LocalDomain=en.wikipedia
LocalUserName=Storkk
LocalSysop=false
CommonsUserName=Storkk
UseHttps=true
LogTransfers=false
OpenBrowserAutomatically=false
AutoUpdate=true
LocalWikiData=
CurrentSourceOption=Category3
SourceCategory=
SourceTextFile=

It has happened a few times in my transfers, and the version I downloaded from github yesterday (1.0.5) is the first version I've tried. Storkk (talk) 12:56, 6 February 2013 (UTC)

It's currently happening for File:Fenwickbeach.JPG, which I won't transfer so you can check it. Storkk (talk) 13:03, 6 February 2013 (UTC)

I have had the same problem with plenty of images. See also User talk:This, that and the other/For the Common Good/Archive 2#Disclaimer. --Stefan2 (talk) 13:24, 6 February 2013 (UTC)

Here's what FTCG spits out for me on Fenwickbeach.JPG:

Extended content

== {{int:filedesc}} == {{Information |Description = {{en|1=Photo by Kit Conn}} |Date = {{according to EXIF data|2006-02-19}} |Source = {{own}} <!-- change this if not own work --> |Author = [[:en:User:Conn, Kit|]] |Permission = |Other_versions = }} == {{int:license-header}} == {{GFDL-user-en-with-disclaimers|Conn, Kit|migration=relicense}} [[:en:it:File:Fenwickbeach.JPG|it:File:Fenwickbeach.JPG]] == {{Original upload log}} == {{transferred from|en.wikipedia||[[:en:WP:FTCG|For the Common Good]]}} {{original description page|en.wikipedia|Fenwickbeach.JPG}} {| class="wikitable" ! {{int:filehist-datetime}} !! {{int:filehist-dimensions}} !! {{int:filehist-user}} !! {{int:filehist-comment}} |- | 00:24, 21 March 2006 || 2,592 × 1,944 (1,283,372 bytes) || {{uv|Conn, Kit|w:en:}} || ''(Photo by Kit Conn)'' |}

Obviously the spurious interwiki would have to be removed by hand, but other than that it seems fine. I can't understand why this works for me and not for other people. — This, that and the other (talk) 04:38, 8 February 2013 (UTC)

0000-00-00 (according to EXIF data)

See Commons:File:Plack.JPG. Maybe you could ignore the EXIF date if it makes no sense? --Stefan2 (talk) 18:33, 17 February 2013 (UTC)

Good point. I'll make FTCG ignore all dates that start with "0000". Others could possibly be useful (e.g. 0008-02-16 might really be 2008). — This, that and the other (talk) 09:14, 18 February 2013 (UTC)

WP:FTCG link

I thought that link was fixed? I was moving images from ITWN, but the link is still directing to the local "WP:FTCG" which doesn't exist of course. Moreover can we get an option wether the "File:" prefix should be included in the {{NowCommons}} tag and if there is only a localizied version (text box to include the name) of that template? (Often without caps, sometimes with/out a whitespace...) mabdul 09:17, 19 February 2013 (UTC)

Are you sure you are using the latest version of FTCG? Woah, sorry, massive bug. I'll upload 1.0.5.1 very soon.

You can change the name of the NowCommons template by using local wiki data files. See User:This, that and the other/For the Common Good/Local wiki data. — This, that and the other (talk) 23:59, 21 February 2013 (UTC)

Metadata

What happened to this file? n:it:File:I3010019.jpg --> File:Manifestazione.jpg The Metadata are "broken" and somehow English Wikipedia wikilinks were added? Please fix it! XD mabdul 10:40, 21 February 2013 (UTC)

That's actually a bug with Commons' metadata handling. Perhap report it to the village pump there. — This, that and the other (talk) 00:01, 22 February 2013 (UTC)

Feature requests

Can we get an additional option "Open file page on original wiki after a successful transfer"?

Just curious... why would you need it? — This, that and the other (talk) 04:08, 26 February 2013 (UTC)

Crosschecking if everything is correctly moved; especially the license - although most wikis do use the same markup for e.g. {{CC-BY-SA}}, it is not working everywhere correctly, language changes, versions etc... mabdul 06:23, 26 February 2013 (UTC)

OK. — This, that and the other (talk) 22:10, 27 February 2013 (UTC)

Can we also get any highlight when there a talk page is on the original wiki? (of course before transferring the image) mabdul 14:47, 25 February 2013 (UTC)

Ah, I had never thought of the file talk page, since they are not used much here on enwiki. I'll look into this for you. — This, that and the other (talk) 04:08, 26 February 2013 (UTC)

Oh my grammar... Yesterday was a bad working day. Yeah, I know that there was an image at ITWN which needs first an OTRS check discussed at the talk page (original deleted on Commons); but I had to double check the file on ITWN because of the missing talk page. BTW - Thanks for the great tool! mabdul 06:23, 26 February 2013 (UTC)

I plan to add a "talk page" check when the talk page is longer than 120 bytes, because of WikiProject tags on en. Does that sound good? — This, that and the other (talk) 22:10, 27 February 2013 (UTC)

Should be good. OTOH you could easily check if the talk page consists only on templates and whitespaces/CRLF. But I'm happy with everything. ;-) As I said: It is a seldom case, but needed: In my case the image was already moved (or original uploaded) to commons and was later deleted. I dunno if the OTRS ticket was added after that or not, but there was an indication on the talk page! (And I saw it luckily before uploading) mabdul 06:49, 28 February 2013 (UTC)

OK, you can go to http://atlight.github.com and get 1.0.5.2. You need to tweak the setting using a local wiki data file: FileTalkMinimumSize=120 (a number in bytes). Use 0 to get a warning when a talk page of any size exists.

I just realised I didn't put the "automatically open file page on source wiki" thing in. Oh well, just give this a go and if it works I can go from there. — This, that and the other (talk) 08:47, 4 March 2013 (UTC)

I see only 1.0.5.1. Is it only incorrectly named or did you miss to upload it there? XD mabdul 09:33, 4 March 2013 (UTC)

Yeah sorry, I'm a bit discombobulated right now. 1.0.5.2 is up. — This, that and the other (talk) 07:09, 5 March 2013 (UTC)

And it even includes the new checkbox in the settings dialog. Have fun with it!! — This, that and the other (talk) 08:37, 5 March 2013 (UTC)

Dollar sign in file name

Howdy. I'm not sure if it is a problem with the template, or your tool, but if the file has a dollar sign in it, the words "Copy to Wikimedia Commons" get inserted into the template.--Rockfang (talk) 22:16, 19 May 2013 (UTC)

Hello there Rockfang, I hope you are enjoying using FtCG! This problem is caused by the string "$1", which has a special meaning in this case. I'll see if I can stop this from happening. Thanks for reporting the bug. — This, that and the other (talk) 03:26, 21 May 2013 (UTC)

File already available in Commons

Hey, I tried to transfer a file to Commons but I got the following error: "Wikipedia is on read-only mode" (or something like that). I restarted FtCG and tried again, but this time it messaged me: "this file is already availbale in Commons". I checked the original article where this file is used and it says that the file is ready to transfer, but I already have transferred it. Could you please help me what to do now. I have used the FtCG before with another file and it worked perfectly. Thank you — Preceding unsigned comment added by Tunderize (talk • contribs) 16:02, 20 June 2013 (UTC)

In some cases, the tool fails to add a {{NowCommons}} template on Wikipedia. When this happens, just add {{subst:ncd|filename on Commons}} manually. --Stefan2 (talk) 00:12, 23 June 2013 (UTC)

An important update

Due to gerrit:79773 (the reason for which is unclear), the naming scheme for login session cookies on Wikimedia wikis changed yesterday. This meant that any attempt to transfer a file sing FtCG gave the message "Login failure: NeedToken". The latest release (1.0.5.6) fixes this issue.

As a result of this change, versions of FtCG prior to 1.0.5.6 will no longer function. If you have automatic updates turned off, please update manually at http://atlight.github.io. — This, that and the other (talk) 07:37, 20 August 2013 (UTC)

Updating

Thanks for your program. It could be really nice if there was a link I could press when its saying there is an update. Christian75 (talk) 19:03, 23 August 2013 (UTC)

Thanks for your suggestion. I've just added this feature to FtCG, but there is no point releasing a new version solely for this feature. So you'll have to wait, unfortunately.

I hope you are enjoying using FtCG! — This, that and the other (talk) 02:47, 24 August 2013 (UTC)

This is what is looks like... I kept the {{imbox}} visual metaphor going. — This, that and the other (talk) 11:17, 24 August 2013 (UTC)

Nice, :-) Christian75 (talk) 17:59, 26 November 2013 (UTC)

Strange behaviour of ESC key

If you try to move a non-free file to Commons, then this message pops up. If you press the ESC key, then the program interprets this as "yes". The program should probably assume "no" instead. I just tested this with File:Delrey-logo.png which I moved to Commons as File:Del Rey logo.png. --Stefan2 (talk) 15:48, 25 August 2013 (UTC)

When I do that (on Windows 7), the ESC key does nothing. Are you using Wine and/or Mono? If so, this seems like a bug in one or other of those frameworks. I could probably work around this behaviour in the code, but to do so I would need you to run this test program and report the results. — This, that and the other (talk) 11:37, 26 August 2013 (UTC)

Yes, I'm usually using Wine. The program does this: enter = yes, click = yes/no (depending on button), escape = cancel. --Stefan2 (talk) 00:12, 27 August 2013 (UTC)

I thought as much. FtCG checks whether the result of the dialog box is No, and if it is something else, it goes ahead and transfers the file. On Windows the only two possible responses are Yes and No, so this logic works. But on your system, there is a third possible response (Cancel), and the logic is ineffective. The workaround is easy and I'll do it soon.

I suggest you report this bug to the Wine project, since FtCG would not be the only program affected. — This, that and the other (talk) 07:08, 27 August 2013 (UTC)

Idea: "Automatic" message to uploader

Hello. I have used your program for some now :-). It could be nice if the program could wirte a talk page message to the uploader of the transfered file... Some nice message, I have just moved your files to commons, and please upload free files there next time. Christian75 (talk)

I think that people would be annoyed if they got messages like this in large quantities. --Stefan2 (talk) 18:35, 26 November 2013 (UTC)

Yes, indeed. On top of that, many uploaders are no longer active. You would be better off to write a personal message on the uploader's talk page if they are continuing to upload their free media to Wikipedia.

Thanks for using FtCG! Feel free to come back here if you have any more feedback or if you find any bugs. — This, that and the other (talk) 23:59, 26 November 2013 (UTC)

Or you could add {{un-commons}} to the uploader's talk page. --Stefan2 (talk) 00:01, 27 November 2013 (UTC)

Ok, my idea was that it should be optional - but the template {{Un-commons}} looks nice and I will use it :-) - Christian75 (talk) 13:53, 5 December 2013 (UTC)

Request for features

Hello. Thanks for your tool. I have cleaned up a lot of images transferred to Commons with this tool, and I have a few suggestions. Because I've never used the tool, I may be suggesting something which, er, is due to a PEBCAK error; feel free to ignore in this case.

• Please place a LARGE, PROMINENT note stating that the uploader should only choose {{own}} if the original uploader is in fact the author. I cannot tell you how many users will just choose that as the default setting for every file, including {{PD-old}} ones. This ultimately results in me leaving nasty messages for people which I regret later.[2] (Please ignore my sarcastic inability to accept blame for my own vices).
• Would you consider using {{own work by original uploader}} instead of {{own}}? I created that template because I think it clarifies things well.
• Please consider verifying a valid EXIF date (e.g., not 0000-00-00 [3]) before applying the {{According to EXIF data}} template.

Magog the Ogre (t • c) 02:29, 25 January 2014 (UTC)

Actually, there is a clear warning saying <!-- change this if not own work -->, see [4]. Unfortunately, some users miss this, and some users might not realise that the file needs to be cleaned up a bit before moving it to Commons. --Stefan2 (talk) 01:04, 27 January 2014 (UTC)

Thanks for your feedback, Magog.

• The hope is that users of FtCG will have some experience with Commons, and that they will have enough clue to remove {{own}} if it is not relevant. If they don't, they really ought to be told about it (I have done this myself on occasion). I don't know what more FtCG can do to remind users to remove {{own}} without getting in the way of experienced users.
• As for {{own work by original uploader}}, yes, that can be changed easily.
• And the EXIF dates: That file was transferred in May 2012, and I'm pretty sure more recent updates of FtCG include code that ignores silly years like 0000 and 0001. If you see any more recent transfers with bogus dates, please let me know.

I'm about to release an update of FtCG to prevent the leaking of RevDel'd information after a recent API change, so I can include the {{own}} change in that release. — This, that and the other (talk) 02:17, 29 January 2014 (UTC)

• I've got boatloads of experience using Commons, and didn't understand that I needed to not choose {{own}}. It needs to be made much clearer in the instructions. - Tim1965 (talk) 17:18, 14 July 2014 (UTC)
  • Hi Tim, and thanks for using FtCG. As I said above, it is really up to the user to understand what is in the right-hand pane. I would have expected anyone who has experience with Commons to understand that whatever appears in the {{information}} template in FtCG is exactly what ends up in the {{information}} template on Commons. I can't see how to make it any clearer that you need to remove {{own work by original uploader}} <!-- change this if not own work --> template when transferring works not created by the uploader, without interfering with the workflows of experienced FtCG users. I would welcome any ideas you may have. — This, that and the other (talk) 09:53, 17 July 2014 (UTC)

API error

I am Argentine, and sorry for my poor English. When I go to transfer an image from wikipedia in English Commons to use it, I "An API error occurred. You must be logged in to upload" appears. I mean, I understand you to say that I am not connected, but I am connected in the Commons as much as I put in the program my username and password. I do not understand that then I do. If I can rsponder, thank you very much. Greetings.--Toxwiki96 (talk) 19:04, 5 March 2014 (UTC)

Hi Toxwiki96, and thanks for trying out FtCG. Do you think you could open the "Settings" window within FtCG, and provide a screenshot of it? That would help me to understand the problem. — This, that and the other (talk) 11:09, 9 March 2014 (UTC)

Now this, thanks, I must have something wrong, but now step photo very well. Sorry to take your time and thanks for helping. Greetings from Santa Fe.--Toxwiki96 (talk) 14:48, 9 March 2014 (UTC)

I have got this problem a couple of times. When this has happened, I have also been logged out in my web browser, so it might not be caused by a bug in this program but by something else. Restarting FTCG solves the problem. --Stefan2 (talk) 23:39, 11 March 2014 (UTC)

• I from Russia, excuse, badly I communicate in English. I had today a problem: when clicking the Transfer button the message floats: There was API error. You must be logged to upload. In settings I didn't change any passwords. I enter projects without problems. I apply a screenshot of settings http://s1.ipicture.ru/uploads/20140501/iF2OYUWL.jpg. Thank you very much.--Dogad75 (talk) 14:28, 1 May 2014 (UTC)

Same problem here. I am on Mac OS X, but have Windows 8.1 running (with Parallels between Windows and Mac). I am trying to upload "Amarapura_CityGate.JPG" from English to commons.

All I get is the message "An API error occurred." "You must be logged in to upload. [ OK ]".

The problem persists, whether or not I have a browser started on Windows, whether or not I am logged in the on Wikipedia. Teeschmid (talk) 19:59, 1 May 2014 (UTC)

I'm having the same problem, just started today. Probably coincidental, but I upgraded FireFox to 29.0 yesterday. No tweaking of settings seems to help. The app is really good, and very helpful, so I'd appreciate it if you'd look into the problem, or provide some suggestions as to what to try to fix it. BMK (talk) 19:26, 3 May 2014 (UTC)

@Beyond My Ken, Dogad75, and Teeschmid: Noted. II'll look into this urgently and should have a fix within 12 hours. — This, that and the other (talk) 02:26, 4 May 2014 (UTC)

Norton AntiVirus

I have had constant problems with FtCG and Norton AntiVirus' SONAR threat detection system – it would often detect FtCG as a piece of malware. As best I could tell, the detection was triggered by FtCG's automatic update check.

Yesterday I reported this problem to the makers of Norton AntiVirus (Symantec), and I got an automated response a few hours later saying "this detection will be removed from our products". Hopefully this prevents this false detection of FtCG in future versions as well as the current version.

If you continue to experience problems with FtCG and Norton AntiVirus (or any other anti-virus/anti-malware systems), please let me know. — This, that and the other (talk) 08:55, 10 March 2014 (UTC)

High DPI Settings

It seems that ForTheCommonGood has a problem with higher DPI settings. I have my computer set at 120 DPI (Windows XP scaling mode off) and I get a lot of overlapping boxes, some of which actually impede function. Normally I'd just use the high DPI compatibility option, but that didn't change anything.

The biggest problem is that "One Earlier Version" is covering up half of the rename input box and the ignore Warnings check box. It seems like there'd be a lot of space to just put that directly under the file identification dialog. The rest of the problems are mostly cosmetic. — trlkly 00:30, 11 March 2014 (UTC)

Hi Trlkly, and thanks for your useful feedback. I use high DPI on one of my user accounts on a Windows 7 system, so I know what it's like when programs can't handle high DPI scenarios! Unfortunately, that user account is not one where I typically use FtCG, so I hadn't spotted the problems. I'll check this out very soon. — This, that and the other (talk) 07:02, 11 March 2014 (UTC)

I've been able to repair most of the issues, except for a couple of rather stubborn text labels (most notably the local wiki data status in the Settings dialog, i.e. the "Currently using en.wikipedia" text). Windows Forms sometimes has trouble with high DPI adjustment, and I can't work out what's causing it to misposition these text elements.

I'll shortly post an update which includes these fixes I've managed so far, as well as a fix to the styling of the wikitext preview dialog. — This, that and the other (talk) 08:48, 13 March 2014 (UTC)

It's a lot better, so thanks. It's at least completely usable now. — trlkly 00:07, 21 March 2014 (UTC)

Important update released

I have just released FtCG 1.0.5.10, available for download at http://atlight.github.io. All FtCG users should update to this version.

In the past few days, users have been noticing that FtCG was giving the error "You must be logged in to upload files" when attempting to transfer a file to Commons. The exact reason for the sudden appearance of this error is unclear, although it may have something to do with bugzilla:64727. Whatever the case, I have taken the opportunity to make FtCG's cookie handling more robust, so that issues like this should not arise in the future.

If the latest version of FtCG is still giving you grief, please let me know.

@Beyond My Ken, Dogad75, and Teeschmid: Thanks for reporting this bug, and sorry it took so long to fix! Hopefully you haven't missed FtCG too much in the meantime :) — This, that and the other (talk) 12:19, 4 May 2014 (UTC)

Many thanks!--Dogad75 (talk) 10:51, 5 May 2014 (UTC)

File history

Hallo,

thank you for the tool FTCG. I use it very often, to transfer pictures from the german Wikipedia to Commons. But I miss a special feature. I would like to be able, to upload all pictures from the (local) File history in the File history of commons. Would it be possible to add such a feature?--79.212.0.147 (talk) 08:55, 7 May 2014 (UTC)

Hello, and thanks for using FtCG! While I won't have time to work on this suggestion in the near future, I think it's a great idea and I will see if I can make it happen within the next couple of months. If you have any more ideas or feedback don't hesitate to let me know. — This, that and the other (talk) 12:13, 12 May 2014 (UTC)

some suggestions

Hi, I am a sysop in fa.wiki I used your tool and it was awesome. I collected some feedbacks from fa.wiki users. Would you please Add/Solve them?

1. Please add a category input-box which user can categorize the image at the transferring process
2. Please add an input-box for {{DEFAULTSORT:}}
3. When we want to transfer the image it shows an alarm which the new name is similar to an existing name. please set it to show this alarm when the name exactly is the same. I tested and it shows alarm for new name which has only 5 similar character with existing image name.
4. Is it possible to convert image format (like .gif to .jpg or .png) before uploading?
5. Is it possible to develop this tool in Js language which we can use directly in local wiki?

Thank you for your time. Yamaha5 (talk) 03:38, 13 August 2014 (UTC)

Hi Yamaha5, and thanks for using FtCG! As you may be aware, I gladly received a local wiki data file from Ebrahimio the other day, and that has now been uploaded to the FtCG website.

1. A category input box has long been on my to-do list. One of the big challenges with this is that the FtCG user interface is already very cluttered. I have always tried to make sure FtCG can be used on a 1024x768 screen, because not everyone has a big screen. I'll really think carefully about how to incorporate this into FtCG.
2. In my experience, it is unusual to need DEFAULTSORT on Commons. I would think it is simple enough to type {{DEFAULTSORT:text here}} any time you do need it.
3. Those alarms (warnings) are actually generated by Wikimedia Commons. FtCG just relays then back to you. You would probably get the same warning if you uploaded the file directly to Commons. If you have concerns about these warnings, please explain in more detail and I could file a bug at Bugzilla for you.
4. Converting image formats is a difficult task to accomplish well. It would be easy for FtCG to perform basic conversions, but to perform conversions properly, without loss of data, it would require a specialized software program like ImageMagick, GIMP, or Photoshop. I do not have the skill to incorporate a high-quality conversion system in FtCG. Additionally, the deletion criterion used to delete files on English Wikipedia that have been transferred to Commons (CSD F8) requires the file to be transferred in the same format, and I think many other wikis have the same requirement.
5. It's funny you should ask this: I have actually written a version of FtCG in JavaScript. However, it doesn't work, due to bugzilla:42473. If that is ever resolved (or bugzilla:6071) then it will work.

Hopefully that helps you. — This, that and the other (talk) 03:11, 17 August 2014 (UTC)

Next version of FtCG: what would you like to see?

I am currently working on the next update to FtCG. Some new features are going to appear in this update, including: a built-in HotCat-like category selection interface (codenamed "CoolCat"); the ability to transfer multiple revisions of a file (in order to preserve the file history, as recommended by CSD F8); and a complete reworking of upload warning handling. It will also remove the brief "freeze-up" that occurs when FtCG's main window opened.

I realise that FtCG does have a number of rough edges, which I have gradually tried to smooth out over the years. I also am aware that, while the current feature set of FtCG suits me pretty well, there are additional features that others would like added to FtCG. Some features that have been added in the past after someone requested them on this page include the wikitext preview feature, the Google Image Search link, and a number of improvements to the wikitext generation algorithm.

So, if you have any requests for what you would like to see in this update, please speak up! I'm keen to hear what you, the users of FtCG, have to say. — This, that and the other (talk) 01:05, 2 September 2014 (UTC)

enWS local data file

I have been using the linked data file at enWS for a while and it seems to be doing the things that I want, to the point that I am letting the community use it. Not sure at what point of their maturity that you want to have files identified to you. Do {{ping}} me if you have any specific feedback. Thanks for the tool. — billinghurst sDrewth 13:28, 5 September 2014 (UTC)

I'll write you some detailed feedback when I have a moment. Thanks! — This, that and the other (talk) 12:30, 9 September 2014 (UTC)

Statements about Linux

“ Tech-savvy Mac OS and Linux users can run this application using Mono and/or Wine[1], with only very minor loss of functionality compared to Windows[2]. ”

If you use Wine, you should note that Wine doesn't support .NET, so you need a separate program for that. Recent versions of Wine are often distributed together with a version of Mono, so maybe this is what you tested. Wine can also be used with Microsoft's .NET software, and this causes different issues than the ones you listed in the second footnote. --Stefan2 (talk) 15:42, 10 September 2014 (UTC)

Thanks, Stefan. Would it be more accurate to say "...using Mono (either by itself, or within Wine)" or something similar? Additionally, I suspect that using Wine with Microsoft's .NET Framework is a rather unusual setup - do you think it is worth "supporting" it? How would I go about testing that particular setup? — This, that and the other (talk) 00:47, 11 September 2014 (UTC)

I installed Microsoft's .NET Framework several years ago, presumably using Winetricks. Try winetricks dotnetnn where nn is the version number, for example "30" for version 3.0 or "40" for version 4.0. I don't remember which version I installed. Some features provided by this software:

• HTTPS works. As HTTPS didn't work with Mono last time I tried, I prefer to use Microsoft's program instead of Mono.
• When clicking on "Transfer", I often get a pop-up message that the transfer has failed. In this situation, it usually means that the file is on Commons but that the local file hasn't been tagged with {{subst:ncd}}. FTCG does not open up any file information pages in my web browser when this happens, so I need to open them myself and check whether things are fine and usually add {{subst:ncd}} manually.
• The text box do not always show the changed text when I'm changing text. To see the text, place another window in front of FTCG and then move away that window again.

As the software works better under Windows than under Linux, I prefer to use Windows if I'm transferring a large number of files at the same time, but this creates extra trouble such as rebooting my computer, so the Wine option is easier if I only need to transfer one file. --Stefan2 (talk) 15:18, 11 September 2014 (UTC)

Whoa, FtCG looks really good visually using Wine+dotnet20! Much better than on Mono. Autocomplete and preview both work flawlessly. For me, on Ubuntu 14.04, I do not see the issue of text boxes not updating, and I do see an issue I also saw on Mono, which was that the transparency checkered grid shows up in orange for some reason. I did come across the problem of NowCommons tagging not working (it seemed to be timing out for some reason), and I also experienced a crash which seemed to come from within .NET's SSL code. In light of that I'll try to improve what I wrote on WP:FTCG. Thanks for your contributions. — This, that and the other (talk) 11:06, 12 September 2014 (UTC)

Russian

Why was a Russian NowCommons tag added instead of an English one in Special:Diff/589203155 and Special:Diff/622296383? --Stefan2 (talk) 16:50, 15 December 2014 (UTC)

Someone using the wrong local wiki data file? — This, that and the other (talk) 11:02, 16 December 2014 (UTC)

Yes, probably. If it becomes a big problem, I guess we could just create a redirect to the English-language template. Yesterday, only those two files used Russian templates, and I solved this by tagging both with English templates. --Stefan2 (talk) 13:22, 16 December 2014 (UTC)

Bug by adding categories

Hallo,

thanks for updating your tool to Version 1.1. I like it very much!

But I found in this Version a Bug. If a want to insert a neu category to the picture I get a System.ArgumentOutOfRangeException. The error message is the following (in german):

Informationen über das Aufrufen von JIT-Debuggen anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung. ************** Ausnahmetext ************** System.ArgumentOutOfRangeException: startIndex darf nicht länger als die Länge der Zeichenfolge sein. Parametername: startIndex bei System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy) bei ForTheCommonGood.CoolCatItem.FinishCategoryAutoComplete(Array results, String extraResult) ************** Geladene Assemblys ************** mscorlib Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000). CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll. ---------------------------------------- ForTheCommonGood Assembly-Version: 1.1.0.0. Win32-Version: n/v. CodeBase: file:///D:/Eigene%20Dateien/Downloads/ForTheCommonGood_1.1.exe. ---------------------------------------- System Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll. ---------------------------------------- System.Windows.Forms Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8008 (FX35W81RTMGDR.050727-8000). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll. ---------------------------------------- System.Drawing Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll. ---------------------------------------- System.Configuration Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll. ---------------------------------------- System.Xml Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll. ---------------------------------------- System.resources Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.7905 (win9rel.050727-7900). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.resources/2.0.0.0_de_b77a5c561934e089/System.resources.dll. ---------------------------------------- Accessibility Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8007 (FX35W81RTMGDR.050727-8000). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll. ---------------------------------------- mscorlib.resources Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8009 (FX35W81RTMGDR.050727-8000). CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll. ---------------------------------------- Microsoft.mshtml Assembly-Version: 7.0.3300.0. Win32-Version: 7.0.3300.0. CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll. ---------------------------------------- System.Windows.Forms.resources Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.7905 (win9rel.050727-7900). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll. ---------------------------------------- ************** JIT-Debuggen ************** Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der Konfigurationsdatei der Anwendung oder des Computers (machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden. Die Anwendung muss mit aktiviertem Debuggen kompiliert werden. Zum Beispiel: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten Ausnahmen an den JIT-Debugger gesendet, der auf dem Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

--84.130.234.40 (talk) 15:23, 22 December 2014 (UTC)

It seems that the output format of the MediaWiki API had changed. Of course, if FtCG was well-written, it wouldn't crash in situations like this. But I'm not a very careful programmer, unfortunately!

I've pushed out version 1.1.0.1 which should fix this issue. Thanks for reporting this issue, and thanks for using FtCG! — This, that and the other (talk) 07:02, 23 December 2014 (UTC)

Thanx for updating your tool in such a short time. --91.2.203.199 (talk) 13:52, 23 December 2014 (UTC)

{{subst:ncd}} not added

Could you add more warnings or make it more difficult to move files to Commons without adding {{subst:ncd}}? There are a few files like this which have been copied to Commons but not tagged with {{subst:ncd}}.

There are over 3,000 files to which {{subst:ncd}} should be added, but only a small portion of them seem to have been uploaded using this tool. --Stefan2 (talk) 23:44, 2 January 2015 (UTC)

The option to tag with {{now Commons}} is on by default. It can be turned off (this is intended for use on {{keep local}} files and similar cases), but will always come back on the next time FtCG is restarted. I suppose it could be turned off by accident, but that seems unlikely to me. Is it a question of a single user, or more than one? — This, that and the other (talk) 03:24, 15 January 2015 (UTC)

I haven't kept any statistics, but I have noticed this problem with a small number of files transferred using FTCG. It seems to occur much more commonly with Commonshelper which doesn't even have an option to add {{subst:ncd}} automatically, and many files with this problem have been uploaded using the upload wizard on Commons, often with wrong author, source and copyright tag. I guess fewer problems occur with this tool than with the other methods thanks to its automatic addition of {{subst:ncd}}. --Stefan2 (talk) 22:53, 19 January 2015 (UTC)

Transferring human-reviewed files

Could a radio button be added, please, to make it easy to select files from Category:Copy to Wikimedia Commons reviewed by a human? --MichaelMaggs (talk) 08:33, 14 January 2015 (UTC)

@MichaelMaggs: Thanks for your suggestion. However, there is only space in the FtCG user interface for three radio buttons. Do you think one of the existing options should be removed?

To be quite frank, I don't see why people bother "reviewing" these files. They may as well just download FtCG themselves (or use an alternative transfer tool) and complete the transfer.

In any case, thanks for using FtCG! — This, that and the other (talk) 05:15, 15 January 2015 (UTC)

User:MichaelMaggs, note that you can easily search through other categories by clicking on the "Other source" radio button and entering the name of the category you are interested in. --Stefan2 (talk) 22:53, 19 January 2015 (UTC)

I would think it more useful to have a radio button for 'reviewed by human' rather than 'reviewed by bot', as the former category has a much higher hit rate of files that can be processed quite quickly in a single session. It's not hugely important, though. --MichaelMaggs (talk) 06:44, 20 January 2015 (UTC)

Own work by original uploader

@This, that and the other:

OK, since our last chat (see /Archive 3), I have had to talk with probably 10 different users about putting own work by original uploader on images where the original uploader was obviously not the author. If I had to do this one more time, a vein will shoot through my forehead and spurt blood on the screen.

Uploaders are clearly not taking the clue. Please stupid-proof this feature in any way that you can. Magog the Ogre (t • c) 02:34, 15 January 2015 (UTC)

@Magog the Ogre: Thanks for the comment (and thanks for the ping!). I try to emphasise that For the Common Good does not do all your work for you, but some people don't seem to understand that. I'll have to have more of a think about this.

Could you provide some examples of files that are being transferred with this erroneous tag? If possible it would be nice to also see the original wikitext from the source wiki, but if you can't get that I can always ask at WP:REFUND, or admin noticeboards on other wikis. Thanks, — This, that and the other (talk) 03:29, 15 January 2015 (UTC)

Uploading multiple versions of a file

There seems to be a bug when uploading multiple versions of a file. After the second file has been uploaded, I always see this error message. The file is nevertheless uploaded (see File:Amarin logo.jpg), but the tool never adds any {{subst:ncd}} tag. --Stefan2 (talk) 21:33, 30 January 2015 (UTC)

• Also, the tool won't upload more than two revisions of a file. I noticed this problem when trying to move a file with four revisions. --Stefan2 (talk) 21:44, 30 January 2015 (UTC)
  • Interesting; I'll look into it. Thanks for reporting this issue. — This, that and the other (talk) 11:11, 3 February 2015 (UTC)
  • Ah, I see what the matter is. This bit of code isn't ideal, but it will do for now. I will change it so that all warnings will be ignored on the second and subsequent revisions to be uploaded to Commons (counting from the earliest revision first). — This, that and the other (talk) 13:04, 3 February 2015 (UTC)
  • @Stefan2: Version 1.1.0.2 is now available for download. I won't release it to auto-update, because it's only an interim fix. — This, that and the other (talk) 13:07, 3 February 2015 (UTC)

Problem!

i! In attempt to load the file from Ruvika jumps out the message: "The Internet inquiry isn't executed. The inquiry was interrupted: The inquiry is cancelled." Photo: http://radikall.com/images/2015/02/13/ecRa7.jpg --Dogad75 (talk) 22:40, 17 February 2015 (UTC)

Hi there. This error is usually a one-off. Often it means that the server took too long to respond to the request ("inquiry"). If this keeps happening, please let me know which files/categories or actions within FtCG are causing it to appear. Thanks, — This, that and the other (talk) 11:27, 18 February 2015 (UTC)

{{NCT}} and parameters in ru.wiki

Hi, This, that and the other, if you remember me :) Is it possible to make bot add not {{NowCommons|File:Nameofthefile}} after the upload, but {{NowCommons|Nameofthefile}}. The template works correctly with both cases but it breaks some other scripts that I use for cleanup of such transferred files... Rubin16 (talk) 16:18, 26 April 2015 (UTC)

Proxy settings

It would be useful to allow proxy settings to be specified as some of us work at places that require authentication Gbawden (talk) 11:26, 17 June 2015 (UTC)

{{self|<license>|author=}} parsing

Hey TTO... {{Self|cc-by-sa-3.0|GFDL|migration=redundant|author=WP-Author-Field}} gets an additional author field for commons: {{self|cc-by-sa-3.0|GFDL|migration=redundant|author=WP-Author field|author=WP-Uploader}}. I do not believe this should happen. See for example en:File:Photo_of_Geoffroy_de_Lagasnerie.jpg. Cheers, Storkk (talk) 16:36, 9 September 2015 (UTC)

@Storkk: I'll look into this. Thanks for the report. (Please feel free to ping me in future, or else I may not see your message in a timely fashion!) — This, that and the other (talk) 06:15, 20 October 2015 (UTC)

{{OTRS permission}}

Hi again, TTO - could FTCG please "translate" Template:OTRS permission to C:Template:PermissionOTRS? Storkk (talk) 12:07, 17 September 2015 (UTC)

Hi Storkk, thanks for the feedback. Since an appropriate redirect exists on Commons, I don't see a good reason to have FtCG change this template when copying files across. — This, that and the other (talk) 06:38, 20 October 2015 (UTC)

Always add same category

Is it possible for the tool to always add e.g. c:Category:Files transferred from Wikipedia by Josve05a, without having to add it each time manually? (t) Josve05a (c) 22:19, 15 November 2015 (UTC)

Hi Josve05a, and thanks for using FtCG! You could do this by customising your local wiki data file. Download the default en.wikipedia file from here, and make two changes using Notepad or a similar text editor:

• Delete (Default) next to LocalDomain at the top
• Add the following replacement section:

[Replacement]
LookFor=$
ReplaceWith=\n\n[[Category:Files transferred from Wikipedia by Josve05a]]

Then import this local wiki data file into FtCG via the Settings dialog box. The drawback to this approach is that you won't receive any updates to the local wiki data file as shipped with FtCG unless you manually update your local wiki data file and re-import it each time.

Is it common or widespread for people to add such categories? I have to admit I find it difficult to understand the purpose of such a category, but if this is a common practice, I could add an additional setting to FtCG allow this to be done more easily. — This, that and the other (talk) 00:54, 18 November 2015 (UTC)

It would certainly help with people being able to track what they have uploaded. I also might suggest adding a category so that it shows what has been uploaded by the tool, which would make success of it easier to track. Kevin Rutherford (talk) 07:45, 7 February 2016 (UTC)

@This, that and the other: I actually went ahead and created a category for the app here, so I hope that can be added. I did note that when I added in the suggested script, it doubles the "transferred" category and puts it above the text with spaces between the lines, so I wonder if there is a way to append it to the end and make it a bit cleaner. Kevin Rutherford (talk) 07:53, 7 February 2016 (UTC)

@Kevin Rutherford: That type of thing could much more easily be implemented in c:Template:Transferred from. In particular, that would capture all files that have previously been transferred using FtCG. And you can use the "CommonsUploads.log" feature in Settings to keep track of what you have uploaded.

I suppose I just don't see the point of people keeping personal categories of files thy have transferred to Commons. Authorship categories, where you create a category to contain the files you have authored, seem reasonable enough. But transfers, where the transferring user has no creative input into the file itself, surely don't merit a personal category for each transferrer. What next - "Category:Files whose metadata was cleaned up by UserName"? — This, that and the other (talk) 08:37, 7 February 2016 (UTC)

New problem—freezing

Hi. I've been using FtCG for a while, and have the current version. Today (after installing a bunch of Windows 7 updates), when I tried several times to transfer File:Blair House 1919.png, it freezes on the "Loading" information box after I click "Transfer". This is the first time this has happened, and any help would be appreciated. Thanks and all the best, Miniapolis 20:35, 12 February 2016 (UTC)

• Hello! I have a similar problem, installed Windows 10. The problem is probably in the program. Thanks for the help! --Dogad75 (talk) 10:42, 14 February 2016 (UTC)

Thanks for the reply. I don't think it's been updated since October, so it may be time. I've been using CommonsHelper in the meantime, but prefer FtCG. All the best, Miniapolis 14:42, 14 February 2016 (UTC)

• This tool is also freezing for me, using Wine (software) version 1.6.2. Does it maybe have something to do with this breaking change? --Stefan2 (talk) 10:24, 15 February 2016 (UTC)
  • Happening for me too on Windows 7. It was working on the 9th. @This, that and the other: pinging you, as requested above. Storkk (talk) 12:18, 15 February 2016 (UTC)
    • Thanks for the reports. I feared that FtCG might have broken after the recent changes to MediaWiki's login infrastructure. Logging you into the wikis is actually one of the more complicated parts of FtCG, believe it or not. I'll look into this urgently. Thanks for your patience, and thanks to Storkk for pinging me. — This, that and the other (talk) 12:24, 15 February 2016 (UTC)

@Miniapolis, Dogad75, Stefan2, and Storkk: I have released version 1.1.0.5 of FtCG, which should now work correctly. I've patched over the issues just enough to keep both HTTP and HTTPS modes working; they may break again when the next round of MediaWiki API changes is made.

On a related note, I have been considering the future of FtCG. In 2011, when I first developed the tool, the only viable alternatives were CommonsHelper and CommonsHelper 2, which was a flaky tool hosted on an even flakier Toolserver. One of my focuses when developing FtCG was efficiency, both in terms of downloading and uploading, but also in terms of requiring minimal wikitext cleanup. I haven't used CommonsHelper since the Toolserver days; I understand it has come a long way in the last 5 years. As users of FtCG, do you feel the tool is still meeting your needs in 2016? Since only a handful of people use FtCG, do you think that the client-based nature of the tool is unattractive for users, or does it simply suffer from a lack of "advertising"? Please let me know your thoughts as I evaluate the next five years of FtCG. — This, that and the other (talk) 13:17, 15 February 2016 (UTC)

@This, that and the other: I still find CommonsHelper more than a little flaky and prefer to see the wikitext before committing, but perhaps I just haven't investigated it enough, or (quite possibly) I'm using it wrong. Storkk (talk) 13:39, 15 February 2016 (UTC)

Note that you can quickly clean up files transferred using CommonsHelper by adding importScript('User:Magog the Ogre/cleanup.js'); to c:Special:MyPage/common.js and then clicking on a link in the toolbox. --Stefan2 (talk) 14:20, 15 February 2016 (UTC)

Many thanks for the update, but I understand your desire not to have to keep doing this for the rest of your natural life :-). FWIW, I much prefer FtCG to CommonsHelper but if you want to eventually pull the plug on FtCG I'll check out Magog's script. I also find CommonsHelper temperamental; FtCG is much more user-friendly for us non-technophiles. Thanks again and all the best, Miniapolis 15:02, 15 February 2016 (UTC)

@Stefan2: thanks for that pointer. It wouldn't have corrected the OTRS template, though, which somehow lost the ticket number. Storkk (talk) 15:11, 15 February 2016 (UTC)

@This, that and the other: I have several years of use your program to transfer files to Commons. The program is very easy to transfer multiple files, it is possible to edit the technical information, use a preview. Many Russian Wikipedia users are enjoying your program, and it would be very sad if you stop to improve it. Many thanks for your program FtCG! Not all of it is used, as it is simply not aware of the existence FtCG program. Sorry for my bad English. Yours faithfully, --Dogad75 (talk) 16:40, 15 February 2016 (UTC)

Let me reassure you that I have no plans to stop supporting FtCG. If no-one was using it, I might have done that, but I've been reassured by your comments. I hope to keep it running (and maybe even add new features as well! You never know) for many years to come. As always, thank you for your continued support of FtCG :) — This, that and the other (talk) 22:35, 15 February 2016 (UTC)

One useful feature could be to accept calls like ForTheCommonGood_1.1.0.5.exe File:Example.svg to automatically open File:Example.svg when starting the program without having to go to a textbox and click on "go". --Stefan2 (talk) 22:49, 15 February 2016 (UTC)

I should note for the record that I tried very hard to implement this, but due to some weird behaviour of the Windows Forms infrastructure with respect to cross-thread communication, I wasn't able to get it to work. Instead, I only succeeded in making the program crash. I might have another go later, but it is actually non-trivial due to the frustrating design of Windows Forms. — This, that and the other (talk) 10:47, 24 May 2016 (UTC)

Licensing

Hi! Upon a quick glance I couldn't find a license for this program on GitHub. What license are you using? I suggest you create a COPYING.md or LICENSE.md file in the GitHub repo to make it clear. Cheers! Pikolas (talk) 14:39, 11 May 2016 (UTC)

Hi Pikolas! Thanks for your interest in FtCG. The program is in the public domain. It says so in the corner of the settings box. In the code, this string is listed somewhere in the DefaultStrings.lang file. I have been meaning to relicense future releases of FtCG under an MIT-style license (which, needless to say, wouldn't apply retroactively), but I haven't got around to it, because at the end of the day, I just don't care much about licensing. I hope this helps to answer your question. — This, that and the other (talk) 10:44, 24 May 2016 (UTC)

Bad examples of own work

@This, that and the other: you asked me here to provide some examples of where users incorrectly used own work. I have compiled a bunch over the past 17 months. They are here: User:Magog the Ogre/bad own work. Clearly it seems users are not understanding something. Magog the Ogre (t • c) 00:10, 23 May 2016 (UTC)

Thanks, Magog. It is tempting to say "if you could only find 8 instances over 17 months, I think there are other, bigger things to worry about". But I have to bear in mind that not many people use FtCG, and if the number of users using the tool went up, I imagine we would see a corresponding increase in this problem, which would give FtCG a bad reputation among Commons patrollers.

I might add a pop-up confirmation dialog box, to appear the first time someone transfers a file using FtCG with the {{own work by original uploader}} text left unchanged in the Commons file description. This would require them to explicitly acknowledge that they have checked that the file is indeed the uploader's own work. I don't have much time to develop this feature right now, but I will keep it in mind. — This, that and the other (talk) 10:52, 24 May 2016 (UTC)

Just to clarify, this wasn't 8 instances, this was 8 different users. There were at very least dozens of instances, possibly hundreds. Maybe make the text bigger or clearer; think like a lost newbie. I don't use the product; I'm grasping at straws too. But I've definitely noticed that more users than not tick this incorrectly. Magog the Ogre (t • c) 01:29, 25 May 2016 (UTC)

403 forbidden

Hi again, @This, that and the other:, and I'm sorry to come here with another problem. When I try to transfer a file, I get the following error message: "The remote server returned an error: (403) Forbidden". I hoped it was a password problem (since I changed my PW a few months ago), but after deleting and re-downloading FTCG with my current PW I get the same error. Hope this is fixable, because even with Magog's script I find CommonsHelper clunky and time-consuming. Thanks again and all the best, Miniapolis 14:08, 18 September 2016 (UTC)

Such a pleasant surprise to actually fix something :-); leaving "Use HTTPS (secure connection)" checked in Settings (I'd unchecked it due to previous problems) fixed the problem. I wonder if an HTTP-HTTPS incompatibility was to blame, since I was logged in on the secure server. Thanks again and all the best, Miniapolis 14:26, 18 September 2016 (UTC)

Hi Miniapolis! I'm glad you worked out what the matter was. I probably should remove that HTTPS checkbox, since FtCG no longer works with HTTPS turned off. Thanks for pointing it out. — This, that and the other (talk) 00:47, 19 September 2016 (UTC)

Redirected categories

@This, that and the other: can you improve FtCG by making it to detect [and fix automatically] introduced categories if they are redirected (like it's done by HotCat, for example)? On commons currently are some bots that work on this task regulary or periodically[5], but probably it would be better if the tool will do the fix automatically. This feature may be added as a user preference as well, if not as a default function. --XXN, 12:42, 26 October 2016 (UTC)

Hi XXN, yes, I agree, this would be good to have. I have little time for working on FtCG at the moment, but I will keep it in the to-do list. Thanks! — This, that and the other (talk) 00:53, 27 October 2016 (UTC)

New source: User uploads (suggestion)

A suggestion, to make available a new source of files for transfer - User uploads. XXN, 16:17, 1 November 2016 (UTC)

An issue with FtCG special variables

Seems that FtCG special variables (%%OriginalUploader%% and %%InterwikiLinkPrefix%%) not always works in [Replacement]. The built-in default instances included works as expected, but if I'm trying to add new ones for the {{Information}} template, at least for me they does not work.[6][7] Can't understand why. The regex $n captures works fine. In these screenshots is a test case trying to find a way in which they works; previously I've also tested them separately and same issue was encountered. --XXN, 17:32, 14 March 2017 (UTC)

As you can see, this was a try to change always by default {{own}} → {{own work by original uploader}}. This probably is a useful and needed thing for many other users, and probably it even can be included as a built-in feature (example). XXN, 17:46, 14 March 2017 (UTC)

Two-factor authentication

Hi This, that and the other, thanks for the wonderful program. I've run into a new problem now that I'm an admin. If I have two-factor authentication enabled on enwiki, I get a login failure warning when transferring files to Commons. I don't expect it's an easy fix (maybe OAuth would work?), but I figured I'd let you know. It'd be great to have 2FA enabled and still be able to use FtCG. clpo13_(talk) 22:12, 10 May 2017 (UTC)

Would Meta:Special:BotPasswords work for that? I haven't tried it yet. --Closeapple (talk) 08:36, 11 May 2017 (UTC)

@Closeapple: That worked! Thanks for the tip. clpo13_(talk) 16:05, 12 May 2017 (UTC)

Dates

Probably FTCG should try to convert dates from formats like long DMY and MDY (e.g.: 1 January 2001 and January 1, 2001) to short machine-readable YMD (2001-01-01) - the preferred format on Commons. --XXN, 14:51, 9 July 2017 (UTC)

Convert to SVG and copy to Wikimedia Commons template

For the Common Good should remove Template:Convert to SVG and copy to Wikimedia Commons, and replace it with Template:SVG after transferring the file to the Commons. Daylen (talk) 18:32, 19 July 2017 (UTC)