#105742Synchronized manipulation of all crop variants
Description
Currently it is not possible to manipulate all crop variants of an image at the same time in the TYPO3 backend.
So if you added an image and want to crop it a bit on all crop variants but the smallest one, you have to do it manually for all crop variants. If you have 6+ crop variants (bootstrap template), this is really annoying and error prone, because you can not set the exact some values for each variant.
It would be nice to have a switch to enable synchronized manipulation of the crop variants.
Reviews 1
Related issues 1
Files 5
History 1532
Show 37 earlier messages
-
Christian Welzel commented <span data-processor="relativetime" data-value="2024-12-02T14:47:35+00:00" > 12/02/24, 14:47 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 87336 status
NewUnder Review <span data-processor="relativetime" data-value="2024-12-03T11:00:25+00:00" > 12/03/24, 11:00 </span> -
Garvin Hicking commented <span data-processor="relativetime" data-value="2024-12-04T18:39:23+00:00" > 12/04/24, 18:39 </span>
Not sure if you saw my comment in the patch tracker, but I also just now saw this: https://docs.typo3.org/p/jweiland/sync-crop-areas/main/en-us/Index.html
Maybe it’s an idea to join forces here and see if the extension route is viable? Maybe even my ideas I raised in the patch comment could be incorporated :)
-
Christian Welzel commented <span data-processor="relativetime" data-value="2024-12-11T17:31:50+00:00" > 12/11/24, 17:31 </span>
I had a look into the description of this extension, but had no closer look (RL is happening…)
As i understood the text and the code (had a short look into it), it uses the DataHandler to copy configurations on save action. This is not, what i want to archive because this is not intuitive to the editor.
-
Gerrit Code Review pushed patch set 2 for main to change 87336 <span data-processor="relativetime" data-value="2025-02-28T12:46:20+00:00" > 02/28/25, 12:46 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 87336 <span data-processor="relativetime" data-value="2025-02-28T13:10:15+00:00" > 02/28/25, 13:10 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 87336 <span data-processor="relativetime" data-value="2025-02-28T13:21:07+00:00" > 02/28/25, 13:21 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 87336 <span data-processor="relativetime" data-value="2025-03-03T10:51:06+00:00" > 03/03/25, 10:51 </span>
-
Christian Welzel commented <span data-processor="relativetime" data-value="2025-04-03T12:02:57+00:00" > 04/03/25, 12:02 </span>
I added a new config option for crop variants to remove them from the list of synchronizable CV.
Now the patch fullfills my needs regarding user experience without being to complex in usage. -
Garvin Hicking changed Tags ux-decision <span data-processor="relativetime" data-value="2025-04-03T21:16:41+00:00" > 04/03/25, 21:16 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 87336 <span data-processor="relativetime" data-value="2025-05-09T12:48:16+00:00" > 05/09/25, 12:48 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 87336 <span data-processor="relativetime" data-value="2025-05-12T13:33:26+00:00" > 05/12/25, 13:33 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 87336 <span data-processor="relativetime" data-value="2025-08-14T11:45:53+00:00" > 08/14/25, 11:45 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 87336 <span data-processor="relativetime" data-value="2025-08-14T12:00:14+00:00" > 08/14/25, 12:00 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 87336 <span data-processor="relativetime" data-value="2025-09-02T16:09:39+00:00" > 09/02/25, 16:09 </span>
-
Gerrit Code Review pushed patch set 11 for main to change 87336 <span data-processor="relativetime" data-value="2025-09-02T16:40:31+00:00" > 09/02/25, 16:40 </span>
-
Gerrit Code Review pushed patch set 12 for main to change 87336 <span data-processor="relativetime" data-value="2025-09-10T10:37:58+00:00" > 09/10/25, 10:37 </span>
-
Rachel Foucard changed Tags
ux-decisionux-approved <span data-processor="relativetime" data-value="2025-09-19T06:39:35+00:00" > 09/19/25, 06:39 </span> -
Garvin Hicking changed attached Screenshot 2025-09-19 at 14.52.41.png attached Screenshot 2025-09-19 at 14.52.53.png <span data-processor="relativetime" data-value="2025-09-19T12:55:32+00:00" > 09/19/25, 12:55 </span>
-
Rachel Foucard commented and changed attached clipboard-202509191544-wxtwf.png attached clipboard-202509191544-2jxvw.png <span data-processor="relativetime" data-value="2025-09-19T13:44:41+00:00" > 09/19/25, 13:44 </span>
Hi,
Thanks a lot for this very good UX improvement proposal! With a few UX refinements, this will feel much smoother for users.
- Synchronize crop variants” is indeed what is happening, we can reduce the technical jargon to make it clearer for non-experts.
- let’s make the flow more flexible so users can change their mind easily or fix their mistakes easily too.
Adding the check box at the top of the list, and then, at the begining of the actions flow means that the user knows in advance that they will apply the crop variants to all the devices. It is not often the case, and we have to think of common use cases like:
- They forgot to check the box and started to define the crop variants for one device
- They reopen an existing setting and just want to apply it for all devices
I suggest to put the option inside each device as a simple button and change the label with “Apply to all”. Please find attached the following screenshots describing the proposed behaviour.
!clipboard-202509191544-wxtwf.png!
clipboard-202509191544-2jxvw.png -
Christian Welzel commented <span data-processor="relativetime" data-value="2025-09-19T14:34:14+00:00" > 09/19/25, 14:34 </span>
I like the idea of these buttons, but there is a problem with the feature to exclude certain cropvariants from being synchronized. With this solution the user does not see in advance, which cv are excluded and will most likely not understand, why this “apply to all” does not work.
The wording of the checkbox can be changed, if someone has a better idea. I didn’t come up with a better one. But perhaps an “apply changes to all crop variants” would be better.
If this option is enabled, the cv, that are excluded, get grayed out. This way the user knows about the exclusion.
-
Riccardo De Contardi commented <span data-processor="relativetime" data-value="2025-09-19T15:10:48+00:00" > 09/19/25, 15:10 </span>
Just some wild thoughts – be careful, not a full solution!
- when you click the button “apply to all” the “unfit” crop variants are grayed out (maybe also with a small icon animation flashing like ⚠️?)
- plus an alert toast on the right bottom like “Could not update/crop some images because…” (better wording required ;)) -
Rachel Foucard commented and changed attached clipboard-202509220937-ws8ae.png <span data-processor="relativetime" data-value="2025-09-22T07:37:57+00:00" > 09/22/25, 07:37 </span>
Hi,
I understand, indeed, if some proportions are not shared by all cases, the user must be warned early enough to avoid frustration. On this point, none of the proposals above are right, because the user will only realize the possibilities after clicking. It’s too late.In this case, it would be much better to list what is possible and what is not possible before clicking, like this:
!clipboard-202509220937-ws8ae.png!
Also, with this list, we can directly apply a setting to specific cases, but not all of them, which can save editors time because it is more flexible. -
Christian Welzel commented <span data-processor="relativetime" data-value="2025-11-26T11:12:08+00:00" > 11/26/25, 11:12 </span>
This is an interesting approach, but a completly different patch and would involve a complete startover.
And i do not like the fact, that the user has to click several times to copy a CV to others, if “all” and a single one do not match his use case.
My patch is meant do simplify the workflow, if all images should be the same (we have that relatively often in our projects).
If the usecase is to make all images but one the same, its also simple: edit all, uncheck the box, edit the one.
Even copying the current CV to all others afterwards is easy: check the box, make a tiny adjustment, undo the adjustment, done.I think this patch should be integrated as it is, and if someone comes up with another usecase and/or better solution, he is welcome to add this/redo the interface. Currently no such functionality is in the core and 14.0.0 is already released. Currently this simple patch for a not so rare usecase is getting heavily overengineered in an effort to satisfy everyones needs.
-
Gerrit Code Review pushed patch set 13 for main to change 87336 <span data-processor="relativetime" data-value="2025-11-26T14:21:02+00:00" > 11/26/25, 14:21 </span>
-
Gerrit Code Review pushed patch set 14 for main to change 87336 <span data-processor="relativetime" data-value="2025-11-27T13:06:09+00:00" > 11/27/25, 13:06 </span>
-
Gerrit Code Review pushed patch set 15 for main to change 87336 <span data-processor="relativetime" data-value="2025-12-01T17:22:16+00:00" > 12/01/25, 17:22 </span>
-
Gerrit Code Review pushed patch set 16 for main to change 87336 <span data-processor="relativetime" data-value="2026-01-22T22:22:20+00:00" > 01/22/26, 22:22 </span>
-
Gerrit Code Review pushed patch set 17 for main to change 87336 <span data-processor="relativetime" data-value="2026-02-13T20:34:29+00:00" > 02/13/26, 20:34 </span>
-
Christian Welzel commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-02-16T10:15:08+00:00" > 02/16/26, 10:15 </span>Applied in changeset commit:9e947323f7595aed6039f8ed8f649683c1a52db5.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-03-31T09:00:40+00:00" > 03/31/26, 09:00 </span> -
Benni Mack changed Related to #89610 <span data-processor="relativetime" data-value="2026-11-09T11:59:06+00:00" > 11/09/26, 11:59 </span>
I already have some code for this. Will prepare a PR soon.