- Issue created by @eyad alanati
- last update
10 months ago Patch Failed to Apply - last update
10 months ago Patch Failed to Apply - Status changed to Needs work
10 months ago 12:46pm 29 February 2024 The Needs Review Queue Bot → tested this issue.
While you are making the above changes, we recommend that you convert this patch to a merge request → . Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)
- Status changed to Needs review
10 months ago 12:49pm 29 February 2024 - Status changed to Postponed: needs info
10 months ago 1:07pm 29 February 2024 - last update
10 months ago Custom Commands Failed Update Core to 10.1.8
go to image styles
edit any of the existing image styles
website will encounter error- last update
9 months ago Custom Commands Failed - 🇹🇷Turkey loker
I've experienced the same problem with a number of 10.3.2 installation. I just haven't need to edit styles before so I could only follow the discussion yet.
- 🇳🇿New Zealand quietone
@eyad alanati, thanks for providing the steps to reproduce. Can you add them to the issue summary to help others who work on this issue?
I tested this on Drupal 10.1.8 using the steps in #9 and did not receive any errors. Leaving the 'steps to reproduce' tag because there seems to be something more that needs to be done to reproduce the error.
- Issue was unassigned.
- 🇳🇿New Zealand quietone
Also changing to Unassigned so that others may look at this.
Original image height or width is zero.
What is the
image.settings:preview_image
config set to on those sites?- 🇮🇳India anmolgoyal74
I am also getting the same error on Drupal 10.2.4. But this error only comes when switching to the ImageMagick toolkit, not with GD.
image.settings:preview_image: core/modules/image/sample.png
- 🇳🇿New Zealand quietone
Drupal 10.1.x is no longer supported. Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to our policies.
Can someone add steps to reproduce in the Issue Summary. I have tried the ones from #9 and did not get the problem.