fix: editing buttons missing in admin when file present

[pajowu]

Description

This PR adds the image-preview-container to the admin file preview. This is needed so that the sass-rules from _image-info.scss gets applied. This fixes the issue described in #1499

Related resources

• #...
• #...

Checklist

• I have opened this pull request against master
• I have added or modified the tests when changing logic
• I have followed the conventional commits guidelines to add meaningful information into the changelog
• I have read the contribution guidelines and I have joined #workgroup-pr-review on
  Slack to find a “pr review buddy” who is going to review my pull request.

I did not do the last item, as the slack-channel no longer exists :)

Summary by Sourcery

Bug Fixes:

• Fix the missing editing buttons in the admin interface when a file is present by adding the 'image-preview-container' class.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR fixes a UI issue in the admin interface by adding the 'image-preview-container' class to the file preview element, which enables the proper application of existing SASS styling rules for editing buttons.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Added 'image-preview-container' class to the file preview element in the admin interface	Added 'image-preview-container' class to the filer-dropzone div when an object is attached Ensures proper application of existing SASS styling rules from _image-info.scss	filer/templates/admin/filer/widgets/admin_file.html

Possibly linked issues

• Editing buttons are cut off in filer field #1499: PR fixes styling issue in admin related to issue's misalignment problem.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @pajowu - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[fsbraun]

@pajowu Thanks for the PR! I suggested a slightly different approach (see above), since I think the issue was introduced by #1490.

Would you like to bump the version in filer/__init__.py and add a comment to the changelog, too? I'd love to release the fix quickly!

[pajowu]

@fsbraun yes, that fixed it as well. I updated the commit accordingly. Thanks :)

[fsbraun]

Thanks! 🙏