Help talk:Extension:FileImporter

Central feedback page for FileImporter/FileExporter.

I have asked this in the Village pump and there it was suggested to ask it here. I want to added images from the te.wikipedia.org to a Commons category, but got the response: "Unfortunately, importing files from the source wiki (te.wikipedia.org) is not yet possible because there is no configuration for the wiki in the configuration list". Is there anyone who can make this possible? ~~~~

Hi, you can make te.wikipedia.org supported by creating an configuration "file" (a wiki site) here: Extension:FileImporter/List of configured wikis. The easiest is to copy-paste the configuration from an other project and then change the content where necessary. The configuration states how templates are to be replaced and what license-templates are compatible with Commons.

The format of the configuration is described here.

Thanks for the info. The problem is that I don't know the Telugu language to change the content where necessary in the copy-paste version.

@వైజాసత్య, Ranjith Sutari: Would one of you please help with this?

The license template needs to be listed as a "good" template.

Why the FileImporter do not allow me to import files with PD-RusEmpire license?

Because it's not listed in the "good templates" list in the FileImporter data page for your wiki. Assuming you are trying to import from the Ukranian Wikipedia, that would be Extension:FileImporter/Data/uk.wikipedia#Good

Ok, thank you. I will add this

Tracked in Phabricator
Task T199453

I apologize for the English from automatic translator .. I am transferring various images from it.wiki and I was wondering if there was the possibility of having the extension replace a value contained in one of the templates to be converted directly. Let me explain, in the Information template there is the "source" field one of the most recurring values ​​is "opera propria" which should be automatically converted to {{own}}, but I didn't understand how it can be done. Thanks

On Commons, that would be "{{own}}".

let me explain better should convert "opera propria" to {{own}}, then I saw that a few days a bot passes to fix it but if there was the possibility to change it immediately it is avoided and maybe it is understandable even by those who do not speak Italian

The short answer is no, FileImporter currently can't convert values in a template. Only template names and parameter names are converted according to the "transfer" rules. However, it is possible to create a conversion template on Commons that is substituted and does the extra conversions you want. phab:T199453 might contain more information.

Per c:Commons:Village_pump/Proposals/Archive/2018/08#No_longer_allow_GFDL_for_some_new_uploads, except for software logos, diagrams and/or screenshots of GFDL-licensed softwares, any new files that are only GFDL licensed are no longer allowed on Commons at all.

Yes, we should.

Only for new uploads. If the file was uploaded to a local wiki before 2018 I think it is still acceptable on Commons.

Tracked in Phabricator
Task T267756

Hi! It is easy to translate a template from local name to Commons name by adding it in the configuration page under translate. For example on sr.wikipedia it is simply to add this code to translate глсд to GFDL:

;глсд:GFDL

But if it is {{self|глсд|Cc-by-sa-3.0}} then FileImporter does not translate глсд to GFDL. Can that be done?

Hi User:Thiemo Kreuz (WMDE). Can you help?

Example of a file in a self template: uk:Файл:Александр Човган.jpg

Example of a file without a self template: uk:Файл:Бейкуський лиман.jpg

One is correctly changed to c:Template:Cc-by-sa-1.0 and the other is not converted but remain c:Template:CC-BY-SA.

FileImporter is able to translate template names, as well as the names of template parameters, but not the content of a parameter. The word "глсд" in your example is content and can't be automatically translated with this tool.

However, it might be possible to add this as a feature. I created phab:T267756 to keep track of this idea.

Thank you. Self template is a very used template so it would be great!

Button is only shown to users in the "autoconfirmed" group of local wiki.

Hello,

I don't have the new tab to export a local file to Commons.

For example, I want to move [https://ko.wikipedia.org/wiki/%ED%8C%8C%EC%9D%BC:Mujujeja1.jpg this file] from wp:ko to Commons, but have no "Export to Wikimedia Commons" tab. It doesn't work either in any other language.

The documentation says "FileExporter is now a default feature on all wikis." so I guess I should not activate anything in my preferences, but can you see what could I do?

Thanks.

(meanwhile, another user moved the file on my request, but I need the feature :) )

It looks like you don't have any edits on this wiki. The export button is only shown to users in the "autoconfirmed" group, which typically means 10 edits must have been made, and the user must have been active for a few days. This is an intentional, very basic safety measure to avoid misuse.

Hello Thiemo,

OK, I understand, thank you.

Tracked in Phabricator
Task T261006

Tracked in Phabricator
Task T261060

I get errors when I try to move

1. vi:Tập_tin:Sơ_đồ_thành_cổ_Tân_Sở.svg : "[3cebc9bf-72cf-4731-8a33-210f65603ea1] 2020-08-21 17:03:10: Fatal exception of type "TypeError""
2. vi:Tập_tin:Plan_de_Son_Tay.svg : "This file (or an older revision of this file) contains elements that cannot be accepted for security reasons: $1"

The first error message does not say anything of use to me. The second does except the $1.

Is it possible to improve the error messages?

Someone was so kind to report the first error on phab:T261006 and the second is not very important to me.

These are super helpful bug reports (not speculating but just repeating what happened, with links). Thank you very much! Both appear to be smaller mistakes we made while working on FileImporter, both loosely related to phab:T253872. I created a ticket for the second issue as well, see phab:T261060.

Thanks, thats great Thiemo. It would of course be nice if FileImporter said "Sorry we can't move version 4. Do you want to move the other versions?". But no need to make things more complicated and risk breaking something if it is just because there are a few files that are wierd. :-D

I have added the files and a few other files to vi:Thể loại:FileImporter error so if you need files to test on then you can just pick some ;-)

The license migration is sometimes a problem. For example on vi.wikipedia and ja.wikipedia. If possible it would be nice if changes like this could be automated. On ja.Wikipedia the changes could look like this. If it makes things too complicated don't try. It can be fixed on Commons. But if it is an easy fix it would be nice.

There is a feature that allows the replacement of template parameters. In this case chuyển đổi= can be changed to migration= automatically. A rule for this can be added to Extension:FileImporter/Data/vi.wikipedia#Transfer. But that's all we have at the moment.

In the discussions at phab:T199453 and phab:T214365 are alternatives discussed that make use of subst: templates on Commons.

Thank you. But changing to "migration=" is only half the solution because we need the part after the "=" to complete the migration.

Off topic: Did you notice what I did with YouTube CC-BY? Someone really wanted to have a review template so I made this and it works :-)

There's another problem: ja:Template:GFDL was converted to c:Template:GFDL, but it should have been c:Template:GFDL-ja!

User:Stefan2 Hmmmm. I missed those disclaimers. It is easy to fix the conversion. I wonder what those disclaimers are.

User:Stefan2 there is a text on c:Template:GFDL-ja saying something like that if file was uploaded before july 2009 then we should use GFDL. It is only GFDL-ja after that date. And only if there was no multi-license.

ウィキペディア日本語版からコモンズへ移入されたファイルのうち、日本語版で2009年7月以前にアップロードされたGFDL単独ライセンスだったファイルには、必ず {{GFDL}} ではなく {{GFDL-ja}} のタグを付してください。

Meaning: If the file was uploaded to jawiki before (not after!) July 2009, then the Commons tag is c:Template:GFDL-ja, not c:Template:GFDL.

なお、日本語版でGFDL/CCマルチライセンスだったファイルには、GFDL-jaのライセンスタグは使用しないでください。

Also, don't use GFDL-ja for GFDL/CC multi-licensed files. I wonder if they are talking about files with ja:Template:Self. Note that {{self|GFDL|cc-by-sa-3.0}} inserts ja:Template:GFDL-no-disclaimers (not ja:Template:GFDL) on the file information page.

I would love to say Oppose for your first point as per c:Commons:Village_pump/Proposals/Archive/2018/08#No_longer_allow_GFDL_for_some_new_uploads.

I do not think its a new upload if we are talking about moving the file from xx.wiki to Commons. Anyway at least from ja.wiki there are probably no files that does not also have cc-by-sa-3.0 or have been license migrated.

User:Stefan2 perhaps we should discuss that on Commons. It is not a bug in FileImporter. Just a matter of changing the settings.

It's a bug in FileImporter or some FileImporter settings (where are those defined?) as ja:Template:GFDL is converted to the wrong Commons template.

User:Stefan2 the settings take 3 seconds to fix. But we need to be sure what the correct is before we change the settings. For those who wanna know more see c:Template talk:GFDL-ja.

I think I solved it at vi.wiki. The script can translate the first part. And the templates on vi.wiki understand the English terms so I just changed all the file pages to English. Problem solved :-) On ja.wiki the solution can be either changing with my bot on ja.wiki or to remove the template during transfer and then let a bot on Commons fix migration.

The problem with GFDL vs GFDL-ja have been fixed on ja.wiki. I changed the license of about 35k files so from now on GFDL=GFDL and GFDL-ja=GFDL-ja. The license migration is also mostly fixed as I changed 99% of the files to use the same migration code as on Commons.

For example, w:File:List icon purple.svg. Wikis hasn't MIT license, so it's hard to move to Commons.

For legal reasons, files must have one of the "good" templates to allow an import. I guess one possibility is to create such a template as described here.

see w:en:Wikipedia:Village_pump_(technical)#Technical_Wishes:_FileExporter_and_FileImporter_become_default_features_on_all_Wikis - why is running appliction config being housed on mwwiki? (ughh Flow still stinks too)

I assume you are talking about the configuration pages at mw:Extension:FileImporter/List of configured wikis. The exact location really doesn't matter that much – from a technical standpoint. We just need to store it somewhere where the community is able to edit the pages. Do you have a suggestion for a better location?