EM Assets picker: assets listed under the "Approved" filter are refused on insert when dam:activationTarget ≠ delivery (Author + DM mode)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start with blocks/shared/aem-assets/filter-schema.js and blocks/edit/da-assets/helpers/config.js to understand the locked Approved filter, then compare it with the insert check in blocks/edit/da-assets/da-assets.js. Reproduce the Author + Dynamic Media flow with dam:activationTarget set to no or contenthub. Done means the picker and insert check accept the same assets, including one whose delivery metadata request returns 200.
Written by the indexing model from the issue text.
Description
Summary
In Author + Dynamic Media mode, the picker lists every approved asset, but the insert check then refuses some of them with "not approved for delivery". The listing and the insert apply different rules.
Setup
aem.repositoryId = author-…
aem.asset.dm.delivery = on
Current behaviour
The listing uses a locked filter, "Asset Status: Approved". It covers dam:assetStatus only (filter-schema.js#L20-L37, switched by aem.asset.dm.approvedonly in config.js#L102-L106).
On select, the insert check refuses any asset whose dam:activationTarget is set to something other than delivery (da-assets.js#L127-L135).
This includes dam:activationTarget = no. That value isn't in the documented delivery/contenthub set, but DM delivers those assets (HTTP 200).
Expected
The listing and the insert check apply the same rule, and that rule matches what DM delivers.
Repro
Configure a site in Author + Dynamic Media mode.
In AEM, approve an asset and set dam:activationTarget to no (or contenthub).
Open the picker. The asset is listed.
Select it. The error panel opens.
GET https://delivery--.adobeaemcloud.com/adobe/assets//metadata returns 200 for the no asset.
Proposed fix
Add dam:activationTarget to the locked listing filter, the same way as dam:assetStatus.
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 74
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 52
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from adobe/da-live
-
ew
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
ew
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug ew
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
good first issue help wanted
Difficulty 1/5 Under an hour Newbie friendliness 88/100
modrollstudio/Modroll-Studio-Website#80 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
area: panel enhancement
Difficulty 1/5 Under an hour Newbie friendliness 72/100
GabrielGirardi/ledge#7 ·
-
0. Needs triage 35-feedback bug
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
oxc-project/oxc#28783 ·
Maintainers usually reply within 1 day