Ah - so it sounds like your query is specifically about the Link Share card listing (which has a completely different implementation than the "normal" Assets Files view listing) .. it might be worth to update your Post title to reflect that. The Link Share view, by default, lists assets in their "na...

Have you thought about creating a 3rd organizational User Group in AEM that has Group1 and Group 2 as its members and assigning the approval that anyone in *that* group? I'm not clear as to why you are creating a Group 1 and Group 2 distinction in the context of this workflow, based on what you said...

Technically the query that is run to collect the results in the card view of an assets folder is: /jcr:root/content/dam/example/* order by @jcr:created descending This means assets are sorted by the dam:Asset's jcr:created property in descending order. Is it possible you are MOVING assets from one f...

To resolve the No OSGi SCR metadata found error, you need to follow the instructions here: Apache Felix - Apache Felix Bundle Plugin Frequently Asked Questions

Hi!First a quick correction; Asset Share Commons [1] is not a Feature Pack but rather an open source project; just want to make sure thats clear.1) Creating an additional filter component with type-ahead; you're best best is to look at the Search Bar component implementation [2] [3] [4]. In alot of ...

Content Fragments created from Content Fragment Models should already be channel agnostic (they are "raw" data).If you want only data points X and Y exposes on Channel A and some other data points Y and Z (of the same Content Fragment) exposes on Channel B; then you'd select them when you defined ho...

Check out .. https://docs.adobe.com/docs/en/dispatcher/disp-config.html#Automatically Invalidating Cached Files  -- This should solve your problem. With your deny all, you're effectively doing resource-only flushing for everything.

What's the stat level and and invalidate config I your dispatcher.any?

sanjays16398239​ It would be helpful if you could provide your log for the invoked flush agent and the dispatcher log (on debug) that shows how dispatcher is processing the flush and finally, the dispatcher log for when you request a page that you now expect to be invalidated.

Double-check your POMs (Parent AND bundle/core) to make sure you are using the proper uberjar and NOT directly specifying the dependency version for:<dependency><groupId>org.apache.sling</groupId><artifactId>org.apache.sling.api</artifactId><version>x.x.x</version><scope>provided</scope></dependency...