Commons talk:CropTool/Archive 2

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
← Archive 1 Archive 2 Archive 3 →

Croptool forced me to vandalize a page

https://commons.wikimedia.org/w/index.php?title=File:Standing_Hippopotamus_MET_DP248993.jpg&action=history

Just let me overwrite it already. I take full responsiblity. - Alexis Jazz ping plz 19:57, 17 July 2018 (UTC)

Hello Alexis Jazz, there seems nothing wrong except this deletion. Or what do you mean is going wrong here? -- User: Perhelion 20:08, 17 July 2018 (UTC)
@Perhelion: I had to blank the page because otherwise Croptool would not allow me to overwrite the image. I probably didn't have to blank the entire page, but I wasn't sure which bit caused Croptool to deny the overwrite so I just blanked it. - Alexis Jazz ping plz 20:13, 17 July 2018 (UTC)
Ok, please be concrete as possible. Was there any error messages or how appears the tool fail, like file protection?? But I guess the "featured-picture" tag protects the file. -- User: Perhelion 20:27, 17 July 2018 (UTC)
I looked in the code and indeed, all 'valued', 'quality' and 'featured' image files are protected, I guess this should be documented. -- User: Perhelion 20:32, 17 July 2018 (UTC)
@Perhelion: "The overwrite option is disabled because the image has passed an assessment process." (I just loaded Croptool again and clicked preview, just like I did before)
Documentation is one thing, I just need to override this kind of "protection". There is also (unrelated) an overwrite protection for artworks (probably intended to force users to upload retouched versions as new files) that likely resulted mostly in users not uploading higher resolution versions of artworks. These kinds of protections are stupid. - Alexis Jazz ping plz 20:39, 17 July 2018 (UTC)
@Alexis Jazz: I believe the theory is that files which have passed an assessment process or have been documented as artworks have done so with significant scrutiny, and any changes should undergo the same scrutiny with different filenames. However, I like your crop better than any of the other versions, so maybe some user groups could be excepted.   — Jeff G. ツ please ping or talk to me 20:49, 17 July 2018 (UTC)
@Jeff G.: the first crop was not lossless, that was my initial reason to make a new crop. {{PD-art}} gets applied to everything and their mother without any kind of scrutiny, but it's another story. That protection also confused bots. I'm not sure that protection is still active, I hope not. - Alexis Jazz ping plz 21:09, 17 July 2018 (UTC)

Button pushers push buttons

Been fine all day, but now getting a 503 error. GMGtalk 18:48, 25 July 2018 (UTC)

aaaand back. Thanks to whoever did something, or nothing. Or maybe I should give it twenty or thirty minutes before posting here next time. GMGtalk 18:54, 25 July 2018 (UTC)

Not artwork

I got an error about overwriting artwork when trying to overwrite File:Museum of Anthropology Armenians 08.jpg:

Upload failed! [api] Received error: abusefilter-warning : ⧼abusefilter-warning-overwriting-artwork⧽

Bull, the only "artwork" that's there: 

{{delete|reason=[[COM:DW]] of artworks whose copyright status is unclear.|subpage=Files in Category:Archbishop Ardak Manoukian Museum|year=2018|month=August|day=1}}

- Alexis Jazz ping plz 15:13, 1 August 2018 (UTC)

Alexis Jazz: That's an issue with the Commons Abuse Filter, specifically Filter 176 ("Overwriting artworks"). It was triggered, as you guessed, by the deletion nomination tag...it simply triggers on any instance of the word "artwork" in the wikitext. There's nothing that CropTool can do differently here. You should be cropping to a different file name any time that a crop is significantly changing the composition of the original image, and looking at your recent overwrites of that image, these are quite significant. — Huntster (t @ c) 20:43, 1 August 2018 (UTC)
@Huntster: they had to be, the alternative is to delete the file completely. If I would crop to a new file, that new file would later be nominated for deletion by someone because "the original was deleted", so overwriting is better. - Alexis Jazz ping plz 20:49, 1 August 2018 (UTC)
Alexis Jazz, I mean, that falls afoul of Commons:Overwriting existing files. The newly cropped file won't be deleted simply because the original was deleted, so long as there is a source URL present and there's no offending copyrighted material in the new work...in the case of File:Museum of Anthropology Armenians 08.jpg, as it stands, there is nothing copyrightable that wouldn't be considered de minimis. Just, in the future, use different filenames, and if someone tries to make a deletion statement, argue it as you would with anything else on Commons. Anyone making such a deletion claim like "the original was deleted" as the sole rationale should be bapped on the nose. — Huntster (t @ c) 21:18, 1 August 2018 (UTC)
@Huntster: Sorry, you're wrong. I've seen it before. Files get deleted because the source is gone. I may not be active on Commons if someone make a DR years from now, so I may not be able to argue that DR. People who make such deletion claims should indeed be bapped on the nose, but instead they are usually given a medal (or the mop). And yes, File:Museum of Anthropology Armenians 08.jpg is safe now, because I've cropped it. The original file, not so sure. The painting may or may not be considered DM, but I'm also not sure about the Christmas tree. Because it's not a real tree. Can a plastic Christmas tree really be considered a utilitarian object? I'm not entirely sure, but I have my doubts. It's not really relevant for the image anyway, the chair and cabinet on the right are not important and if we are calling the painting DM there can be no harm in cropping it. Leaving us with exactly what I cropped. - Alexis Jazz ping plz 22:59, 1 August 2018 (UTC)
By the way, about Special:AbuseFilter/176: that should be disabled entirely anyway. The only thing it does is deny us higher-resolution overwrites from good faith users (and in some cases, bots). It doesn't prevent any noteworthy amount of abuse. - Alexis Jazz ping plz 23:04, 1 August 2018 (UTC)
I'm not saying it doesn't happen, I'm saying it's still the wrong way to go about things. Regardless, the Christmas tree is definitely a utilitarian object, and nothing else notable in that image would fall under copyright or require a DM consideration. I'd suggest discussing the edit filter issue at Commons:Abuse filter...that's a topic I have no experience in. — Huntster (t @ c) 03:03, 2 August 2018 (UTC)
@Huntster: I'm just curious and I could be wrong so please enlighten me: what is the use (utilitarian) of a plastic Christmas tree, other than decoration? I just can't think of anything. - Alexis Jazz ping plz 04:35, 2 August 2018 (UTC)
@Alexis Jazz: The use is supporting belief, faith, lights, ornaments, etc. while reducing long-term costs and keeping pine needles off the floor. In a store or mall, the use is additionally to spur and prolong the Christmas gifting spirit of shoppers.   — Jeff G. ツ please ping or talk to me 12:28, 3 August 2018 (UTC)
@Jeff G.: Supporting belief and faith is also done by religious statues, are those utilitarian too? Plastic trees are a convenient replacement for real trees, but does that mean a convenient replacement for the real Santa Claus is also utilitarian? If encouraging the Christmas gifting spirit makes something utilitarian I guess all this crap is utilitarian too? The only way I really see is to consider a plastic tree as a thing to keep up lights, a glorified holder. Not sure that would hold up. And perhaps the bare plastic tree would be considered too similar to the original to be eligible for copyright. - Alexis Jazz ping plz 13:21, 3 August 2018 (UTC)

Old versions

CropTool could work also on previous version(s) of files (not only the latest one). miktalk 10:36, 2 August 2018 (UTC)

Yes, I know several images needing exactly this. Incnis Mrsi (talk) 06:06, 3 August 2018 (UTC)
@Mik and Incnis Mrsi: Until that suggestion is implemented, you can ask for previous versions of images to be cropped at Commons:Graphic Lab/Photography workshop‎.   — Jeff G. ツ please ping or talk to me 12:06, 3 August 2018 (UTC)
@Jeff G.: I’ll better use jpegtran myself rather than request such things on-wiki. Incnis Mrsi (talk) 12:16, 3 August 2018 (UTC)

CropTool taking forever

Tracked in Phabricator
Task T198503

Stuck on "just a moment" for several minutes, needs to be restarted. Editorofthewiki (talk) 22:17, 2 August 2018 (UTC)

@Editorofthewiki and Danmichaelo: I have confirmed and reported this at https://github.com/danmichaelo/croptool/issues/116.   — Jeff G. ツ please ping or talk to me 02:28, 3 August 2018 (UTC)
@Editorofthewiki: It has been restarted again and the issue has been folded into the ongoing task.   — Jeff G. ツ please ping or talk to me 12:16, 3 August 2018 (UTC)

description/categories

Example for Original file description -- Geagea (talk) 12:09, 20 October 2018 (UTC)

Two things are bother me in the new cropped file:
The new file always gets the old description. I suggest that the description should get Original file description: ... It is also be good if we can have the option to add new description.
Also it will be nice if we can remove and add categories. -- Geagea (talk) 11:35, 21 August 2018 (UTC)

More simply, it would be nice if it would just open the full description page before committing the upload so that all the things could be adjusted as needed. — Huntster (t @ c) 13:28, 21 August 2018 (UTC)
I don't understand the advantages in the workflow in comparison to the status quo. Right now, CropTool links you to the new description page, which you can then edit like any other page, with all the usual tools like HotCat. I don't see the use of reimplementing an editing interface or adding anything else just so that a "wrong" description page isn't displayed for a few minutes until the cropping editor gets to updating it – there's no real harm in this. What's being proposed here seems like bloatware to me. Tokfo (talk) 04:21, 22 August 2018 (UTC)
It's a matter of simplifying the process. Reduce two or more steps into one streamlined process. — Huntster (t @ c) 06:56, 22 August 2018 (UTC)
Most of the users do not change the description, you can check it if you want, so the Original file description: ... is essential change. Also most of users do not remove extra categories. Maybe if they have the list of categories with +/- it would be easier for them remove them. When I see files edit summey: "Added/updated {{Image extracted}} using CropTool", I know that some categories should be removed. I think that the suggestion of Huntster is good also but not instead of my suggestion. -- Geagea (talk) 10:11, 22 August 2018 (UTC)
I agree and should have been more specific in my statement. Appending Original file description: ... would be an excellent step forward regardless. — Huntster (t @ c) 13:05, 22 August 2018 (UTC)
@Geagea: I like the use of {{Information field}} for this.   — Jeff G. ツ please ping or talk to me 12:52, 20 October 2018 (UTC)

Feature requests

Hi Danmichaelo,

According to this discussion (in German), it would be great, if the CropTool could name the original image as "source" and add the cropping user as additional "author" in the infobox. That's apparently necessary to fulfill all requirements of the CC licenses. Would you think that's possible?

Cheers,

--MB-one (talk) 13:34, 16 May 2018 (UTC)

Interesting discussion, I haven't really thought about licensing implications. I'll experiment a little to see what can be done. At least replacing the source field should be fairly straightforward. Adding the cropping user can probably be done in the simple cases where the information template is used in a fairly standard way at least. Guess "Cropped by X" should be a template so it can be translated. – Danmichaelo (δ) 11:27, 19 May 2018 (UTC)
How about if the Tool checks, if the CropUser ist the original uploader (then does nothing), otherwise uses a cropped-template, that uses tilde-characters as the default parameter, but can be replaced with input from the tool? --C.Suthorn (talk) 09:02, 24 October 2018 (UTC)

Precise/lossless mode

I suggest renaming "precise" mode to "lossy" mode and "lossless" to "quality" mode (leave the descriptions intact). And make sure lossless (quality) is the default (I'm not sure if it already is).

People seem to select "precise" pretty much always when 9 times out of 10 (if not more) there was no need. Precise sounds good, "lossless" has no meaning to them. - Alexis Jazz ping plz 01:08, 10 November 2018 (UTC)

Alexis Jazz If you write only "lossy" you can be sure that no one will be use it forever :). Before using crop tool people must read the guidelines, where modes are fully detailed. Moreover 9 time of 10 people use the lossy mode but do not overwrite the original image. So there is no actually any loss of quality. Lossless mode it's very time consuming because you need many attempts to reach your goal--Pierpao.lo (listening) 15:46, 10 November 2018 (UTC)
Why not both? If you make each option occupy one line, there's enough space to write something like:
  • Precise crop (will lose quality)
  • Preserve quality (slightly larger crop)
If it's possible (now in the realm of feature requests), the tool could even pre-calculate how many pixels larger the losslessly cropped image will be, and then
  • tell the user something like "3px taller, 4px wider than selected", or
  • only allow the user to select an area of sizes that will be preserved precisely while "lossless" is selected, and/or
  • not allow the user to select "precise" at all if that calculation yields 0px taller and 0px wider.
I don't know how easy that is; can that calculation be done if you input only the image dimensions and desired cropped area? Tokfo (talk) 16:00, 10 November 2018 (UTC)
@Tokfo: Anything is possible. I don't maintain the tool though. Your suggestion with two lines would also be fine. Automatically switching to lossless mode when the calculation is 0px 0px shouldn't be super hard, but I can't say for sure.
@Pierpao: Lossless is only an issue if you are cropping a 640 × 480 photo. On a 3000 × 2000 photo, the maximum 7 pixels rounding error is just 0.35% of those 2000 pixels and 0.23% of those 3000 pixels. And that's if you get the maximum error. - Alexis Jazz ping plz 19:53, 10 November 2018 (UTC)

Converting file type

It would be great if it would become possible to upload the cropped image in a different file type compared to the original image. This would be useful if the filetype of the original image is not appropriate (e.g. PNG for photographs or JPEG or diagrams). --Leyo 15:30, 3 January 2018 (UTC)

I carried it on GitHub. -- User: Perhelion 23:08, 19 January 2018 (UTC)
Thanks, I spotted it there. Let's hope for an implementation. --Leyo 14:58, 31 January 2018 (UTC)
@Danmichaelo: What's the status? --Leyo 23:05, 10 November 2018 (UTC)
There's a few other things I'm planning to do with Croptool first, but you'r welcome to upvote the issue on GitHub if you would like to have it prioritized. – Danmichaelo (δ) 20:04, 11 November 2018 (UTC)

Abuse Warning

I try to remove a non free frame, uploading on the same image of course but I received an abuse warning. Why? it is a nonsense--Pierpao.lo (listening) 15:48, 10 November 2018 (UTC)

It's unlikely that anyone will be able to help you if you don't say which image you're talking about. Tokfo (talk) 16:07, 10 November 2018 (UTC)
@Pierpao: your file is probably classified as "artwork". Just hit upload again (make sure overwrite is still selected), it'll come through. - Alexis Jazz ping plz 19:58, 10 November 2018 (UTC)
Thanks Alexis Jazz and Tokfo--Pierpao.lo (listening) 09:05, 11 November 2018 (UTC)

Flip over

Another useful feature would be to (losslessly) mirror a picture (horizontally or vertically). miktalk 07:48, 21 August 2018 (UTC)

This sounds like something closer to the scope of User:Rotatebot than CropTool. Tokfo (talk) 04:23, 22 August 2018 (UTC)
As long as it is restricted to lossless rotations, it would be helpful to be able to do it on the spot with a tool rather than to have to wait for a bot. --MB-one (talk) 08:48, 22 August 2018 (UTC)
If something like this were to be implemented (by any tool), a note regarding guidelines on usage should be added, see explanatory text at Category:Flopped images and Category:Flopped images of persons. Flopped images depicting people, works of art, or other identifiable objects should generally not be used if it would mislead the viewer. Flopping images of animals, symbols, or objects (tools, food, etc) is a more appropriate usage, as would be fixing images that are incorrectly flopped or flipped. --Animalparty (talk) 23:40, 10 May 2019 (UTC)

Received only 6141873 of 7547111 bytes

File:Sriwijaya Air Boeing 737-236, Lion Air Boeing 737-4Y0, and Express Air Boeing 737-337; @CGK 2014 (14805654601).jpg

"Received only 6141873 of 7547111 bytes from https://upload.wikimedia.org/wikipedia/commons/5/52/Sriwijaya_Air_Boeing_737-236%2C_Lion_Air_Boeing_737-4Y0%2C_and_Express_Air_Boeing_737-337%3B_%40CGK_2014_%2814805654601%29.jpg before the server closed the connection. Please retry in a moment."

- Alexis Jazz ping plz 14:41, 1 December 2018 (UTC)

This has been happening randomly for the past few days. It's not just affecting CropTool, but everyone who tries to download full-size images from Commons, see phab:T210890. I'm considering adding a workaround (resume the broken download in some way), but will give it a few days first to see if they can fix the issue. – Danmichaelo (δ) 22:35, 3 December 2018 (UTC)
Changed my mind and added a workaround now. Turned out to be not much work, but loading will be slower until the issue is resolved. – Danmichaelo (δ) 22:59, 3 December 2018 (UTC)

Time out: 502 Bad Gateway

@Danmichaelo: , CropTool seems to have a problem. After a long time out I see: "502 Bad Gateway nginx/1.13.6" - Robotje (talk) 11:30, 17 December 2018 (UTC)

Now it works again. If somebody did a restart or so, thanks for that. - Robotje (talk) 12:26, 17 December 2018 (UTC)
Yeah, I had to restart it earlier today. – Danmichaelo (δ) 16:46, 17 December 2018 (UTC)
@Danmichaelo: Thanks, still no joy with auto-restart?   — Jeff G. ツ please ping or talk to me 17:45, 17 December 2018 (UTC)
Nope, not yet. – Danmichaelo (δ) 18:19, 17 December 2018 (UTC)

Blue Winged Kookaburra-4 (11407435085).png

To my surprise, the CropTool has removed the Adobe RGB (1998) ICC profile. This happened only on PNG images, with JPGs is everything OK. --Ras67 (talk) 15:03, 4 January 2019 (UTC)

Need to look more into this. Created an issue to track it: https://github.com/danmichaelo/croptool/issues/128 – Danmichaelo (δ) 06:35, 20 February 2019 (UTC)

does not work for yuewp

Try https://zh-yue.wikipedia.org/wiki/File:Ju_Deyuan_20140202.jpg . Does it say file not found? I guess this bug is related to the irregular langcode too.--Roy17 (talk) 00:54, 8 January 2019 (UTC)

@Roy17: This has now been fixed, thanks for reporting. – Danmichaelo (δ) 06:34, 20 February 2019 (UTC)

Requests/wishlist

I use CropTool often, it's a great time saver and tool. I just have some suggestions for ways to improve it:

  • When toggling between Aspect ratios (Free, Keep, Custom), it would be nice if the selection window stayed put (or at least somewhat) rather than jumping back to a default position in the center: often times while trying to keep the original aspect ratio I'll zoom in and position, only to realize that a Free size would make a bit more sense (e.g. left edge needs to come in just a bit), yet clicking Free forces me to readjust and re-center the selection window rather than just making a slight change.
  • I've recently been using the Custom aspect ratio settings more often, to make crops a bit more standard. I think a good addition would be a pop-up menu or drop down selectable menu with some of the most commonly used standard aspect ratios (e.g. 3:2, 4:3, 16:9, 1:1, see [1] and [2]). I think this would aid in improving the aesthetics of crops, and making it easier for people to find ratios that 'look good' without too much tinkering or background knowledge of photographic composition. Of course, they could enter their own truly custom ratios as well.
  • It would be helpful to have an option to rotate the crop window (not the image) 90 degrees, and back, with one click, e.g. for extracting a nicely composed portrait out of a landscape-oriented photo. I think the more easily one can visualize different crops, and toggle between them, the quality of such crops will be improved. Thanks! --Animalparty (talk) 19:33, 17 January 2019 (UTC)
@Jeff G.: It seems that with large files it sometimes takes a few tries before everything loads smoothly. Like sometimes the first try I'll get a broken image link, and the second try the image will load but then an error arises during preview. It could just be a connection issue on my end. --Animalparty (talk) 04:44, 31 January 2019 (UTC)
@Animalparty: Do you still have problems with large images? In general it's supposed to work with files up to around 50 MB, but I guess timeouts can happen if the server is busy in general. If you have some recent examples, I'm happy to check if there's something interesting in the logs. – Danmichaelo (δ) 23:32, 19 February 2019 (UTC)
I haven't noticed insurmountable problems lately: some large images just take a couple attempts to go smoothly. --Animalparty (talk) 23:34, 19 February 2019 (UTC)
A couple attempts still sounds a bit annoying. If you happen to remember an example, let me know. Or when it happens again. And thanks for the ideas btw., agree that they would improve the tool. I'll add them to my list. – Danmichaelo (δ) 23:42, 19 February 2019 (UTC)

Errors

Anybody else getting 502 and 503 errors until you just button mash refresh till it works? I mean, it does eventually work, but it takes like a dozen refreshes. GMGtalk 17:39, 12 February 2019 (UTC)

Bueller?...Bueller? GMGtalk 13:35, 14 February 2019 (UTC)
@GreenMeansGo and Danmichaelo: I did not experience that, but I did experience "Upload failed! [api] Received error: verification-error : File extension ".pdf" does not match the detected MIME type of the file (image/jpeg)." and untrue "The overwrite option is disabled because this is a multipage file." when trying to crop File:1900 Utah Agricultural College football team.pdf.   — Jeff G. ツ please ping or talk to me 14:50, 14 February 2019 (UTC)
Evad37, you apparently can do computer magic. Any chance you can help us peons over at Commons? GMGtalk 00:31, 15 February 2019 (UTC)
Hi all. I did take a quick look at the source code, but couldn't see any obvious problems. There does seem to be relatively recent activity (Dec 2018) on the Github repo, so you could try adding new issues for these bugs over there, or contacting the main contributor danmichaelo. - Evad37 [talk] 01:06, 15 February 2019 (UTC)
@Evad37: I pinged him at 14:50 UTC, three posts back.   — Jeff G. ツ please ping or talk to me 02:41, 15 February 2019 (UTC)
I've filed these as issue #124 and issue #125 on GitHub - Evad37 [talk] 02:49, 16 February 2019 (UTC)
Thanks for filing the issues and sorry for my slow reply. My activity is a bit on and off due to other projects, but I'm still (actively) maintaining CropTool and over time I hope to be able to swap some components to possibly reduce the number of 5XX incidents. And Jeff_G., I'll look into the PDF issues – Croptool do not have support for creating PDF files, so it should automatically suggest a .jpg extension for the new file, but apparently it does not. Of course, being able to choose between jpg and png would also be good. – Danmichaelo (δ) 23:20, 19 February 2019 (UTC)
@Danmichaelo: Thanks.   — Jeff G. ツ please ping or talk to me 02:20, 20 February 2019 (UTC)
@GreenMeansGo and Danmichaelo: I reported the "No webservice" issue at https://github.com/danmichaelo/croptool/issues/130.   — Jeff G. ツ please ping or talk to me 14:38, 7 March 2019 (UTC)
@Danmichaelo: Thanks for restarting it. @GreenMeansGo: Please try again.   — Jeff G. ツ please ping or talk to me 15:08, 8 March 2019 (UTC)
I managed to crop three of the six files I couldn't yesterday. But I'm still getting 502 and 503 errors, and half the time when I am able to set the proportions for the crop, it fails to upload. GMGtalk 15:57, 8 March 2019 (UTC)
@GreenMeansGo: Please ping @Danmichaelo when reporting such errors here, and consider reporting such things on github.   — Jeff G. ツ please ping or talk to me 20:37, 8 March 2019 (UTC)
I'll try to remember to ping. I'm afraid Github is beyond my technical competence, as is much of what goes on at phab. GMGtalk 15:59, 9 March 2019 (UTC)
@GreenMeansGo: Thanks. Writing Github Issues and Phabricator Tasks is easy if you stick to text and bare URLs.   — Jeff G. ツ please ping or talk to me 18:22, 9 March 2019 (UTC)

jpegtran exited with code 2

@Danmichaelo: I got "[Error] Command "/data/project/croptool/jpeg-9a/jpegtran -copy all -crop '3024x1189+0+0' '/mnt/nfs/labstore-secondary-tools-project/croptool/public_html/files/b920c594697f84cc1a30698e1ce76b08ec330ee7.jpg' > '/mnt/nfs/labstore-secondary-tools-project/croptool/public_html/files/b920c594697f84cc1a30698e1ce76b08ec330ee7_cropped.jpg' 2>&1" exited with code 2: 2" while trying to crop File:2019 Virginia Avenue train tunnel entrance.jpg. See also https://github.com/danmichaelo/croptool/issues/131.   — Jeff G. ツ please ping or talk to me 14:57, 9 March 2019 (UTC)

Seems like jpegtran (lossless) fails for incomplete JPEG files. Precise/lossy cropping most likely still works though. – Danmichaelo (δ) 15:05, 10 April 2019 (UTC)

Stopped working

After using the tool hundreds of times, it's stopped working for me. I always go from a media file, & for the first time it now asks me what file I want to crop. When I enter the file name, nothing happens. Why?

Also, it's long been a problem that I have to do the log-in/connect/authorization thing randomly every few times I use the tool. It's supposed to be one-off, but I must have done it dozens of times. Johnbod (talk) 15:38, 16 March 2019 (UTC)

@Johnbod: The first part sounds like it might have been related to the bug I fixed yesterday. Let me know if you still have problems (please provide a link to an example image). As for the authorization issue, I'm not aware of specific issues on that side. If you use the same browser and don't wipe cookies, you should remain logged in for a long time (a year I think), but there might of course be some issue I'm just not aware of on that side. – Danmichaelo (δ) 20:13, 25 March 2019 (UTC)
Ok thanks - I do wipe cookies, though I think the authorization is required more often than I do that. By the way, I tend to get 2 "Crop tool" sidebar entries, & I found one of them had the first problem above, and the other didn't. Cheers, Johnbod (talk) 21:11, 25 March 2019 (UTC)
Oh dear. After restarting my machines - I now have exactly the same problem, so can't use the crop tool. There's no point "providing a link to an example image" as all images take me to the same page which doesn't work. I get asked "What to crop? / Enter the URL or filename for an image you would like to crop." I put the file name in, it confirms it exists, then I press "Open" and NOTHING HAPPENS. EVER! Johnbod (talk) 15:22, 27 March 2019 (UTC)
@Johnbod: It works for me. Did you "connect it to your Wikimedia account" or reauthorize with OAuth? What file were you trying to crop?   — Jeff G. ツ please ping or talk to me 00:08, 28 March 2019 (UTC)
Yes, yet again. It was the same with ALL files, but now it is working again. And once again I have two Crop tools on my sidebar (both of which now work - at first only one did). Is it possible it takes 3+ hours after re-re-authorizing for the tool to work properly? Johnbod (talk) 03:40, 28 March 2019 (UTC)
@Johnbod: Try removing the code from User:Johnbod/common.js and you should get rid of the duplicate link. – Danmichaelo (δ) 19:19, 2 April 2019 (UTC)
Hmm - that might well remove the one that works! Johnbod (talk) 19:39, 2 April 2019 (UTC)
@Johnbod: Probably not, the escaping is better in MediaWiki:Gadget-CropTool.js than in your version. – Danmichaelo (δ) 15:07, 10 April 2019 (UTC)
Ok, thanks - next time I have trouble - for now it's fine. Johnbod (talk) 15:11, 10 April 2019 (UTC)

autoblocked?

When attempting to upload a crop of this image I repeatedly receive the message "Upload failed! [api] Received error: autoblocked : Your IP address has been blocked automatically, because it was used by a blocked user." As far as I know, I am not blocked and am the only one using my IP address. This persists after logging out and re-authorizing with CropTool. Is this a glitch or am I somehow shadow blocked? --Animalparty (talk) 20:06, 18 April 2019 (UTC)

Does Animalparty expect CropTool to do data processing inside the user’s browser, seriously? Incnis Mrsi (talk) 20:23, 18 April 2019 (UTC)
@Incnis Mrsi: I'm just trying to troubleshoot a problem. I don't fully understand your question. I was able to use the tool this morning, and now I can't. I'm able to upload using Flickr2Commons. I'm not asking anyone to look at my browser, seriously. --Animalparty (talk) 20:28, 18 April 2019 (UTC)
@Animalparty: I don't think it's just you - I'm getting the same error message. @Danmichaelo: Did you change something recently, or is this a Labs problem? Pi.1415926535 (talk) 20:57, 18 April 2019 (UTC)
@Pi.1415926535: Nope, didn't change something recently. Not sure if it's caused by a local block here at Commons, or something else, but I tried reporting it at Commons:Administrators' noticeboard/Blocks and protections in any case. Special:Log is timing out at the moment, so I'm not able to check. – Danmichaelo (δ) 13:39, 19 April 2019 (UTC)

Blocked by this tool without reason or notification

I don't use this tool by blocked message: 

Upload failed! [api] Received error: autoblocked : Your IP address has been blocked automatically, because it was used by a blocked user.

I do not know why I was blocked without notification, or for what reason. Thanks Shooke (Talk me in spanish, english or italian) 22:24, 18 April 2019 (UTC)

@Shooke: Don't worry. This message means that the server IP has been blocked, not you. But why is there an IP block on the Toolforge server? I have no idea, will try to find out. – Danmichaelo (δ) 13:22, 19 April 2019 (UTC)
@Danmichaelo: OK, Saludos Shooke (Talk me in spanish, english or italian) 13:29, 19 April 2019 (UTC)
Ok, so it's back working after 4nn1l2 from Commons:Administrators' noticeboard/Blocks and protections helped unlifting the autoblock of a user that had happened to have used CropTool before being blocked. It's a little surprising that IPs used when editing through tools like CropTool are included in the set of autoblocked IPs, but that seems to be the situation. – Danmichaelo (δ) 15:11, 19 April 2019 (UTC)
The IP range for Toolforge was just added to MediaWiki:Autoblock whitelist. I'm not 100 % sure, but thi might prevent this problem from happening again in the future. – Danmichaelo (δ) 18:36, 19 April 2019 (UTC)
Thanks for your quick response! Pi.1415926535 (talk) 21:33, 19 April 2019 (UTC)

Can 'overwrite' been changed as default setting?

CropTool uses "overwrite" (the old file) as a default setting, whereas I consider "upload as new file" a better option, because the original file will sill exist and can still be used on Commons. Is it possible to change the default setting to "upload as new file"? Ymnes (talk) 09:33, 4 May 2019 (UTC)

webp files

It seems that the tool can't yet handle webp files like File:Theatre, Birmingham - circa 1774-1779 - attributed to Hubert Cornish.webp. Could that be enabled, please? — Preceding unsigned comment added by Pigsonthewing (talk • contribs) 20:07, 7 May 2019‎ (UTC)

Correct, that is something that should be added. I created an issue for it here: https://github.com/danmichaelo/croptool/issues/136 – Danmichaelo (δ) 22:41, 17 June 2019 (UTC)

croptool not appearing on file page

I am trying to split this image into two new pics, and the CropTool is not showing in the sidebar. I also get an error using the URL version: 

File «Parasite140083-fig3 Figs 15-22.tif» found on «commons.wikimedia.org».

I've used the tool many times before. --NessieVL (talk) 14:32, 6 June 2019 (UTC)

Apparently the tool just doesn't like that it is a TIFF file, since it is appearing correctly elsewhere. Hmm. — Huntster (t @ c) 02:31, 7 June 2019 (UTC)
Yeah, the tool is only built for jpg, png, and gif files currently. You can do it locally with GIMP or other image editing tools. Pi.1415926535 (talk) 02:43, 7 June 2019 (UTC)
Okay, then the description page may not want to read "It supports JPEG, PNG, TIFF and (animated) GIF files, and can also extract single pages from DJVU and PDF files as JPEG for cropping." ? — Huntster (t @ c) 09:37, 7 June 2019 (UTC)
Pinging @Danmichaelo.   — Jeff G. ツ please ping or talk to me 16:37, 7 June 2019 (UTC)
@NessieVL, Huntster, and Pi.1415926535: Sorry for the slow reply! Turned out tiff support was broken after an upgrade, but it's now back working. – Danmichaelo (δ) 22:38, 17 June 2019 (UTC)
As for it now showing in the menu for TIFF files, it should once this edit request is processed. – Danmichaelo (δ) 22:46, 17 June 2019 (UTC)
Thanks for taking care of this, Danmichaelo! — Huntster (t @ c) 23:01, 17 June 2019 (UTC)
Thanks for the fix. I was able to crop the image (twice, actually) using the 'manual' mode. However, the tool still does not appear in the sidebar for that image. --NessieVL (talk) 12:41, 19 June 2019 (UTC)
Yeah, I'm waiting for some Commons administrator to handle this: MediaWiki_talk:Gadget-CropTool.js#Add_TIFF. – Danmichaelo (δ) 20:56, 22 June 2019 (UTC)

Uploading over redirects

I fairly often see the tool uploading over redirects, e.g., [3]. Can you please put in a check to disallow this? Thanks. Magog the Ogre (talk) (contribs) 22:13, 5 July 2019 (UTC)

It should no longer load in a redirect page. Masum Reza📞 04:59, 19 October 2019 (UTC)
@Magog the Ogre: Hm, that's odd. It's supposed to show a warning before overwriting any page, redirect or not: https://github.com/danmichaelo/croptool/issues/98 . Do you see this from multiple users? – Danmichaelo (δ) 12:11, 19 November 2019 (UTC)
@Danmichaelo: I don't use the tool. I only see its effects. Magog the Ogre (talk) (contribs) 23:14, 19 November 2019 (UTC)

Unable to crop

CropTool doesn't seem to like Robert Banks Jenkinson, 2nd Earl of Liverpool.jpg. The file size is 421.59 MB. Perhaps this might be beyond the capabilities of the tool? Can anyone help me with this? AlbanGeller (talk) 04:48, 19 October 2019 (UTC)

Could you describe the problem in detail? Are you able to see the image in CropTool interface? Or it's just taking too much time to load? Masum Reza📞 04:57, 19 October 2019 (UTC)
It just times out after loading for five minutes. The page resets itself. AlbanGeller (talk) 04:59, 19 October 2019 (UTC)
The tool itself downloads images from Commons before cropping. That image probably is the biggest in size I've seen. It would take some time to download it, then prepare it for cropping. No wonder it just times out. Try to crop it in your computer. :P Masum Reza📞 05:06, 19 October 2019 (UTC)
@Danmichaelo: Could you look into this? Masum Reza📞 05:09, 19 October 2019 (UTC)
@AlbanGeller and Masumrezarock100: Sorry, didn't see this! Yeah, it runs on the shared environment at Toolforge and unfortunately doesn't handle very large files. It used to show an error for images larger than 100 megapixels[4], but seems like that got lost during some refactoring. I'll try to get that back since it would at least be better to have an error message than just a spinner that never ends. – Danmichaelo (δ) 11:58, 19 November 2019 (UTC)

Unable 2 crop, yet new suggested name is added onto the original image

I tried cropping this image: File:A mikxture of liverworts from Kunstformen der Natur (1904), plate 82.jpg, in order to extract one species: Scapania subalpina (Dumortier) = Scapania subalpina (Nees ex Lindenb.) Dumort., gametophyte. The tool works, creates a boundary around this species, but I'm unable to save with new name 'Scapania subalpina (Dumortier) gametophyte'. The error given is 'Upload failed because of the following warning(s): badfilename'. I wonder what seems to be the problem? Cell Danwydd (talk) 14:11, 5 December 2019 (UTC)

Standard ratios

As well as being able to set the aspect ratio to "Free", "Keep" or "Custom", it would be good to be able to select from a short list of pre-defined standard ratios, such as, say, 4:5/5:4, 9:16/16:9, etc. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:12, 15 November 2019 (UTC)

Ah, yeah, this one: https://github.com/danmichaelo/croptool/issues/99 :) Agree it would be good to have, just haven't prioritized fixing it yet. – Danmichaelo (δ) 12:05, 19 November 2019 (UTC)
I'd forgotten raising that (tbf: in 2017); in fact I'd forgotten there is a GitHub page! Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:45, 20 December 2019 (UTC)

Remember my last crop

I've just cropped a small number of images, all to the same dimensions, (example 1, example 2). Each time, I had to redraw the outline; it would be helpful if CropTool could remember the dimensions and location of my last crop; or at least offer a setting to do so. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:40, 20 December 2019 (UTC)

Now on GitHub: [5]. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:47, 20 December 2019 (UTC)

Installation

@Danmichaelo: Hello! Is there a way to install this tool globally? As you can with User:Rillke/SVGedit.js? I think that would be nice :). Taking the talk here instead of your talk page so others like me can see my question and your answer.Jonteemil (talk) 00:23, 17 February 2020 (UTC)

@Jonteemil: Yes. Make sure to disable the local gadget here at Commons first to avoid getting the link twice. Then add something like this to your m:Special:MyPage/global.js:
if (mw.config.get('wgNamespaceNumber') === 6 && mw.config.get('wgIsArticle') &&
	/(PNG|GIF|JPE?G|DJVU|PDF|TIF?F)/i.test(mw.config.get('wgTitle').slice(-4)))
    mw.loader.load( '//commons.wikimedia.org/w/index.php?title=MediaWiki:Gadget-CropTool.js&action=raw&ctype=text/javascript' );
Since MediaWiki:Gadget-CropTool.js includes its own check for file extension, you could also use this slightly shorter version, which also do not limit you to the currently supported extensions if more are added in the future:
if (mw.config.get('wgNamespaceNumber') === 6 && mw.config.get('wgIsArticle'))
    mw.loader.load( '//commons.wikimedia.org/w/index.php?title=MediaWiki:Gadget-CropTool.js&action=raw&ctype=text/javascript' );
– Danmichaelo (δ) 16:21, 18 February 2020 (UTC)
Okay, I think I’ll use the shorter version then. Thanks!Jonteemil (talk) 23:38, 18 February 2020 (UTC)

Great tool

Just discovered this, great tool; that said while it automatically removes the image from the watermarked category, it leaves images in Category:Images requiring trimming as evidenced with File:高輪海岸の石垣石0308.JPG FaNoFtHeAiRiCeLaNd (talk) 19:32, 9 January 2020 (UTC)

@FaNoFtHeAiRiCeLaNd: A very neat tool indeed! What do you mean with the tool automatically removing images from the watermarked category? {{Trimming}} was added before the cropped versions were uploaded in the file you mentioned. Also, when you have trimmed the files you can remove the template :).Jonteemil (talk) 22:38, 2 March 2020 (UTC)
@FaNoFtHeAiRiCeLaNd and Jonteemil: Actually, it should be able to remove {{Trimming}} as well. When cropping a page with such a template, CropTool should show a checkbox "I've trimmed the image" checkbox, which, if checked, removes the template. It's a little late to debug now, but let me know if there's still an issue with this. By the way, I just noticed that there was a new alias {{Remove frame}} to {{Remove border}}, so I added support for that one now. – Danmichaelo (δ) 19:34, 7 July 2020 (UTC)

.svg

Wondering what it would tag to get this tool working on .svg? User:Fæ just uploaded nearly 3,000 here[6] Doc James (talk · contribs · email) 22:15, 15 February 2020 (UTC)

An SVG guru can probably advise on how to tack on a viewBox for any image, which may be a workable way of doing it. Extending CropTool might not be too hard. But... I'm no SVG wizard. --Fæ (talk) 22:46, 15 February 2020 (UTC)

@Sarang, JoKalliauer, and Perhelion: Are you able to help? --Leyo 20:04, 16 May 2020 (UTC)

@Doc James: I do not see any relation to Category:Our_World_In_Data#mw-category-media.
As Fæ said, adding/editing viewBox is a duable way of lossless cropping. (thats completly different task than Croping Rasterimages).
The CropTool could crop (existing) PNG-Previews, however Previews are always (>99%) lossy (croping PNG is not lossy). And large lossy Previews need more disk-space than the lossless svg. (SVG-gurus will decline such sulutions, since they "kill" all advantages of svgs.)
 — Johannes Kalliauer - Talk | Contributions 10:02, 17 May 2020 (UTC)
User:JoKalliauer we have a lot of .svgs in that category. Often I want to crop off the top and put those details in a caption instead. And move the source to a reference. Doc James (talk · contribs · email) 12:27, 17 May 2020 (UTC)


@Doc James: I recommend to use User_talk:Rillke/SVGedit.js.
I explain the croping of File:Covid-confirmed-cases-since-100th-case.svg
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" style="font-family:Lato, &#x27;Helvetica Neue&#x27;, Helvetica, Arial, sans-serif;font-size:18px;background-color:white;text-rendering:optimizeLegibility;-webkit-font-smoothing:antialiased" width="850" height="600"><g class="HeaderView"><g transform="translate(774, 15) scale(0.29)"><svg width="210" height="120" viewBox="0 0 210 120" fill="none" xmlns="http://www.w3.org/2000/svg">
in the first tag 
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" style="font-family:Lato, &#x27;Helvetica Neue&#x27;, Helvetica, Arial, sans-serif;font-size:18px;background-color:white;text-rendering:optimizeLegibility;-webkit-font-smoothing:antialiased" width="850" height="600">
change width="850" height="600" to viewBox="0 0 850 600" this does not change anything, now crop the top by 70 and the bottom by 30, this results in viewBox="0 70 850 500" and "removes" the title and the source. (Actually it is still stored, but not visible in the visible part of the image)
Click preview and check result
so the second number in viewBox="0 70 850 500" is the offset from the top (70px) and the forth number ist the height (500) since 70 is removed at the top and 30 at the bottom it is 100 smaller than before.
I Know it is not a tool, but you see a Tool could be programmed quite easily
 — Johannes Kalliauer - Talk | Contributions 16:46, 17 May 2020 (UTC)

Okay thanks will look at this Doc James (talk · contribs · email) 01:19, 18 May 2020 (UTC)

Missed this discussion, but as mentioned on User_talk:Danmichaelo#I_would_like_to_expand_CropTool_with_svg-support, I'm happy to try to add SVG support to CropTool if provided with the necessary commands to do the cropping itself, since I'm not that familiar with SVG myself. – Danmichaelo (δ) 19:36, 7 July 2020 (UTC)

Rotation

First: this is a great tool, and I'll keep using it even if you don't address my issue, but...

In "precise" mode, when you start rotating the object, it does a sudden zoom in for no terribly apparent reason. I am guessing your intent is that you don't want people slopping off the edge of the image, but there really ought to be a way for an experienced user to override this. It is particularly annoying for those of us who are typically making adjustments of less than 1°, where they zoom in is quite excessive. Compounding the problem: if you use the mousewheel to zoom back out, you still seem to lose up to a few hundred pixels at the left edge, and there doesn't seem to be any way to see them or to use the graphical adjustment to bring the left edge of the selection past what is visible. I can usually get around this by working with the numeric part, but if I preview and don't have exactly what I want, going "back" snaps things back to the left edge of the visible portion, rather than leaving the numbers as I had them. Very annoying.

If any of that is unclear, I'll gladly do a Zoom session or some such to show you what happens, just get hold of me if you want that. - Jmabel ! talk 00:32, 13 May 2020 (UTC)

@Jmabel: Interesting, I normally don't use the zoom functionality myself, so I just haven't noticed how bad this was. From what I can see, there are at least two things that should be improved: (i) The crop box should not change when zooming (and it should probably be hidden initially, so that you can zoom in initially without having the default zoom box extend beyound the frame), and (ii) the zoom level and crop box should not change when rotating. Agree? I will look into if can address those in the coming weeks and let you know it goes. Update: Seems like I've actually tried to address the issue of selection changing upon zooming once before, but it seems to work better in the latest version of the library, so I will give it another try. – Danmichaelo (δ) 20:28, 7 July 2020 (UTC)
Great! - Jmabel ! talk 00:43, 8 July 2020 (UTC)

The tool returns "[error] undefined" when trying to rotate high resolution images by another value than 90. 180 or 270 degrees. Example: File:Potsdamer Platz Filmmuseum Boulevard der Stars Gerhard Lamprecht.jpg (crop to 6900x6900, rotate 20 degree, top: 2642, left: 2391) --C.Suthorn (talk) 05:27, 8 July 2020 (UTC)

Urgently missing features

Hello, this is a useful tool but it is being misused in some cases: 1) people create derivative works for fun without using them in any projects, furthermore 2) sometimes new versions are created for which a new version of the existing version should be enough and 3) it doesn't care about the categories, which may or not apply to the derivative work. I have tons of images on Commons and everytime I happen to see an edit with this tool I know that I will have to rework it. My suggestions for the 3 issues mentioned: 1) please, advise the user that creating new files consumes resources and therefore it shall only be done for a good purpose; 2) often a new version of the existing file fixes the problem (e.g. to get rid of a watermark), thus there should be an option whether creating a new file or updating the existing one; 3) All user categories (which are hidden) shouldn't be reused for the new file and categories like "Quality images of ..." or "Featured pictures of ..." or "Valued images..." should be removed if a new file is created as the derivative works are not eligible of those awards. Any chance to work on these topics! Thank you! Poco a poco (talk) 13:54, 5 April 2020 (UTC)

Poco, there are some issues with this request. 1) Commons does not discourage contributors based on a concern for "resource consumption". It never has and, unless something drastic changes, it never will. 2) The option to update the existing file or create a new file already exists here, so I'm not sure what you're wanting to be changed. 3) User categories should probably remain; in many cases, the uploader is also the author...simply cropping an image doesn't change that and the tool cannot determine when removal would be appropriate or not. That said, I absolutely agree that the Promotion-type categories you mention should be removed, as they only ever apply to a specific file. — Huntster (t @ c) 14:57, 5 April 2020 (UTC)
@Poco a poco: I've taken some steps in the past to try to address these issues. For instance, the automatic addition of {{Image extracted}} to the original image, to reduce the number of duplicate crops of the same image. Users who carry out a duplicate crop despite {{Image extracted}} being there, will probably also ignore a warning banner. When it comes to categories/templates, I maintain lists of templates and categories that should not be copied over to a new page. So CropTool should not copy categories/templates for "valued images" etc. If it does, it's either a bug, or a category/template which are not matched by my patterns. Please let me know if you come across specific examples, and I can look into them. – Danmichaelo (δ) 19:58, 7 July 2020 (UTC)
Hi Danmichaelo, thank you for your reply. In this example you can see a couple of examples of what could be removed after cropping: "Featured pictures..." and "Quality images...". It would be also great to replace "Images by ..." with "Derivative works from images by ..." (if the cat is existing), but not sure whether there is a convention for that. IMHO it would be the right thing to do. --Poco a poco (talk) 18:56, 8 July 2020 (UTC)

If the object (e.g. cars) is incidental, is it okay to crop it?

This picture (File:Crystal River Seafood, Tallahassee.JPG) also shows a Category:Toyota Corolla. Can I upload a cropped image of the car? SpinnerLaserz (talk) 03:20, 1 July 2020 (UTC)

  • If what you're cropping on is copyrighted, then possibly not, because the whole image may be covered by COM:DM but your crop may not. This isn't really a technical question about CropTool though, so doesn't really belong on this page. In general you can certainly do this, though in most cases it will result in a very low resolution image that may not be very useful if the subject is something we have other images of. Tokfo (talk) 15:33, 1 July 2020 (UTC)
    • But the image he was asking about is high enough resolution, and a car is a utilitarian object, so there is no problem with copyright. - Jmabel ! talk 19:32, 1 July 2020 (UTC)
      • I had a quick look at the image, and it appears to me that, while the original image is of high resolution, the resulting crop would be low quality. But this isn’t really the place for that discussion. Brianjd (talk) 14:12, 5 September 2020 (UTC)

Document overwrite vs upload as new file

I’ve just commented on a user dispute, where a user was warned against inappropriate overwriting of files and told to use CropTool. That user has expressed confusion, because this page does not mention that CropTool can save the crop as a new file. I could edit the page myself, but I’m not sure where the best place to mention this is. Brianjd (talk) 14:16, 5 September 2020 (UTC)

Deactivate

Is there some way to deactivate CropTool? I do not see any such information in the instructions. Thank you. Toccata quarta (talk) 16:57, 11 September 2020 (UTC)

Crop tool doesn't appear in my menu

I've activated CropTool. It shows as enabled (ticked) in my preferences|gadgets list. But it doesn't show up in Tools in my left menu bar. What am I missing? Thanks. Kognos (talk) 20:47, 17 September 2020 (UTC)

@Kognos: It shows up imho only on jpegs and pngs, did you try it on https://commons.wikimedia.org/wiki/File:Croptool-01.png ? does # CropTool show up ?  — Johannes Kalliauer - Talk | Contributions 07:59, 19 September 2020 (UTC)
@JoKalliauer: Thanks for responding even though the query is out of scope! I realised that it only shows in the tools when you have an appropriate file type in scope. Kognos (talk) 16:29, 20 September 2020 (UTC)

Removing a passage that seems to be outdated

This RecentChanges link: https://commons.wikimedia.org/w/index.php?hidebots=1&translations=filter&hideWikibase=1&tagfilter=OAuth+CID%3A+593&limit=1000&days=30&title=Special:RecentChanges&urlversion=2 is not working for me, so I removed it. —Justin (koavf)❤T☮C☺M☯ 00:37, 15 August 2020 (UTC)

@Koavf: I fixed it to reflect the new v1.5 tag in this edit.   — Jeff G. ツ please ping or talk to me 06:31, 13 December 2020 (UTC)

90° rotated

Why the CropTool yesterday and today charge the imagens rotated 90°? Can you correct the fault? Thanks. Leonprimer (talk) 00:29, 15 October 2020 (UTC)

Can you give an example? Been going through a few of your latest uploads and they looked fine to me? Jean-Fred (talk) 09:50, 15 October 2020 (UTC)
Jean-Frédéric, I just had a similar problem. I opened a vertical image in CropTool, and to make it look right in the tool, I needed to rotate it 90°. (The original image was 70% carpet and 30% object; the point was to crop it so it would be a horizontal image focused on the object.) But when it uploaded, the 90° rotation was wrong. I've asked the bot to un-rotate it, but there's something going wrong somewhere. Images shouldn't show up one way in the CropTool and a different way when they're uploaded. WhatamIdoing (talk) 19:19, 10 December 2020 (UTC)
Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons_talk:CropTool/Archive_2&oldid=572559880"