Media Renaming with Reliable Crops and Focal Points
Upload renaming now works in place with focal point edits that persist, automatic cache refreshes, animated GIFs that keep moving, and an instant Usage tab showing asset usage.
Once a file was in your media library, its name was fixed, so a hurried upload like "IMG_4821.jpg" stayed that way wherever it appeared. You can now rename existing uploads in place from the media and files edit screens, so your library stays legible and your team can find the right asset by name. Renaming keeps the existing file type, so links to the asset keep working without a re-upload.
Renaming that keeps everything connected
When you rename an upload, Basker copies the asset to its new name, updates the record, and tidies away the old copy in the background. The file extension is preserved, so the content type and existing references stay intact and nothing downstream breaks. The rename is confirmed as soon as the record is updated, even while the cleanup finishes behind it.
Focal points and crops that hold
Adjusting only the focal point is now treated as a metadata change rather than a re-upload, so setting which part of an image survives a crop no longer reverts to centre after a refresh. When you do crop, Basker re-fetches the true original at full resolution in its original format instead of a transcoded copy, so each crop starts from the source rather than compounding earlier compression. Re-cropped images refresh in browser and edge caches straight away, so editors and patrons see the new version rather than a stale render. A stale uniqueness rule that surfaced as "the following field is invalid: filename" on some assets has also been cleared, so those saves go through.
Animated GIFs, extensionless images, and an instant Usage tab
Animated GIFs now keep moving when resized, so a looping clip stays a loop rather than collapsing to a single frame. Images stored without a file extension are recognised by their content type and resize correctly instead of being served at full size. The Usage tab, which shows where an asset is used, now reads from a maintained index rather than scanning your whole library on each request, so it opens promptly even on large libraries instead of timing out.