Virtual Media Attachment Creation for major media types

[subodhr258]

Overview

Currently Virtual Attachment is only created for Videos.

Screenshot:

Task

The Virtual Attachment creation process needs to be done for other main media types as well:

1. Audio
2. Image
3. PDF

This will help associate with an attachment ID within wordpress, and prevent issues like this one:

[subodhr258]

For virtual video we are using the actual created ID after attachment creation, we can do the same for other media types.
Ref: a534ae3
cc: @KMchaudhary

[subodhr258]

https://github.com/rtCamp/godam-core/issues/534#issuecomment-3550726977

This issue will also be solved by creating a new attachment for images.
It can be tested once virtual media attachment creation is complete.

Update:
It turns out that this ticket does not solve that issue and as a workaround we have added this PR to remove GoDAM Tab support from Featured Image

[KMchaudhary]

When we upload an image to WordPress, it automatically generates multiple resized versions. These sizes are later used for optimized rendering on the frontend.

For example, the _wp_attachment_metadata for an image looks like this:

{
  "width": 2560,
  "height": 1707,
  "file": "2025/12/pexels-evelin-magnus-2156241912-34155611-1-scaled.jpg",
  "filesize": 413584,
  "sizes": {
    "medium": {
      "file": "pexels-evelin-magnus-2156241912-34155611-1-300x200.jpg",
      "width": 300,
      "height": 200,
      "mime-type": "image/jpeg",
      "filesize": 11231
    },
    "large": {
      "file": "pexels-evelin-magnus-2156241912-34155611-1-1024x683.jpg",
      "width": 1024,
      "height": 683,
      "mime-type": "image/jpeg",
      "filesize": 76250
    },
    "thumbnail": {
      "file": "pexels-evelin-magnus-2156241912-34155611-1-150x150.jpg",
      "width": 150,
      "height": 150,
      "mime-type": "image/jpeg",
      "filesize": 6899
    },
    "medium_large": {
      "file": "pexels-evelin-magnus-2156241912-34155611-1-768x512.jpg",
      "width": 768,
      "height": 512,
      "mime-type": "image/jpeg",
      "filesize": 45624
    }
  },
  "image_meta": {
    "aperture": "0",
    "credit": "",
    "camera": "",
    "caption": "",
    "created_timestamp": "0",
    "copyright": "",
    "focal_length": "0",
    "iso": "0",
    "shutter_speed": "0",
    "title": "",
    "orientation": "0",
    "keywords": []
  },
  "original_image": "pexels-evelin-magnus-2156241912-34155611-1.jpg"
}

In the case of a virtual image attachment, we only have the original image. We don’t receive the resized versions from GoDAM Central. To resolve this, we have four possible approaches:

1. Generate resized versions using WordPress functions
   WordPress can generate all image sizes locally based on the site’s media settings.
   Con: This isn’t a true virtual image scenario; WordPress becomes the source for resized files instead of the CDN. As this is a temporary solution, we need to invest time to fix the issue once a solid solution is available from GoDAM Central.

2. Define media settings in GoDAM Central and generate the resized versions there
   These generated files can be used to populate the _wp_attachment_metadata field.
   Con: The generated sizes won’t match each WordPress site’s media settings.

3. Provide a URL-based image resizing API
   Con: This is expensive to run on Bunne Net (@geekofshire).

4. Hybrid approach: WordPress sends a size-generation request to GoDAM Central
   When a virtual image attachment is created, WordPress sends the required image sizes. GoDAM Central generates missing versions on demand.
   Pro: Works across multiple WordPress sites, each with different media size configurations, without needing a URL-based resizing API.

cc: @joelabreo227 @kishan-gondaliya-7270 @elifvish @geekofshire @subodhr258

Need to discuss before going forward with implementation.

[KMchaudhary]

• https://github.com/rtCamp/godam-core/issues/597 needs to be completed from the Frappe end as part of this issue.