-
Notifications
You must be signed in to change notification settings - Fork 630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make InvalidVolumeException easier to debug #2803
Comments
Thanks for the suggestion! Changed for the next release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my case, i have deleted an old volume after migrating the images to an S3 volume.
But, some fields are still linked to the old volume, resulting in a
InvalidVolumeExcepion
being thrown.In my case, this is thrown when trying to save a channel, so there is no way for me the know which field it concerns.
The message states:
This field’s single upload location Volume is missing
.Perhaps, if you'd include the actual field name where the exception in generated, it would be a lot easier to find the culprit, and update the settings, instead of playing hide and seek with all the asset fields.
Exception gets thrown here
https://github.com/craftcms/cms/blob/develop/src/fields/Assets.php#L657-L696
The text was updated successfully, but these errors were encountered: