Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

While replacing an asset with new file meta data get lost

Aperta
  • Qualcosa non va?
#12,047 0 commenti 2 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
laravel, php
Ambito
backend

Direzione di ricerca

Start by tracing the asset replacement dialog through the save action and the code that writes asset metadata in the .meta folder; the issue does not name source files or tests. Reproduce the steps with an image that has custom metadata, replace it with a differently named image, and save with removal of the old image enabled. Done means the replacement retains the existing metadata in its new .meta YAML file.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

assets
Bug description

My users are facing the following problem:
If you replace an image, by uploading a new one with a different name, the metadata gets lost.

The editorsdesk would love to use the replacement feature from time to time, because after publishing an article they often find the need to modify/crop/change/whatever an image afterwards again. But as we use several custom metadata fields in the assets blueprint, (a11y, legal, copyright, stuff...) its quite annoying to upload the modified image a second time, to than fill out all theses fields and to then search/find the image in library to change it the article.

Using an image file with the same name is also not an option as mentioned here: #11229

How to reproduce
  • Upload an image to the library
  • Add some metadata to the image
  • Save the image
  • Look into the .meta folder -> old.jpg.yaml existing
  • Replace the image by uploading a new one using the replace-dialogue (do not click save yet)
  • Look into the .meta folder -> old.jpg.yaml and new.jpg.yaml existing
  • Save the image by clicking the Save button. (toggle remove old image is on )
  • Look into the .meta folder -> new.jpg.yaml existing
  • Look into the .meta/new.jpg.yaml file -> metadata are lost
Logs
Environment
Environment
Application Name: DAV
Laravel Version: 11.45.1
PHP Version: 8.3.23
Composer Version: 2.8.10
Environment: local
Debug Mode: ENABLED
URL: dav-av.ddev.site
Maintenance Mode: OFF
Timezone: Europe/Berlin
Locale: de

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

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

Statamic
Addons: 6
Sites: 3 (DAV, JDAV, JUBI)
Stache Watcher: Enabled
Static Caching: Disabled
Version: 5.63.0 PRO

Statamic Addons
alpenverein/nginx-utility: dev-dev
el-schneider/statamic-auto-alt-text: 0.3.2
jacksleight/statamic-bard-mutator: 3.0.4
jonassiewertsen/statamic-external-link: 1.9.0
mitydigital/sitemapamic: 3.3.0
thehome/statamic-elasticsearch: dev-es8
Installation

Fresh statamic/statamic site via CLI

Additional details

No response

Lingua principale
PHP
Stelle
4.9k
Fork
647
Merge medio
1g 9h
PR unite (30g)
102

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di statamic/cms

Tutte le issue di statamic/cms

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.