Commons talk:CropTool

This is the talk page for discussing improvements to Commons:CropTool.

• This is not a forum for general discussion of the page’s subject.
• Put new text under old text. Click here to start a new topic.
• Please sign and date your posts by typing four tildes (~~~~).
• New to Commons? Check out the project scope. Ask questions, get answers.

Archives: 1, 2, 3

	Maintenance notice
	Maintenance for this tool is at https://github.com/danmichaelo/croptool - please do not report bugs in Phabricator tasks. You can see the last edit it tagged here.

Lossless mode no longer working?

@Danmichaelo, is lossless mode still working. I used to get messages that the crop size had been adjusted because I wasn't starting on a multiple of 8 or 16, but this has gone away. Similarly, there's a bug report on github (#170) reporting that files that should be uncroppable in lossless mode are now working, but produce the same files as if they were in precise mode. Is the tool silently falling back to precise when lossless doesn't work (which would be undesirable), or is something else going on here? Perhaps a bug introduced in the September 2020 refactoring? Ahecht (TALK
PAGE) 14:59, 15 June 2022 (UTC)

Looking into the code more, it seems like the September 2020 refactor fundamentally broke things. The various types of crop were broken out into subclasses (for example, lossless Jpeg cropping was broken out into JpegFile and Gif cropping to GifFile), but as far as I can tell the only subclasses that are actually being called out by the program in FileRepository.php are TiffFile, DjvuFile, PdfFile, and SvgFile, all of which return errors instead of actually working. All other file types are being handled by the generic imagemagick call in File.php.

This is why lossless crops are no longer lossless, Gif files say they are being cropped with precise or lossless mode instead of "gif mode", and TIFFs, PDFs, and DJVUs no longer work.

If these issues aren't easy to resolve, perhaps to the tool should be rolled back to 1.4 (before the refactoring). Ahecht (TALK
PAGE) 14:18, 17 June 2022 (UTC)

just confirming this issue persists 2023-01.--RZuo (talk) 11:53, 15 January 2023 (UTC)

Since about 9-2021 Danmichaelo's only contributions have been edits to wikidata and some edits in norwegian and finnish wikipedia about some meta-topics (bot problems, ...). I seem to remember that them was unhappy with a decission at english wikipedia. That leaves two ways of action: Appease them to return to wikipedia, or find a new maintainer for croptool. Just waiting woll not help. C.Suthorn (talk) 15:34, 15 January 2023 (UTC)

sigh :/

there were a few commits https://github.com/danmichaelo/croptool/commits/master .

i know someone might have to take over, but i reposted this thread because this is a major issue which should not be archived until it's resolved. RZuo (talk) 18:25, 15 January 2023 (UTC)

WebP format support

Just realized that WebP format is not supported so requesting its support be added, thanks. Ohsin (talk) 05:33, 27 April 2023 (UTC)

Ditto. SVTCobra 07:51, 26 May 2023 (UTC)

Another one. In the meantime, can someone point me in the right direction of how to crop otherwise, I'm trying to get File:Jude Belligham vs Almería.webp in a better size for a portraint in a infobox. Ortizesp (talk) 07:19, 16 October 2023 (UTC)

Structured Data

Is it possible to also copy structured data while cropping? Currently, if some data is only stored in structured data, it is lost. As an example, please see the coordinates for this picture: File:Bagdad Mine in Yavapai County, Arizona - ISS048-E-17035 - View of Arizona (cropped).jpg Schlurcher (talk) 18:54, 29 May 2023 (UTC)

If this is done, there needs to be some control over it: for example, we don't necessarily want to copy "depicts" for things that are outside of the resulting crop. - Jmabel ! talk 20:52, 29 May 2023 (UTC)

504 Gateway Time-out

CropTool isn't working for me. I get a "504 Gateway Time-out". Is something wrong with the tool, or is it a toolforge issue? Schwede66 00:09, 1 September 2023 (UTC)

Also getting a timeout error! --Engineerchange (talk) 04:08, 1 September 2023 (UTC)

Same problem. Mehedi Abedin 06:55, 1 September 2023 (UTC)

@Schwede66: and @Mehediabedin: works for me now! --Engineerchange (talk) 14:34, 1 September 2023 (UTC)

Excellent! Schwede66 14:38, 1 September 2023 (UTC)

Received error: no-such-entity

I'm trying to crop https://croptool.toolforge.org/?title=Catherine_McCord.jpg - when I select the rectangle I want, and press "Preview" I get "[Error] [api] Received error: no-such-entity : Could not find an entity with the ID "##Q2942000"." --GRuban (talk) 20:26, 13 September 2023 (UTC)

@GRuban: I cropped it to File:Catherine McCord (cropped).jpg with Jpegcrop for you, and replaced what I could. Usages should catch up eventually.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 13:01, 16 October 2023 (UTC)

WikiThanks

--GRuban (talk) 14:06, 16 October 2023 (UTC)

@GRuban: You're welcome.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 17:49, 16 October 2023 (UTC)

cropping fails after rotation of large files

When trying to rotate and crop the file for this, it failed. To work-around it, I cropped it in two steps.

I had the same problem when trying to crop the same region from another large file. Error message displayed was "[Error] undefined". Enhancing999 (talk) 09:56, 16 October 2023 (UTC)

new option: crop from several tiles

Map tile #1165 is part of a series 250 tiles.

Sometimes one would want to crop an area stretching across two adjacent tiles (with the one left, right, above or below).

Ideally, one would specify two files with their alignment and then be able to crop from both at once. Enhancing999 (talk) 10:01, 16 October 2023 (UTC)

• Can't really expect this tool to do everything. Download to your computer and do that in GIMP, Photoshop, etc. - Jmabel ! talk 23:48, 16 October 2023 (UTC)

Feature request re updating of Template:Image extracted

Currently this tool will usefully add or update {{Image extracted}} on existing file pages when a crop is generated. However, this is unnecessary when the new crop overrides an existing one, and which is already listed in the template at the source file page. A useful feature request is to suppress the updating of {{Image extracted}} when the cropped image is already listed there. — RAVENPVFF · talk · 16:57, 8 November 2023 (UTC)

Grid engine will shut down on December 14th, tool will stop working

@Danmichaelo, per https://grid-deprecation.toolforge.org/t/croptool, croptool is still running on Grid Engine. This will be shutting down in less than two weeks unless the developer applies for an extension, in which case it would shut down next February. Unless something is done, this tool will stop functioning at that time. See https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/VIWWQKMSQO2ED3TVUR7KPPWRTOBYBVOA/ Ahecht (TALK
PAGE) 15:53, 2 December 2023 (UTC)

This seems quite important, and I will also post it on the Village pump.- Jmabel ! talk 17:58, 2 December 2023 (UTC)

See also wikitech:News/Toolforge Grid Engine deprecation.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 13:32, 3 December 2023 (UTC)

Issue logged at https://github.com/danmichaelo/croptool/issues/190 - Jmabel ! talk 19:07, 3 December 2023 (UTC)

i saw a commit last year called "Move jobs to kubernetes" https://github.com/danmichaelo/croptool/commit/9a8e9a2849d3df0513b84137c8b863199fad9dc1 . :/ --RZuo (talk) 06:30, 7 December 2023 (UTC)

I’m surprised, and concerned, that this hasn’t attracted more attention so far. Is this good news, though? -- Tuválkin ✉ ✇ 16:07, 9 December 2023 (UTC)

@Tuvalkin: https://phabricator.wikimedia.org/T319653#9387586 certainly is.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 02:50, 10 December 2023 (UTC)

what's happening on 14 dec? is the tool migrated? or is it extended to 14 feb? RZuo (talk) 18:45, 11 December 2023 (UTC)

@RZuo: Extended unless phab:T319653 is completed in time.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 19:15, 11 December 2023 (UTC)

i saw https://github.com/danmichaelo/croptool/pull/182 . i was wondering, since migration is still being worked out, would User:Christoph Jauera (WMDE) and User:TMg maybe want to consider forking and rehosting the tool, in case it's at risk of being discontinued? RZuo (talk) 19:28, 11 December 2023 (UTC)

@Danmichaelo, @RZuo, @Jeff G.,

What is the current status of the Commons crop tool? Has Grid Engine been migrated over to Kubernetes yet? Is this relevant- https://phabricator.wikimedia.org/T313550 ? -- Ooligan (talk) 17:24, 12 January 2024 (UTC)

@Ooligan: From what I can see, Dan has been given more tools, we are waiting for him.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 10:23, 13 January 2024 (UTC)

Crop Tool has not been working for hours today.

Fyi, @Danmichaelo, @RZuo @Jeff G. After clicking, the tool does not load the image to be cropped. Thanks, -- Ooligan (talk) 05:44, 21 January 2024 (UTC)

same for me. https://croptool.toolforge.org keeps loading without any progress. RZuo (talk) 09:25, 21 January 2024 (UTC)

@Ooligan: Right, you had the last upload 00:01, 21 January 2024 (UTC), ten hours ago. That URL times out for me.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 10:02, 21 January 2024 (UTC)

Not working!

For me, visiting the Toolforge site or clicking the tool on the sidebar results in a screen saying "Wikimedia Toolforge Error" BhamBoi (talk) 23:41, 21 January 2024 (UTC)

@BhamBoi: Right, "Wikimedia Toolforge Error

This Grid Engine web service cannot be reached. Please contact a maintainer of this tool."   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 00:55, 22 January 2024 (UTC)

Yes, that's the message I've see, too. --Rosiestep (talk) 13:17, 22 January 2024 (UTC)

Same for me. Any idea when this will be fixed? TurboGUY (talk) 13:39, 22 January 2024 (UTC)

@Rosiestep, @BhamBoi,@TurboGUY,@Jeff G., @Leonprimer. See https://phabricator.wikimedia.org/T314664

This link has a volunteer in April 2023 noting that "Migrate remaining tools off Gridengine" is "in progress" here: https://phabricator.wikimedia.org/T313405 (and still in progress with regards to the popular and unique CropTool), while the "GridEngine" was noted on 22 January by fnegri as Toolforge: Decommission the Grid Engine infrastructure.

Question: I'm not technically astute, but shouldn't the "in progress" tool migration off the GridEngine be completed or "closed" before "decommisioning" that GridEngine?

Additionally, the Category:Extracted images has 651,000+ files. I'm guessing the vast majority related to the currently orphaned and still needed- CropTool. Thank you, Ooligan (talk) 01:54, 23 January 2024 (UTC)

Also, The Wikitech "timeline" states that GridEngine will stop on February 14, 2024, not January 21, 2024 (three weeks premature?) here: https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation Ooligan (talk) 02:10, 23 January 2024 (UTC)

@Ooligan: Yes, of course the "in progress" tool migration off the GridEngine should be completed or "closed" before "decommisioning" that GridEngine.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 02:21, 23 January 2024 (UTC)

From yesterday the tool doesn't work. I opened an issue at https://github.com/danmichaelo/croptool/issues but it seems @Danmichaelo: didn't read it. Does know anybody how to reach him? He's the developer of the tool. Leonprimer (talk) 16:22, 22 January 2024 (UTC)

Please note that Dan has not edited Commons since 15:18, 14 November 2023 (UTC), 2 months, 8 days, 11 hours and 51 minutes ago (69 days).   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 03:09, 23 January 2024 (UTC)

Tool seems to be back up. Sjoerd de Bruin (talk) 08:33, 23 January 2024 (UTC)

Working for me now too. I wonder what the problem was? TurboGUY (talk) 10:35, 23 January 2024 (UTC)

@Sjoerddebruin and TurboGUY: Responding for me, too. The first upload in three days was today at 08:08 (UTC). Thanks for the reports.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 11:07, 23 January 2024 (UTC)

Just want to say thank you, as I use this tool almost every day. --Rosiestep (talk) 18:34, 23 January 2024 (UTC)

February 14

is the latest apparent deadline for final resolution of CropTool's future, per https://phabricator.wikimedia.org/T319653 ----- Quote: "The [[ https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation | planned grid shutdown date ]] is February 14th.

Seems like right now the webservice [[ https://sal.toolforge.org/log/vwRYNY0BxE1_1c7syK2M | just needed a restart ]], at least the interface loads now.''"

• So, what is the plan to get this CropTool migration completed and resolved?
• Can or should Wikimedia Foundation staff help to "save" CropTool? --Ooligan (talk) 15:30, 24 January 2024 (UTC)
  • @Sannita (WMF): any chance someone can look into this before it quite likely becomes a crisis in three weeks? - Jmabel ! talk 20:14, 24 January 2024 (UTC)

    and someone cites "Valentine's Day" as a reason to procrastinate.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 23:06, 24 January 2024 (UTC)

    @Jmabel to be completely honest, it's hardly possible to fix this problem in such a short time. It's extremely difficult that WMF will overtake the development of CropTool, as well as postponing the deprecation of the engine. Sannita (WMF) (talk) 12:28, 25 January 2024 (UTC)

    • @Sannita (WMF): have you (or anyone you know of) heard anything from Dan on this? I'm wondering whether we should presume he is working on this or if it would make more sense to presume that the tool is abandoned. - Jmabel ! talk 18:59, 25 January 2024 (UTC)

      from what i can tell in the phab tasks, migration to k8s is stalled due to missing dependencies? https://phabricator.wikimedia.org/T313550

      but User:Taavi closed that task.

      Dan says, "On Toolforge, I'm trying to get djvu working in CropTool again after having moved to kubernetes, but having a hard time. There's no compilers in the php7.4 image, so I was recommended to try the rub27 image. I was able to compile things there, but not to get the binaries to run in the php7.4 image due to missing shared libraries. It's probably possible to create fully standalone binaries that don't depend on shared libraries, but it's a bit beyond my knowledge (I tried adding a --disable-shared flag). It would be very helpful if compilers could be added to the php7.4 image, what's the process for requesting that?" https://wm-bot.wmcloud.org/logs/%23wikimedia-cloud/20220721.txt

      take note this chat was back in july 2022... RZuo (talk) 20:28, 25 January 2024 (UTC)

      @Jmabel I have no news about it, and nobody I asked to has info on that. :( Sannita (WMF) (talk) 10:51, 26 January 2024 (UTC)

      Drop the smilies and do your job. -- Tuválkin ✉ ✇ 20:29, 28 January 2024 (UTC)

      @Tuválkin: I understand your frustration, but the fact is that WMF did not create this tool and the team Sannita works with have never been formally asked to be responsible for it. Yes, it would be nice to have paid staff with a general responsibility to support tools for Commons. No, that staff does not exist. I don't know your background, but anyone who's worked in the software industry would say that there are few organizations where anyone much below VP level has the authority to take on a sizeable project that was not assigned to them and expend resources on it.

      The person who seems to have dropped the ball here is danmichaelo, who took on this responsibility and seems to have let go of it without informing anyone that he had done so. I believe that as recently as October everyone presumed he was on top of this and would provide a timely solution, and even when we got an extension in early December to buy time, the general presumption that was that we were buying time for him to complete this task. For all I know, he might yet plan to fix this, but if so he is sure not letting anyone know what is going on, and clearly at this point we have to presume he will not do this. I've posted a note at the Village pump hoping to find someone who will at least assess the task, if not take it on.

      In the larger picture: yes, this situation where individual volunteers take on responsibility for a tool, with no management structure, not even mutual management by peers, is insane, and I've said so before. We keep having broken tools and having to scramble to even work out who might solve the problem. As recently as October, the tool that propagates {{Move cat}} requests for the Delinker was broken, and the only reason it got fixed was I ran into someone at WikiConference North America who was able to make the needed fix then and there, but had no interest in taking over responsibility, and warned that the tool will probably break again in a matter of months because of continual changes in the operating environment. And, as far as I know, nothing ever went any further, so it will break again. - Jmabel ! talk 04:01, 29 January 2024 (UTC)

      Thanks, Jmabel. I replied to him below. I understand ths situation, but we either make a huge stink and get this fixed now, or we won’t have an integrated image cropper in two weeks time. I don’t blame Sannita nor Danmichaelo nor anyone individually — I blame those who ever thought that migrating to Kubernetes could/should be done without a guarantee that it would be seamess for the user and everything will still work after the change. Accepting that such migrations always have losses, widespread as it is, is totally unacceptable.

      As for basic functionalities that are in the hands of individual users, well maybe Mediawiki should be working on integrating them in a the basic package? Image cropping and category moving surely are more important for a wiki to offer than some of the stuff they are currently planning to introduce (I bet there at people there drooling at the prospect of adding so called AI to the next major mediawiki version…).

      -- Tuválkin ✉ ✇ 15:54, 29 January 2024 (UTC)

      As far as I remember Danmichaelo was alienated by a decision at the english (?) Wikipedia more than a year ago. Even if something is done to overcome this alienation, it may well be that them has started other activities by now, and I assume it unlikely that them will return and put the effort into croptool, that is needed to keep it running in the long run. So either @Sannita (WMF) makes maintainance a priority of WMF, or a volunteer takes over CropTool or it is a dead tool. C.Suthorn (@Life_is@no-pony.farm - p7.ee/p) (talk) 20:40, 28 January 2024 (UTC)

      • How would one even be able to take over such a tool? Jmabel ! talk 22:32, 28 January 2024 (UTC)

        If the maintainer (all maintainers if there is more than one) of a tool is inactive, a new maintainer can be assigned (provided there is someone who actually wants to become the maintainer). In worst case someone could do a fork of the tool (povided someone wants to do a fork and become its maintainer). C.Suthorn (@Life_is@no-pony.farm - p7.ee/p) (talk) 00:14, 29 January 2024 (UTC)

      "I believe that as recently as October everyone presumed he was on top of this and would provide a timely solution, and even when we got an extension in early December to buy time, the general presumption that was that we were buying time for him to complete this task."

      that's certainly not true. anyone who has tried to understand problems croptool has, or even contribute to the code, would have visited the github repo and found out that Dan has probably proactively stopped working on this for a few years already. i dont know the reason, but i've seen C.Suthorn and also other users talking about an incident/conflict/... that drove Dan away.

      the blame should certainly be on the website development. on one hand, a widely used functionality has to remain maintained solely by volunteers for a decade. on the other hand, wmf cries for money every single year and has stacked up hundreds of millions.

      volunteers are volunteers. they can stop working however they like and dont have any responsibility and dont have obligation to tell anyone.

      not wanting to gossip, but i'm curious (but wont be surprised since i also fell victim) about what alienated Dan. RZuo (talk) 06:57, 29 January 2024 (UTC)

      @RZuo: maybe some people knew Dan had "left the building" but I sure didn't. I don't remember seeing any posts saying "no one seems to be maintaining CropBot, is someone interested in taking it over" prior to my posting that on the Village pump yesterday, when I became aware of the situation. If others knew, it would have been wise to bring it up and seek a solution.

      Are there other important tools that you believe have been abandoned? The only other one I'm aware of is the one that handles "move cat" for the Delinker. - Jmabel ! talk 19:04, 29 January 2024 (UTC)

      @Tuvalkin I understand the frustration over the lack of maintenance of a tool that I used too as a volunteer, but I can't do anything but repeat that there is hardly the chance that WMF can step in, especially with such a short notice. WMF taking over tools maintained by the community -- this tool, as well as any other tool -- would require a major decision from top management, as @Jmabel correctly notes, since we're talking either understanding how a tool not developed by insiders works or re-do it from scratch. Either way it's going to take time, effort, and in the end money I'm in no position whatsoever to commit (for as much as I would like, and I can tell that I would like it very much). This is a periodical discussion within and with the Foundation, and my unfortunate position is the one I'm in: telling people that WMF cannot do anything for the moment, and that I will try to pass it on to the higher-ups that we need to take a decision on it for the next fiscal years (plural intended). I hope this clarifies my position, and that my options are unfortunately limited to the extreme. Sannita (WMF) (talk) 09:49, 29 January 2024 (UTC)

      You job as Community Liason is to keep the editing community feeling happy about the WMF. Are we happy? We’re not. So, either do your job, or quit. (I’d quit, if I were you. I quit cushier jobs for worst bosses. I’m poor now, but at least I’m not coding for scamming crooks nor for major polluters.)

      Don’t give us that company line about not wanting to step on the toes of the user community who’s sovereign in their own tool management. The WMF certainly didn’t feel that way about MediaViewer and VisualEditor and all that nonsense you forced on us.

      Besides, nobody’s asking the WMF to create nor mantain an image cropping tool: We’s asking the WMF to be able to migrate instrastructure without jeoperdizing existent functionalities. It’s not to much to ask, it’s the lowest possible bar, and it’s time the WMF leadership understands that the «break everything» philosophy doesn’t cut for a mature wiki ecosystem. If they rather be disruption brats, they should quit and join Musk somewhere cozy — we’ll easily elect someone better.

      (Also, fix Global Login already? It’s been 10 years. I’m typing this and the preview shows my IP, while in other windows I’m logged in. Can you be less incompetent?)

      -- Tuválkin ✉ ✇ 15:43, 29 January 2024 (UTC)

      @Tuvalkin Thanks for your comment. I will make sure it will be heard, to underline that community is serious about this issue. Sannita (WMF) (talk) 16:47, 29 January 2024 (UTC)

      Thanks for your attention on this problem! I think stating that it is too soon a deadline for WMF to help is true, and I definitely understand the difficult situation you are in. However, I do think the tool is widely used by the userbase (I use it daily or close to it) and should be considered a top priority by WMF. I think it should be brought to leadership as such, and hopefully you can find a new developer to work on the tool, even if it is after the tool expires next month. If necessary, I think putting a bounty on this type of problem in a developer community, like StackOverflow, can be helpful. The technical issues at hand appear fairly complex. --Engineerchange (talk) 15:58, 29 January 2024 (UTC)

      @Engineerchange People involved with the GridEngine deprecation on Toolforge already know about this situation, I made sure of it. I will keep an eye on the situation, and I will help -- in my volunteer capacity -- to try to find someone who can support the tool for the foreseeable future. Sannita (WMF) (talk) 16:44, 29 January 2024 (UTC)

Thanks for your help and for staying cool when the flaming gets hot. --SJ+ 21:13, 29 January 2024 (UTC)

maybe we can solve this step by step.

according to https://wm-bot.wmcloud.org/logs/%23wikimedia-cloud/20220721.txt

"djvulibre, imagemagick and ghostscript" are missing in Kubernetes (k8s).

i think the first step we should take is making imagemagick work. that will make croptool work for images. dont care about the djvu and pdf for now.

or as Dan said, "could probably do without imagemagick if I used built-in php methods, but it requires a small rewrite". someone good at php can rewrite the code to do without magick. RZuo (talk) 07:16, 29 January 2024 (UTC)

May I take it that besides imagemagick, it also lacks graphicsmagick? Because for simple purposes they are more or less interchangeable, and it would be trivial to switch from one to the other. - Jmabel ! talk

Ad hoc alternative

https://jpegclub.org/losslessapps.html

so, which one of these can be recommended as an alternative for users?--RZuo (talk) 07:02, 29 January 2024 (UTC)

i've only used "cPicture [Jürgen Eidt] (Windows 10+) - Windows Photo Explorer, supports JPEG 9" which is ok, except two problems: i dont know how to zoom in while setting the frame to crop; an intermittent popup problem.--RZuo (talk) 07:02, 29 January 2024 (UTC)

You mean this as an alternative way to keep the existing tool and workflow, yes? (And not as a separate standalone piece of software, I mean.) -- Tuválkin ✉ ✇ 15:57, 29 January 2024 (UTC)