Issue with ACS commonss renovator | Community
Skip to main content
Level 2
May 20, 2024

Issue with ACS commonss renovator

  • May 20, 2024
  • 1 reply
  • 993 views

Hi,

 

I am using ACS commons renovator to pull the report of images which has no reference in pages. As our content is very huge, when a single image is referred in multiple pages in multiple locales, "Referred In" column in report each cell it is exceeding 32767 characters and it is throwing below error.

 

 

 

<h1>Error during requesting: '/var/acs-commons/mcp/instances/683A99AD07F315B2/_jcr_content/report.xlsx'<h3>Error Message:</h3>
<pre>java.lang.IllegalArgumentException: The maximum length of cell contents (text) is 32767 characters</pre><h3>Processing Info:</h3>
<table style='font-family: monospace'>

 

so, I want to customize renovator like it should only give true or false if the image has reference or not, instead of listing all the pages in which it is referred in "Referred In" column.

 

Can someone help here.

 

Thanks,

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

EstebanBustamante
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 20, 2024

Hi, 

 

This is a known issue in acs-commons: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2146. this is apparently solved, so please try a newer version of acs that include the fix mentioned in the thread.

 

Hope this helps

Esteban Bustamante
Nimma05Author
Level 2
May 20, 2024

Hi @estebanbustamante ,

 

I am using ACS commons version 6.6.0 still I am facing this issue. In my scenario single image is referred in multiple pages so exceeding the limit.

 

The link you have shared is for images and tags, they have provided the fix in TagReporter.java  https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/2154/commits/bcfdee9b2305bf7d6a5f97cf5248f047108eeea8

 

So, I am thinking that might be reason it is still not working in latest version.

 Am I correct? @estebanbustamante 

 

Thanks,