-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All jpg files were ignored during campaign file upload round one creation #234
Comments
Hey @geertivp! Thanks for this. The I was able to load the images when I loaded it as a "File List", but got failures when trying to load it as a google sheet and CSV. The UI error says that disqualifications were due to round settings, but the server logs show that entries simply weren't loaded (see screenshot of logs below), so there's something else going on. Since you've worked around via Category import, I'll dig into it as time allows. Thanks again for the report! |
Ah, it just occurred to me, If you export your file list as a CSV (basically put quotes around all image filenames, but the easiest/best way is to export from Excel/GSheets), and also make the first row be This is very finicky, and we'll have to improve this in the next version, but for now there's another workaround for folks with spreadsheets / long file lists. Thanks again! |
Actually, I was wrong in the file contents sample above. When I initially encountered the problem, I actually loaded a file URL from a webserver with the following content:
(having "_" in the images file names instead of spaces...) |
The default file type for images on Wikimedia Commons is jpg.
When using the Montage file interface to create the first round of a campaign, all files in the campaign were ignored, because only jpeg is registered in module montage/rdb.py
DEFAULT_ALLOWED_FILETYPES = ['jpeg', 'png', 'gif', 'svg', 'tiff', 'xcf', 'webp']
Problem:
This is a blocking error, when using the file interface.
Solution:
This problem did not occur when using a Category upload.
More context:
The text was updated successfully, but these errors were encountered: