You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In contentlets with multiple binary fields, if you open the info pane in any given binary field, it correctly displays version path, ID path, etc., but the File Link only spits out the first Binary in the contentlet.
Steps to Reproduce
Open contentlet with multiple binary fields with uploaded assets
Click the "i" button to open the info pane
Click the File Link
Result will be the first binary asset, no matter which one you had opened.
Screen.Recording.2024-05-07.at.12.02.43.PM.mov
This problem is caused by the URL path; the file link needs to include the field variable name of the binary field in question, similar to how it appears in the Version and Id paths.
The variable name is so important, we can even omit the file name itself as long as the variable name is included (note the address below).
Acceptance Criteria
File links should change to refer to their respective target images. I think it needs to change from
Parent Issue
No response
Problem Statement
In contentlets with multiple binary fields, if you open the info pane in any given binary field, it correctly displays version path, ID path, etc., but the File Link only spits out the first Binary in the contentlet.
Steps to Reproduce
Screen.Recording.2024-05-07.at.12.02.43.PM.mov
This problem is caused by the URL path; the file link needs to include the field variable name of the binary field in question, similar to how it appears in the Version and Id paths.
The variable name is so important, we can even omit the file name itself as long as the variable name is included (note the address below).
Acceptance Criteria
File links should change to refer to their respective target images. I think it needs to change from
https://{host}/dA/{contentId}/{fileName}?{languageId}
to
https://{host}/dA/{contentId}/{binaryVarName}/{fileName}?{languageId}
dotCMS Version
dotcms-core 1.0.0-SNAPSHOT (April 30, 2024 11:38 AM)
Proposed Objective
User Experience
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: