Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

ashu4pma
ashu4pma
Offline

Badges

Badges
13

Accepted Solutions

Accepted Solutions
15

Likes Received

Likes Received
17

Posts

Posts
38

Discussions

Discussions
7

Questions

Questions
31

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by ashu4pma
Customize the badges you want to showcase on your profile
Re: Assets Search: - Adobe Experience Manager 15-05-2018
Please elaborate which predicate you have added. "Fulltext Predicate" may not work as it becomes obsolete after OmniSearch introduced in 6.2 and removed in subsequent release.If you have used "Property Predicate" then it should work. If it is not working even after using "Property Predicate" then share following details:1. Values provided to this predicate (property name, placeholder etc.)2. The search GET request parameters (open browser's debugger and trigger search)

Views

2.5K

Like

1

Replies

0
Re: Error Message when changed optional field to mandatory for metadata schema. - Adobe Experience Manager 11-05-2018
Yes it may not work as I can see card's path is hardcoded to /libs at [1]. The "/libs/" should be removed from [1] to allow overlaying. You can log a product's enhancement request to get it done. Thanks[1]/libs/granite/omnisearch/content/metadata/asset

Views

2.7K

Like

1

Replies

0
Re: Error Message when changed optional field to mandatory for metadata schema. - Adobe Experience Manager 10-05-2018
Fine it will be Line #52 if AEM 6.2 + latest CFP./libs/dam/gui/coral/components/admin/contentrenderer/card/assetomnisearch/assetomnisearch.jsp#L52

Views

2.7K

Likes

0

Replies

0
Re: Error Message when changed optional field to mandatory for metadata schema. - Adobe Experience Manager 10-05-2018
The cards rendered on Search Page has different code and including CardBanner using absolute URL. Please check the component at [2] Line no. 54You should overlay this as well, and refer to /card-banner.jsp overlaid in /apps. Considering you are asking this for AEM 6.3, since this has been fixed in 6.4.[2]/libs/dam/gui/coral/components/admin/contentrenderer/card/assetomnisearch/assetomnisearch.jsp#L54

Views

2.7K

Like

1

Replies

0
Re: Crop renditions - Adobe Experience Manager Assets 08-05-2018
Can you confirm if the Dynamic Media is enabled? if not use [0] to enable it.In Assets (when Dynamic Media is disabled), the image edit operations (cop, rotation etc.) results into destructive binary edit. Where as in case of Dynamic Media enabled, the image edit operations are performed using modifiers and doesn't modify the binary. Refer[1] for more details on DM.[0] Configuring Dynamic Media with Feature Packs 14410 and 18912 [1] Adding Dynamic Media Assets to Pages

Views

2.8K

Likes

0

Replies

0
Re: Asset direct link is downloading not open asset on new tab - Adobe Experience Manager Assets 07-05-2018
Yes uncheck the checkbox(Enable Content Disposition for all paths).

Views

20.7K

Like

1

Replies

0
Re: Asset direct link is downloading not open asset on new tab - Adobe Experience Manager Assets 03-05-2018
This was a security fix at Sling level, the disposition filter has been added to force this behavior. See [0].To undo this behavior (not recommended), you can disable the component[1].Thanks[0] SLING-4883Extend content disposition filter protection to jcr:data[1] org.apache.sling.security.impl.ContentDispositionFilter[2] http://10.42.36.65:4502/system/console/components/org.apache.sling.security.impl.ContentDispositionFilter

Views

20.7K

Likes

5

Replies

3
Re: Error Message when changed optional field to mandatory for metadata schema. - Adobe Experience Manager 30-04-2018
Hi,Not sure which AEM version you are talking about here, my reply assumes it is for 6.4 (though most of it will be applicable even for previous versions too).-> expectation was it gives an error if any those mandatory fields are is not authored for new assets . For this definition of "new assets" needs to be shape out first, to keep it simple, I am considering assets which are ingested in last 24 hours are new assets.-> Is there a way to not to display such error for the already existing assets...

Views

2.7K

Like

1

Replies

0
Re: Remove Insights tab in DAM Asset Meta Data - Adobe Experience Manager 23-04-2018
Then I would consider this as a product bug and overlay extension should work.The form under /libs goes to /conf when extended at the project level (Administrator role). All customizations needed at a project level for OOTB forms /libs go to /apps. (Solution Integrator role)Say at the project level, it is decided to hide Insight Tab so that any user admin can't see when metadata schema is being defined under /conf for the project. Then OOTB form offered from location /libs should be extensible t...

Views

2.4K

Like

1

Replies

0
Re: Remove Insights tab in DAM Asset Meta Data - Adobe Experience Manager 19-04-2018
The Insights form exist at location [0]. Try overlay the form using [1] and hide. If it doesn't work then log a hotfix request to get fix from Product.Thanks[0] /libs/dam/content/schemaeditors/forms/insights[1]Apache Sling :: Resource Merger (org.apache.sling.resourcemerger)

Views

2.3K

Like

1

Replies

0