Have you tried to manually delete your bundle in the OSGI console and deploy your bundle via Maven again? This will tell you if there is an issue with the deployment or the bundle.

What version of AEM are you using? I believe that we started supporting server-side sorting for OOTB properties starting in AEM 6.3. However, I don't believe have support for custom properties yet.

Are you using the admin account to edit the permission? Or are you using a different user? If you are using a different user, which group does the user belong to?

Personally, I have not seen any issue.Based on your description, there should be some log messages that will help you to narrow down the source of the problem. I would suggest posting some error messages that you are seeing so we can help on the forum. If the issue is more involved with too many pro...

As previously mentioned, the feature that you are looking for it not available. However, we are always looking to improve the product. If you have some suggestions on how to improve the tagging UI, please open a support ticket with us. Our product management will review them for future releases.

Have you considering using the parameter "p.limit" as described here [1].[1] Query Builder API

I do not think that HTL has such functionality to distinguish internal/external links. You will need to write something custom to handle case a use case. Take a look at this [1] to help you in creating this customization.[1] https://wcm.io/handler/link/usage.html

When you set up your Dispatcher flush agent, use the property "Agent User Id" and specify a user that will be reading the content and flushing it. You will need to create this new user and configure the user to only have read permission on the path(s) that you want this user to flush (e.g. /content/...

Try recompiling all your JSP pages [1] to see if that would help.[1] http://<host>:<port>/system/console/slingjsp

Several things to check.1. When you upload the document initially, check to see if the metadata has the property @dam:sha1 with a value.2. If item 1 is fine, then upload the document again. This time enable query debugging to see if the query below gets executed.//element(*, dam:Asset)[(jcr:content/...