Skip to main content

Filter by idea status

10000+ Ideas

lutzULevel 3

External Link Checker UI: improve UI and provide downloadInvestigating

Request for Feature Enhancement (RFE) Summary: Enhance External Link Checker page Use-case: As en editor I want know about broken external on my website which I'm responsible for and want to fix the links efficiently. Current/Experienced Behavior: Under /etc/linkchecker.html you get a list which but you can not export it to a csv. Imaging you have a lot of editors working on AEM instance each responsible for different subtrees reflecting different business groups. Now it is hard to figure out the error for specific paths in order to fix this. It is even harder if error occurs not just on a single page but in blueprint page and the connected livecopy pages (imagine 20 livecopies) - here the column get's flooded (just very long comma separated list) and hard to retrieve the information out of that.   Link to documentation: https://experienceleague.adobe.com/docs/experience-manager-65/content/sites/administering/operations/external-link-checker.html?lang=en#external-link-checker Improved/Expected Behavior: Enhance the existing overview with option to export: with the exported list you could filter for paths in the referrer column and assign the list to responsible editors. Maybe a filtering directly in the UI regarding the referrer column would be even better, to see just the paths of /content which I'm responsible for not the ones of whole instance and to export this filtered view. It would be even better if I would informed about broken external links via email providing all the necessary information, meaning path to page and the external link which is not working there. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable):   Code package (if applicable):  

JamesAp1New Participant

Add jcr:created to ntBaseLucene index or change DAM interface to use better indexInvestigating

Request for Feature Enhancement (RFE) Summary: Our system has some DAM folders with more than 1000 PDFs in a single folder.  We are encountering an index error when using the default Assets interface. Use-case: This should occur in an AEM system with no custom code, provided that some DAM folders have huge numbers of assets in them. The user opens Assets and traverses the system using various views. Some folders may fail to open in certain views. Current/Experienced Behavior: This appears in the log: *WARN* [10.240.32.86 [1693910873433] GET /mnt/overlay/granite/ui/content/tree.0.html/content/dam/document-library/corporate-pensions HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed 1000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where ischildnode(a, '/content/dam/document-library/corporate-pensions') order by [jcr:created] desc /* xpath: /jcr:root/content/dam/document-library/corporate-pensions/* order by @6655266:created descending */, path=/content/dam/document-library/corporate-pensions/*); consider creating an index or changing the query   Subsequent investigation showed the most common places this query was coming from is:/mnt/overlay/granite/ui/content/tree.0.html (117 in 4 hours)/assets.html (97 in 4 hours) Improved/Expected Behavior: Currently the system seems to pick the ntBaseLucene query, which doesn't have the jcr:created in the index.  Either that index should be changed, or the system should use the ntFolder index, which does have that. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP17 Customer-name/Organization name: Not disclosed Screenshot (if applicable): N/A Code package (if applicable): N/A