Skip to content

[6.x] Keep crop copies in the asset selector - #15741

Merged
duncanmcclean merged 1 commit into
6.xfrom
keep-crop-copies-in-asset-selector
Oct 29, 2026
Merged

duncanmcclean merged 1 commit into
6.xfrom
keep-crop-copies-in-asset-selector

Conversation

@duncanmcclean

Copy link
Copy Markdown
Member

This pull request fixes an issue where cropping an asset from the asset selector and choosing "Save as Copy" would take you away from the entry you were editing.

This was happening because the asset browser's editor redirects to the new copy after cropping, which makes sense on the Assets page, but not when the browser is being used as a selector. If the entry had unsaved changes, you'd also get the "You have unsaved changes" dialog.

This PR fixes it by disabling the redirect when the browser is autoselecting uploads (ie. when it's being used as a selector). Instead, the editor closes and the copy gets selected, just like an upload would be.

Cropping from an assets field itself was fixed in #15284.

Fixes #15739

@duncanmcclean
duncanmcclean merged commit b450fb9 into 6.x Oct 29, 2026
65 checks passed
@duncanmcclean
duncanmcclean deleted the keep-crop-copies-in-asset-selector branch October 29, 2026 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cropping an asset from within an entry loses context: unsaved-changes conflict and no return to the entry after “Save as Copy”

1 participant