Curator no longer loads images from S3 on overview after upgrading to v4

[Kovah]

I have upgraded to v4 recently and now noticed that the media overview of Curator is broken, as it tries to load all media files from the local disk. This cannot work, as all files are stored in S3. Interestingly, Curator correctly shows the media file when on the view/edit pages for a single media file.

According to the Upgrade notes the cloud_disk config key was removed and is now automatically detected. Is it possible that this could be broken for the dashboard?

Sample URL from the dashboard: https://my-site.com/curator/2025/ec2de0ce-...-8f077df960f0.jpg?fit=crop&fm=webp&h=640&w=640&s=0ad4d2012...d052960 which leads to a 500 error. In the logs, this appears: Could not find the image 'public/2025/ec2de0ce-...-8f077df960f0.jpg'.

I have the default_disk configuration set to the disk which is connected to my S3 bucket. All media files are stored in the database with said disk.

[awcodes]

Those pages are using Glide to try to optimize the asset delivery. Probably not ideal with s3. Unfortunately, I don't have an s3 bucket setup that I can test with.

Easiest solution at the moment would probably be to override the Media Model to change the accessors for those views. You might have sizing issues with this approach though.

public function thumbnailUrl(): Attribute
{
    return Attribute::make(
        get: fn (): string => Storage::disk('s3')->url($this->path),
    );
}

public function mediumUrl(): Attribute
{
    return Attribute::make(
        get: fn (): string => Storage::disk('s3')->url($this->path),
    );
}

public function largeUrl(): Attribute
{
    return Attribute::make(
        get: fn (): string => Storage::disk('s3')->url($this->path),
    );
}

If you want to submit an issue with a reproduction repo I can look into possibly doing a proper fix.