Feature/328 Add option to activate ImageResize plugin #362
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Hi,
There have been many discussions and multiple issues raised regarding this topic. A lot of users, including our company, would like to use the ImageResize plugin. While we already utilize image transformations, we have a specific use case where content managers need to make precise, pixel-perfect adjustments to images—such as slightly resizing them. This is not practical to achieve with transformations alone.
Until there is an integrated solution that provides handles for easy image resizing within the Craft ImageTransform plugin, I propose this temporary solution that includes the original ImageResize plugin.
By default, ImageResize is disabled. However, I have introduced a new configuration parameter, enableImageResize: true, which allows developers (who are aware of potential issues with ImageResize) to enable it if needed.
I couldn’t find any specific contribution guidelines, but I’ve done my best to follow best practices. If there are any issues with this PR, I’m happy to address them right away. If this proposal is declined, you can still check out my fork and include it as a private plugin instead of the original one. (Please note that my fork will not receive frequent updates if new features are added to the official craftcms/ckeditor plugin.)
Looking forward to your feedback!
Related issues
#328 #101 #273 #94 #94