New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If Generic List contains more than 8 items it produces a stack trace and does not render. #2503
Comments
@aberberich is this on the new touch UI generic lists? |
hey there, I'm running through the same issue and in my case, it has - somehow - something to do with url rewriter enabled. when I disable the rewriter, the page shows up with more than 7 items (in my case, something near 150). |
Is there any update for this issue? |
We are facing this issue in AEM version |
Hi, did anyone figure out this use case? we are facing similar issue in Upgraded environment, cannot reproduce in local instances. |
Were you ever able to locate a solution? We are seeing the exact same issue. When disabling the link rewriter it goes away for us as well. |
We are also facing same issue. Please help.. @davidjgonzalez |
Issue: acs commons generic lists with more than 8 items gives 500. Hi, I am able to reproduce the issue with latest acs-commons 5.3.2 on latest AEM 6.5.13 having /apps/project/config/rewriter. As suggested, first tried removing rewriter node in /apps/project/config/rewriter helped. Fix: update node property order="-1" from its current value order="10" in /apps/project/config/rewriter/ as per the latest /libs/cq/config/rewriter/default order="-1" Note: 4.3.2 is a working version of acs-commons which supports classic and does not has this generic-lists issue. Hope it helps! Thanks |
Required Information
Expected Behavior
When I open an ACS Commons Generic List with more than 8 items it should render properly.
Actual Behavior
When I open an ACS Commons generic list with more than 8 items I am given the following stack trace,
listStacktrace.txt
Steps to Reproduce
Links
This issue has previously been reported on the ticket below, however it was marked as stale and never fixed. We have attempted the fixes detailed in that ticket and they were not successful.
#2325
The text was updated successfully, but these errors were encountered: