Browser: Chrome 110
OS: Windows
Version 2.4.1 fixed the Media Offload display issue, but the fix only addressed media that uses a Public URL.
Some Media Offload plugins deliver media to the frontend through a Media Stream/Proxy instead of exposing a direct Public URL. Media handled this way can still have display issues in Bricks.
I’ve already got a prompt for you guys to check:
Fix the Media Offload compatibility issue where media delivered through a Media Stream does not display correctly in Bricks.
Version 2.4.1 already fixed media that uses a direct Public URL. Do not change that existing behavior.
Focus only on Media Stream-based delivery.
Please:
-
Trace how Bricks currently resolves and renders media URLs.
-
Identify why streamed/proxied media responses fail to display.
-
Fix Bricks so media delivered through a stream endpoint can render correctly.
-
Do not require the media URL to be a direct physical file URL.
-
Preserve stream endpoints, query parameters, authentication parameters, and dynamically generated URLs exactly as provided.
-
Do not convert the stream URL back into a local WordPress upload path.
-
Do not rely on file extensions in the URL to determine whether the media is valid.
-
Keep the existing Public URL fix from version 2.4.1 unchanged.
-
Make the smallest possible change necessary to support Media Stream rendering.
Before changing code, locate the exact part of the media rendering pipeline that rejects, rewrites, or fails to handle the stream URL, then fix that specific behavior.