Skip to content
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

CP Exception when editing an image / asset #7129

Closed
flolanger opened this issue Nov 27, 2022 · 2 comments · Fixed by #7131
Closed

CP Exception when editing an image / asset #7129

flolanger opened this issue Nov 27, 2022 · 2 comments · Fixed by #7131
Labels

Comments

@flolanger
Copy link
Contributor

flolanger commented Nov 27, 2022

Bug description

When editing an image / asset inside a collection entry and save it, the following exception occurs in the CP:
Bildschirmfoto 2022-11-27 um 23 18 51

How to reproduce

On any collection with an asset field type:

  1. Open entry with asset field type
  2. Edit existing asset and click "Save".
  3. -> Asset-Preview is missing now
  4. Save the entry
  5. -> CP Exception occurs (see screenshot above)

Logs

No response

Environment

Environment
Application Name: Laravel
Laravel Version: 9.41.0
PHP Version: 8.1.12
Composer Version: 2.4.4
Environment: local
Debug Mode: ENABLED
URL: localhost
Maintenance Mode: OFF

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: statamic
Database: mysql
Logs: stack / single
Mail: smtp
Queue: sync
Session: file

Statamic
Addons: 1
Antlers: runtime
Version: 3.3.58 PRO

Statamic Addons
pecotamic/sitemap: 1.4.0

Installation

Existing Laravel app

Antlers Parser

runtime (new)

Additional details

No response

@flolanger flolanger changed the title CP Exception when editing an image CP Exception when editing an image / asset Nov 27, 2022
@robdekort
Copy link
Contributor

Confirmed. Happens with any asset field in the blueprint,. Root, replicator or bard.

@arthurperton
Copy link
Contributor

This was introduced by #7072.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants