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

Offloaded attachment download resolves to a missing local file

Aperta
  • Qualcosa non va?
#1,119 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
php, wordpress
Ambito
backend

Direzione di ricerca

Inizia con Optml_Media_Offload::generate_image_meta(), add_new_actions() e alter_attached_file_response() in inc/media_offload.php. Esegui composer phpunit -- tests/test-media.php, quindi riproduci l’azione di download di WordPress o dell’estensione utilizzando un allegato appena sottoposto a offload. Il lavoro è completato quando il flusso di download è coperto e non segnala più la mancanza di un file locale, mentre i test esistenti di offload e rollback rimangono validi.

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

Descrizione

bug-report bug-report-triage customer report

Summary

Downloading a newly offloaded WordPress attachment can return a file-not-found error. Expected behavior is for an offloaded attachment to remain downloadable. Actual behavior is that the attachment's local source has been removed while the download-facing file lookup resolves to a nonexistent local path, preventing administrators from retrieving the media.

Customer context

Product / area: Optimole WordPress plugin, Image Storage attachment downloads
Version: Customer version not provided; inspected source is 4.2.11
Environment: WordPress admin; browser and WordPress/PHP versions not provided
Integration / third party: Optimole cloud storage
Reported error / symptom: Downloading the newly uploaded attachment returns “file not found” while Optimole is active
Impact: Administrators cannot download affected offloaded attachments through workflows that consume the WordPress attached-file path

Reproduction notes

Reported reproduction:

  1. Keep Optimole active with Image Storage/offloading in use.
  2. Upload an image through WordPress.
  3. Attempt to download the uploaded attachment.
  4. Observe a “file not found” error.

Runtime reproduction was not performed, but the existing unit test and inspected source confirm that the filtered attached-file path does not exist after offload.

Diagnosis

Conclusion

The offload path removes the local source and rewrites attachment metadata to a remote marker. The globally registered get_attached_file filter then combines that remote metadata with the local uploads directory, producing a path for which the source confirms no local file exists. This directly matches the reported file-not-found download behavior. No matching GitHub issue was found.

Where this likely occurs
  • inc/media_offload.php — Optml_Media_Offload::generate_image_meta() lines 1478–1521 validates an Optimole URL, deletes the local source, and stores a remote id: path in attachment metadata.
  • inc/media_offload.php — Optml_Media_Offload::add_new_actions() lines 2654–2701 registers alter_attached_file_response() globally on get_attached_file for the new-offload path.
  • inc/media_offload.php — Optml_Media_Offload::alter_attached_file_response() lines 2715–2728 prefixes the local uploads directory to the remote metadata value.
  • tests/test-media.php — Test_Media::test_image_processed() lines 297–316 explicitly confirms that get_attached_file() resolves to a path that does not exist after processing.
  • Commit 31022521 introduced alter_attached_file_response() in the offloading-without-database-replacement work. Available history does not identify a release where this download path worked before breaking.
Engineering notes

The local deletion is intentional for Image Storage, but get_attached_file is a filesystem-path contract used by WordPress and extensions for attachment operations. The inspected filter is global despite its nearby comment discussing an Elementor file-existence check. The exact download controller used on the customer site is unknown, but any inspected workflow relying on this filtered local path encounters the absent file represented in the existing test.

Test coverage status

tests/test-media.php — Test_Media::test_image_processed() lines 297–316 and Test_Media::test_image_sync() lines 326–346 cover remote URL generation and explicitly assert local-file absence. Test_Media::test_image_rollback() lines 348–358 covers restoration. No relevant coverage was found during inspection for downloading an offloaded attachment or for a consumer requiring a readable result from get_attached_file().

What to verify or explore next
  • May be worth reproducing through the exact WordPress or extension download action that reports “file not found.”
  • May be worth running composer phpunit -- tests/test-media.php with a focused download consumer around a newly offloaded attachment.
  • Compatibility checks may be useful for core media actions and common attachment-download integrations that consume get_attached_file.
Unknowns / follow-up
  • The exact download UI or extension invoking the file lookup is not provided.
  • The customer's plugin version and attachment metadata are unavailable.

Confidence

Confidence: 95/100

Repository inspection independently confirms a stale offload-limit warning path and a missing local download target after offload. The blank-rendering symptom is credible but remains unconfirmed without the affected remote response or offloading logs.

Source: HelpScout #3431088020
Generated by bug-report-triage (ID: bug-report-triage_6a8f62001e0958.60696283)

Lingua principale
PHP
Stelle
73
Fork
14
Merge medio
2g 12h
PR unite (30g)
18

Preparare l'ambiente

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 Codeinwp/optimole-wp

Tutte le issue di Codeinwp/optimole-wp

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.